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
This is a question I guess for @AlexanderRichert-NOAA or @RatkoVasic-NOAA. Us MAPL folks (okay, mainly me) were looking at maybe cleaning up the MAPL CMake and one of the things I focused on was the option for building ExtData2G support. Looking around here I see that ufs-weather-model-static has:
So I imagine the ability not to have ExtData2G was for NOAA.
Does anyone remember why ExtData2G was not wanted by UFS? We have some memory that maybe it was yaFyaml related (not sure) but at the moment ExtData2G actually uses ESMF to process YAML.
I was also sort of motivated because recently we found that our ExtData1 RC files in some places in GEOS/GOCART might be getting stale as a user accidentally ran with ExtData1 and found missing imports because only the yamls had the correct entries.
The text was updated successfully, but these errors were encountered:
I don't know offhand... @junwang-noaa, @BrianCurtis-NOAA can you answer Matt's question about why UWM doesn't use ExtData2G?
I think we do install with the extdata2g variant enabled in the main stack, which is what UWM developers are generally using (I don't know offhand if anyone uses the ufs-weather-model-static stack at this point).
This is a question I guess for @AlexanderRichert-NOAA or @RatkoVasic-NOAA. Us MAPL folks (okay, mainly me) were looking at maybe cleaning up the MAPL CMake and one of the things I focused on was the option for building ExtData2G support. Looking around here I see that ufs-weather-model-static has:
So I imagine the ability not to have ExtData2G was for NOAA.
Does anyone remember why ExtData2G was not wanted by UFS? We have some memory that maybe it was yaFyaml related (not sure) but at the moment ExtData2G actually uses ESMF to process YAML.
I was also sort of motivated because recently we found that our ExtData1 RC files in some places in GEOS/GOCART might be getting stale as a user accidentally ran with ExtData1 and found missing imports because only the yamls had the correct entries.
The text was updated successfully, but these errors were encountered: