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
The cache on JASMIN. Presuming these will be a GWS initially, but could go to object store when we have netCDF S3.
CFStore will be creating CFA files that it will need to see for ingestion, both at the original cycle and when re-aggregating as cycles are added. (So the aggregation will likely see the "existing aggregation CFA" and the next cycle, after which it will discard the next aggregation in favour of the new grand aggregation.)
WE also anticipate that users may want to use cf-python directly on these aggregation files.
The text was updated successfully, but these errors were encountered:
The cache on JASMIN. Presuming these will be a GWS initially, but could go to object store when we have netCDF S3.
CFStore will be creating CFA files that it will need to see for ingestion, both at the original cycle and when re-aggregating as cycles are added. (So the aggregation will likely see the "existing aggregation CFA" and the next cycle, after which it will discard the next aggregation in favour of the new grand aggregation.)
WE also anticipate that users may want to use cf-python directly on these aggregation files.
The text was updated successfully, but these errors were encountered: