Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

wrf.exe error with option ifire=2

rut_sevilla

New member
Hello, I followed the steps of this tutorial for running WRF_Fire with real data: How to run WRF-Fire with real data - openwfm . When I run ./wrf.exe with the option ifire=1, the 'fire' variables do not appear in the results. However, when I run it with ifire=2, I get the following error:
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
with errorcode 1.

NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on exactly when Open MPI kills them.
--------------------------------------------------------------------------
I tried running it with 8, 4, 2, and 1 CPU, and in all attempts, it crashed.

namelist.input, rsl.error.0000 and rsl.out.0000 are attached.

If you have any idea, please let me know.
Thank you.

Rut
 

Attachments

  • rsl.error.0000
    7.4 KB · Views: 0
  • rsl.out.0000
    6.3 KB · Views: 0
  • namelist.input
    5.7 KB · Views: 3
Rut,
I am sorry that we don't support real-time WRF-FIRE system. WRF-FIRE has been evolved separately from WRF-ARW since 2010.
Hope someone in the community may have information regarding the issue you have.
 
Hi @rut_sevilla
If you want to try ifire=1, I suggest you compile the latest version (W4.4-S0.1) of WRF-SFIRE, which you can find here.
Feel free to open a bug issue on GitHub if you continue to have the same troubles.
 
Top