Skip to content

Conversation

biljanaorescanin
Copy link
Contributor

@biljanaorescanin biljanaorescanin commented Jan 3, 2025

Somehow during branch sinking some commits got lost and we just noticed now during coupled run testing.
Issue was hydrostatic question.

To test this PR we need GCMv12-rc10 and its branches.

These commits were originally on #61

Copy link

github-actions bot commented Jan 3, 2025

This PR is being prevented from merging because you have not added one of our required labels: 0 diff, 0 diff trivial, Non 0-diff, 0 diff structural, 0-diff trivial, Not 0-diff, 0-diff, automatic, 0-diff uncoupled. Please add one so that the PR can be merged.

@biljanaorescanin biljanaorescanin added 0 diff trivial The changes in this pull request are trivially zero-diff (documentation, build failure, &c.) Skip Changelog labels Jan 3, 2025
@@ -121,6 +124,13 @@ def ask_questions():
"validate": lambda text: validate_geosit_time(text),
"when": lambda x: x.get("input:shared:GEOS-IT", False) and not x.get("input:shared:MERRA-2", False),
},
{
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oooh. This one is tricky. By default, GEOSgcm v12 is non-hydrostatic. So, anyone remapping from v12 to v12+ would prefer this to be True by default. But then, anyone remapping anything older (v11, say) would want True

I am not sure what to do here. @wmputman might have more insight.

Copy link
Contributor Author

@biljanaorescanin biljanaorescanin Jan 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I think this makes also issues for coupled runs from older restarts. Coupled restarts are always hydrostatic I think.
@wmputman what should be our defaults?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@biljanaorescanin "Coupled restarts are always hydrostatic" well...huh. I did not know that. I've been doing any test MOM6 runs with v12 as non-hydro.

Maybe @wmputman has FV3 setup in such a way now that it doesn't matter? If not, I know MERRA-2 is hydrostatic but what about GEOS-IT? I assume it is, but since @biljanaorescanin added GEOS-IT we'd probably want some default for that too.

@biljanaorescanin
Copy link
Contributor Author

biljanaorescanin commented Jan 3, 2025

@mathomp4 @wmputman @sdrabenh @zhaobin74 what we need to do is go from MOM6-NLv3-72 levels (hydrostatic RST) to MOM6-v12-181 levels (non-hydrostatic RST)? OR all is hydrostatic for coupled runs? Input and Output?

Currently remap will skip remapping upper. I think it is due to hydrostatic option. But I will see with @weiyuan-jiang how to fix this once we know what it needs to be.

Update:
Branch will run and create all restarts with no issues. Issue before was .nc4 extension on input files. I totally forgot we can't have that.

@biljanaorescanin biljanaorescanin marked this pull request as ready for review January 3, 2025 20:21
@biljanaorescanin biljanaorescanin requested a review from a team as a code owner January 3, 2025 20:21
@sdrabenh sdrabenh merged commit dbbfe57 into feature/sdrabenh/gcm_v12 Feb 6, 2025
6 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 diff trivial The changes in this pull request are trivially zero-diff (documentation, build failure, &c.) Skip Changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants