Validation test input files were down loaded from http://code.google.com/p/cfast/source/browse/#svn/trunk/cfast/tags/Version%206.1.1/. While running “FMSNL 5.in” and “NBS MV100O.in”, CFAST generated text output rather than numeric values for the listed circumstances.

What steps will reproduce the problem?
1. Download listed files from code.google.com/
2. Run files using CFAST version 6.1.1
3. Observe listed parameters for listed time steps

What is the expected output? What do you see instead?
Expected outputs for the affected parameters were numeric values of zero 
or near zero values.
For FMSNL 5.f.csv, the affected parameters were “MV Inflow to 1” and “MV 
Outflow from Out”. The affected time steps were 541-900 for both 
parameters.  
For NBS MV100O.s.csv, the affected parameters were “Entry to Fire Ro- 
Lower CO2” and “Entry to Fire Ro Lower CO”.  The impacted time steps were 
387 - 809 and 394 - 807 respectively.
Observed outputs were text resembling scientific notation that omitted 
the "E". It was noted that the text output, if read as a numeric value, 
would have been extremely small, on the order of 1E-100/1E-152.

What version of the product are you using? On what operating system?
The version of CFAST used was 6.1.1.
CFAST was run on a MS XP Professional operating system with an Intel Core 
2 duo processor

Please provide any additional information below.
Although operationally, the observed output may be treated as zero, these 
observation occurred during a validation effort and require a fix or 
explanation for resolution.

Original issue reported on code.google.com by kil...@bechtel.com on 30 Dec 2009 at 6:05

atwhaley / cfast

Validation test input files were down loaded from http://code.google.com/p/cfast/source/browse/#svn/trunk/cfast/tags/Version%206.1.1/. While running “FMSNL 5.in” and “NBS MV100O.in”, CFAST generated text output rather than numeric values for the listed circumstances. #48