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

CORE / TIER1 / TIER2 priorities #5

Open
jesusff opened this issue May 24, 2024 · 0 comments
Open

CORE / TIER1 / TIER2 priorities #5

jesusff opened this issue May 24, 2024 · 0 comments

Comments

@jesusff
Copy link
Member

jesusff commented May 24, 2024

We need to clarify the meaning of the priority labels internally for I4C. For CORDEX, the meaning is quite loose regarding how mandatory is it to produce a field, especially sub-daily data.

For the moment, in the I4C data request, both CORE and TIER1 fields are mandatory, the difference being that CORE variables will fit in a central server, while TIER1 ones might need to be stored locally and exchanged in another way. These are 1hr 3D variables only requested by the emulators task (T3.3) groups, which are mostly the CPRCM output producers.

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

1 participant