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

How could roocs cope with orchestrate requests for multiple dataset IDs? #197

Open
agstephens opened this issue Nov 10, 2021 · 0 comments
Open
Assignees

Comments

@agstephens
Copy link
Contributor

agstephens commented Nov 10, 2021

Example request:

  • Take a collection of CMIP6 ensemble members for a given expt+model+variable:
    • maybe defined with a wildcard, e.g. foo.baa.foo2.baa2.*.foo3.baa3
  • Subset both in space/time (operation 1: subset)
  • Regrid both to the same grid (operation 2: regrid)
  • Calculate the ensemble average of all of them (operation 3: ensemble_average)

Implications for "roocs" stack:

  • rook needs to consolidate a list of files (as output from operation 1) into:
    • a sequence of FileMapper objects
  • daops can receive and consolidate multiple FileMappers as inputs
  • all interfaces can handle receiving multiple dataset IDs (somehow)
  • interfaces need to be able to receive wildcards in dataset IDs and resolve them via search/lookup (of catalog?)
@agstephens agstephens self-assigned this Nov 10, 2021
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