-
Notifications
You must be signed in to change notification settings - Fork 26
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
Common location for observational datasets? #37
Comments
We have our sea ice observational data in: /glade/campaign/cesm/development/pcwg/ice/data One thing we do for the CICE Consortium data is we put it on Zenodo. I think they allow 50GB datasets. We end up breaking the datasets up. We also tag releases of the model here: https://zenodo.org/communities/cice-consortium?q=&l=list&p=1&s=10&sort=newest |
We are trying to put all the relevant ocean datasets (obs and reanalysis) under |
not sure how this is supposed to be set up, but trying to run CUPiD out of the box I get the following permission error |
I changed the permissions on this file and it is now readable by everyone. Let me know if you are still having issues. |
I'm still getting the same permission error, and can't see anything below the |
Please try again. |
That did the trick. Thanks @gustavo-marques |
Currently the ADF is capable of comparing model simulations to certain reanalysis and observational datasets, which are accessible by all ADF users, at least when running on Casper. However, right now all of those observational datasets are under people's personal directories, for example here:
/glade/work/nusbaume/SE_projects/model_diagnostics/ADF_obs
I suspect that this strategy will be difficult to maintain long-term, especially as other non-ADF diagnostics are brought into CUPiD that need their own specialized datasets.
Given this, should there be work to identify a common location where all of the CUPiD-relevant observational datasets are stored? Along those lines are several things that should probably be discussed at some point:
I assume it will take multiple group discussions to figure all of this out, but I just wanted to open this issue now, as it may impact how at least the ADF is integrated into CUPiD.
The text was updated successfully, but these errors were encountered: