We have a GPAW-setups module that GPAW pulls in that contains the files
from https://wiki.fysik.dtu.dk/gpaw-files
So yes, going for a module (based in Core if using HMNS) is good, and
always including it makes it easier for the users.
Judging from the version number you're aiming for, it might
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
but I think it makes sense to provide this data as well.
I see
$.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
3 matches
Mail list logo
