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

Set time value for averaged quantities to midpoint of averaging period #23

Closed
phillips-ad opened this issue Apr 1, 2022 · 1 comment
Labels
wontfix This will not be worked on

Comments

@phillips-ad
Copy link

This is linked to ESCOMP/CAM#159 and ESCOMP/CTSM#1059, and involves setting the WW3 output time value to the center of the averaging period. Different components may end up handling output differently, but the going consensus so far is to separate instantaneous data streams from averaged/min/max data streams. This might be what is happening with present output, but as the output does not contain a time_bounds array (see #22) I cannot check this.

@billsacks
Copy link
Member

Based on discussion with @klindsay28 and @phillips-ad this isn't feasible for CESM3 and isn't critical, so we're closing it as a wontfix.

@billsacks billsacks closed this as not planned Won't fix, can't repro, duplicate, stale Apr 16, 2024
@github-project-automation github-project-automation bot moved this from Todo ~ months to Done (or no longer holding things up) in CESM: infrastructure / cross-component SE priorities Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
Status: Done (or no longer holding things up)
Development

No branches or pull requests

2 participants