Open msulprizio opened 3 years ago
Will HEMCO standalone then need a wrapper too?
Perhaps. We can also think about making it a submodule in HEMCO standalone and/or having a compile time switch to tell HEMCO when to compile NcdfUtil.
Okay, we can also think through the implications for other projects using HEMCO and how a new dependency will fit into their design (GEOS, CESM, NOAA models).
But perhaps none of them use NcdfUtil so we could start by blocking it off with MODEL_CLASSIC as a test.
I can try to separate out NcdfUtil for 13.1.0. Also I can add the Cmake build sequence.
I have removed the 13.1.0 milestone for now. This item can go in when it is ready, but may not necessarily be a top priority.
This would require a bit of work in order to handle potential namespace confusion. Leave it for later.
NcdfUtil is used by both GEOS-Chem and HEMCO. Instead of being embedded in both code repositories and having duplicate code, we should remove NcdfUtil from https://github.com/geoschem/geos-chem and https://github.com/geoschem/hemco and add as a Git submodule in https://github.com/geoschem/geos-chem-classic.
NcdfUtil is already a separate Github repository (https://github.com/geoschem/ncdfutil) and is up-to-date with the code currently in both GEOS-Chem and HEMCO as of today (29 Sep 2020).