Large total optical depth warnings in running WRF-Chem while using RADM2-MADE/SORGAM chemistry option (chem_opt=11)

[Ankan]

Dear all,
I am running WRF-Chem (version 3.9.1.1) using RADM2-MADE/SORGAM, including aqueous reactions (chem_opt=11). I have successfully prepared anthropogenic emission input data from the EDGAR v5 MOZART dataset using anthro_emis, biogenic emission input data from the MEGAN dataset using megan_bio_emis and fire emission input data from the FINN v1.5 dataset using fire_emis and included chemical initial and lateral boundary condition files to the wrfinput and wrfbdy files from the MOZART4-GEOS5 dataset using mozbc utilities provided by NCAR. Note that all of the emission files are mapped as per RADM2-MADE/SORGAM. However, when I ran wrf.exe, I got large total optical depth warnings at 16 hours and 40 minutes, and after that, these warnings were repeated every twenty minutes. I suspect these are coming every 20 minutes, maybe because I set 'radt=20'. I tried several sensitivity test simulations to find out the root cause of the warnings. For instance, when I gave a run by setting only 'biomass_burn_opt = 0' with other options on, the result is the same. When I set 'biomass_burn_opt', 'bio_emiss_opt' and 'emiss_opt' to '0', though the warnings came a little bit later at 18:00:00, but the result is the same. That makes me think that there should be no issue with emission input files.
In all the above mentioned cases, I ran wrf.exe by setting dust_opt = 3, and I noticed that the range of TOT_DUST is quite absurd: 0 to 6.15E-16. Is it wrong then?
However, when I set dust_opt=0, the warnings only came for the first day of simulation at 15:40:00 and then similar kinds of warnings started coming at 02:00:00 on the next day.
The warning that came at 15:40:00 is as follows:
Timing for main: time 2015-12-25_15:40:00 on domain 1: 12.39783 elapsed seconds
-------------------------
WARNING: Large total optical depth of 5.16 at point i,j,ib= 18 13 1
Diagnostics 1: k, tauaer300, tauaer400, tauaer600, tauaer999
1 0.03 0.02 0.01 0.00
2 0.04 0.02 0.01 0.00
3 0.05 0.03 0.01 0.00
4 0.06 0.04 0.02 0.00
5 0.14 0.09 0.04 0.01
6 0.82 0.59 0.32 0.11
7 0.92 0.66 0.35 0.13
8 0.03 0.02 0.01 0.00
9 0.01 0.01 0.01 0.01
10 0.02 0.02 0.02 0.01
11 0.02 0.02 0.02 0.01
12 0.02 0.02 0.01 0.01
13 0.01 0.01 0.01 0.01
14 0.01 0.01 0.01 0.01
15 0.01 0.01 0.01 0.01
16 0.01 0.01 0.01 0.01
17 0.01 0.01 0.01 0.01
18 0.02 0.02 0.01 0.01
19 0.01 0.01 0.01 0.01
20 0.01 0.01 0.01 0.00
21 0.01 0.01 0.01 0.00
22 0.00 0.00 0.00 0.00
23 0.00 0.00 0.00 0.00
24 0.00 0.00 0.00 0.00
25 0.00 0.00 0.00 0.00
26 0.00 0.00 0.00 0.00
27 0.00 0.00 0.00 0.00
28 0.00 0.00 0.00 0.00
29 0.00 0.00 0.00 0.00
30 0.00 0.00 0.00 0.00
31 0.00 0.00 0.00 0.00
32 0.00 0.00 0.00 0.00
33 0.00 0.00 0.00 0.00
34 0.00 0.00 0.00 0.00

I also tried, dust_opt=1, and this time the simulation stopped without throwing any errors in the rsl files. In the wrfrun.log file, the following line is printed:
===================================================================================
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
= PID 80121 RUNNING AT durga
= EXIT CODE: 11
= CLEANING UP REMAINING PROCESSES
= YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================================================
Intel(R) MPI Library troubleshooting guide:
Documentation Library
===================================================================================

So, is something going wrong with dust aerosols? Is there any particular dust_opt suitable for chem_opt=11?
Also, when I set the three options - seas_opt, dmsemis_opt and dust_opt to '0', the simulations didn't work out.
However, when I didn't include initial and boundary conditions from mozbc, the simulation stopped after twenty minutes. So, is there any issue with the mozbc.input file?
I am really clueless. So, any help on this will be highly appreciated. I am attaching my namelist.input file (run by setting dust_opt=0) for your convenience. Please take a look at it and let me know if there are any mistakes in the settings. I am really looking forward to hearing from you.
Thank you for your time and consideration.
With regards,
Ankan

 

[Ankan]

Hello everyone,
Update:
I set dust_opt = 4, and dust_schme = 3 and gave 12 days of WRF-Chem run for the parent domain. The simulation had now been completed successfully. The thing is, though the run was completed successfully, only on some days warnings related to large total optical depths are coming, but not on all days. And are these warnings hampering my result? Or can it be ignored?

Also, when I gave a run for nested domain using ndown, I noticed that the large total optical depth warnings started coming at 01:40:00 on the first day for every 20 minutes since then. Because of this, the size of the rsl files are so large (simulation is going on for the second day out of 12 days, and the size of the most of the rsl.error.00* file is in GB) and probably this causes the space of /home/ directory to be used by 86% from 37% though simulation is stll remaining for the rest of the 10 days. So, I suspect the simulation of 12 days for the nested domain may not be completed due to the lack of space in the future. Therefore, is there any solution to this? Can anyone please guide me in this regard? That will be really helpful. Thank you for your time.
With regards,
Ankan

 

[Ankan]

Hello everyone,
Update:
The large optical depth warnings (mentioned in the last message) came for the first three days. Then the warnings stopped coming. But, again, on the 8th day out of 12 day of the simulation, similar warnings started coming. One important note is that since the rsl files were too large, I had to delete some of them to clear space in the /home/ directory. I don't know if the process is correct or not. I wonder if these warnings can hamper my result. Can anyone please guide me? That will be very helpful for me. Thank you in advance.
With regards,
Ankan