Remove landIceMask from diagnostics computation#672
Conversation
This was removed earlier but inadvertently got added back in.
TestingI ran the QU240wISC test case through the forward run on my laptop. That proves to me that the code compiles and runs with ice-shelf cavities without issues but it does not prove that it addresses E3SM-Project/E3SM#3797. @jonbob or @darincomeau, would it be easy for you to cherry-pick this fix and see if it helps? |
|
@xylar - I'll cherry-pick this right now and see if it fixes our problem |
|
@xylar - that did fix the issue with the ECwISC30to60E1r2 mesh. Thank you so much for jumping in |
jonbob
left a comment
There was a problem hiding this comment.
Tested by cherry-pick and verified that it fixes our observed issue
|
@mark-petersen, any chance of getting this in to E3SM today? |
darincomeau
left a comment
There was a problem hiding this comment.
I can confirm this worked for me in resolving the domain issue we were seeing with ECwISC30to60E1r2. Thanks!!
mark-petersen
left a comment
There was a problem hiding this comment.
Approved based on visual inspection of this code, previously removed. Also ran nightly regression suite and QU240wISC sanity check, all match bfb with ocean/develop using gnu optimized on grizzly.
|
We will plan to merge this on Monday. |
) Update mpas-source: fix landIceMask bug This PR brings in a new mas-source submodule with changes only to the ocean core. It fixes a bug in the MPAS-O landIceMask computation in diagnostics. See MPAS PR MPAS-Dev/MPAS-Model#672 Fixes #3797 [BFB]
Update mpas-source: fix landIceMask bug This PR brings in a new mas-source submodule with changes only to the ocean core. It fixes a bug in the MPAS-O landIceMask computation in diagnostics. See MPAS PR MPAS-Dev/MPAS-Model#672 Fixes #3797 [BFB]
…nto ocean/develop This was removed in MPAS-Dev#447 but inadvertently got added back in in MPAS-Dev#457. It should be the first step toward addressing E3SM-Project/E3SM#3797
This was removed in #447 but inadvertently got added back in in #457.
It should be the first step toward addressing E3SM-Project/E3SM#3797