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

Decide where the CFA files for CANARI are going #117

Open
bnlawrence opened this issue Sep 28, 2023 · 0 comments
Open

Decide where the CFA files for CANARI are going #117

bnlawrence opened this issue Sep 28, 2023 · 0 comments
Milestone

Comments

@bnlawrence
Copy link
Collaborator

bnlawrence commented Sep 28, 2023

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.

@bnlawrence bnlawrence added this to the CANARI-MVP milestone Sep 28, 2023
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