Distributing bxdecay0 data and gA data on CVMFS? about bxdecay0 HOT 3 CLOSED

Basically the resources/data dir contains various types of informations:

a) descriptive files that are read from the code to generate list of identifiers programmatically:
- background_isotopes.lis
- dbd_isotopes.lis
- dbd_modes.lis
b) physics data files like in the dbd_gA directory

They are not of the same nature. The a) files should be distributed with the code for they are read from the bb_utils.cc source at runtime.
I see no problem to make b) optionnaly distributable provided it does not enforce additional constraint or technological dependencies. The only case is for dbd_gA of course and it makes sense to be able to handle these large files on its own way like we can do with G4 datasets.

I think the a) files should be moved in some specific "resources/description/" directory and let the "resources/data" for specific datasets possibly managed by other means.

from bxdecay0.

Additionally, there is no reason why BXDECAY0_RESOURCE_DIR would be the shared root of BxDecay0 data.
I prefer BXDECAY0_RESOURCE_DIR to be used for non-data resources files (*.lis, legacy code...) and introduce specific BXDECAY0_XXX_DATA_DIR envs for specific datasets possibly installed/published through external tools.

from bxdecay0.

From commit #25718c8, the BXDECAY0_DBD_GA_DATA_DIR environment variable is used to locate a base directory which must contains the DBD gA datafiles. Such a directory must store the data/dbd_gA/vX.Y/ directories to fulfill the path naming scheme used so far in BxDecay0.

from bxdecay0.