Skip to content

Add NCO spec to conda dev file - #877

Closed
forsyth2 wants to merge 1 commit into
mainfrom
issue-875-nco-dev
Closed

forsyth2 wants to merge 1 commit into
mainfrom
issue-875-nco-dev

Conversation

@forsyth2

Copy link
Copy Markdown
Collaborator

Summary

Objectives:

  • Specify NCO explicitly in the conda dev file

Issue resolution:

Select one: This pull request is...

  • a bug fix: increment the patch version
  • a small improvement: increment the minor version
  • a new feature: increment the minor version
  • an incompatible (non-backwards compatible) API change: increment the major version

Small Change

  • To merge, I will use "Squash and merge". That is, this change should be a single commit.
  • Logic: I have visually inspected the entire pull request myself.
  • Pre-commit checks: All the pre-commits checks have passed.

@forsyth2 forsyth2 self-assigned this Sep 21, 2026
@forsyth2 forsyth2 added the semver: bug Bug fix (will increment patch version) label Sep 21, 2026
@forsyth2

Copy link
Copy Markdown
Collaborator Author

Closing per my comment here. zppy does not actually use NCO, which is why it was never defined here. zppy only defines run_nco function and nco_path parameter to switch the path used for it for multiple called tasks.

@forsyth2 forsyth2 closed this Sep 22, 2026
@forsyth2
forsyth2 deleted the issue-875-nco-dev branch September 25, 2026 20:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

semver: bug Bug fix (will increment patch version)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: e3sm_to_cmip failing due to srun error

1 participant