boundary file + fds2ascii + smokeview

[gforney]

Application Version: 5.5.1 64 bit (mpi)
SVN Revision Number: 6385
Operating System: windows server 2003

Describe details of the issue below:

see mesh.fds
jet fire with low speed (100 m/s)
5 x 5 x 5 m geometry divided in 8 equal meshes, wall on a side.
Target: evaluate the heat radiation on the wall.
- First problem: on fds2ascii the output is a 0kb file.
                            input data: BNDFfile, alldata, domain limited, coord x
0 0, y 2.4 2.4, z 0 5, 
                            time aver 1-5sec, direction -2, 1,1 (also tried in x 0.1
0.1)
- Second problem: with smokeview infinite loop when trying to charge BNDFfile

   ........
   boundary time=0.00 
   boundary time=0.00
   boundary time=0.00
   reallocating memory
   ........

   flame and smoke are ok

Original issue reported on code.google.com by luca.piantelli on 2010-09-02 09:44:36

---

• Attachment: mesh.fds

[gforney]

I'll take a look at it.

Original issue reported on code.google.com by mcgratta on 2010-09-02 13:37:05

[gforney]

Smokeview (32 bit, Windows, SVN 6645) worked for me. What version of Smokeview are you
using?

This is my session for fds2ascii. The file is not empty.

Enter Job ID string (CHID):
mesh
  What type of file to parse?
  PL3D file? Enter 1
  SLCF file? Enter 2
  BNDF file? Enter 3
3
  Enter Sampling Factor for Data?
  (1 for all data, 2 for every other point, etc.)
1
  Domain selection:
    y - domain size is limited
    n - domain size is not limited
    z - domain size is not limited and z levels are offset
    ya, na or za - slice files are selected based on type and location.
        The y, n, z prefix are defined as before.
y
  Enter min/max x, y and z
-1 1 0 3 0 5
  1   MESH  3,  RADIATIVE HEAT FLUX
  2   MESH  4,  RADIATIVE HEAT FLUX
  3   MESH  7,  RADIATIVE HEAT FLUX
  4   MESH  8,  RADIATIVE HEAT FLUX
  Enter starting and ending time for averaging (s)
4 5
  Enter orientation: (plus or minus 1, 2 or 3)
-2
  Enter number of variables
1
 Enter boundary file index for variable 1
1
 Enter output file name:
junk.csv

Original issue reported on code.google.com by mcgratta on 2010-09-02 15:51:41

[gforney]

I use smokeview 64 bit, last version available on the site (downloaded with fds).
Now smokeview works with a new simulation (same as before but 10x10x10 meters and with
a mesh of 8 millions).
Empty file

&TIME T_END = 1/  (short time just to try)

&MESH IJK = 100,100,100 XB = -5.0, 0.0, -5.0, 0.0, 0.0, 5.0/
&MESH IJK = 100,100,100 XB =  0.0, 5.0, -5.0, 0.0, 0.0, 5.0/
&MESH IJK = 100,100,100 XB = -5.0, 0.0,  0.0, 5.0, 0.0, 5.0/
&MESH IJK = 100,100,100 XB =  0.0, 5.0,  0.0, 5.0, 0.0, 5.0/
&MESH IJK = 100,100,100 XB = -5.0, 0.0, -5.0, 0.0, 5.0,10.0/
&MESH IJK = 100,100,100 XB =  0.0, 5.0, -5.0, 0.0, 5.0,10.0/
&MESH IJK = 100,100,100 XB = -5.0, 0.0,  0.0, 5.0, 5.0,10.0/
&MESH IJK = 100,100,100 XB =  0.0, 5.0,  0.0, 5.0, 5.0,10.0/

.....

&OBST XB = -5.0, 5.0, 4.95, 5.0, 0, 10.0, SURF_ID = 'IRON_WALL', BNDF_OBST = .TRUE./

.....

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

Z:\>cd Z:\Simulazioni_FDS\jet_fire_2

Z:\Simulazioni_FDS\jet_fire_2>fds2ascii_win_64
  Enter Job ID string (CHID):
mesh
  What type of file to parse?
  PL3D file? Enter 1
  SLCF file? Enter 2
  BNDF file? Enter 3
3
  Enter Sampling Factor for Data?
  (1 for all data, 2 for every other point, etc.)
1
  Domain selection:
    y - domain size is limited
    n - domain size is not limited
    z - domain size is not limited and z levels are offset
    ya, na or za - slice files are selected based on type and location.
        The y, n, z prefix are defined as before.
y
  Enter min/max x, y and z
-5
5
0
5
0
10
  1   MESH  1,  RADIATIVE HEAT FLUX
  2   MESH  1,  RADIATIVE HEAT FLUX
  3   MESH  1,  RADIATIVE HEAT FLUX
  4   MESH  1,  RADIATIVE HEAT FLUX
  Enter starting and ending time for averaging (s)
.5
1
  Enter orientation: (plus or minus 1, 2 or 3)
-2
  Enter number of variables
1
 Enter boundary file index for variable 1
1
 Enter output file name:
test.txt
  Writing to file...      test.txt

Z:\Simulazioni_FDS\jet_fire_2>

Original issue reported on code.google.com by luca.piantelli on 2010-09-02 20:40:56

[gforney]

Looks like a 32 vs 64 bit problem. I have to check to see if the fds2ascii program is
64 bit.

Original issue reported on code.google.com by mcgratta on 2010-09-02 20:55:19

[gforney]

Today I tried on the other machine, a dual core with windows 32 bit and everythink seems
to work (just few seconds of the first simulation). The only think I can do is to read
the file with fds2ascii instead of fds2ascii_win_64. 

Original issue reported on code.google.com by luca.piantelli on 2010-09-02 21:04:32

[gforney]

The 64 bit fds2ascii should work with the 64 bit version of FDS. If it does not, tell
me.

Original issue reported on code.google.com by mcgratta on 2010-09-02 21:13:35

[gforney]

now it works, but it the wrong way..

Here what I did:
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

Z:\>cd Z:\Simulazioni_FDS\jet_fire_2

Z:\Simulazioni_FDS\jet_fire_2>fds2ascii_win_64
  Enter Job ID string (CHID):
mesh
  What type of file to parse?
  PL3D file? Enter 1
  SLCF file? Enter 2
  BNDF file? Enter 3
3
  Enter Sampling Factor for Data?
  (1 for all data, 2 for every other point, etc.)
1
  Domain selection:
    y - domain size is limited
    n - domain size is not limited
    z - domain size is not limited and z levels are offset
    ya, na or za - slice files are selected based on type and location.
        The y, n, z prefix are defined as before.
y
  Enter min/max x, y and z
-5
5
-5
5
0
10
  1   MESH  1,  RADIATIVE HEAT FLUX
  2   MESH  1,  RADIATIVE HEAT FLUX
  3   MESH  1,  RADIATIVE HEAT FLUX
  4   MESH  1,  RADIATIVE HEAT FLUX
  Enter starting and ending time for averaging (s)
0
1
  Enter orientation: (plus or minus 1, 2 or 3)
-2
  Enter number of variables
1
 Enter boundary file index for variable 1
1
 Enter output file name:
test.txt
  Writing to file...      test.txt

Z:\Simulazioni_FDS\jet_fire_2>

Notice the version of fds2ascii for win 64
attached there are the fds file and the output.
In y = -0,5 there is only the vent "wind"
After writing coordinates of all the domain (as you can see above) the program recognize
only 4 meshes.
What I need is only values in x=0, y=4.95, z=0-10 (in front of the flame in the downwind
direction)

Original issue reported on code.google.com by luca.piantelli on 2010-09-02 21:41:07

---

• Attachment: mesh.fds
• Attachment: test.txt

[gforney]

On the workstation I have both the version of FDS, the 64 bit version and the 32 bit
one. They are installed in two different folders and I change the environment variable
when I want one of the two versions.
This morning I tried to read the output files with the 32 bit package. Results are
the same. 
x = 0, 0   y = 4.95 , 4.95  z = 0, 6.0 ---> empty file

In the post before I reported 

x = -5.0, 5.0   y = -5.0, 5.0   z = 0, 10  ----> all the domain!

shouldn't be all the meshes? 1,2,3,4,5,6,7 and 8 ?!
I can't understand the list of the meshes it reports... 

Original issue reported on code.google.com by luca.piantelli on 2010-09-05 07:23:10

[gforney]

I think I understand the problem now. It is more simple than I thought. I believe that
we forgot to include the latest version of fds2ascii in the last release. Type:

fds2ascii -v

and report what you see.

Original issue reported on code.google.com by mcgratta on 2010-09-06 18:06:35

[gforney]

kevin,
there is a mistake in my bundler, it is picking up the wrong version of fds2ascii.
 Let me know what version you are expecting and I will make sure it gets in the bundle
correctly.

Original issue reported on code.google.com by gforney on 2010-09-06 18:23:04

[gforney]

[mcgratta@acrux intel_linux_32]$ fds2ascii -v
 fds2ascii 2.1.0 Revision: 6404

Come to think of it, this might have been changed after the last release, so maybe
the bundling procedure is OK.

Original issue reported on code.google.com by mcgratta on 2010-09-06 18:36:14

[gforney]

I don't understand where you want I type fds2ascii -v
I typed "  fds2ascii -v    " in the command prompt but it doesn't work because obviously
there isn't the path set in the environment variables.
I remind you that the version I am using is the following "Bundled FDS and Smokeview
for 64 bit Windows (SVN r6385,6366)" released the 23rd of june.

Original issue reported on code.google.com by luca.piantelli on 2010-09-06 18:45:55

[gforney]

I typed:
fds2ascii_win_64 -v

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

Z:\>fds2ascii_win_64 -v
 fds2ascii 2.0.0 Revision: 6325

Z:\>

Original issue reported on code.google.com by luca.piantelli on 2010-09-06 18:49:16

[gforney]

OK, that is the problem. There is a newer version of fds2ascii that will be released
with the next version (this week) that should fix the problem. I will mark the issue
as "Fixed", but please confirm that the new version works.

Original issue reported on code.google.com by mcgratta on 2010-09-06 18:51:53

[gforney]

Ok, problem has been solved!

Original issue reported on code.google.com by luca.piantelli on 2010-09-09 20:06:43

[gforney]

Thanks for checking it out!

Original issue reported on code.google.com by mcgratta on 2010-09-09 20:10:02

[gforney]

I found a problem with fds2ascii in the following case 
I report details

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

Z:\>cd Z:\Simulazioni_FDS\pool_fire

Z:\Simulazioni_FDS\pool_fire>fds2ascii_win_64
  Enter Job ID string (CHID):
pool_fire_1
  What type of file to parse?
  PL3D file? Enter 1
  SLCF file? Enter 2
  BNDF file? Enter 3
3
  Enter Sampling Factor for Data?
  (1 for all data, 2 for every other point, etc.)
1
  Domain selection:
    y - domain size is limited
    n - domain size is not limited
    z - domain size is not limited and z levels are offset
    ya, na or za - slice files are selected based on type and location.
        The y, n, z prefix are defined as before.
y
  Enter min/max x, y and z
0
0
10.9
10.9
0
10
  1   MESH  3,  RADIATIVE HEAT FLUX
  2   MESH  4,  RADIATIVE HEAT FLUX
  3   MESH  7,  RADIATIVE HEAT FLUX
  4   MESH  8,  RADIATIVE HEAT FLUX
  Enter starting and ending time for averaging (s)
20
60
  Enter orientation: (plus or minus 1, 2 or 3)
-2
  Enter number of variables
1
 Enter boundary file index for variable 1
1
 Enter output file name:
test.txt
  Writing to file...      test.txt

Z:\Simulazioni_FDS\pool_fire>

I want data on the line x=0, y=10.9, z=0-10
Output is only in the region z=0-5, so only half the domain
Output file and fds file are attached

Original issue reported on code.google.com by luca.piantelli on 2010-09-13 06:54:22

---

• Attachment: test.txt
• _Attachment: pool_fire_1.fds_

[gforney]

changed the way I defined the mesh but things got worse
Now there are still 8 meshes but each mesh is high 10 m.
I attached files and details

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

Z:\>cd Z:\Simulazioni_FDS\pool_fire_1

Z:\Simulazioni_FDS\pool_fire_1>fds2ascii_win_64
  Enter Job ID string (CHID):
pool_fire_1
  What type of file to parse?
  PL3D file? Enter 1
  SLCF file? Enter 2
  BNDF file? Enter 3
3
  Enter Sampling Factor for Data?
  (1 for all data, 2 for every other point, etc.)
1
  Domain selection:
    y - domain size is limited
    n - domain size is not limited
    z - domain size is not limited and z levels are offset
    ya, na or za - slice files are selected based on type and location.
        The y, n, z prefix are defined as before.
y
  Enter min/max x, y and z
0
0
10.9
10.9
0
10
  1   MESH  5,  RADIATIVE HEAT FLUX
  2   MESH  6,  RADIATIVE HEAT FLUX
  3   MESH  7,  RADIATIVE HEAT FLUX
  4   MESH  8,  RADIATIVE HEAT FLUX
  Enter starting and ending time for averaging (s)
0.1
0.5
  Enter orientation: (plus or minus 1, 2 or 3)
-2
  Enter number of variables
1
 Enter boundary file index for variable 1
1
 Enter output file name:
test_2.txt
  Writing to file...      test_1.txt

Z:\Simulazioni_FDS\pool_fire_1>

Original issue reported on code.google.com by luca.piantelli on 2010-09-13 14:02:32

---

• _Attachment: test_1.txt_

[gforney]

Have you considered using the new LINE output format in FDS? This allows you to specify
a line of points where you want to record either a gas or solid phase property. Then,
an output file produces a spatial profile plot. This might be easier than using fds2ascii.

Original issue reported on code.google.com by mcgratta on 2010-09-16 17:18:12

[gforney]

So is your suggestion the following?

&DEVC XB = 0.0, 10.9, 0.0, QUANTITY = 'RADIATIVE HEAT FLUX', ID = 'z=0'/
&DEVC XB = 0.0, 10.9, 6.0, QUANTITY = 'RADIATIVE HEAT FLUX', ID = 'z=6'/

Original issue reported on code.google.com by luca.piantelli on 2010-09-18 07:19:31

[gforney]

Ok, I tried with the following

&DEVC XB = 0.1, 10.9, 0.1, QUANTITY = 'RADIATIVE HEAT FLUX',IOR = -2, ID = 'z=1'/

and it works.

If you try with XB = 0.0, 10.9, 0.0 ..... with z from 0.0 to 10.0 with an increase
of 0.1, the error is the following

ERROR: Reposition DEVC No.   6. FDS cannot determine which boundary cell to assi
gn
ERROR: Reposition DEVC No.   1. FDS cannot determine which boundary cell to assi
gn

The critical point is at the boundary of two meshes.

If you are interested in the problem with fds2ascii_win_64 see issue 1200 for details.

Thank you.

Issue not solved but found an alternative way.

Original issue reported on code.google.com by luca.piantelli on 2010-09-18 07:57:07

[gforney]

Did you include the keyword POINTS on the DEVC line? And if so, are all the points on
the line attached to the surface?

Original issue reported on code.google.com by mcgratta on 2010-09-20 12:48:22

[gforney]

No, I didn't.

&OBST XB = -10.0, 10.0, 10.9, 11, 0.0, 10.0, SURF_ID = 'IRON_WALL'/

&DEVC XYZ = 0.1, 10.9, 2.0, QUANTITY = 'RADIATIVE HEAT FLUX',IOR = -2, ID = 'z= 2.0'/
&DEVC XYZ = 0.1, 10.9, 3.0, QUANTITY = 'RADIATIVE HEAT FLUX',IOR = -2, ID = 'z= 3.0'/

The .csv file seems to be correct.

Original issue reported on code.google.com by luca.piantelli on 2010-09-20 13:03:32

[gforney]

The keyword POINTS instructs FDS to create a separate file with a time-averaged profile
of the QUANTITY along a LINE whose coordinates can be given by XB. This is easier than
specifying a separate DEVC line for each point. The Users Guide contains more details.
Search on the word POINTS.

Original issue reported on code.google.com by mcgratta on 2010-09-20 13:30:09

[gforney]

Ok, thank you. I will have a look!

Original issue reported on code.google.com by luca.piantelli on 2010-09-20 14:50:44

[gforney]

(No text was entered with this change)

Original issue reported on code.google.com by mcgratta on 2010-10-27 17:22:08