You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Soon ESMA_env will move to use Baselibs 7.18.1 whose main change is moving from HDF5 1.10 to 1.14. GEOSgcm seems pretty agnostic to this as any HDF5 work is done through netCDF (solely I think).
The "CONUS" and "GLOBAL" tests passed for both Intel and GNU. The GLOBAL/assim case is akin to running GEOSldas.x within the SMAP L4_SM system and exercises the reading of h5 files.
The SMAP L4 ops system has additional uses of hdf (e.g., creating the h5 product files for L4_SM and L4_C), although I'm not sure if @jardizzo uses ESMA_env to build the other components of the SMAP L4_SM system (other than GEOSldas). I'll inquire.
@gmao-rreichle Well, glad to hear GEOSldas can at least consume HDF5 just fine. My guess is if SMAP L4 does use Baselibs, they probably have no reason or need to use newer ones. So we could be good!
Soon ESMA_env will move to use Baselibs 7.18.1 whose main change is moving from HDF5 1.10 to 1.14. GEOSgcm seems pretty agnostic to this as any HDF5 work is done through netCDF (solely I think).
But GEOSldas has an entire file based on HDF5, so we want to be careful.
As such, I've made a branch here:
which updates the ESMA_env to use Baselibs 7.18.1.
I'm hoping nothing happens, all works well, and life is good. 🤞🏼
See also #701
The text was updated successfully, but these errors were encountered: