You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, ARCO-ERA5 is updated monthly with a 3 month delay. This matches when the "final" version of ERA5 is available, ~2 months delayed.
However, there is also a preliminary version of ERA5 called ERA5T, which is updated daily with a ~5 day delay. In theory, ERA5T could look different from the final version of ERA5, but according to ECMWF this has only happened once.
In practice, I think we could safely update ARCO-ERA5 to update much more frequently, which would be quite useful for downstream operations. Let's look into this after solving the current race condition involved with resizing datasets: #81
The text was updated successfully, but these errors were encountered:
Currently, ARCO-ERA5 is updated monthly with a 3 month delay. This matches when the "final" version of ERA5 is available, ~2 months delayed.
However, there is also a preliminary version of ERA5 called ERA5T, which is updated daily with a ~5 day delay. In theory, ERA5T could look different from the final version of ERA5, but according to ECMWF this has only happened once.
In practice, I think we could safely update ARCO-ERA5 to update much more frequently, which would be quite useful for downstream operations. Let's look into this after solving the current race condition involved with resizing datasets: #81
The text was updated successfully, but these errors were encountered: