Moving to v12 BCS

[biljanaorescanin]

This PR will offer v12 boundary conditions version instead of v11.
We are moving from v11 after we fixed a localized bug user found in the set over Argentina.

More details on that bug fix are in this PR: GEOS-ESM/GEOSgcm_GridComp#944
Set was verified in offline simulations by @gmao-rreichle

Set is used in testing for future default BCS candidate.

[biljanaorescanin]

@mathomp4, @sdrabenh not sure about this run fail for me in sandbox all runs, any ideas?

[gmao-rreichle]

@mathomp4, @sdrabenh not sure about this run fail for me in sandbox all runs, any ideas?

Are the required v12 bcs in place?

[gmao-rreichle]

@mathomp4, @sdrabenh not sure about this run fail for me in sandbox all runs, any ideas?

PS: I just realized that the "build" fails, not the "run". So potential lack of a specific resolution of v12 bcs doesn't explain it (but may still be an issue).
PPS: My bad -- the "build-test" failed because the "run" tests failed. So could it be the lack of v12 bcs after all?

[biljanaorescanin]

Are the required v12 bcs in place?

I think all we use is there now. But here is path if someone wants to check:
/discover/nobackup/projects/gmao/bcs_shared/fvInput/ExtData/esm/tiles/v12/geometry
I do need to run stretched grid and high res cases but all including C360 and lower is there.

[mathomp4]

@gmao-rreichle @biljanaorescanin My guess is you've broken the scripts I used to make experiments. They are sensitive to changes in gcm_setup sometimes (especially if a question changes).

I'll need to clone this on discover and track that down fix my scripts and then update the CI to recognize it.

[mathomp4]

Okay. First CI fix attempt running...