remap upper stretched cube in

[weiyuan-jiang]

The branch is a merge of the branches feature/wmputman/remap_upper_stretched_cube_in and main. Testing is underway...

[wmputman]

Looks good to me

[mathomp4]

I believe, per @weiyuan-jiang, that this relies on updates in FVdycoreCubed_GridComp, so it should probably be undrafted when @sdrabenh undrafts all the other update PRs.

[biljanaorescanin]

Well its mix of all of these:
GEOS_Util | (b) feature/wjiang/bill_remap_upper_stretched_cube_in
MAPL | (b) feature/wmputman/KM_v11_5_1_remap_upper
GEOSgcm_GridComp | (b) feature/wmputman/KM_v11_5_1_post_mgb_updates
FVdycoreCubed_GridComp | (b) feature/wmputman/KM_v11_5_1_remap_upper
fvdycore | (b) feature/wmputman/KM_v11_5_1_remap_upper
GEOSgcm_App | (b) feature/sshakoor/linking_new_bcs

[mathomp4]

Note for @weiyuan-jiang, @wmputman has an update for the milans on a branch: feature/wmputman/KM_v11_5_1_remap_upper

You can see the differences here:

feature/wjiang/bill_remap_upper_stretched_cube_in...feature/wmputman/KM_v11_5_1_remap_upper

I'm mainly talking about the MPI settings. I'm not too sure what the other changes are (QOS and Ostia).

[biljanaorescanin]

If we run our testing package all our tests will fail for upper restarts when compared to baseline. All tests are CF.
Surface restarts are the same.
Here are tests outputs:
/discover/nobackup/borescan/REMAP_TESTS/
and here is baseline we compare with:
/discover/nobackup/projects/gmao/SIteam/Remapping_Test_Cases/

@sdrabenh @wmputman who is best to help us with validation of upper restarts? Someone needs to confirm this is what we want to see.