Dump nTuples on batch without jobID
When running on a batch system and writing out nTuples, the user has to ensure that each job writes to a different nTuple file. The easiest way to do so is to include $(jobID)
in the file or path name. Forgetting to do so will result in a wrong or non-existing root file (and no related error message). Apart from the lack in user friendliness, this behaviour it is unfavorable from a conceptual perspective: Everything runs fine locally, but not on the batch system. Ideally, the same input files should work in both cases.
My suggestion: when parsing the file name, check if it contains the jobID. If yes, fine. If not, automatically prepend $(jobID)
to the file name.
Edited by Konstantin Lehmann