As currently stands G4LatticeReader will only read a single path off of G4LATTICEDATA when searching for crystal map files. To avoid contaminating the central G4LATTICEDATA directory with custom crystal map files, G4LatticeReader::OpenFile was modified to first split fDataDir into separate paths (in user-entered order) and search each for the desired lattice file, rather than search an unmodified fDataDir. For users with only a single path defined on G4LATTICEDATA, this change will not affect the search for crystal map files.
Additionally, the main CMakeLists.txt file was modified slightly to avoid a failure condition with git describe; this change is documented in the commit comments.
As currently stands G4LatticeReader will only read a single path off of
G4LATTICEDATA
when searching for crystal map files. To avoid contaminating the centralG4LATTICEDATA
directory with custom crystal map files, G4LatticeReader::OpenFile was modified to first split fDataDir into separate paths (in user-entered order) and search each for the desired lattice file, rather than search an unmodified fDataDir. For users with only a single path defined on G4LATTICEDATA, this change will not affect the search for crystal map files.Additionally, the main
CMakeLists.txt
file was modified slightly to avoid a failure condition withgit describe
; this change is documented in the commit comments.