Skip to content

Boundary conditions - v13 based on MOM6/v2 ocean bathymetry (OM4) #1149

Draft
sinakhani wants to merge 50 commits intodevelopfrom
skhani/develop
Draft

Boundary conditions - v13 based on MOM6/v2 ocean bathymetry (OM4) #1149
sinakhani wants to merge 50 commits intodevelopfrom
skhani/develop

Conversation

@sinakhani
Copy link

@sinakhani sinakhani commented Aug 28, 2025

  • This PR adds updates for files in makebcs directory to include MOM6/v2 ocean bathymetry.
  • This PR also adds the wiring for handling (atmos) TOPO versions (but v13 bcs still have v1 TOPO).
  • This is non-zero diff for MOM6 in coupled mode, but zero-diff otherwise (AMIP).

@sinakhani sinakhani requested a review from a team as a code owner August 28, 2025 23:13
@sinakhani sinakhani added the 0-diff AMIP 0-diff for uncoupled AMIP runs label Aug 28, 2025
@biljanaorescanin biljanaorescanin marked this pull request as draft August 28, 2025 23:53
Copy link
Contributor

@gmao-rreichle gmao-rreichle left a comment

Choose a reason for hiding this comment

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

see comments below

@sinakhani
Copy link
Author

I have make changes based on the given comments. Please let me know what you think about this version. Thank you @gmao-rreichle @mathomp4 @biljanaorescanin

Copy link
Contributor

@gmao-rreichle gmao-rreichle left a comment

Choose a reason for hiding this comment

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

Thanks, @sinakhani. See more comments below

@sinakhani
Copy link
Author

I just cleaned up the text for merged cases "v12", "v13", and "v14". Please feel free to make further changes. Thank you.

@mathomp4 mathomp4 added the 0 diff The changes in this pull request have verified to be zero-diff with the target branch. label Aug 29, 2025
@biljanaorescanin
Copy link
Contributor

This PR was tested for BCS creation for both old v12 set and new v14 .
Zero diff to v12 with addition to TOPO linking. New version v14 is sourcing right files.
BCS run's for resolutions we do not have new bathymetry file will use v1 so we can create full set of BCS.

@biljanaorescanin biljanaorescanin marked this pull request as ready for review September 11, 2025 16:59
Copy link
Contributor

@gmao-rreichle gmao-rreichle left a comment

Choose a reason for hiding this comment

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

see comments below

@biljanaorescanin biljanaorescanin marked this pull request as draft September 12, 2025 14:03
@gmao-rreichle gmao-rreichle changed the title Boundary conditions v14 based on MOM6/v2 ocean bathymetry (OM4) Boundary conditions v14 based on MOM6/v2 ocean bathymetry (OM4) and "v2" topography for atmosphere Sep 12, 2025
@biljanaorescanin biljanaorescanin added the Not 0-diff coupled Non 0-diff for coupled AGCM/MOM5/MOM6/CICE4/CICE6 model label Jan 22, 2026
@biljanaorescanin biljanaorescanin changed the title Boundary conditions v14 based on MOM6/v2 ocean bathymetry (OM4) and "v2" topography for atmosphere Boundary conditions - v13 based on MOM6/v2 ocean bathymetry (OM4) Jan 22, 2026
@biljanaorescanin
Copy link
Contributor

@gmao-rreichle I think I implemented all your comments but please let me know if I missed something.
I am retesting it now.

@biljanaorescanin
Copy link
Contributor

I've re-tested few grids and res just to confirm it is zero diff to before and what we want as far as behavior. And all looks good.

Copy link
Contributor

@gmao-rreichle gmao-rreichle left a comment

Choose a reason for hiding this comment

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

@biljanaorescanin : I just pushed a commit with a few minor updates to the comments and white space. One of the updates might affect a log file, so technically it may not be zero-diff w.r.t. the v13 bcs that you already generated. But there's no need to re-generate the v13 bcs just because of the minimal log file change.
See also in-line comments below.

Comment on lines +229 to +230
TOPO_VERSION = TOPO_VERSION,
mom6_bathy_version = MOM6_BATHY_VERSION,
Copy link
Contributor

@gmao-rreichle gmao-rreichle Jan 28, 2026

Choose a reason for hiding this comment

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

Don't we need to end these lines with "\"?

Comment on lines +31 to +40
def _normalize_lbcsv(label: str) -> str:
v = (label or "").strip()
m = re.match(r'[vV]?\d+|[A-Za-z0-9]+', v) # accepts v13 / 13 / NL3 / etc.
if not m:
return v
key = m.group(0)
# normalize numeric like '13' -> 'v13'
if key.isdigit():
key = 'v' + key
return key
Copy link
Contributor

Choose a reason for hiding this comment

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

Why do we need this "normalize" function? Don't we always have a 3-char alphanumeric string for "bcs_version"? When would we have "bcs_version=13" (without the leading "v")?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

0-diff AMIP 0-diff for uncoupled AMIP runs 0 diff The changes in this pull request have verified to be zero-diff with the target branch. Not 0-diff coupled Non 0-diff for coupled AGCM/MOM5/MOM6/CICE4/CICE6 model

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

Comments