firemodels / fds

Fire Dynamics Simulator
https://pages.nist.gov/fds-smv/
Other
668 stars 625 forks source link

FDS levelset, fire not crossing mesh #13479

Open 3dfirelab opened 1 month ago

3dfirelab commented 1 month ago

using FDS-6.9.1-825-g48a6b66-master and the config below, my fire is not crossing the mesh where the ignition takes place. image

my config :

Desired resolution: 10.0m
DEM layer: elevation
Landuse layer: fuelmap
Landuse type file: ...pontdeVilomara/practical4/2-qgis2fds/Landfire.gov_F13.csv
Fire layer: ignitionLine_canyon
FDS DEVCs layer: FIXME
Wind file: ...da/FDS/LS-elpontdeVilomara/practical4/2-qgis2fds/wind.csv

&HEAD CHID='pdV' TITLE='Description of input_pdV' /

MISC LEVEL_SET_MODE parameter
 1: Wind not affected by the terrain. No fire.
 2: Wind field established over the terrain, then frozen. No fire.
 3: Wind field following the terrain, no fire.
 4: Wind and fire fully-coupled.

&MISC ORIGIN_LAT=41.7123801
      ORIGIN_LON=1.8945025
      NORTH_BEARING=0.
      TERRAIN_IMAGE='input_pdV_tex.png'
      LEVEL_SET_MODE=1 
      THICKEN_OBSTRUCTIONS=T /

&TIME T_END=3600. /

Example REAC, used when LEVEL_SET_MODE=4
_REAC ID='Wood' SOOT_YIELD=0.005 O=2.5 C=3.4 H=6.2
      HEAT_OF_COMBUSTION=17700. /

Domain and its boundary conditions
5 · 8 meshes of 346.6m · 278.3m · 331.8m size and 30294 cells each
&MULT ID='Meshes'
      DX=346.59 I_LOWER=0 I_UPPER=4
      DY=278.26 J_LOWER=0 J_UPPER=7 /
&MESH IJK=34,27,33 MULT_ID='Meshes'
      XB=-866.59,-520.01,-1113.01,-834.76,211.57,543.35 /
&VENT ID='Domain BC XMIN' DB='XMIN' SURF_ID='OPEN' /
&VENT ID='Domain BC XMAX' DB='XMAX' SURF_ID='OPEN' /
&VENT ID='Domain BC YMIN' DB='YMIN' SURF_ID='OPEN' /
&VENT ID='Domain BC YMAX' DB='YMAX' SURF_ID='OPEN' /
&VENT ID='Domain BC ZMAX' DB='ZMAX' SURF_ID='OPEN' /

Wind rose at domain origin
&DEVC ID='Origin_UV' XYZ=0.,0.,543.25 QUANTITY='U-VELOCITY' /
&DEVC ID='Origin_VV' XYZ=0.,0.,543.25 QUANTITY='V-VELOCITY' /
&DEVC ID='Origin_WV' XYZ=0.,0.,543.25 QUANTITY='W-VELOCITY' /

Terrain (38802 OBSTs)
&OBST XB=-867.59,-857.62,1104.04,1114.03,211.57,237.18 SURF_ID='A02' /
&OBST XB=-857.62,-847.65,1104.04,1114.03,211.57,237.18 SURF_ID='A02' /
&OBST XB=-847.65,-837.68,1104.04,1114.03,211.57,237.18 SURF_ID='A02' /
&OBST XB=-837.68,-827.71,1104.04,1114.03,211.57,237.27 SURF_ID='A02' /
&OBST XB=-827.71,-817.74,1104.04,1114.03,211.57,236.93 SURF_ID='A02' /
&OBST XB=-817.74,-807.77,1104.04,1114.03,211.57,236.43 SURF_ID='A02' /
&OBST XB=-807.77,-797.80,1104.04,1114.03,211.57,235.93 SURF_ID='A02' /

## FULL LIST OF OBST REMOVE -- TOO LONG 
## let me know the best way to share long config file.

&TAIL /
marcosvanella commented 1 month ago

Please add a .txt extension to your input file and attach it in the thread.

3dfirelab commented 1 month ago

here it is input_pdV.fds.txt

and it this can be useful, I run it using

#source /opt/intel/oneapi/setvars.sh
cd $SLURM_SUBMIT_DIR
export OMP_NUM_THREADS=1
time mpirun -n $SLURM_NTASKS /opt/FDS/Build/fds_impi_intel_linux input_pdV.fds
marcosvanella commented 1 month ago

I'll run the case with latest source here.

marcosvanella commented 1 month ago

The issue is related to having non exact match of the deltas used in the mesh MULT line and the specified mesh size. Replace your MULT and MESH lines by:

&MULT ID='Meshes' DX=346.59 I_LOWER=0 I_UPPER=4 DY=278.26 J_LOWER=0 J_UPPER=7 / &MESH IJK=34,27,33 MULT_ID='Meshes' XB=-866.59,-520.00,-1113.01,-834.75,211.57,543.35 /

And run your case again. I will post an issue with the qgis2fds developers to make sure DX, DY in mult match exactly the XB sizes in meshes.

3dfirelab commented 1 month ago

thanks a lot for the super quick answer it worked on my side too.

johodges commented 1 month ago

Could you upload your qgis project file? I'll take a look and see what is going on.