Public Data Resource

Synthetic Temperature Data for Predicting Flashover Occurrence Using Surrogate Temperature Data

Contact: Wai Cheong Tam..
Identifier: doi:10.18434/mds2-2479
Version: 1.0 First Released: 2022-10-26 Revised: 2022-10-26
This data set provides heat detector temperatures in a single-story ranch structure with a living room, kitchen, dining room, and three bedrooms. 20000 sets of detector temperatures are generated using CData [1]. The data set are obtained based on simulation runs with various fire conditions and door opening conditions. The fire is described based on t-squared law. The peak heat release rate and time to peak range from approximately 1667 kW to 4620 kW and from 210 s to 1540 s, respectively. A detailed description of this work can be found in Ref. [2].

[1] Reneke, P.A., Peacock, R.D., Gilbert, S.W. and Cleary, T.G., 2021. CFAST Consolidated Fire and Smoke Transport (Version 7) Volume 5: CFAST Fire Data Generator (CData). NIST Technical Note 1889v5. Gaithersburg, MD.

[2] Fu, E.Y., Tam, W.C., Wang, J., Peacock, R., Reneke, P., Ngai, G., Leong, H.V. and Cleary, T., 2021, May. Predicting Flashover Occurrence using Surrogate Temperature Data. In Proceedings of the AAAI Conference on Artificial Intelligence (Vol. 35, No. 17, pp. 14785-14794).
Research Areas
NIST R&D: Fire: Fire detectionFire: Fire fightingFire: Fire risk reduction
Keywords: Flashover Prediction; Recurrent Neural Network; Validation with Experimental Data; Smart Fire Fighting
These data are public.
Files

Loading file list...

Version: 1.0 First Released: 2022-10-26 Revised: 2022-10-26
Cite this dataset
Wai Cheong Tam (2021), Synthetic Temperature Data for Predicting Flashover Occurrence Using Surrogate Temperature Data , National Institute of Standards and Technology, https://doi.org/10.18434/mds2-2479 (Accessed 2024-10-12)
Repository Metadata
Machine-readable descriptions of this dataset are available in the following formats:
NERDm
Access Metrics
Metrics data is not available for all datasets, including this one. This may be because the data is served via servers external to this repository.