Giter Site home page Giter Site logo

fds-smv's People

fds-smv's Issues

Enhancements wish list - low priority 

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.

Original issue reported on code.google.com by [email protected] on 11 May 2007 at 10:06

Example files for Detectors 

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.

Original issue reported on code.google.com by [email protected] on 8 May 2007 at 3:35

Spray Burner results vary with nozzle orientation. 

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

Original issue reported on code.google.com by [email protected] on 10 May 2007 at 1:54

Binary versions 

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.

Original issue reported on code.google.com by emanuele.gissi on 2 May 2007 at 2:57

CTRL---access violation 

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',INITI
AL_STATE=.FALSE./


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

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

&TAIL /

Original issue reported on code.google.com by [email protected] on 9 May 2007 at 6:44

Libimf.so problem in smv5 taken from FDS_5_RC3-SMV_5_RC2_Linux.tar.gz, too. 

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.

Original issue reported on code.google.com by emanuele.gissi on 3 May 2007 at 7:04

Confusing IGNITION_TEMPERATURE and REFERENCE_* in User's Guide 

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.

Original issue reported on code.google.com by koverholt on 15 May 2007 at 11:44

Bad links in http://groups.google.com/group/fds-smv 

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.

Original issue reported on code.google.com by emanuele.gissi on 11 May 2007 at 10:47

VEL_T 

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

Original issue reported on code.google.com by [email protected] on 7 May 2007 at 4:14

Attachments:

Suggestions for Windows installation package 

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

Original issue reported on code.google.com by [email protected] on 8 May 2007 at 1:21

FDS Users Handbook RC3 

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

Original issue reported on code.google.com by [email protected] on 4 May 2007 at 12:55

REFERENCE_TEMPERATURE vs IGNITION_TEMPERATURE vs TMPIGN 

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?

Original issue reported on code.google.com by [email protected] on 11 May 2007 at 6:32

Attachments:

sv5p0_linux_RC3 core dumps (devices.svo seems the cause) 

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.

Original issue reported on code.google.com by emanuele.gissi on 9 May 2007 at 7:12

Vent off problem 



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

Original issue reported on code.google.com by [email protected] on 15 May 2007 at 6:13

Attachments:

Flow problem 

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

Original issue reported on code.google.com by [email protected] on 11 May 2007 at 6:44

Attachments:

Smoke Detector get a negative value, even negative infinity 

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 /

Original issue reported on code.google.com by [email protected] on 10 May 2007 at 11:17

Attachments:

FDS Users Handbook 

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"

Original issue reported on code.google.com by [email protected] on 4 May 2007 at 12:49

Mass specific extinction Coefficient 

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

Original issue reported on code.google.com by [email protected] on 9 May 2007 at 5:05

RC4: SLCF quantity carbon monoxide not appropriate for SLCF 

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 /

Original issue reported on code.google.com by [email protected] on 18 May 2007 at 3:40

Attachments:

Smokezip.exe compression error for path with spaces 

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

Original issue reported on code.google.com by koverholt on 7 May 2007 at 9:43

Numerical instability 

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?

Original issue reported on code.google.com by [email protected] on 17 May 2007 at 8:51

Attachments:

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.