geoschem / HEMCO

The Harmonized Emissions Component (HEMCO), developed by the GEOS-Chem Support Team.
https://hemco.readthedocs.io
Other
17 stars 33 forks source link

Change the Scale of soil NOx emission for a given mask #152

Closed Wangxxxxxuan closed 2 years ago

Wangxxxxxuan commented 2 years ago

Hello, I know HEMCO has very powerful features. But as a beginner, I found it difficult to try to change HEMCO. Recently, I want to change NOx emissions from soils on the Tibetan Plateau. And get inspiration from The HEMCO User's Guide (http://wiki.seas.harvard.edu/geos-chem/index.php/The_HEMCO_User%27s_Guide#Scale_factors) and HEMCO examples (http://wiki.seas.harvard.edu/geos-chem/index.php/HEMCO_examples#:~:text=As%20of%20HEMCO%20v1.1.006%2C%20the%20emission%20date%20can,hour%20can%20be%20set%20in%20the%20same%20manner) .So I added four lines of command to the original HEMCO.

SoilNOx : on NO --> Use fertilizer NOx : true --> ScaleField_NO : SOILNOX_SCALE

104 SOILNOX_ARID $ROOT/SOILNOX/v2014-07/soilNOx.climate.generic.05x05.nc ARID 2000/1/1/0 C xy unitless NO - 1 1 104 SOILNOX_NONARID $ROOT/SOILNOX/v2014-07/soilNOx.climate.generic.05x05.nc NON_ARID 2000/1/1/0 C xy unitless NO - 1 1 *104 SOILNOX_SCALE 1.0 - 2000/1/1/0 C xy unitless 333 1 1**

333 SOILNOX_SCALE 0.0/0.0/0.0/0.0/0.0/0.0/0.0/0.0/0.0/0.0/0.0/0.0 - 2000/1-12/1/0 - xy 1 1 5000

5000 SOILNOX_MASK 75/24/105/40 - 2000/1/1/0 xy 1 1 75/24/105/40

Now I have two questions. The first problem is that my Geos-Chem will report an error after the change. "Reading fields of HEMCO configuration file: HEMCO_Config.rc

HEMCO ERROR: Closing bracket does not match opening bracket: EMISSIONS, expected: SoilNOx --> LOCATION: BracketCheck (hco_config_mod.F90)"

The next question is that the difference between "OFFLINE_SOILNOX: true # 1980-2021" and "SoilNOx: on NO". Do I need to change the "OFFLINE_SOILNOX“?

Thank you very much. Best regards, Wang

msulprizio commented 2 years ago

Hi @Wangxxxxxuan. Could you please attach copies of the following files here so we can better assist you:

Note: You will need to change their extensions to .txt for Github to allow the attachments.

Wangxxxxxuan commented 2 years ago

Hi @Wangxxxxxuan. Could you please attach copies of the following files here so we can better assist you:

  • HEMCO_Config.rc
  • HEMCO.log
  • hcox_soilnox_mod.F90 (if modified)

Note: You will need to change their extensions to .txt for Github to allow the attachments.

HEMCO.txt HEMCO_Config.txt

Hi, msulprizio: I am very sorry for the late reply. I tried a few more changes after yesterday's question but failed, so I changed the command to the above description and ran again. In addition, I have changed the extensions of HEMCO_Config.rc and HEMCO.log to HEMCO_Config.txt and HEMCO.txt. I don't think I've changed hcox_soilnox_mod.F90 so it's not uploaded. Looking forward to your suggestions.

Wangxxxxxuan commented 2 years ago

After dozens of errors I have solved the problem. During running boundary condition, the longitude and latitude of MASK were integral multiples of 5 and 4 respectively.

My code is as follows. --Country/region masks-- 1011 SOIL_MASK 75/24/105/40 - 2000/1/1/0 C xy 1 1 75/24/105/40 END SECTION MASKS

After that, make a connection between MASK and SCALE. --- Day-of-week scale factors --- 333 SOIL_SCALE 0/0/0/0/0/0/0 - - - xy unitless 1 1011

Finally, link SCALE to the source's MASKID. --- Offline soil NOx emissions --- (((OFFLINE_SOILNOX (((.not.SoilNOx 0 SOILNOX_NO $ROOT/OFFLINE_SOILNOX/v2019-01/0.5x0.625/$YYYY/$MM/soilnox_05.$YYYY$MM$DD.nc SOIL_NOx 1980-2021/1-12/1-31/* C xy kg/m2/s NO 333 3 2 ))).not.SoilNOx )))OFFLINE_SOILNOX

I don't know if the above steps are correct. But after running ./gcclassic, the program works.

Thank you again for your help.

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. If there are no updates within 7 days it will be closed. You can add the "never stale" tag to prevent the Stale bot from closing this issue.

yantosca commented 2 years ago

Thanks for your feedback @Wangxxxxxuan. Your steps do indeed look correct. I'll close out the issue.