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

Order of dimensions for ensemble model output #275

Open
knutfrode opened this issue Jan 24, 2024 · 2 comments
Open

Order of dimensions for ensemble model output #275

knutfrode opened this issue Jan 24, 2024 · 2 comments
Labels
question Further information is requested or discussion invited

Comments

@knutfrode
Copy link

As far as I can understand, CF-convention has no restrictions on the order of dimensions, but recommends using the order
(time, depth/height/z, y, x)

But is there a recommendation/requirement for the order of the additional ensemble/realization dimension for output from ensemble ocean or atmospheric models?
E.g. (ensemble_number, time, depth/height/z, y, x) or (time, depth/height/z, ensemble_number, y, x) ?

@knutfrode knutfrode added the question Further information is requested or discussion invited label Jan 24, 2024
@davidhassell
Copy link
Collaborator

Hello @knutfrode,

I don't know of any such recommendation or requirement, but I personally would go for (ensemble_number, time, depth/height/z, y, x) on the grounds that, depending on your access patterns, netCDF may be faster when the dimensions are ordered from slowest moving to fastest moving, left to right.

@sethmcg
Copy link

sethmcg commented Jan 24, 2024

There is such a recommendation in the second paragraph of section 2.4. "All other dimensions should, whenever possible, be placed to the left of the spatiotemporal dimensions." This is in accordance with the COARDS recommendation for ordering of additional dimensions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested or discussion invited
Projects
None yet
Development

No branches or pull requests

3 participants