Hi all, I am having a strange problem while running REAL.EXE for my WRF-Chem run. REAL.EXE generates the expected wrfbdy_d01 file but it contains only chemical boundary species; it does not contain meteorological boundary species (e.g., U_BXS, V_BXS etc.). There is no error or warnings and REAL.EXE runs sucessfully. WRF.EXE runs fine even without the meteorological boundary species. However, I noticed a weired boundary artifact on wind fields which was explainable by the absence of meteorological boundary species in wrfbdy_d01.
When I run a clean WRF-only setting (without &chem), REAL.EXE generates meteorological boundary species normally in the wrfbdy_d01 file. I have found a workaround to this issue by first running the REAL.EXE with wrf-only setting and then merging the chemical boundary species from the chem-enabled REAL.exe. However, I want to know what is causing this and make sure it is not causing any further unidentified issues.
I am using WRFChem v4.7.1 with chem_opt 203 and emiss_opt = 13 but this behaviour persists with other chem options.
Thank you for looking into this problem. I am attaching my namelist file.
Sagar
When I run a clean WRF-only setting (without &chem), REAL.EXE generates meteorological boundary species normally in the wrfbdy_d01 file. I have found a workaround to this issue by first running the REAL.EXE with wrf-only setting and then merging the chemical boundary species from the chem-enabled REAL.exe. However, I want to know what is causing this and make sure it is not causing any further unidentified issues.
I am using WRFChem v4.7.1 with chem_opt 203 and emiss_opt = 13 but this behaviour persists with other chem options.
Thank you for looking into this problem. I am attaching my namelist file.
Sagar