$.02
Not 1), else you have users duplicating a common data set
and wasting space.
Not 2) else you have the test set in every install you do which
may be excessive.
I would/should do 3). As it is, we just have a /scratch/datasets that
we dump larger datasets into (without any EB in the picture).
Jack Perdue
Lead Systems Administrator
High Performance Research Computing
TAMU Division of Research
j-per...@tamu.edu http://hprc.tamu.edu
HPRC Helpdesk: h...@hprc.tamu.edu
On 06/28/2018 11:52 AM, Mikael Öhman wrote:
I'm looking at creating a config for GPAW-1.4.0 (with libvdwxc), and a
user requested us to also provide the data-sets.
GPAW's installation instructions basically asks users to take of this
normally, by running
$ gpaw install-data <dir>
but I think it makes sense to provide this data as well.
I see some alternatives:
1. Don't do anything and just leave it to users to do this themselves.
2. Add a post-install step that basically does
curl http://wordpress.org/latest.tar.gz
<https://urldefense.proofpoint.com/v2/url?u=http-3A__wordpress.org_latest.tar.gz&d=DwMFaQ&c=ODFT-G5SujMiGrKuoJJjVg&r=yuyoBkmTkIQPbv1BTF9U27ww5Lm7GhsMmWcQG9gmjbA&m=5tvBPsA978weN5mT2sNFBiaeSjqbC0tAFYbuiUA4jRU&s=dVAyiwsFlX7EZahIw1ACEaitNIMIjG4Tss2EkmEN_dI&e=>
| tar xvz
into a suitable directory
3. Create "Atomic-PAW-0.9.2-dummy.eb" that just contains the dataset.
Maybe add it as a dependency, or just provide it (but leaving the
option for users to pick another method, in case they need a different
data-set for some reason).
I'm tempted to do option 3, without any dependencies, and just let
users opt-in to use them when suitable. Win-win?
Best regards, Mikael
