As brought up by @ofuhrer in VulcanClimateModeling/fv3gfs#41, on production systems we'd like the data cache to go to some kind of scratch folder and not /home/username. There should be a way to specify where the download cache should be stored.
I think the "correct" option would be to store the download location in the appdirs folder (/home/username) as a string in a text file (yaml?), and allow the user to specify where they want the data to be stored when they call python -m fv3config.download_data (e.g. with a --location=/scratch command-line argument). When we import the package it would then load the download location from its configuration file.
Related to this, there should be a way the user can easily get the download location (without having to explicitly check that text file, if that's the approach we take to specifying location).
As brought up by @ofuhrer in VulcanClimateModeling/fv3gfs#41, on production systems we'd like the data cache to go to some kind of scratch folder and not
/home/username
. There should be a way to specify where the download cache should be stored.I think the "correct" option would be to store the download location in the appdirs folder (
/home/username
) as a string in a text file (yaml?), and allow the user to specify where they want the data to be stored when they callpython -m fv3config.download_data
(e.g. with a--location=/scratch
command-line argument). When we import the package it would then load the download location from its configuration file.