firemodels / fds Goto Github PK

Comparing the Verification Guide, different results were got for the 
Detectors (both beam_detector and aspiration_detector). In 
beam_detector_devc.csv, obscuration of 0 % was shown for the 3 detectors.

Example file: fan_test.fds
Error: The domain appears to be sealed, but no pressure ZONEs are declared.

In table 13.9 (for material properties) of the user guide REFERENCE_RATE, 
NU_RESIDUE, N_REACTION, N_S, N_T etc. are included. Could please add some 
discussion on these properties?

Flow fields are not nice, if the walls are one grid cell thick
in the input file. They used to be fine, say, some month ago but
not any more. See the attached examples, one with 1 grid cell
thick walls and the other with 2 grid cell thick walls.
I did not yet do a test, where the walls are very thin, i.e.,
zero width: read.f90 should have 'thicken_obstructions=.true.'
for the evacuation flow grids. Probably, this case will also
have the same bug. Below is the source version:

 Compilation Date : May 27, 2007        
 Version          : 5_RC4+              

Ciao,
Timo Korhonen

Hello,

I modified the jvenart's example file. I found a problem in it. In this 
case the humidity is 25%. I notice the water vapor is in the methane flow 
like in ambient air, but the methane mass fraction is 1.0. I think is a 
problem.  I attached the test.fds and a jpg file from the problem.

Thank you your attention

Regards,

Csaba

Tried running the device_test example file on a Dell Optiplex GX260 and got
the following output.  Have run over a dozen of the other examples without
issue on the same machine.

C:\Program Files\NIST\FDS\Examples\DT>fds5 device_test.fds > device_test.err

 Fire Dynamics Simulator

 Compilation Date : April 30, 2007
 Version          : 5_RC3

 Job TITLE        : Test sprinklers, heat detectors and smoke detectors

 Job ID string    : device_test

forrtl: severe (157): Program Exception - access violation
Image              PC        Routine            Line        Source
fds5.exe           005912F0  Unknown               Unknown  Unknown
fds5.exe           005943C5  Unknown               Unknown  Unknown
fds5.exe           005CB750  Unknown               Unknown  Unknown
fds5.exe           005CCA1C  Unknown               Unknown  Unknown
fds5.exe           0064C784  Unknown               Unknown  Unknown
fds5.exe           00638B35  Unknown               Unknown  Unknown
kernel32.dll       7C816FD7  Unknown               Unknown  Unknown

C:\Program Files\NIST\FDS\Examples\DT>

I have run into a problem where the addition of sprinklers to a house 
appears to be causing a numerical instability.  I am modeling a small 
house.  With no forced flow, the simulation runs without issue.  When I 
add the DEVC, PROP and PART lines to include sprinklers, a numerical 
instability occurs within the first 5 seconds.  In viewing vector slices, 
there appear to be relatively high velocities near some of the walls.  Any 
ideas about why this is occurring?

Using SMV_RC4 (May 23 in title)

If time is stopped, and I move a grid, time starts back up again.

The enclosed file illustrates that when there is the THICKNESS parameter 
in a SURF definition, the fire fails to burn (hrr.csv file shows no heat 
output).  By removing the THICKNESS parameter, the fire burns OK.

I am wondering if it is possible to show the total heat release rate from
case_hrr.csv in SmokeView alongside the scenario so that the user can
easily see the total HRR results. Maybe on the side as a text number in kW?

I see the different ways to see HRR (HRRPUV slice, case_hrr.csv, and using
a HRR DEVC plane) and I am thinking that putting in the total HRR somewhere
more visible in SmokeView would be more user friendly. I say this because I
have seen many new users misinterpret the HRRPUV as the total HRR of the
fire, since it is usually the closest thing that they can find that
resembles "HRR" in the menu.

I don't know if this is sensible or not, but I think it would be a nice and
user-friendly feature if possible.

I try a simple case with one smoke detector.
the Smoke Detector get a negative value, even negative infinity.
I have try a few different case within the same domain.

case 1:
size of cell: 0.4m*0.4m*0.25
fire: t-square fire(3MW)
the detector get negative value and then get negative infinity.

case 2(a finer grid)
size of cell: 0.2m*0.2m*0.2m
fire: t-square fire(3MW)
the detector get negative value then get positive number.

case 3:
size of cell: 0.4m*0.4m*0.25
fire: HRR is a constant(3MW)
the detector has not get any negative value.

xls file of devc is attach as attachment,the input file is list below:
&HEAD CHID='device_test', TITLE='Test sprinklers, heat detectors and smoke
detectors' /
&MESH IJK=75,25,20, XB=0.0,30.0,0.0,10.0,0.0,5.0 /
&TIME TWFIN=600.0 /
&SURF ID='FIRE', HRRPUA=500.,TAU_Q=-252/ PART_ID='smoke' /
&VENT MB=XMAX SURF_ID='OPEN' /
&VENT XB=6,10.0,3,7,0.0,0.0, SURF_ID='FIRE' /
&PART ID='smoke', MASSLESS=.TRUE., SAMPLING_FACTOR=1 /
&PART ID='water', WATER=.TRUE.,    SAMPLING_FACTOR=1 /
&PROP ID='Acme Smoke'
      CLASS='SMOKE DETECTOR' /
&DEVC XYZ=2.00,0.50,4.95, PROP_ID='Acme Smoke', ID='smoke_1' /


&SLCF PBY=0.5, QUANTITY='TEMPERATURE', VECTOR=.TRUE. /
&SLCF PBX=3.5, QUANTITY='TEMPERATURE', VECTOR=.TRUE. /

&DUMP DT_PL3D=300. /

&TAIL /

I already posted the problem in the discussion group but the subject was 
changed to something else. Anyway, for the attached file I am 
having "STOP: Numerical Instability" after 59 seconds of simulation time.

Thanks

I found some discrepancy regarding smoke parameters. In Technical Reference
Guide (Draft: April 30, 2007) on page 39 there is an explanation about
smoke detectors.   
Equation (3.103)  gives an expression for the percent obscuration per unit
length. In this equation a Greek symbol kappa  is the specific extinction
coefficient, and there is explanation that “for most flaming fuels, a
suggested value for k is 8700 m2/kg ± 1100 m2/kg at a wavelength of 633 nm”
which comes from G.Mulholland and C. Croarkin paper. 

However, in the User Manual Draft, (April 30, 2007) on page 54 there is an
explanation regarding factors contributing to light extinction coefficient
and visibility.  Equation 4.12 characterizes parameters contributing to the
light extinction coefficient and thus to visibility (Eq 4.13) 
Km is called the MASS EXTINCTION COEFFICIENT and  “the default value is 
7600 m2/kg, a value suggested for flaming combustion of wood and plastics”.

However, the MASS EXTINCTION COEFFICIENT and the specific extinction
coefficient are the same parameter.  Therefore I wonder why two different
values are given? and what value is used in FDS for smoke detectors, is it
8700?
In REAC (Reaction Parameters) you can change the Km, but does it affect the
smoke detector as well? (kappa)

Best regards,
Sebastian
University of Ulster,
Northern Ireland

Better error messages that will stop the case if something is not specified
right.

A preprocessing read of the input file that checks for proper syntax and
also checks for conflicting input parameters.

As far as I understood T_Create and T_Remove are being removed and the 
function is offered by DEVC.
The actual users handbook still shows several T_CREATE which should be 
removed:

P. 25 "It is a good idea to inspect the geometry by running either a setup 
job (TWFIN=0 on the TIME line) or a short-time job to test the operation 
of T CREATE and/or T REMOVE."

P. 87 "T_CREATE Real Time to Create Obstruction s"

Hi,

The title says it all.

Dave

P. 12 &VENT CB=’XMIN’,SURF_ID=’OPEN’ /
should be changed in &VENT MB=’XMIN’,SURF_ID=’OPEN’ /

FDS5 RC1 
I have been running the varification samples and compairing the results to 
the varification guide.   In running the spray_burner sample as given, I 
get the expected results.  However, when I change the nozzle orientation 
to horizontal, the heat release rate never reaches 2MW.  It peaks out at 
around 1.75MW (average).  With the nozzles pointed up, instead of down, 
the HRR peakes out at around around 1.85MW (average).  When the HRR is 
graphed, the shape of the curve is the same as illustrated in the 
documentation, just that the upper platue never reaches 2MW in these two 
scenarios.

Is this an issue with FDS; or my lack of understanding of 3 dimensional 
spay fires?

Regards
MK

P83 Table B.3

The default value of INITIAL_STATE for DEVC should be .FALSE. 

In the user guide, I believe the table containing the output parameters for
the DUMP line has an error.  The default value for DT_PL3D is listed as
TWFIN/NFRAMES.  It is my understanding that this should be TWFIN/5, as
noted earlier in the guide.

Also, there appears to be an extra / in the sample reaction lines given. 
Each of these lines has a slash between the HEAT_OF_COMBUSTION and IDEAL
parameters, in addition to at the end of the line.

Jennifer

When I use the ONLY fuction_type in CTRL namelist group, I get  
a program exception. 
FDS5 version: RC3
OS: WinXP-SP2

the detail error message list as below:

D:\FDS5_test>fds5 ctrl.fds

 Fire Dynamics Simulator

 Compilation Date : April 30, 2007
 Version          : 5_RC3

 Job TITLE        : TEST

 Job ID string    : CTRL_TEST

forrtl: severe (157): Program Exception - access violation
Image              PC        Routine            Line        Source
fds5.exe           004AFCC2  Unknown               Unknown  Unknown
fds5.exe           004AF48E  Unknown               Unknown  Unknown

input Data file:

&HEAD CHID='CTRL_TEST',TITLE='TEST'/
&MESH IJK=12,20,16,XB=0,3,0,5,0,4/
&TIME TWFIN=10/

&ZONE /

&DEVC XYZ=2,2,2,ID='D_1',QUANTITY='TIME',SETPOINT=4.0,INITIAL_STATE=.TRUE./
&DEVC XYZ=2,2,2,ID='D_2',QUANTITY='TIME',SETPOINT=7.0,INITIAL_STATE=.TRUE./
&DEVC XYZ=2,2,2,ID='D_3',QUANTITY='TIME',SETPOINT=9.0,INITIAL_STATE=.FALSE./


&CTRL
ID='C_1',FUNCTION_TYPE='ONLY',n=2,LATCH=.FALSE.,INPUT_ID='D_1','D_2','D_3',INITIAL_STATE=.FALSE./


&OBST XB=2,2.5,3,4,2,3,COLOR='GREEN',CTRL_ID='C_1'/

&SLCF PBZ=0.5,QUANTITY='TEMPERATURE'/

&TAIL /

Downloaded sv5p0_linux_RC3.
Copied it into Smokeview former directory.
Submitted a test case: room_fire. It hangs:

$ ../sv5p0_linux_RC3 room_fire.smv
reading: room_fire.smv
reading input file
   pass 1
Reading device definitions from: ../devices.svo
Segmentation fault (core dumped)

Moved devices.svo to devices.svo.orig
so that Smokeview cannot find it anymore
Submitted the same test case and *it works properly*:

$ ../sv5p0_linux_RC3 room_fire.smv 
reading: room_fire.smv
reading input file
   pass 1
   pass 1 completed
   pass 2
      Loading colorbar texture:  - completed
   pass 2 completed
   pass 3
pass 3 complete
   pass 3 completed
   pass 4
   pass 4 completed
reading input file completed
beginning wrap up - 
wrap up completed
*********************************************************************
*********************************************************************
The US Department of Commerce makes no warranty, expressed or
implied, to users of Smokeview, and accepts no responsibility
[...]

In my opinion this has something to do with devices.svo

I am ready to send whatever you need.
Thank you, once more. Emanuele.

I am having the following error message upon restarting a stopped 
simulation by adding RESTART=.TRUE. to the &MISC line. 

Thanks, Kam.

forrtl: severe (67): input statement requires too much data, unit 90, file 
C:\Documents and Settings\lhp06103\My Documents\StecklerRoom\FDS\Try-
restart\try-restart_01.restart
Image              PC        Routine            Line        Source
fds5.exe           0064AC6E  Unknown               Unknown  Unknown
fds5.exe           00647F2C  Unknown               Unknown  Unknown
fds5.exe           005F97E2  Unknown               Unknown  Unknown
fds5.exe           005F940F  Unknown               Unknown  Unknown
fds5.exe           005F4D40  Unknown               Unknown  Unknown
fds5.exe           005F4384  Unknown               Unknown  Unknown
fds5.exe           005A62CC  Unknown               Unknown  Unknown
fds5.exe           005D0177  Unknown               Unknown  Unknown
fds5.exe           0064EAD4  Unknown               Unknown  Unknown
fds5.exe           0063AE85  Unknown               Unknown  Unknown
kernel32.dll       7C816FD7  Unknown               Unknown  Unknown

FDS is primarily to simulate natural fires. Can a feature be added so that 
we can conduct furnace simulations?

When passing an .fds file name using the full path and it exceeds 50
characters, there is a fortran runtime error during file write.

I recommend setting the Max path length to 1024 characters and the max file
name size to 256.  These are the defaults for Mac OS X.

This issue is carried over from FDS5_RC2. When using Smokeview and 
selecting Load > Compression > Compress on a case, the command will not 
work if the path to the FDS files has a space in it, (i.e. C:\Documents 
and Settings\KOverholt\Desktop\FDS Models\Aspiration 
Detector\aspiration_detector.smv).

Smokezip will work on the same path if it is invoked from the DOS command 
line, but the error shown below occurs when using the Smokeview interface 
to invoke smokezip.

This error occured using FDS5_RC3 which comes with the April 12, 2007 
build of Smokeview 5.0.0 Beta.

This is the output from the smokeview console:

Compressing...
Executing shell command: C:\Program Files\NIST\Smokeview\smokezip.exe  -s
C:\Documents and Settings\KOverholt\Desktop\FDS Models\Aspiration Detector
aspiration_detector.smv
'C:\Program' is not recognized as an internal or external command, operable
program or batch file.
Compression completed

When launching sv5_linux (taken from FDS_5_RC3-SMV_5_RC2_Linux.tar.gz) in
Linux Ubuntu Feisty (7.04) this error appears:

sv5_linux: error while loading shared libraries: libimf.so: cannot open
shared object file: No such file or directory

Note that previous versions (older sv5 and sv4) worked perfectly.
FDS_5_RC2-SMV_5_RC2_Linux.tar.gz had the same problem (already filed the
issue to sourceforge).

This version needs the Intel Compiler shared library "libimf.so".
I suggest to revert sv5_linux to a statically linked libimf.so

(fds5 rc2 seems to work fine for me: it runs. But I cannot visualize the
results ;-)

Emanuele Gissi.

Hello Bryan,

In this case the material flow out from a tank. It’s a simple case. 
My problem in this case that the temperature rising  above the lower hole, 
and the vertical velocity rising too. I don’t understand it. I’m not sure 
it is a mistake. May be is it friction? I upload the tank4.zip file with 
tank.fds and a jpg file from it. 

Thank you your help

Csaba

I am comparing some liquid fuel fire simulation with FDS4 and FDS5. 
Absorption coefficient is a new parameter introduced in FDS5.  As per 
table 13.9 of FDS5 User Guide its default value is given as 50000. Is it 
the same for solid and liquid materials?
Secondly, given that in FDS4, there is no absorption coefficient, what 
will be its equivalent (default) value for a liquid material in FDS4 
simulation?

COLOR='INVISIBLE' as described in section 8.6 of the FDS user's guide does 
not seem to be working.  

Hi,

I worked through the activate_vents.fds example and added comments to help 
me understand, and remember, how it works. If you think the file would be 
of use, then you are welcome to use it.

Dave

Hello,

I found a bug is in the subroutine SUBROUTINE COMBUSTION_FR(NM)
of fire.f90. (this is in FDS_5_RC3, I have not checked whether
this is still present in FDS_5_RC4)

The folliwng line:
X_O_S = X_O(NR) + DTT*DX_FDT*RN%N_O/RN%N_F

should be:
X_O_S = X_O(NR) + DTT*DX_FDT*RN%NU(RN%I_OXIDIZER)/RN%NU(RN%I_FUEL)

Thanks!
Arnaud

Hi,

I installed the latest Windows package (RC 3.1) and re-booted. I didn't 
have a Smokeview desktop icon appear. It would be nice if there were 
desktop icons for both Smokeview and FDS (command prompt). 

I opened a small number of the example files in Notepad and none of them 
had line breaks (although they do so in Wordpad). If the example files are 
cut and pasted from Wordpad into Notepad and saved, then they will open 
appropriately in Notepad.

Dave

Hello,
As a result of your reply in Issue no 28, I modified my input files and I
was trying to obtain information on CO using SLCF, however I couldn’t see
all  slices which were described in input file.

When I asked for 2 slices in input file, I was able to see only one in
Smokeview, and when I asked for 4, I got only 2.
You will find attached 2 input files, error 1 (for 2 slices) and error 2
(for 4 slices).

All simulations were made in RC5

Regards
Sebastian Ukleja

I attempt to use SV5_RC4 with some earlier fds4 out files however the 
geometric colours are incorrect for some blockages (green) and they 
change to red when the vent opens. How can I get them to revert back to 
the original settings I had? I do not want to run the problems again; 
too large! and need to get the greater size and resolution data for the 
rendered snapshots.

Jim

Hi,

I've taken your file device_test.fds and stripped out everything but the 
sprinklers (see below). I would like to vary the flow rate over time. I 
tried using a controller function from  activate_vents.fds, which didn't 
work.

Any ideas?

Thanks
Dave





&HEAD CHID='sprinkler_pressure', TITLE='Test of change in sprinkler 
pressure' /

&MESH IJK=30,10,10, XB=0.0,3.0,0.0,1.0,0.0,1.0 /
&MESH IJK=10,40,10, XB=3.0,4.0,0.0,4.0,0.0,1.0 /

&TIME TWFIN=60.0 /

&SURF ID='FIRE', HRRPUA=500. /

&VENT XB=3.0,4.0,4.0,4.0,0.0,1.0, SURF_ID='OPEN' /
&VENT XB=0.6,1.0,0.3,0.7,0.0,0.0, SURF_ID='FIRE' /


&PART ID='water', WATER=.TRUE., SAMPLING_FACTOR=1 /


&PROP ID='Acme Sprinkler'
      QUANTITY='SPRINKLER LINK TEMPERATURE'
      FLOW_RATE=180.  
      RTI=50.
      ACTIVATION_TEMPERATURE= 74.
      OFFSET= 0.05
      SPRAY_ANGLE=50.,55.
      PART_ID='water' /



&DEVC XYZ=0.50,0.50,0.95, ID='sprinkler_1', PROP_ID='Acme Sprinkler' /
&DEVC XYZ=1.50,0.50,0.95, ID='sprinkler_2', PROP_ID='Acme Sprinkler' /
&DEVC XYZ=2.50,0.50,0.95, ID='sprinkler_3', PROP_ID='Acme Sprinkler' /
&DEVC XYZ=3.50,0.50,0.95, ID='sprinkler_4', PROP_ID='Acme Sprinkler' /
&DEVC XYZ=3.50,1.50,0.95, ID='sprinkler_5', PROP_ID='Acme Sprinkler' /
&DEVC XYZ=3.50,2.50,0.95, ID='sprinkler_6', PROP_ID='Acme Sprinkler' /


&SLCF PBY=0.5, QUANTITY='TEMPERATURE', VECTOR=.TRUE. /
&SLCF PBX=3.5, QUANTITY='TEMPERATURE', VECTOR=.TRUE. /

&DUMP DT_PL3D=30. /

&TAIL /

Material properties and reaction parameters that can be given as inputs 
are listed in table 13.9 and 13.18 respectively in the user guide. Could 
you please list the name of the bench-scale or other tests that can be 
used to obtain these properties and parameters?

I am an active tester of the new versions of FDS and SMV.

I found a bug (shared instead of static library in SMV) that you corrected
immediately. But I have to wait for RC3 to continue my test.

I think that you could ease the testers' work in one of this two ways:
1) (preferred) please publish an automatic nightly-build version of the
software, as other projects do.
2) please set up a page where you explain how to predictably and uniformly
compile the source. If possible, using open source tools... (I work on Linux).

As always, I thank you in advance.

Glenn, I have a simple isosurface of hydrogen volume fraction that shows 
up badly in SV. I've attached the file.

I was trying to obtain information on CO using SLCF, however I couldn’t see
the results in smoke view. (RC3) Today I made an input file as simple as
possible and I’ve used RC4. As a result I’ve got the following error:
SLCF quantity carbon monoxide not appropriate for SLCF

This seems to be strange because in user manual p90 with carbon monoxide is
written D,I,P,S, which means that slice file should be OK.

Is that a bug or I did something wrong?

Regards
Sebastian Ukleja

My input file:

&HEAD CHID='error', TITLE='title'  / 
&MESH IJK=10,10,10, XB=0.0, 1.0, 0.0, 1.0, 0.0, 1.0 / 
&TIME TWFIN=0. / 
&VENT MB='YMIN',SURF_ID='OPEN' / 
&SLCF PBY=0.1, QUANTITY='carbon monoxide'
&SLCF PBY=0.2, QUANTITY='carbon monoxide'
&TAIL /

Until recently, we have been using FDS4 to model a stack of wood and 
plastic pallets.  In FDS4 the results compared quite favourably with 
experiments having fine tuned the input file until we obtained the desired 
results.  Based on discussion I have had with the developers we changed to 
FDS5 and after modifying the file to the new input formats we ran the same 
case substituting REFERENCE_TEMPERATURE for TMPIGN.  When we ran this in 
FDS5 we had almost instantaneous ignition of the fuel.  We then changed 
REFERENCE_TEMPERATURE to IGNITION_TEMPERATURE and obtained a significantly 
slower growth than the FDS4 results.  I have attached a pdf graph showing 
the RHR for the three cases along with the data files for all three runs.  

The user’s manual does gives very limited discussion for 
IGNITION_TEMPERATURE.  Can you shed some light on this problem for us?

I just get the last FDS version (fds5_OSX_PPC_G4, 5 637 967 bytes). 
I just run activate_vents.fds and find the same bug that with the 
previous one. 
In fact, it seems that FDS has not only one frame counter but many, 
and that the frame counter is not the same, depending on the data. 
For Slice-file/Velocity Y=05 -> 77 frames, times always stay at 0 
For Slice file/U-Velocity Y=0.5 -> 28 frames, times running from 0 to 
0.9 
For Slicefile/V-Velocity Y=0.5 -> 77 fames, timaes always stay at 0 


If, at same time, I try to run particule data Smokeviw crash. 


computing particle color levels 
smokeview(347,0xa000ed88) malloc: ***  Deallocation of a pointer not 
malloced: 0xbfbe00; This could be a double free(), or free() called 
with the middle of an allocated block; Try setting environment 
variable MallocHelp to see tools to help debug 
Segmentation fault 

A few ideas for enhancements that I would find useful (maybe some others 
would too!)

1.) Ability to specify maximum CFL #.  CFL < 1 is needed for stability, 
but I've found running with a smaller CFL # helps limit numerical funny 
business. 

2.) Ability to specify species specific heat capacity.  If you add an 
extra species via &SPEC and it's not one of the few that FDS "knows" (CO, 
CO2, H2O, H2, CH4) then FDS calculates its specific heat as cp = (R/M)*g/
(g-1) where R is the gas constant, M is the molecular weight, and g is 
cp/cv. This doesn't work very well for high molecular weight species, i.e. 
with g = 1.4 and M = 100 g/mol, you get cp = 291 J/kg-K, which is too low.

3.) Gas-phase volumetric heat sources (unrelated to combustion and not 
tied to a blockage or vent).  In my research I've used this as 
an "igniter" in flame spread simulations because it's much cleaner than 
putting in a blockage, heating it up, and removing it after whatever 
you're trying to burn ignites. 

4.) Ability to use the finite-rate combustion model with the pyrolysis 
model. Right now line 2592 in read.f (subroutine READ_MATL) checks to see 
if a solid reaction has NU_FUEL > 0 and if so it sets MIXTURE_FRACTION 
= .TRUE.. So if you set a combustible solid and a finite-rate reaction, 
FDS complains because it thinks you're trying to simultaneously use the 
mixture fraction combustion model with the finite rate combustion model. 
Also, in subroutine COMBUSTION_FR, line 300 exceeds array bounds because N 
is cycled from 0 to N_SPECIES but NU has bounds 1:20. 

Could the ability to specify Smagoronsky constant can be added? 

This the text of the page linked in the summary:

"""
This is the primary discussion forum for FDS and Smokeview related topics.
The FDS and Smokeview homepage is ***HERE***
The New FDS-SMV Development page on Google Code is ***HERE***
Please see the List of Beta Testers, if you have been part of testing FDS,
please edit the page and add yourself to the list.
"""

The starred links are wrong as they point to fds-sv and not fds-smv!

Emanuele.

User's Guide Draft from April 30

In looking at appendix B9 (MATL Properties) it does not list
IGNITION_TEMPERATURE as a parameter even though it is explained and used in
the example on page 31 under 'Solid Fuels that Burn at a Specified Rate'.

Also, the REFERENCE_TEMPERATURE listing in Appendix B9 has a description of
'Ignition Temperature' which is confusing due to redundancy.

Finally, the REFERENCE_RATE isn't expanded on very much, which leaves me
wondering how much of an effect it and the other parameters described here
will have on the results.

I see the SmokeView PPC beta 5 available on the page
http://www.fire.nist.gov/fds/svtest/ from December 21st. I am wondering if
there is an updated version available.

Also, on the Sourceforge page, Glenn had posted the SV source and I am
wondering if it can be posted up again on this Google Code site.

Thanks.

I have another problem with my tank file. When I leave the obstacle from 
bottom of the tank and I close the vent. Than bottom of the specie mix 
with air too quick(may be untrue). That I avoid this symptom I created 
this obstacle. Have you another solution so I avoid this symptom. I 
attached the problem tank.fds file without obstacle line.  

Csaba

The parameter VEL_T seems not to work right.

The line
&SURF ID='LOUVER',VEL=-2.0,VEL_T=2.0,0.0 /
causes nothing but the VEL=-2.0

&SURF ID='LOUVER',VEL=-2.0,VEL_T=0.0,2.0 /
causes a flow I thought to appear with VEL_T=2.0,2.0 +/- 

Boris Stock
BFT Cognos

Hello,

I ran this case in rc4. I have problem too. When the Vent was closed, the 
benzene mix with air. But air isn't there bottom of the tank. I attached 
file tank.fds and jpg file from problem.