Program stops at reading anthropogenic emission file when using ndown

[Xin Zhang]

Dear all,

I'm trying to run WRF-Chem with ndown for 3 domain simulation and have some problems.

Here're my steps:

1. run real.exe, prepare emissions, initial and boundary files for all 3 domains.

2. run for domain 1

3. change max_dom = 2, copy wrfinputd02 to wrfndi_d02 and run ndown.exe

4. mv wrfinput_d02 to wrfinput_d01, same for wrfbdy file

5. Copy anthropogenic emission files of domain 2 and rename them to wrfchemi_00z_d01 and wrfchemi_12z_d01

6. Follow the same steps above for biogenetic emissions.

7. run for domain 2 (actually domain 1 now)

It ran well for 7 hours (starting from 18 UTC 20190724).

But, the program stopped at 01:00 UTC 20190725 when reading the anthropogenic file.

Here's the end of rsl.error.0000:

d01 2019-07-25_01:00:00            2 input_wrf: wrf_get_next_time current_date: 2019-07-25_01:00:00 Status =            0
**WARNING** Time in input file not being checked **WARNING**
input_wrf.F reading 4d real E_CO
 date 2019-07-25_01:00:00
 ds            1           1           1
 de          150           1         150
 ps            1           1           1
 pe           15           1           7
 ms           -4           1          -4
 me           22           1          14
d01 2019-07-25_01:00:00 module_io.F: in wrf_read_field

Although the job log reminded me that there's error in rsl.error.0344, I suppose this is caused by the part of reading anthropogenic file.

Because if I turn auxinput_5 off, the program will work well ...

Anyway, here's the end of rsl.error.0344:

d01 2019-07-25_00:59:50 calling photolysis driver
 photolysis_driver: called for domain            1
d01 2019-07-25_00:59:50 calling ftuv_driver
d01 2019-07-25_00:59:50 no aerosols initialization yet
no aerosols initialization yet
forrtl: severe (174): SIGSEGV, segmentation fault occurred

If anyone has experience of running WRF-Chem with ndown, could you help me with this problem?

Thanks,

Xin

[Xin Zhang]

Another question of ndown:

Is turning feedback off as same as using ndown?

If so, maybe I can try "feedback = 0, 0, 0" instead of ndown which needs multiple steps.

[Xin Zhang]

Update:

Using "feedback = 0" gets the same error, but a little later (2019-07-25_01:14:50) than using ndown (2019-07-25_00:59:50).

If I start the ndown running from 2019-07-25_00:00:00 instead of  2019-07-24_18:00:00,

the issue happens at 2019-07-25_02:15:00 ...

[Xin Zhang]

Update 2:

I tried the same namelist and emission files with WRF-Chem V3.7.1 instead of WRF-Chem V4.1.4, it works well.

And, if I turned off the input of anthropogenic emission in WRF-Chem V4.1.4, it also works well.

So, I suppose some differences lead to the failure which is related to reading the anthropogenic emissions.