Format of .q file names - should handle simulation times greater than 99,999 seconds

[GoogleCodeExporter]

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:

I am attempting to use FDS to simulate diffusion of methane from the 
surrounding rock into mine tunnels.  My simulation times are lengthy, and 
I have need to run simulations of 864,000 seconds (10 days) or longer.  A 
typical small input file is below.  The mesh is tiny (4,1,6), runs very 
fast and will produce the error in less than 10 minutes execution time. 

The program is fine through 172,792.15 simulation seconds, but then it 
bombs giving the following message: 

forrt1: severe <43>: file name specification error, unit 14, file C: 
\Documents ans Settings\Owner\My Documents\FDS_CH4Models\FDSTimeTest 
\time_test_1_*****_25.q 

After 86,400 simulation seconds, the program writes a file called 
time_test_1_86400_26.q  I think you can see the problem.  The fortran file 
name can accomodate 5 digits, and I am attempting to stick in 6 digits 
(172800). 

If possible, please allow 8 digits in the naming of this .q file
That many digits would accomodate simulation times up to 99,999,999 
seconds or 1157 days which is way beyond anything I could possibly need.  
I certainly need 6 digits, but that would only accomodate simulation times 
up to 999,999 seconds or 11 days, and I am certain I need more.

Many thanks for your kind attention to this matter.

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

PS - A quick fix to this bug was provided by Jason Floyd who recommended 
suppressing the .q files by fixing DT_PL3D > T_END in the $DUMP command.
That fix does work.

&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, 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:15

[GoogleCodeExporter]

Will do -- this will be in FDS 5.3.0, which we will release either today or 
over the 
weekend. We also think we've found the memory leak as well.

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

• Changed state: Started

[GoogleCodeExporter]

Can you confirm that the program is now working properly?

Original comment by mcgra...@gmail.com on 10 Feb 2009 at 6:16

• Changed state: Fixed

[GoogleCodeExporter]

I had to verify this myself. KM

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

• Changed state: Verified