Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Surface Wall Flux Validation #2230

sprankleray started this conversation in General
Discussion options

Hello,
I’m hoping you can tell me what I’m missing here. I’m trying to run some of the validation cases found on github for V7.7.5; currently looking at wall surface flux. Figure 10.1 indicates that the NIST/NRC Long wall and Short wall test CFAST runs are relatively accurate when compared to the test data. In fact, the Long Wall Heat Flux curve for NIST/NRC Test 8 shown on page 262 of the V&V Guide and reproduced in the attached file shows maximum flux values of about 3 kW/m2 and 4 kW/m2 for Targets 1 and 2 respectively.

However, when I run NIST_NRC_T8.in and plot incident flux curves for Target 1 and Target 2 from the devices.csv output file, I get different (lower) values; see attached.

The shape of the curves is about the same but the maximum flux values are lower at about 2 kW/m2 for Target 1 and slightly over 3 kW/m2 for Target 2. It seems the most likely reason I’m getting different results is that I’m not looking at the correct data. I want to look at wall surface flux and only the curves above from page 262 of the V&V Guide connect Target 1 and Target 2 flux to wall flux. There’s nothing in the input file itself other than that these targets are indeed located on the surface of the long wall. And there’s nothing I can find in the output files; that is, I can’t find a *.csv output file that has a column labeled "Wall Surface Flux."

I note that the descriptive text provided in Section 10.1 (page 127) of the V&V Guide, for the NIST/NRC tests indicates that the actual measured flux values are net flux rather than gauge flux. But that would seem to show a need to alter the empirical test data in the curves presented above and on page 262, and I assume that has been done. It would not alter a comparison of the results I obtained using v 7.7.5 and those presented on page 262, also using v 7.7.5. Any light you can shed on this would be appreciated.

Thanks,
Ray

Wall Flux comparison of V&V Guide pg 262 to new case-1.pdf

You must be logged in to vote

Replies: 4 comments 8 replies

Comment options

My first thought is that this might be an issue with "net", or "total", or "incident" heat flux. Depending on the device, sometimes we measure a "gauge" heat flux. As I recall, some of the devices used in these experiments measured the heat flux to the hot wall, as opposed to a cold water-cooled heat flux gauge. Take a look at all output columns with heat flux and see if any match with what is in the guide.

You must be logged in to vote
0 replies
Comment options

Kevin, Thanks for the quick response. I noted the aspect you mention here as it appears in Section 10.1 (pg 127) of the V&V Guide. However, wouldn't that only affect the model output v the empirical test results? I'm looking at running v7.7.5 for NIST/NRC_T8.in and getting the same results that are presented, in chart form, for the same input file and the same version of CFAST, v7.7.5. Unless you altered the *.csv files, my output of v7.7.5 should be identical to yours, as long as I'm reading the right columns. I couldn't find any other columns or any other *.csv that gave flux results to match those curves in the V&V Guide, even when in validation output mode. Thanks Ray From: Kevin McGrattan ***@***.***> Sent: Thursday, February 5, 2026 4:45 PM To: firemodels/cfast ***@***.***> Cc: sprankleray ***@***.***>; Author ***@***.***> Subject: Re: [firemodels/cfast] Surface Wall Flux Validation (Discussion #2230) My first thought is that this might be an issue with "net", or "total", or "incident" heat flux. Depending on the device, sometimes we measure a "gauge" heat flux. As I recall, some of the devices used in these experiments measured the heat flux to the hot wall, as opposed to a cold water-cooled heat flux gauge. Take a look at all output columns with heat flux and see if any match with what is in the guide. - Reply to this email directly, view it on GitHub<#2230 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFZGHI5RN5URQOFI7EG6YA34KO2WPAVCNFSM6AAAAACUEWIPUCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNZRGIYDENY>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
You must be logged in to vote
0 replies
Comment options

I plotted all the heat flux outputs for Target 1 for the most recent version of this case in the GitHub repository. There appears to be one curve that peaks at 3 kW/m2, but I'm too old to distinguish all these pastel colors. I'll take a closer look tomorrow, or take another look at your output file and the one in the git repo.

image
You must be logged in to vote
3 replies
Comment options

Did you find the heat flux column that matches the plot in the CFAST Validation Guide?

Comment options

Kevin,
I did find it thank you for sending that. So, I was looking at the wrong data. The curve that peaks at about 3 kW/m2 is from the column Target Total Gauge Flux for Target 1 and is only available in the output validation mode. It appears to line exactly up with the Long Wall Heat Flux data curve on page 262 of the V&V Guide.

I was looking at the Target Incident Flux which is defined in the CFAST User’s Guide (pg. 56) as the "total heat flux striking the front surface of the current target." The User’s Guide defines the Target Total Gauge Flux as the "total net heat flux to the front surface of the current target assuming the target radiative losses are at ambient temperature (validation output only)." My first inclination would be to assume that incident flux (total flux in) would always bound total gauge flux (total flux in less radiant flux out). But that’s obviously incorrect.

Regardless of why it’s incorrect, it leads me to ask how we should be using the validation output data. Until now, I considered it inappropriate to use that data for fire modeling purposes. However, it’s clearly being used in the V&V Guide to make a comparison against empirical test data. If I’m trying to model postulated real world fire scenarios, this data indicates I should be using the validation output results in my analysis. For this particular case, if I didn’t use the validation output data, I would be under-reporting flux to the wall.

Can you provide some additional information on the validation output data and whether or not it can/should be used for analysis purposes as appropriate output data for realistic fire modeling?

Thanks
Ray

Comment options

rpeacoc Feb 9, 2026
Collaborator

I should note that all the validation results were run with the -v option in cfast which sets the net heat flux calculations to be consistent with the room temperature water-cooled heat flux gauges used in the experiments

Comment options

There is a flag called `validation_flag` in the CFAST source code and it appears that it mainly outputs various quantities in units that are more typically used in validation exercises. As for heat flux, it might convert the net heat flux to a gauge heat flux, which is what is typically done for validation. If I recall correctly, we converted both the experimental measurements and modeled values of net heat flux to a gauge heat flux to make comparisons easier model to model. Net heat flux depends on the predicted wall temperature, whereas for gauge the surface temp is assumed ambient.
...
Message ID: <firemodels/cfast/repo-discussions/2230/comments/15745139@ github.com>
You must be logged in to vote
5 replies
Comment options

Let me try to re-state in different words.
In the validation mode, heat flux to a target is calculated, based on a wall surface temperature assumed to be ambient. This results in an increased flux value because heat flux is dependent on the temperature difference. When not in the validation mode, heat flux to a target uses a calculated wall surface temperature (higher than ambient), so the heat flux value is lower, and more physically accurate.

So, that means I should NOT use validation mode when analyzing postulated real-world fire scenarios. Is that correct?

Comment options

If you want to know the flux of energy absorbed at the solid surface, you do not want the "cold gauge" result. However, I am not sure if CFAST adds extra output quantities in "validation" mode, or if it redefines existing quantities.

Comment options

Yes, but whether CFAST adds extra output quantities in "validation" mode, redefines existing quantities, or modifies empirical data for comparison, it makes no difference. The point is that the validation mode results are (or at least might be) modified and therefore less accurate at modeling actual flux values than the output quantities provided in the non-validation mode.

Flux levels delivered to a target are often an important parameter in determining whether a postulated fire might cause excessive damage as in say for example, exceeding a damage threshold of 6 kW/m^2 for thermoplastic electrical cables (NRC Inspection Manual, Chapter 0609, Appendix F Attachment 6, "Guidance for the Identification of Targets and their Ignition and Damage Criteria," [https://www.nrc.gov/docs/ML1808/ML18087A410.pdf]). It's very important for users to understand what CFAST output parameters should or should not be used in performing thermal analysis.

It sounds as if you're agreeing that CFAST users should NOT employ spreadsheet output results identified in Table C.1 of the CFAST User's Guide as "validation output only" without at least addressing the modifications that may have been made to those outputs. Is that right?

Comment options

By default, CFAST outputs the "net" and "incident" heat flux. For regulatory purposes, you probably want to use the incident because that would be consistent with a simple "point source" model in which the temperature of the target is not taken into account and assumed to be ambient.

image
Comment options

Yes, but whether CFAST adds extra output quantities in "validation" mode, redefines existing quantities, or modifies empirical data for comparison, it makes no difference. The point is that the validation mode results are (or at least might be) modified and therefore less accurate at modeling actual flux values than the output quantities provided in the non-validation mode.

Flux levels delivered to a target are often an important parameter in determining whether a postulated fire might cause excessive damage as in say for example, exceeding a damage threshold of 6 kW/m^2 for thermoplastic electrical cables (NRC Inspection Manual, Chapter 0609, Appendix F Attachment 6, "Guidance for the Identification of Targets and their Ignition and Damage Criteria," [https://www.nrc.gov/docs/ML1808/ML18087A410.pdf]). It's very important for users to understand what CFAST output parameters should or should not be used in performing thermal analysis.

It sounds as if you're agreeing that CFAST users should NOT employ spreadsheet output results identified in Table C.1 of the CFAST User's Guide as "validation output only" without at least addressing the modifications that may have been made to those outputs. Is that right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet

AltStyle によって変換されたページ (->オリジナル) /