Naser
Member
Hello,
I am trying to update my WRF-Chem version from 3.9.1 to 4.6.0. I am using the same namelist settings. My met_em files were created with WPS 4.6.0.
For emissions:
Timing for Writing wrfout_d01_2024-02-10_00:00:00 for domain 1: 2.97221 elapsed seconds
d01 2024-02-10_00:00:00 CALL med_read_wrf_chem_emiss
mediation_integrate: med_read_wrf_chem_emissions: Open file wrfchemi_00z_d01
HOURLY EMISSIONS UPDATE TIME 0.0 0.0
mediation_integrate: med_read_wrf_chem_emissions: Read emissions for time 2024-02-10_00:00:00
d01 2024-02-10_00:00:00 NetCDF error: NetCDF: Attribute not found
d01 2024-02-10_00:00:00 NetCDF error in ext_ncd_get_dom_ti.code CHAR, line 83 Element TITLE
d01 2024-02-10_00:00:00 Error trying to read metadata
d01 2024-02-10_00:00:00 File name that is causing troubles = wrfchemi_00z_d01
d01 2024-02-10_00:00:00 You can try 1) ensure that the input file was created with WRF v4 pre-processors, or
d01 2024-02-10_00:00:00 2) use force_use_old_data=T in the time_control record of the namelist.input file
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 342
---- ERROR: The input file appears to be from a pre-v4 version of WRF initialization routines
-------------------------------------------
When I use force_use_old_data=T, the model runs successfully, but the rsl output increases in size and has too much below:
Warning: refi is larger than lookup table range and reset to maximum bound at SW band 1
Warning: refi is larger than lookup table range and reset to maximum bound at SW band 2
The output is also strange; for example, PM10 is less than 1 μg/m³ in the entire domain.
Could you please advise on why this is happening and how to resolve the issue?
Thank you,
Naser
I am trying to update my WRF-Chem version from 3.9.1 to 4.6.0. I am using the same namelist settings. My met_em files were created with WPS 4.6.0.
For emissions:
- Biogenic emissions were generated using bio_emiss to produce the wrfbiochemi files.
- Anthropogenic emissions are user-generated with a 12-hour interval format (wrfchemi_00z_d01, wrfchemi_12z_d01, wrfchemi_00z_d02, wrfchemi_12z_d02).
- real.exe completes successfully, but the wrfinput file differs from what I get in WRF-Chem 3.9.1.
- When running WRF-Chem 4.6.0, the model stops after creating d01 for 00, and it does not proceed to d02 or other forecast hours. Instead, it shows the following error:
Timing for Writing wrfout_d01_2024-02-10_00:00:00 for domain 1: 2.97221 elapsed seconds
d01 2024-02-10_00:00:00 CALL med_read_wrf_chem_emiss
mediation_integrate: med_read_wrf_chem_emissions: Open file wrfchemi_00z_d01
HOURLY EMISSIONS UPDATE TIME 0.0 0.0
mediation_integrate: med_read_wrf_chem_emissions: Read emissions for time 2024-02-10_00:00:00
d01 2024-02-10_00:00:00 NetCDF error: NetCDF: Attribute not found
d01 2024-02-10_00:00:00 NetCDF error in ext_ncd_get_dom_ti.code CHAR, line 83 Element TITLE
d01 2024-02-10_00:00:00 Error trying to read metadata
d01 2024-02-10_00:00:00 File name that is causing troubles = wrfchemi_00z_d01
d01 2024-02-10_00:00:00 You can try 1) ensure that the input file was created with WRF v4 pre-processors, or
d01 2024-02-10_00:00:00 2) use force_use_old_data=T in the time_control record of the namelist.input file
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 342
---- ERROR: The input file appears to be from a pre-v4 version of WRF initialization routines
-------------------------------------------
When I use force_use_old_data=T, the model runs successfully, but the rsl output increases in size and has too much below:
Warning: refi is larger than lookup table range and reset to maximum bound at SW band 1
Warning: refi is larger than lookup table range and reset to maximum bound at SW band 2
The output is also strange; for example, PM10 is less than 1 μg/m³ in the entire domain.
Could you please advise on why this is happening and how to resolve the issue?
Thank you,
Naser