firemodels / cfast Goto Github PK

What steps will reproduce the problem?
1. Attached test case has a target in a room without a fire locate on a 
wall surface. 

What is the expected output? What do you see instead?
Observed target temperature goes down below ambient temeprature before 
recovering.  It should never be possible for a target temperature to be 
below the ambient temperature

When data file path is longer than 128 characters, CFAST fails with an 
error 102.

What steps will reproduce the problem?
1. Run standard file with two fires.  
2. Look at *.n.csv output file to observe data shift.

What is the expected output? What do you see instead?

Data file is comma delimited with a header for each data column.  Headers 
for normal output file shifted two places near the right part of the 
file.  Right-most two columns do not have standard text headers.

What version of the product are you using? On what operating system?
CFAST 6.1.0.912   Windows Professional SP2

Please provide any additional information below.

When commas are included in the title for a CFAST simulation, only the 
part of the title up to the first comma shows up in the printed output 
file.

Likely problem is in routine that reads comma-separated input file.

What steps will reproduce the problem?
1. Add mechanical vent with 0 % filter efficiency
2. Save file
3.

What is the expected output? What do you see instead?
EVENT F lines should only be included if filter efficiency <> 0

Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Test case attached.  Two fans, one in and one out of single room
2. At about t=818 s in the simulation, time step goes to 10^-9
3. Use f5 to see time step in command prompt execution of cfast

While varying the “lower oxygen limit” we find version 6.0.10
unable to accept anything but 0% or 10% regardless of what we try. Is
that intentional? 

[deleted issue]

Compiler directives in input.f are no longer necessary but prevent easy 
compilation on other platforms.

What steps will reproduce the problem?
1. Change the heat of combustion for an object file to a value less then 
1.31E07 J/kg.
2. CFAST will indicate an error: Fire object XXX has a heat of combustion 
less than 1.31E07 J/kg or grater then 5E08 J/kg.

What is the expected output? What do you see instead?

Several common items have published effective heat of combustion values of 
less than 1.31E-07 J/kg and should not prompt an error message (e.g., 
wood, tissue paper, etc. per SFPE Handbook, pp 3-143).  The error 
threshold should be set lower than 1.3E07 J/kg.

What version of the product are you using? On what operating system?
6.1.1.54

Please provide any additional information below.

Sample input file attached.

There is a bug in the code that interpolates the opening 
fraction between the beginning and end of the decay period.  Since the 
GUI automatically sets the decay parameter to 1 s, it did not have any 
significant impact on the output for nearly all model users.  

When the interval is longer (which can only be accomplished by hand-editing the 
input file), you would see a small initial drop that stayed constant 
until the end of the decay period when the vent would "jump" to its 
final position. 

The headers in the CFAST csv files seem difficult to use.  To estimate the net 
flow between 
rooms four columns of data were needed in CFAST 5.1 (i.e., upper-in, upper-out, 
lower-in, and 
lower-out). Based on the current headers I am having trouble establishing which 
column 
presents which data.

From CFAST version 6

Inflow from  2  to 1
Outflow to  2  from 1
Mixing to Upper 1  ( 2 )
Mixing to Lower 1  ( 2 )
Inflow from  2  to 1
Outflow to  2  from 1
Mixing to Upper 1  ( 2 )
Mixing to Lower 1  ( 2 )

From CFAST version 5 

Upper Inflow  1-  2(  1)
Upper Outflow  1-  2(  1)
Lower Inflow  1-  2(  1)
Lower Outflow  1-  2(  1)
Mixing to Upper  1-  2(  1)
Mixing to Lower  1-  2(  1)

These should be reviewed and updated to make them as simple and clear as 
possible.

[deleted issue]

What steps will reproduce the problem?
1. Installing CFAST
2.
3.

What is the expected output? What do you see instead?

On trying to run a report I get an error:

"GLUT: smokeview.exe Application Error" 

"The instruction at "0x7c901010" referenced memory at "0x00000034". 
"The memory could not be read."

What version of the product are you using? On what operating system?

6.0.10

Please provide any additional information below.

Running XP SP3 (error is attached)

Any assistance welcomed regards,

N.

Remove button on the Fire Objects page does not remove a fire object.

The external ambient temperature is set at 113 deg.F and when the 
radiation fraction is set to 0.2, the program stalls. The program will not 
run if the temeprature is set to greater than 107 deg.F.
Under the same conditons of 113 deg.F ambient, but with radiation 
fractions of 0.3 and 0.4, the program runs successfully. Why would the 
program not accept the 113 deg.F ambient at radiation of 0.2?

Also the ceiling jet always seems to default itself to "Ceilings & 
Walls"(=WALLS...is it really solving for ceilings AND walls??) when you re-
open the file even though you didn't save it like that. Moreover, it 
doesn't seem as if when you run under the same conditions, but change the 
CJET function, that it makes any difference in the temperature output. 
Maybe this is something simple, but the Technical and especially Users 
guide need to better address errors if the program "doesn't like" some 
inputs.

What version of the product are you using? On what operating system?
6

Please provide any additional information below.
.in file attached

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

I noticed that the CJET gives various alternatives to the calculation 
input in the GUI which are Off, Ceiling, Ceiling & Walls, ALL. If you look 
at the .in script file produced from the GUI, the CJET command 
specifies "CJET,WALL" when in the GUI "Ceiling & Walls" is selected for 
ceiling jet. The user manual does not recommend using only the wall 
command. Could you clarify what exactly the calculation input is telling 
it to do?

What version of the product are you using? On what operating system?
6.0.10

Please provide any additional information below.

Technical Manual 6.

 There is a graph in the technical manual on page 45 that has 3 lines and 
3 different symbols. The key shows 2 symbols. One is repeated. Which one 
goes where? Graph attached.

Dear CFast Team,
I compiled the actual source code for cfast (not the GUI, just CFast) on 
Ubuntu 8.04 and it works. Here are three suggestions, which I think make 
it easier for other interested persons to do the same...

Maybe you can change this few "issues" at the source directory, I think 
they should have no influence for a windows system

1. Rename SIZES.fi to sizes.fi, because Linux is case sensitive. The file 
is included as sizes.fi in the SOURCE Code, so Linux doesn't find 
SIZES.fi. I renamed it by hand, then it works.

2. In file "output.f" there is a call "USE DFLIB" (subroutine 
deleteoutputfiles (outputfile), line 3014). I think, this call is not 
required, because there are only "standard calls" in this function. If you 
do not have a Visual Fortran compiler (or the dflib library), there is an 
error (I got one). I compiled succesfully without the "USE DFLIB" call, so 
I think it is not necessary for a succesful run and can be deleted in the 
code.

3. Compiler Directives in "input.f": Are these directives for actual PC's 
required? The Intel Compiler gave me some warnings, maybe they can 
removed???

Attached to this post you will find a makefile which based on the FDS5 
makefile. With this makefile I compiled the code with an Intel Fortran 
compiler on Ubuntu 8.04. Maybe you can put it into the source directory.

Best Regards from Germany
Christian Rogsch

Dear Sir/Madam,

I have a question about the output results from CFAST, in the help topic, it 
says the unit of 
temperature is in Kelvin.  Is this correct?  Because I have a fire give me an 
upper layer temperature 
of 225 (unit), and the flux in ambient target is 1.95kW/m2.  If the temperature 
is in Kelvin, then I 
wouldn't expect to have such a high heat flux on the ambient target.  I also 
noted that in the upper 
layer temperature of the RunModel window, the unit used is in Celsius.
Would you please clarify this. 

When length units are changed from meters, default locations for targets and 
detectors do not 
calculate correctly.  Default fire location is correctly calculated.

Problem is lack of units conversion when calculating the actual location from 
the room dimensions.

A saved file with a target, where the target solution method is set 
to "steady", opens with the Method indicating "Implicit."  It would seem 
that it should open with the method set to "Steady".  The input file line 
in the saved file is:  TARGET,1,1,3,1,0,-1,0,GLASS,STEADY,PDE

At the moment, CFAST does not include a calculation of the plume temperature.  
This can impact 
targets directly above the fire such that the temperature of the target will be 
underestimated. 
Methods are available for this calculation in Heskestad's chapter of the SFPE 
handbook.

At this point, a routine exist to calculate the plume centerline temperature 
(see PlumeTemp in fire.f, 
but it is not connected to any CFAST calculation.  There are two places for 
this connection:  targets 
and detectors.  When the target or detector is located at the x&y position of a 
fire, the local gas 
temperature (that's currently set to the layer temperature for targets and the 
ceiling jet temperature 
for detectors (regardless of the height of the detector)) could be calculated 
by the plume 
temperature correlation

If an input file contains a target location (X, Y, and/or Z) of -1 (the 
default value that should equate to the center of the room), CFAST fails 
at initialization.  Normally, the GUI takes care of this so most users 
will never see this problem (you have to manually edit a target to include 
the -1).

What steps will reproduce the problem?
1. I build two compartments over each other. Connect them with a vertical
vent and build a fire in the lower room.
2. booth compartments have horizontal vents
3.

What is the expected output? What do you see instead?

I expected that the flow comes inside the lower room and flow out at the
upper room.

I saw insteed, the flow goes out both openings.

What version of the product are you using? On what operating system?

CFAST 6.1.0.32 Windows XP

Please provide any additional information below.

Code is missing for detectors.  Copy code from hvents or others to fix.

What steps will reproduce the problem?
1. I build a compartment with one vertical vent. 
2. Then I dublicated the vents to get more cross area.
3.

What is the expected output? What do you see instead?

I expected with the dublicated vents I will get different result, but with
one or multiple vents the result is the same.
It seems the programm doesnt sum up the vents.

What version of the product are you using? On what operating system?

CFAST 6.1.0.32 Windows XP

Please provide any additional information below.

Attached file was run from the CEdit GUI.  Output files were then reviewed 
in Excel.

CEdit provides the switch to establish a one-zone compartment on the 
Compartment Geometry page under Flow Characteristics.  The applicable word 
in the pull down menu is SHAFT.  This results in a keyword line starting 
with ONEZ in the *.in file, which is as expected.

The output files for the compartment (Compartment 2 in the attached files) 
presents both an upper layer and lower layer output in the *.n.csv and 
*.s.csv.  For the normal file the upper layer and lower layer temperatures 
in Compartment 2 are numerically equal, but in the species file the upper 
and lower layer values for O2, C02, H2O, and TS are not numerically equal. 

It would seem that only one layer column for a one-zone compartment should 
be published in the output files.  If two are to be published they should 
be numerically equal.

Version 6.1.0.24

What steps will reproduce the problem?
1. Run sample problem.
2. Look at column O, rows 45-48 of *.f.csv.  The first value is 0.484672-
155 rather than 0.484672E-155.  If the E is included as with all values 
above 0.1E-99 then it could be read as a number by most spreadsheet 
programs.

What version of the product are you using? On what operating system?
CFAST 6.1.1.54.



Please provide any additional information below.

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.

User's need a way to check the authenticity of CFAST distribution and installed 
data files.  Adding a 
checksum for the files and instructions for calculating checksums for files 
would fill this need.

Rick,

Have received the error below a couple of times while making changes to 
the filter efficiency value to something on the order of 99.97%.  Along 
with this, the * does not always seem to come on in the CEdit title bar 
when a change is made to the Filter Efficiency input, and even if a * is 
present saving the file does not present the correct value when reopened. 

For now I am working around this in two ways:  Doing a “Save As” to 
capture the revision or manually changing the *.in file using WordPad.

Will continue preparing the sample problem.  Please let me know if this is 
something that is occurring on this end.

Thank you,

What steps will reproduce the problem?
1. Situation : At #1 fire compartment, I want to install two supply grills 
from outside on east and west wall respectively. At the same time, I want 
to install two return grills to outside on south and north wall 
respectively.
   Question : is it possible to designate the grill locations at forced 
ventilation?
2. Situation : I want to install twe supply grill at the same center 
height by forced ventilation. 
   Question? Then, can CFAST distinguish the difference of two grills due 
to the same input conditions?  

What version of the product are you using? On what operating system?
- CFAST 5.1.1.54 and Window XP

What steps will reproduce the problem?
1. Mechanical vent into a room with not other vents
2. No fire needed
3. Use default values for fan cutoff pressure

What is the expected output? What do you see instead?
Flow through mechanical vent should go to zero at specified (default) 
upper pressure limit.  Instead, it does not stop.

I have also noticed a problem with the CFAST species excel. I might be 
wrong on this one but as you may already know, after CFAST runs a 
simulation it creates 4 excel spreadsheets which give various readings on 
the simulation at any given or specified time. I have noticed that in 
the “species” or “xxxx.s” spreadsheet the column titles seem not to 
line 
up with the sets of numbers below them. A good example in my case would be 
that the Upper Layer OD of the compartment which had a fire (in my 
scenario) never went beyond 0.00, which makes no sense because that is the 
compartment where I imagine would have the highest OD in the upper layer. 
Besides the O2 column, all the other column titles and number sets seem to 
be misaligned.

What steps will reproduce the problem?

1. I build three rooms and connected them with holes over the full wallsize.
Then I placed a fire in the middle compartment
2.
3.

What is the expected output? What do you see instead?

I expected to have the same layer high with same temperature in each room.

I got a higher temperature with a smaller layer high in the middle compartment.




What version of the product are you using? On what operating system?

CFAST 6.1.0.32, Windows XP 

Please provide any additional information below.

The CFAST Technical Manual (SP1026, page 9) recommends that the ratio of 
vent area connecting two compartments and the smaller compartment volume 
should not exceed 2 m^-1.  This value seems high.  A double door 
arrangement on a 3 meter x 3 meter room has an area to volume ratio of 
about 0.2.  Is 0.2 the correct value to present in SP1026?

The response to issue 19 was:  “Our intention was to insure that the vent 
does not get too large in relation to the room size.  A ratio of the room 
volume to vent area (not the other way around) of about 2 m is now used in 
the documentation.”

The current text (SP 1026, April 2009) is:  “In a single compartment, the 
ratio of the area of vents connecting one compartment to another to the 
volume of the compartment should not exceed roughly 2 m.”

The units in the current SP 1026 do not seem consistent.  Is a revision to 
the text planned?

[deleted issue]

Incorrect mechanical ventilation inputs (and others) in the input file do 
not lead to the model stopping prior to simulation start. Error is at line 
70 of cfast.f.  errorcide should be spelled errorcode. Corrected line 
allows model to correctly stop.  Fixed in revision 43.

Output in the *.n.csv spreadsheet output includes HRR (and other 
variables) for each user-specified fire, but does not include any vent 
fires calculated by the model resulting from under-ventilated burning of 
one or more of the user specified fires.

There seems to be a discrepancy between the total trace species generated and 
the sum of the 
trace species in compartment layers and filters.  Simple two room test case is 
attached.

Details documenting the problem is also attached as a PDF.

What steps will reproduce the problem?
1. Running the attached input file the mechanical ventilation does not 
appear to run at the rate prescribed.
2. I have similarly found this in other more simple geometries
3. I have tried modifying the defined ventilation rate and still the 
outpuf is not as defined

What is the expected output? What do you see instead?
Expect output files to state that the mechanical flow out of a compartment 
is as defined within the input file in regards to both volume and steady 
state - rather the volume is seen to decrease over time and is not as 
defined. 

What version of the product are you using? On what operating system?
Version 6

Please provide any additional information below.
I was wondering what would cause this to occur. Thanks

In CFAST user's guide is given a parameter to control the way time steps 
are dealt with. It is fisrt called DTCHE, then DTCHECK in the manual 
(appendix A), but only DTCHE is recognized.

Nevertheless, a negative entry on DTCHE should turn off this function, but 
it doesn't.

Moreover, feeding DTCHE with high time steps (like 0.1 s) seems to give 
dubious behaviour : After detection of the time steps going under the 
limit, CFAST goes on with time steps much smaller than the given limit 
(far under 0.1 s in my example). This therefore leads to an also excessive 
calculation time.

I am using CFAST 6.0.4.831 on Windows XP 

What steps will reproduce the problem?
1. open file compiled from version 6.0.10.61027
2. try running it
3. get "CFAST finished" before a second has passed

What is the expected output? What do you see instead?
The file running. It doesn't do anything other than display "CFAST finished"

What version of the product are you using? On what operating system?
CFAST v6.1.1.54 on Windows Vista Home Premium

Please provide any additional information below.
Just upgraded from 6.0.10.61027, won't run old files

Calculation of total mass of pyrolysate and total mass of trace species is 
incorrect in revision 18.  Calculated amount is just flow, not total mass.

Suggested solution is to modify integrate mass routine to include delta-t 
term in summation.

What steps will reproduce the problem?
1. Using a dual core dell hybrid
2. with Vista
3. Running sample

What is the expected output? What do you see instead?
cfast running

What version of the product are you using? On what operating system?
CFAST 6.0.10.61027, Windows Vista

Please provide any additional information below.

Using sample file CFAST just crashes.


See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.InvalidCastException: Conversion from string "  0.0     " to type
'Single' is not valid. ---> System.FormatException: Input string was not in
a correct format.
   at Microsoft.VisualBasic.CompilerServices.Conversions.ParseDouble(String
Value, NumberFormatInfo NumberFormat)
   at Microsoft.VisualBasic.CompilerServices.Conversions.ToSingle(String
Value, NumberFormatInfo NumberFormat)
   --- End of inner exception stack trace ---
   at Microsoft.VisualBasic.CompilerServices.Conversions.ToSingle(String
Value, NumberFormatInfo NumberFormat)
   at Microsoft.VisualBasic.CompilerServices.Conversions.ToSingle(String Value)
   at CEdit.RunModel.RunTimer_Tick(Object sender, EventArgs e)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1826 (QFE.050727-1800)
    CodeBase:
file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
CEdit
    Assembly Version: 6.0.10.61027
    Win32 Version: 6.0.10.61027
    CodeBase: file:///C:/Program%20Files/CFAST6/CEdit.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e
089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/Sy
stem.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.1434 (REDBITS.050727-1400)
    CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d5
0a3a/Microsoft.VisualBasic.dll
----------------------------------------
C1.Win.C1Preview.2
    Assembly Version: 2.0.20063.41006
    Win32 Version: 2.0.20063.41006
    CodeBase: file:///C:/Program%20Files/CFAST6/C1.Win.C1Preview.2.DLL
----------------------------------------
C1.C1Preview.2
    Assembly Version: 2.0.20063.41006
    Win32 Version: 2.0.20063.41006
    CodeBase: file:///C:/Program%20Files/CFAST6/C1.C1Preview.2.DLL
----------------------------------------
System.Design
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Design/2.0.0.0__b03f5f7f11d50a3a/Sys
tem.Design.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50
a3a/System.Configuration.dll
----------------------------------------
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Acc
essibility.dll
----------------------------------------
System.Data
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase:
file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.
Data.dll
----------------------------------------
C1.Win.C1FlexGrid.2
    Assembly Version: 2.6.20071.312
    Win32 Version: 2.6.20071.312
    CodeBase: file:///C:/Program%20Files/CFAST6/C1.Win.C1FlexGrid.2.DLL
----------------------------------------
NPlot
    Assembly Version: 0.9.9.0
    Win32 Version: 0.9.9.0
    CodeBase: file:///C:/Program%20Files/CFAST6/NPlot.DLL
----------------------------------------
C1.Win.C1Sizer.2
    Assembly Version: 2.1.20063.16
    Win32 Version: 2.1.20063.16
    CodeBase: file:///C:/Program%20Files/CFAST6/C1.Win.C1Sizer.2.DLL
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System
.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

File name:  DOE095a

Summary:  Stalling on lack of pressure solution

Attached file was run from the CEdit GUI.  CFAST stalls 151 seconds.  

CEdit Error window states:

Log: ERROR, DASSL - IDID= -8
Log:  pressure in room  1
Log:  Solution component with the greatest error is
Log: ierror,r1,r2 =  660    0.1516D+03    0.8408D-03
Log: AT T (=R1) AND STEPSIZE H (=R2) THE ITERATION MATRIX IS SINGULAR

Stalling on a 200 kW fire in a 3.6 m by 2.0 m room with door gap and 
forced ventilation is unexpected.

Version 6.1.0.24

If the door soffit is increased from 0.01 to 0.011 problem runs to 
solution.

version : CFAST 6.1.1.54
OS : window XP

Happy New Year to CFAST users.

Without mechanical ventilation, it works.
If I input mechanical ventilation from compartment #1 to outside, error 
message shows, which tells it needs #2 compartment.

I built #2 compartment and by use of horizontal walls to open, then, the 
messsage comes; "Fatal: Horizontal flow vent 2 is not connected between 
two existing compartments. Select compartment connections."

Is there any way to make forced ventilation from 1 compartment to outside 
or from outside to 1 compartment?

In addition, is there any way to make opening from 1 compartment to 
outside by use of horizontal flow vents?

I attach my file with revised thermal.csv and object files.

The CFAST User Guide (May 2008 Revision) notes that for the specification
of boundary materials "There can be as many as three layers per boundary,
but they are specified in the thermal database itself. (See the explanation
in the section on auxiliary files for additional details.)"  

However, the referenced section on auxiliary files is not included in the
document.  There is no explanation for the inputs in the Technical
Reference Guide either (May 2008)

1.  Is this feature still available in CFAST?  I understand that it may not
be compatible with the GUI.  Is it still available for text editing of the
input file and thermal.csv file?
2.  If the capability is still available, please provide documentation for
the inputs and usage of the multi-layer feature.

Thank you

What version of the product are you using? On what operating system?
May 2008 documentation
CFAST version 6.1.1.49