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

I/O Runtime Wishlist #2939

Open
1 of 4 tasks
AaronDonahue opened this issue Aug 5, 2024 · 1 comment
Open
1 of 4 tasks

I/O Runtime Wishlist #2939

AaronDonahue opened this issue Aug 5, 2024 · 1 comment

Comments

@AaronDonahue
Copy link
Contributor

AaronDonahue commented Aug 5, 2024

There have been a number of feature requests regarding runtime I/O. This issue is meant to collect them all into one place so we can manage them.

  • Check if list of output variables is valid - see Check output streams yaml files at buildnml time #2246
  • Compare ATM dt with the frequency of output. This is an issue when the output frequency may be smaller than dt.
  • Make sure no two output streams will share a name (i.e. overwriting each other). This is a pretty edge case, so not high priority.
  • Make sure all required keys are present. i.e. filename_prefix, grid, fields, frequency, etc.
@bartgol
Copy link
Contributor

bartgol commented Aug 6, 2024

Two thoughts

  • The second box is done, if we agree that dt_out>dt_atm should not be allowed.
  • Do you want these checks done at runtime or buildnml time? I don't think the 1st check can be done at buildnml time, since it requires knowledge of each atm proc implementation (buildnml does not know what each atm proc produces). And we already have a check at runtime: IO will throw if the field is not found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants