Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use NCO to automatically exclude 3D variables #704

Open
3 tasks done
forsyth2 opened this issue Apr 4, 2025 · 1 comment
Open
3 tasks done

Use NCO to automatically exclude 3D variables #704

forsyth2 opened this issue Apr 4, 2025 · 1 comment

Comments

@forsyth2
Copy link
Collaborator

forsyth2 commented Apr 4, 2025

Request criteria

  • I searched the zppy GitHub Discussions to find a similar question and didn't find it.
  • I searched the zppy documentation.
  • This issue does not match the other templates (i.e., it is not a bug report, documentation request, feature request, or a question.)

Issue description

See #697 (comment). This should allow us to skip the vars_exclude parameter. Note this requires using the latest NCO.

@czender
Copy link

czender commented Apr 4, 2025

Note that as currently implemented, this functionality works when the user does not provide and extraction list for what we call global timeseries. In that case ncclimo creates its own extraction list of all the single-level, 2D spatial timeseries variables. If a user explicitly specifies a multi-level field (e.g., like U in EAM or H2OSOI in ELM) then ncclimo will fail. If there is interest, I can make ncclimo ignore bad user choices (i.e., multi-level fields), though that can be a slippery slope. Feedback welcome.

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

No branches or pull requests

2 participants