Config file for download cache settings #220
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a new config file in home. This will come handy to set some paths once (and once for all).
This config file is different from the params.cfg in that it stores information which is going to be consistent accross all runs (e.g.: topo data, climate data, etc).
I also had to revert some of your changes @TimoRoth because the concept of a single download cache directory is not possible for these data. Your solution was definitely more elegant, but the data we download is structured and can be used outside oggm. This change allows to keep a structure in the downloaded data. Note that the default config is to have a single cache directory with all data inside, so exactly what you had.