Skip to content

Implement the first implementation of STOFS Pacific - #238

Open
SorooshMani-NOAA wants to merge 2 commits into
developfrom
feature/pacific_mvp
Open

SorooshMani-NOAA wants to merge 2 commits into
developfrom
feature/pacific_mvp

Conversation

@SorooshMani-NOAA

Copy link
Copy Markdown
Collaborator

Description

Type of change

  • New feature (non-breaking change that adds functionality)
  • New system or port (new OFS yaml, cards, fix-file set)

Change characteristics

  • Changes outputs (values, COMOUT files or names, archives)? No
  • Breaking change to existing functionality? No
  • Requires a nos-utils submodule bump (nos-workflow) or a paired nos-workflow change (nos-utils)? Yes, needs additional ADT yaml processing
  • Requires new or regenerated fix files on the machine? Yes, because of the new system new fix files will be required
  • Requires a re-prep or a new hotstart before the next cycle? Yes, the new system needs to be re-preped from scratch
  • Machines affected: both

How has this been tested?

not tested yet

Checklist

  • Dependent PRs merged and published (nos-utils before any submodule bump)
  • pytest suite passes
  • Existing operational behavior preserved, or the change is called out above
  • No edits to a shared FIXofs while it is cycling
  • Self-review done; yaml comments and docstrings updated where behavior changed
  • No markdown files added to the repo (this template is the only exception)

Comment on lines +84 to +85
rtofs_3d_region: ""
rtofs_freq: daily

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

These would need further commits in utils for rtofs processing

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟡 Changes recommended

Missing Pacific registration and incomplete coupled-mode defaults prevent a usable workflow configuration.

2 open findings
What changed in this PR

Introduces initial STOFS-3D Pacific configuration within the existing SCHISM workflow.

Changes:

  • Adds Pacific grid, forcing, runtime, and post-processing settings.
  • Adds a standalone overlay with static river inputs.
  • Sets an explicit Atlantic ADT datum offset.
File Description
parm/​systems/​stofs_3d_pac_ufs.yaml Adds the initial Pacific system configuration.
parm/​systems/​stofs_3d_pac_ufs_standalone.yaml Selects standalone execution and static river files.
parm/​systems/​stofs_3d_atl_ufs.yaml Sets the ADT datum offset to -0.45.

🧠 Review effort: Balanced


💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

_base: schism

system:
name: stofs_3d_pac

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

I added a descriptor registration: ab3b50f

prefix: stofs_3d_pac_ufs

execution:
mode: ufs # ufs (default, UFS-Coastal DATM) | standalone (classic SCHISM sflux)

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

This is a draft; I'll revisit this when standalone works as expected. At this point I just want to keep the file organization the same.

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.

2 participants