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

Generalize Downloader #12

Open
liellnima opened this issue Oct 10, 2024 · 1 comment · May be fixed by #13
Open

Generalize Downloader #12

liellnima opened this issue Oct 10, 2024 · 1 comment · May be fixed by #13
Assignees

Comments

@liellnima
Copy link
Collaborator

Requests to extend the downloader for more internal (and later external) use cases.

  • project tag in configs: generalize downloader to be able to retrieve data from cmip6, cmip6plus, e3sm, input4mips, and if possible more.
  • get rid of look up tables: especially for "scenarios" and "models" we are limiting ourselves with the lookup tables (especially for input4mips) - those lists seem to be narrowed down to our core dataset, and hence the code blocks to downloads any data that is outside of our current core dataset. Finding a new way to handle this rather general problem would be great. It would give us more freedom and make the code base probably smaller? (when getting rid of the lookup tables)
  • add more optional specs to configs: ensemble member number that is downloaded, temporal frequency, nominal resolution. we might want to extend that further upon requests or find another way how people can extend this themselves.
  • adapt input4mips: unintuitive behavior: input4mips currently downloads every experiment of the desired variable. We might want to separate between downloading specific ssp scenarios or historical data.

Testing config files can be found in "downloader" for all those cases.

@f-PLT f-PLT self-assigned this Oct 11, 2024
@liellnima
Copy link
Collaborator Author

Adding more information: Dependency on selected scenarios must be removed

@liellnima liellnima linked a pull request Oct 26, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

2 participants