how to skip sfire_model of wrf.exe in em_fire/hill

[fengggli]

Hi Jan,

Hope you are doing well!

Brief

I am currently prototyping a runtime framework to configure and deploy in-situ workflows and I have been playing with WRF-SFIRE model as a potential use case.

The resulting workflow is somehow similar to what I saw in the standalone fire model as described in https://wiki.openwfm.org/wiki/How_to_run_the_standalone_fire_model_in_WRF-SFIRE , and I also saw the similar instructions you provided in “B. fire.exe” section in https://github.com/openwfm/WRF-SFIRE/blob/3c960d725cfab7597bcfcdecb5bc55f70a7e640e/standalone/README.txt#L22-L32

I followed the above steps and the execution seem successful (using the em_fire/hill case). However, I do have some questions(related to performance comparison between the default coupled and standalone execution modes):

Questions

Q1. It seems to me that although sfire_model function is called by both the standalone fire.exe (in step 7), and also earlier at the coupled WRF-SFIRE (in step 5). Is the one in step 5 necessary?

• the standalone calls fire_model here: https://github.com/openwfm/WRF-SFIRE/blob/3c960d725cfab7597bcfcdecb5bc55f70a7e640e/standalone/fire_main.F#L265
• The coupled WRF-SFIRE calls fire_model here: https://github.com/openwfm/WRF-SFIRE/blob/3c960d725cfab7597bcfcdecb5bc55f70a7e640e/phys/module_fr_sfire_driver.F#L1112

Q2 If it's possible to skip the fire_model in the coupled WRF-SFIRE, how should I do that?

• I noticed there is "fmoist_only" field from the registry.fire, which might be used to skip the actual fire execution? https://github.com/openwfm/WRF-SFIRE/blob/3c960d725cfab7597bcfcdecb5bc55f70a7e640e/phys/module_fr_sfire_driver.F#L292
• I added fmoist_only = .true., to the &fire section of my namelist.input and rerun ideal.exe and wrf.exe, but it seems to have no effects on the coupled WRF-SFIRE, the sfire_model is still called and perhaps I am doing something wrong here?

Thanks! Feng

[fengggli]

I found the instructions in here https://wiki.openwfm.org/wiki/Fuel_moisture_model, and tried again today with (true, true,true,0) with those fields in the namelist.input. And it works as expected (fire model is skipped). Close this now. Thanks again for the documentation!

fmoist_run | fmoist_interp | fmoist_only | fire_fmc_read | Function -- | -- | -- | -- | -- .true. | .true. | .false. | 0 | Run the fuel moisture model, create the arrays fmc_gc and fmc_g, and use fmc_g in the fire model. .true. | .true. | .true. | 0 | Run the fuel moisture model and create the arrays fmc_gc and fmc_g in wrfout only, the fire model does not run. .true. | .false. | .true. | 0 | Run the fuel moisture model and create the array fmc_gc in wrfout only, the fire model does not run. .false. | .true. | .false. | 0 | Interpolate the fuel moisture fields fmc_gc from wrfinput to fmc_g and use it in the fire model. .false. | .false. | .false. | 0 | Run the fire model using the fuel moisture map fmc_g from wrfinput. .false. | .false. | .false. | 1 | Run the fire model using the same fuel moisture fmc_g=fuelmc_g everywhere, as given in namelist.fire.