-
Notifications
You must be signed in to change notification settings - Fork 16
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
CORDEX-CMIP6 storage requirements estimation #40
Comments
This is a first estimate, only for CORE variables and with an assumed average 60% compression rate wrt to raw binary float precision. This value can be adjusted (e.g. by comparing with real processed output).
|
I think such an approach should work as an basic estimate. RCMs with non rotated grids usually provide larger domains but some RCM groups may provide only a subset of the Tier1 and 2 variables. Are all simulations for EUR-12 only 892.6 Tb ? |
Yes, but this is only CORE variables and only those simulations planned so far in this repo. I paste here the summary including all tiers:
|
Now it looks reasonable :-) as we need an estimate for all CORE, Tier1 and 2 variables. |
Although I don't expect many variables from Tier2. |
Ok, this is the remaining one 😉 : CORE + Tier1
|
Just for the record: some reasonable approximations are in place until all domains are defined in https://github.com/WCRP-CORDEX/domain-tables/blob/main/CORDEX-CMIP5_rotated_grids.csv simulation-status/storage_estimate.py Lines 30 to 34 in bc8c5a3
|
I think 10 PB sounds like an reasonable estimate. In any case, it's impossible to provide exact size :-) |
In order to secure the archival of CMIP6-driven simulations in ESGF, we first need to estimate the volume of data that we will be producing. An accurate estimate is difficult due to the dependence of the compression rates on the different variables and even on the different models as the effective model resolution affects compression.
A very rough estimate should, in principle, be easily extracted by combining the information in:
The text was updated successfully, but these errors were encountered: