#include in fhicl files does not handle full path
we have another bug with loading of the fhicl configuration files. Below a user put the entire path in the #include statement and got back a "Can't find file" error. I would have thought that would be a reasonable thing to do - ie really specify completely where to find a file.
On a related note, we are also seeing that the searching through the $FHICL_FILE_PATH isn't working correctly either. I have my $FHICL_FILE_PATH set to
where each of those directories contains a job directory that holds my fcl files. The first directory holds a subset of the files in the second. I would expect a #include statement set to
to search through first som/path and then through some/other/path looking for the requested file. It appears to only work however, if all the files are in the job directory in the directory from which I run the executable.
Is this maybe already one of the fixes in the new set of externals that Lynn made up for me today?
Begin forwarded message:
[novagpvm02] vahle:/nova/app/users/vahle/arttest>ART_DEBUG_CONFIG= nova -c job/runplaneclusters.fcl -s /nova/data/art/genie_gen.root terminate called after throwing an instance of 'cet::exception' what(): ---- search_path BEGIN Can't find file "/grid/fermiapp/nova/novaart/novasoft/releases/development/job/services.fcl" ---- search_path END
finds the file