search

Yinan-Scott-Shi / fds-smv

Automatically exported from code.google.com/p/fds-smv
0 stars 0 forks source link

Problem with long simulation times - error message - forrtl: severe <170>: Program Exception - stack overflow #624

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Please complete the following lines...

Application Version: 5.1.0
SVN Revision Number: 1162
Compile Date: Tuesday 08 Jan 2008
Operating System: Microsoft Windows XP Home Edition Version 2002 Service 
Pack 2

Describe details of the issue below:

Below are two input files.  The small mesh (4,1,8) runs to a T_END of 
432,000.  The large mesh (10,1,30) is identical to the smaller file, 
except it produces the stack overflow error at 287,088.78 simulation 
seconds.  The output from the smaller mesh is reasonable. 
Density remains more or less constant at about 1.2; temperature 
remains constant at 20, and pressure increases slightly, since we are 
replacing air with lighter methane.  The larger mesh (10,1,30) appears 
to be well behaved up to the failure point. 

The smaller file runs to completion in about 15 minutes on my laptop.  The 
larger file runs to the failure point in about 2.5 hours.

I would like to get this problem or mis-understanding of FDS resolved. 
As part of our research program here on the behavior of methane gas in 
mines, I have numerous simulations planned with FDS. 

Thank you in advance for your help. 

Karl Zipf 
Senior Mining Engineer 
NIOSH - Pittsburgh Research Laboratory
412-386-4097

This small mesh (4,1,8) runs to completion at T_END = 432,000 seconds 

&HEAD CHID='time_test_1',TITLE='flux in only from roof plus diffusion' / 
&MESH ID='AIR_INITIAL' IJK=4,1,8, XB=0.0,1.0,-0.1,+0.1,0.0,3.0 / 
&MISC BACKGROUND_SPECIES='AIR' / 

&OBST XB= 0.0,1.0,-0.1,0.1,0.0,0.0,SURF_ID='INERT' / bottom 

&SPEC ID='METHANE' / methane 
&SURF ID='CH4influx', MASS_FLUX(1)=2e-6 / 
&VENT XB= 0.0,1.0,-0.1,0.1,3.0,3.0, SURF_ID='CH4influx' / 

&SURF ID='massoutflux_left',  MASS_FLUX_TOTAL=3.333333333e-7 / 
&VENT XB= 0.0,0.0,-0.1,0.1,0.0,3.0, SURF_ID='massoutflux_left' / 

&SURF ID='massoutflux_right', MASS_FLUX_TOTAL=3.333333333e-7 / 
&VENT XB= 1.0,1.0,-0.1,0.1,0.0,3.0, SURF_ID='massoutflux_right' / 

&TIME T_END=432000.0 / 
&DUMP NFRAMES=120, DT_PL3D = 500000.0, FLUSH_FILE_BUFFERS=.TRUE. / 

&SLCF PBY=0.0, QUANTITY='METHANE_VF', VECTOR=.FALSE. / 
&SLCF PBY=0.0, QUANTITY='METHANE',    VECTOR=.FALSE. / 
&SLCF PBY=0.0, QUANTITY='PRESSURE',   VECTOR=.FALSE. / 
&SLCF PBY=0.0, QUANTITY='TEMPERATURE',VECTOR=.FALSE. / 
&SLCF PBY=0.0, QUANTITY='DENSITY',    VECTOR=.FALSE. / 

&DEVC XYZ=0.5,0.0,3.0, QUANTITY='METHANE_VF', ID='CH4 3.0' / 
&DEVC XYZ=0.5,0.0,2.0, QUANTITY='METHANE_VF', ID='CH4 2.0' / 
&DEVC XYZ=0.5,0.0,1.0, QUANTITY='METHANE_VF', ID='CH4 1.0' / 
&DEVC XYZ=0.5,0.0,0.0, QUANTITY='METHANE_VF', ID='CH4 0.0' / 

&DEVC XYZ=0.5,0.0,3.0, QUANTITY='PRESSURE', ID='Pressure 3.0' / 
&DEVC XYZ=0.5,0.0,2.0, QUANTITY='PRESSURE', ID='Pressure 2.0' / 
&DEVC XYZ=0.5,0.0,1.0, QUANTITY='PRESSURE', ID='Pressure 1.0' / 
&DEVC XYZ=0.5,0.0,0.0, QUANTITY='PRESSURE', ID='Pressure 0.0' / 

&DEVC XYZ=0.5,0.0,3.0, QUANTITY='TEMPERATURE', ID='Temperature 3.0' / 
&DEVC XYZ=0.5,0.0,2.0, QUANTITY='TEMPERATURE', ID='Temperature 2.0' / 
&DEVC XYZ=0.5,0.0,1.0, QUANTITY='TEMPERATURE', ID='Temperature 1.0' / 
&DEVC XYZ=0.5,0.0,0.0, QUANTITY='TEMPERATURE', ID='Temperature 0.0' / 

&DEVC XYZ=0.5,0.0,3.0, QUANTITY='DENSITY', ID='Density 3.0' / 
&DEVC XYZ=0.5,0.0,2.0, QUANTITY='DENSITY', ID='Density 2.0' / 
&DEVC XYZ=0.5,0.0,1.0, QUANTITY='DENSITY', ID='Density 1.0' / 
&DEVC XYZ=0.5,0.0,0.0, QUANTITY='DENSITY', ID='Density 0.0' / 

&TAIL 

This larger mesh (10,1,30) fails after 288,000 simulation seconds with 
the error message 
forrtl: severe <170>: Program Exception - stack overflow 
It is identical in all respects to the smaller mesh. 

&HEAD CHID='CH4_flux_in_only_1',TITLE='flux in only from roof plus 
diffusion' / 
&MESH ID='AIR_INITIAL' IJK=10,1,30, XB=0.0,1.0,-0.1,+0.1,0.0,3.0 / 
&MISC BACKGROUND_SPECIES='AIR' / 

&OBST XB= 0.0,1.0,-0.1,0.1,0.0,0.0,SURF_ID='INERT' / bottom 

&SPEC ID='METHANE' / methane 
&SURF ID='CH4influx', MASS_FLUX(1)=2e-6 / 
&VENT XB= 0.0,1.0,-0.1,0.1,3.0,3.0, SURF_ID='CH4influx' / 

&SURF ID='massoutflux_left',  MASS_FLUX_TOTAL=3.33333333e-7 / 
&VENT XB= 0.0,0.0,-0.1,0.1,0.0,3.0, SURF_ID='massoutflux_left' / 

&SURF ID='massoutflux_right', MASS_FLUX_TOTAL=3.33333333e-7 / 
&VENT XB= 1.0,1.0,-0.1,0.1,0.0,3.0, SURF_ID='massoutflux_right' / 

&TIME T_END=432000.0 / 
&DUMP NFRAMES=120, DT_PL3D = 500000.0, FLUSH_FILE_BUFFERS=.TRUE. / 

&SLCF PBY=0.0,QUANTITY='METHANE_VF',VECTOR=.FALSE. / 
&SLCF PBY=0.0,QUANTITY='METHANE',VECTOR=.FALSE. / 
&SLCF PBY=0.0,QUANTITY='PRESSURE',VECTOR=.FALSE. / 
&SLCF PBY=0.0,QUANTITY='TEMPERATURE',VECTOR=.FALSE. / 
&SLCF PBY=0.0,QUANTITY='DENSITY',VECTOR=.FALSE. / 

&DEVC XYZ=0.5,0.0,3.0, QUANTITY='METHANE_VF', ID='CH4 3.0' / 
&DEVC XYZ=0.5,0.0,2.0, QUANTITY='METHANE_VF', ID='CH4 2.0' / 
&DEVC XYZ=0.5,0.0,1.0, QUANTITY='METHANE_VF', ID='CH4 1.0' / 
&DEVC XYZ=0.5,0.0,0.0, QUANTITY='METHANE_VF', ID='CH4 0.0' / 

&DEVC XYZ=0.5,0.0,3.0, QUANTITY='PRESSURE', ID='Pressure 3.0' / 
&DEVC XYZ=0.5,0.0,2.0, QUANTITY='PRESSURE', ID='Pressure 2.0' / 
&DEVC XYZ=0.5,0.0,1.0, QUANTITY='PRESSURE', ID='Pressure 1.0' / 
&DEVC XYZ=0.5,0.0,0.0, QUANTITY='PRESSURE', ID='Pressure 0.0' / 

&DEVC XYZ=0.5,0.0,3.0, QUANTITY='TEMPERATURE', ID='Temperature 3.0' / 
&DEVC XYZ=0.5,0.0,2.0, QUANTITY='TEMPERATURE', ID='Temperature 2.0' / 
&DEVC XYZ=0.5,0.0,1.0, QUANTITY='TEMPERATURE', ID='Temperature 1.0' / 
&DEVC XYZ=0.5,0.0,0.0, QUANTITY='TEMPERATURE', ID='Temperature 0.0' / 

&DEVC XYZ=0.5,0.0,3.0, QUANTITY='DENSITY', ID='Density 3.0' / 
&DEVC XYZ=0.5,0.0,2.0, QUANTITY='DENSITY', ID='Density 2.0' / 
&DEVC XYZ=0.5,0.0,1.0, QUANTITY='DENSITY', ID='Density 1.0' / 
&DEVC XYZ=0.5,0.0,0.0, QUANTITY='DENSITY', ID='Density 0.0' / 

&TAIL

Original issue reported on code.google.com by rz...@cdc.gov on 30 Jan 2009 at 8:50

GoogleCodeExporter commented 9 years ago 
This was due to a memory leak, meaning that memory was being allocated over and 
over 
due a particular call. In this case, a simple INQUIRE statement. We fixed and 
will 
test your case.

BTW, the reason for posting all this here is that we can associate our bug fix 
with 
the original submission of the request. Helps us to understand what the problem 
was 
that we fixed.

Original comment by mcgra...@gmail.com on 30 Jan 2009 at 8:55

GoogleCodeExporter commented 9 years ago 
Hello Mr. Mcgratta,
How are you coming with the memory leak problem?  Were you able to diagnose 
the "bug" and test the fix with my case?  
Your assistance is very much appreciated.  I would like to download a corrected 
version of FDS and get back to my studies.
Please let me know if I can help or provide any additional info on this problem.
Best regards,
Karl Zipf
Senior Mining Engineer
NIOSH - Pittburgh Research Lab

Original comment by rz...@cdc.gov on 4 Feb 2009 at 1:39

GoogleCodeExporter commented 9 years ago 
We fixed both bugs, and I ran your case successfully. Download the new version 
which 
is available on the Downloads page. Then confirm that the problem is fixed.

Original comment by mcgra...@gmail.com on 4 Feb 2009 at 1:45

GoogleCodeExporter commented 9 years ago 
I had to verify this myself. KM

Original comment by mcgra...@gmail.com on 17 Feb 2009 at 3:19