-
Notifications
You must be signed in to change notification settings - Fork 7
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
Add new 0.66 degree MOM6 grid into make_bcs #712
Conversation
Sync develop into main
Sync develop into main
Thanks, @yvikhlya. Looks ok to me but...
Once item 1. is addressed, I'm happy to approve the PR. We'll then need to work with @sdrabenh to merge #707 and the present PR in the correct order (item 2.). We don't have to wait for item 3 since the py versions aren't ready for prime time anyway, but we have to remember to make the changes sooner rather than later. |
@yvikhlya Will either add your river routing patch script to this PR or provide a link to it (by posting it elsewhere)? Once you do it, I'll take the Thanks! |
Label error. Requires exactly 0 of: Contingent - DNA, Needs Lead Approval, Contingent -- Do Not Approve. Found: enhancement, Contingent - DNA, 0 diff structural |
I use this script |
Thank you @yvikhlya And for the record the
is: #681 |
@gmao-rreichle I've tested both options (T3MOM6 and T2MOM6) and they will produce whole set of boundary conditions. I presume science was tested by @sanAkel and @yvikhlya and resulting boundary conditions are what they expect to get. |
No! I haven't yet tested. @sdrabenh, |
GEOSagcm_GridComp/GEOSphysics_GridComp/GEOSsurface_GridComp/Utils/Raster/make_bcs
Outdated
Show resolved
Hide resolved
GEOSagcm_GridComp/GEOSphysics_GridComp/GEOSsurface_GridComp/Utils/Raster/make_bcs
Outdated
Show resolved
Hide resolved
GEOSagcm_GridComp/GEOSphysics_GridComp/GEOSsurface_GridComp/Utils/Raster/make_bcs
Outdated
Show resolved
Hide resolved
Note, this PR is showing runtime failures with CircleCi. Has this PR been run or could this be an automated test issue? @mathomp4 is this a Ci data issue? |
ln -s $MAKE_BCS_INPUT_DIR/ocean/MOM5/360x200 data/MOM5/360x200 | ||
ln -s $MAKE_BCS_INPUT_DIR/ocean/MOM5/720x410 data/MOM5/720x410 | ||
ln -s $MAKE_BCS_INPUT_DIR/ocean/MOM5/1440x1080 data/MOM5/1440x1080 | ||
ln -s $MAKE_BCS_INPUT_DIR/ocean/MOM6/72x36 data/MOM6/72x36 | ||
ln -s $MAKE_BCS_INPUT_DIR/ocean/MOM6/360x210 data/MOM6/360x210 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now, I intend to check it all myself. I have queued it, but have no ETA when I'll get to it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sanAkel sorry just saw your comment. That is what I suspect
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Boundary Conditions package would have failed @sanAkel if files weren't there.
So files were at location when I was running and are still there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sanAkel @sdrabenh I don't think it's that. It's dying in run so it gets through the scripting.
My first guess is that the CI does a checkout-if-exists
step and so it's not just picking up this branch but also the yv/feature/mom6-0.66deg
in GEOS_OceanGridComp as seen in GEOS-ESM/GEOS_OceanGridComp#21
That PR from @yvikhlya is based on develop
in the Ocean GC repo and in there line 653 (which is where the model is dying) is crapping out on:
call MAPL_GetPointer(EXPORT, T_Freeze_e, 'T_Freeze', _RC)
If that line requires, say, a new mom6 tag or something, it's possible the CI is just "unhappy" until the latest Ocean/MOM6 combo is brought into GEOSgcm fixture itself.
So this might be a case of we have to superpower merge it in because of CI issues.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sanAkel It's just really a consequence of the CI scripting trying to be smart. This seems "safe" to pull in because, as @gmao-rreichle says below, it's touching a script my CI does not care about. But the yv/feature/mom6-0.66deg
branch in Ocean GC doesn't quite run without some change elsewhere.
If you, @sdrabenh, @biljanaorescanin, and @gmao-rreichle are fine with this, I can power it in with admin powers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But the yv/feature/mom6-0.66deg branch in Ocean GC doesn't quite run without some change elsewhere.
It touches only several configs. How can this affect the build?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you, @sdrabenh, @biljanaorescanin, and @gmao-rreichle are fine with this, I can power it in with admin powers.
I'm generally ok with the changes but we MUST coordinate this PR with #707. At this moment, #707 is ready, and I assume @sdrabenh will merge it first. Then we have to modify this PR in response. So please refrain from using superpowers unless we have this sorted, so we're not inadvertently merging a conflicting set of PRs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I go with @gmao-rreichle - his word be the final one!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you, @sdrabenh, @biljanaorescanin, and @gmao-rreichle are fine with this, I can power it in with admin powers.
I'm generally ok with the changes but we MUST coordinate this PR with #707. At this moment, #707 is ready, and I assume @sdrabenh will merge it first. Then we have to modify this PR in response. So please refrain from using superpowers unless we have this sorted, so we're not inadvertently merging a conflicting set of PRs.
@gmao-rreichle Please put a DNA label
Thanks @mathomp4 . If @gmao-rreichle @biljanaorescanin @sanAkel @yvikhlya are fine with this PR, I have no objection to @mathomp4 powering it through. |
None of the above was introduced by |
Still need to do 360x210 clean up. Wait for one more commit please. Edit: Done. |
Label error. Requires exactly 0 of: Contingent - DNA, Needs Lead Approval, Contingent -- Do Not Approve. Found: enhancement, Contingent - DNA, 0 diff structural |
…_GridComp into yv/feature/mom6-0.66deg
Label error. Requires exactly 0 of: Contingent - DNA, Needs Lead Approval, Contingent -- Do Not Approve. Found: enhancement, Contingent - DNA, 0 diff structural |
Label error. Requires exactly 0 of: Contingent - DNA, Needs Lead Approval, Contingent -- Do Not Approve. Found: enhancement, Contingent - DNA, 0 diff structural |
GEOSagcm_GridComp/GEOSphysics_GridComp/GEOSsurface_GridComp/Utils/Raster/makebcs/make_bcs
Show resolved
Hide resolved
@yvikhlya, @biljanaorescanin, @sdrabenh, @mathomp4: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re-approve
FYI: @danholdaway, @Dooruk |
and return back old 360x210 MOM6 grid in case someone wants to run it with old land.