-
Notifications
You must be signed in to change notification settings - Fork 38
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
Download instructions for the MSWEP data #1505
Comments
@jeromaerts perhaps you can comment on the version and (public) availability of MSWEP? |
I ran into the same issue while we ran all the recipes for the release of v2.5 (#2535). So I downloaded the old version (v220) of the MSWEP data to be able to run the recipe Getting the data But the inconsistency between the version of the MSWEP data used in the recipe (v220) and the officially available version (v280) remains. I think we should either update the recipe_hydro_forcing.yml or our instructions on how to get the data from. |
I can see this turning into an endless chase of the most recent version, so I'd prefer to update the instructions. |
Thanks, I agree. I will transfer this to ESMValCore since info on natively supported non-CMIP datasets lives there |
Describe the bug
The MSWEP data needed for the recipe
hydrology/recipe_hydro_forcing.yml
are a bit difficult to download. The current instructions can be found in the ESMValCore documentation but the link there (http://www.gloh2o.org/mswep/) only gives access to the latest version of the data (V280). For that the user needs to apply to get access to a Google Drive folder where the data are stored. On that page, it is said:Currently the
hydrology/recipe_hydro_forcing.yml
uses MSWEP V220 data but these can't be found on the official website. I could only download them using a link in the description of the PR #969 which introduced the on-the-fly cmorization for MSWEP data. I'm not sure that link follows the requirement for Tier3 data and that V220 is still distributed.It would be good to clarify the following points:
The text was updated successfully, but these errors were encountered: