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

Have time-stamps for "averaged" output history data be middle of interval, but "instantaneous" be end #413

Open
ekluzek opened this issue Jul 26, 2023 · 1 comment · Fixed by #460
Labels
cesm-coupling For cesm coupling
Milestone

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Jul 26, 2023

This is important to comply with the latest convention decided in the CESM co-chairs group. time-stamps for history data that is averaged should be the middle of the interval, and time_bounds should be reported as the start and end of the interval. For instantaneous data (so history data output as "daily" with a daily time-step) the time-stamp should be the end of the interval, and time_bounds NOT included in output.

This was decided in co-chairs on 7/24/2023, and we want it to be put in place for all CESM components by end of Summer.

@nmizukami
Copy link
Collaborator

I can make this happen fairly easily now (see PR #475 for standalone), but for now using average for aggregation of all variables because there is no capability to outputs into multiple output file streams.

@ekluzek ekluzek added this to the cesm3.0.0 milestone Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cesm-coupling For cesm coupling
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants