WRF-Fire crashes at start when adding nested domains (d02+d03). d01-only runs, but first ignition doesn’t start.

[Jesufemi Olowe]

Hello everyone,
I’m running a WRF-Fire simulation and I’m stuck with two related issues:

1) Model crashes when I include nested domains (d02 and d03)​

• d01-only: runs successfully.
• d01 + d02 + d03: crashes very early (near the beginning of the run).

Domain setup:

• d02 and d03 are both nested inside d01 (they are separate child domains, not one inside the other).
• (I will attach my namelist.input)

MPI / decomposition:

• For d01-only, I typically use a decomposition like nproc_x=8, nproc_y=6 (48 ranks) and it runs.
• For d01+d02+d03, I have tried 48, 64, and 128 MPI ranks but it still crashes at the beginning.
• The crash happens regardless of the rank count I tried.

I have attached:

• the rsl.error.* and rsl.out.* from the most recent failing run (128 ranks),
• the full namelist.input

2) In d01-only runs, first fire does not ignite but second fire burns​

In the d01-only case (which runs), I have two ignitions configured:

• Ignition 1 should start at ~6.5 hours, but it never ignites.
• Ignition 2 start 14.3 hrs but ignites and burns as expected.

So I’m wondering:

• Could there be an issue with the ignition timing (start time / run time / conversion), ignition coordinates, or ignition line definition?

Questions​

1. What are the most common reasons WRF-Fire runs fine on d01-only but crashes immediately when adding nested domains?
2. Are there recommended checks for nest configuration (parent/child ratios, i/j start locations, time step ratios, feedback settings, etc.) specific to WRF-Fire?
3. For the ignition problem: what are the typical reasons an ignition scheduled at 6.5 hours never starts, while another ignition does?

Thanks a lot for any help—happy to provide any additional diagnostics.