[FEATURE REQUEST] Overhaul HEMCO_Config.rc file

[msulprizio]

We would like to overhaul the HEMCO_Config.rc file to make it easier to understand and modify. This Feature Request will track progress on that work and list some of our wishlist items.

• [ ] Convert HEMCO_Config.rc to YML
• [ ] Split HEMCO_Config.rc into two files - one with switches and settings; one with file paths, timestamps, variables, etc. (similar to GCHP's ExtData.rc)
• [ ] Rethink use of units entry in HEMCO_Config.rc. For example, should we remove completely and assume all input fluxes are in kg species/m2/s and provide warning or crash when units in the netCDF file differ?
• [ ] Rethink time cycle flags
• [ ] Separate emissions and non-emissions data entries

[jimmielin]

Hi Melissa,

Thanks for opening this discussion! I also wanted to chime in regarding a possible feature to consider when overhauling HEMCO_Config.rc. The HEMCO grid feature introduced in 13.1.0 is currently facing some performance issues, as the meteorological fields are (unnecessarily) regraded to the finer grid and back to the model grid.

The solution to this is to include a flag for HEMCO to know which kind of data is non-emissions and does not need to be masked/scaled on a finer HEMCO grid. Perhaps a custom flag could be provided as part of the HEMCO configuration file as some kind of metadata? For example, E for “emissions”, M for “meteorology”, D for other input data, etc. This way, HEMCO can recognize data that doesn’t need to be regridded back-and-forth. We might actually use two HEMCO instances for this, because HEMCO internally requires all data to have the same X, Y, Z dimensions.

Any thoughts or suggestions are welcome!

[yantosca]

Also see related issue #79

[stale[bot]]

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.