Initial commit of NEMO NEI 2019

[drnimbusrain]

@bbakernoaa For the NEMO NEI2019 here, I assume this is what you meant by adding new config? I updated to NEI2109 based on the [develop] branch cmaq_gfs_megan config. Also not sure if we are targeting this NEI2019 update to the [develop] or [production/AQMv7] branch.

Also required changes to NEXUS utils such as the linker script, maybe @zmoon can help here, and then changes to workflow to do a test run.

[drnimbusrain]

Thanks @bbakernoaa

@zmoon can you help update the NEXUS utils/python linker scripts to this PR to accommodate these updates to use the NEMO/NEI2019 emissions. You can see examples of their emission files for correct linking on Hera at: /scratch1/RDARCH/rda-arl-gpu/Barry.Baker/emissions/nexus/NEMO/NEI2019/v2023-03/$mm Instead of daily files, these merged 2D files are provided as four representative days (two weekdays and two weekend days) per month and could be linked accordingly for the NEXUS/HEMCO simulation date. Thanks!

[zmoon]

Thanks @drnimbusrain , did you want me to do it in this branch?

[drnimbusrain]

Yes please

…

On Fri, Sep 6, 2024, 12:04 PM Zachary Moon ***@***.***> wrote: Thanks @drnimbusrain <https://github.com/drnimbusrain> , did you want me to do it in this branch? — Reply to this email directly, view it on GitHub <#54 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGLFYNXSQKGGQLEWHNQ4MG3ZVHHARAVCNFSM6AAAAABNM2FANWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZUGM3TKOJUGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[drnimbusrain]

Thanks @drnimbusrain , did you want me to do it in this branch?

@zmoon

[zmoon]

@drnimbusrain here's a little example of what I've currently got set up:

> mkdir tmp
> ./nexus_nei2019_linker.py -s /scratch1/RDARCH/rda-arl-gpu/Barry.Baker/emissions/nexus/ -w ./tmp --no_read_hemco_time -d 2023-09-27
file map size: 84
src dir: /scratch1/RDARCH/rda-arl-gpu/Barry.Baker/emissions/nexus
work dir: ./tmp
date: 2023-09-27, month: 9, isoweekday: 3
linking /scratch1/RDARCH/rda-arl-gpu/Barry.Baker/emissions/nexus/NEMO/NEI2019/v2023-03/09/NEI2019v1_0.1_degree_20190910_all.nc to ./tmp/NEMO/NEI2019/v2023-03/09/NEI2019v1_0.1_degree_20230927_all.nc

But besides adding this ability to test single dates, the CLI should be the same and you should be able to just swap for this new Python script in the workflow nexus emission Bash script.

[drnimbusrain]

@drnimbusrain here's a little example of what I've currently got set up:

> mkdir tmp
> ./nexus_nei2019_linker.py -s /scratch1/RDARCH/rda-arl-gpu/Barry.Baker/emissions/nexus/ -w ./tmp --no_read_hemco_time -d 2023-09-27
file map size: 84
src dir: /scratch1/RDARCH/rda-arl-gpu/Barry.Baker/emissions/nexus
work dir: ./tmp
date: 2023-09-27, month: 9, isoweekday: 3
linking /scratch1/RDARCH/rda-arl-gpu/Barry.Baker/emissions/nexus/NEMO/NEI2019/v2023-03/09/NEI2019v1_0.1_degree_20190910_all.nc to ./tmp/NEMO/NEI2019/v2023-03/09/NEI2019v1_0.1_degree_20230927_all.nc

But besides adding this ability to test single dates, the CLI should be the same and you should be able to just swap for this new Python script in the workflow nexus emission Bash script.

Ok, thank you Zach, let me test it with swapping the workflow's exaqm_nexus_emission.sh script to use this new python linker script. Ill make the necessary changes to the following places:

1. https://github.com/ufs-community/ufs-srweather-app/blob/aqm_dev/scripts/exaqm_nexus_emission.sh#L214
2. https://github.com/ufs-community/ufs-srweather-app/blob/aqm_dev/scripts/exaqm_nexus_emission.sh#L260-L277

For changes in 2 above, I assume there is not a new "nexus_nei2016_control_tilefix.py" script, and we still use this one, correct?

Thanks again!

[zmoon]

not a new "nexus_nei2016_control_tilefix.py" script

May need to, let's see. It seems all it does is replace 2016$MM$DD with the target year. So for 2019 I suppose we would need to do the same, to replace the 2019 in 2019$MM$DD.

ROOT/NEMO/NEI2019/v2023-03/$MM/NEI2019v1_0.1_degree_2019$MM$DD_all.nc  

But could that line not be written like

ROOT/NEMO/NEI2019/v2023-03/$MM/NEI2019v1_0.1_degree_$YYYY$MM$DD_all.nc  

instead? Then the script to modify the NEXUS config shouldn't be needed?

@drnimbusrain : Yes, I it seems better that way, but for now will just add new one in case there is something else, maybe Barry can comment.

[drnimbusrain]

Actually best way is to remove the year specific entirely and have the config be agnostic to this (as we do for some other global inventories), and use the configs as just "NEI" not NEI2016, NEI2019 etc. We should do this in the future.

[drnimbusrain]

Actually best way is to remove the year specific entirely and have the config be agnostic to this (as we do for some other global inventories), and use the configs as just "NEI" not NEI2016, NEI2019 etc. We should do this in the future.

Well, not really sure about this either. I think we would want to maintain easy ways of testing any available inventory with simple switches, e.g., keeping both capabilities for NEI2016 vs. NEI2019, and going forward.

[drnimbusrain]

@zmoon getting the following error for a August 01-07, 2023 test on Hera:

All executables will be submitted with command \'srun -n 80 --export=ALL\'.
2023-08-01 12:00:00 2023-08-01 17:00:00
2023-08-01 12:00:00
file map size: 36
src dir: /scratch2/NCEPDEV/naqfc/RRFS_CMAQ/emissions/nexus
work dir: /scratch1/NCEPDEV/stmp4/Patrick.C.Campbell/expt_dirs/aqmna13_gfs_v16_test_aqm_dev_cmaq54_nei2019/tmp/nexus_emission_00.414949/input
date: 2023-08-01, month: 8, isoweekday: 2
error: no file found for month 8, iwd 2
FATAL ERROR:
ERROR:

[drnimbusrain]

Ah, hang on, I think I have another error in the workflow script with the incorrect version (-v) when running the linker script.

[drnimbusrain]

@zmoon @bbakernoaa The NEMO NEI2019 have been tested (against current NEI2016v1) in AQMv8 for August 01-07,2023:

Ozone Spatial Differences:

Ozone Scorecards

PM2.5 Spatial Differences

PM2.5 Scorecards

[drnimbusrain]

Full evaluations of NEMO NEI2019 emissions updates on AQMv8 shown here: https://drive.google.com/drive/folders/1Dxl46SCrBNX_INiFiM-aU3K_IzJYy6wL

[drnimbusrain]

@bbakernoaa @zmoon After the tests the NEI2019 results here seem reasonable, with some definitive improvements in ozone.

If good, can we merge into develop now, as I would like to open a new branch/PR for next global update config on top of the updated NEI for our testing? I do have UFS-SRW-App workflow updates, but those PRs will need to wait and find the correct branch from fluid situation at EMC with workflows.

[drnimbusrain]

@bbakernoaa Thanks! @zmoon Good to merge?