Skip to content

Conversation

@alperaltuntas
Copy link
Member

This PR brings in major changes for introducing runoff to ocean mapping capability:

  • improvements in CIME_interface for retrieving domains, resolutions, and maps.
  • Addition of custom runoff grid stage.
  • A ProConPy change: allow all guarded child stages' guards to be false, in which case the stage is determined by backtracking to the next stage of an ancestor.
  • Introduce runoff to ocean mapping stage: users now have the option to select a standard map (if available for chosen rof and ocn grids), or create a custom map (using mom6_bathy mapping module.)

This commit adds the ability to specify a custom runoff grid.
This includes changes to the grid options, relational constraints, and
the grid stages. The custom runoff grid stage is added to the stage
pipeline, right after the custom lnd grid stage.
Previously, _process_domain_constraints generated the disjunction
of compset and not_compset constraints read in from ccs_config
xml files, but we really want the conjunction of not_compset constraints
alongside the disjjunction of compset constraints. This commit
achieves that. Also made a minor change in custom runoff grid relational
specification.
in which case, the current stage skips all (guarded) children
and backtracks.
CHanges include:
 - New runoff to ocean mapping flag and parameters.
 - Runoff mapping generator widget
 - Relational constraints
 - New guarded mapping stage following runoff stage (only activates
   if mapping is necessary.
 - If a standard mapping file is found between the selected runoff
   and ocean grids, the user has the option to use that standard map.
 - xml changes for mapping files.
@alperaltuntas alperaltuntas self-assigned this Dec 8, 2025
Copy link
Collaborator

@manishvenu manishvenu left a comment

Choose a reason for hiding this comment

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

This all works for me, I did get a environment conflict early on, but it disappeared at some point, and I'm not sure why.

I don't understand the ProConPy stuff, but the runoff stage, widget, and processing code makes sense to me.

@alperaltuntas alperaltuntas merged commit 466b55a into main Dec 11, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants