Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EASE grid name change #673

Closed
biljanaorescanin opened this issue Aug 14, 2023 · 3 comments
Closed

EASE grid name change #673

biljanaorescanin opened this issue Aug 14, 2023 · 3 comments

Comments

@biljanaorescanin
Copy link
Contributor

In creating a V06 set of boundary conditions for @lcandre2, we encountered problems with the EASE grid name change within the tile file.
Currently, "ldas_setup" only works with the old name.
For example: from legacy_bcs M36 Nlv3 in SMAP_EASEv2_M36_964x406.til
has: SMAP-EASEv2-M36
but if we run boundary conditions now, we get an output with name change SMAP_EASEv2_M36 (or most recent: EASEv2_M36)

If we try to run with the new grid name, system is not flexible and won't find the tile. We get this error:

GEOSldas::Initialize 555

For now fix is implemented manually, by going into EASE grid set and changing the ease grid name in tile file.
Maybe we need to implement partial name search? Look for just M36 and no - or _

@weiyuan-jiang @gmao-rreichle

@weiyuan-jiang
Copy link
Contributor

Basically you need the MAPL fix here. Would you please give a try ? GEOS-ESM/MAPL#2307

@biljanaorescanin
Copy link
Contributor Author

With this change in MAPL, both options will run.
One downside, though, is we will have to update few repos in components.yaml, env and cmake, to make MAPL develop branch run with GEOSldas. I think a non-zero diff change has been been implemented a while back, so maybe we can talk when is a good time to do this. For now we have a fix and we know how to make it run if anyone needs new boundary conditions.

@gmao-rreichle
Copy link
Contributor

addressed with #680

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants