Dear all,
Our current implementation is a bit confusing for lumi input files. Here is an example
A developer finished his work on the skimmer, validated, pushed to master and created a new tag.
A user tries to skim with the latest DCS only json ( because this is what he should do). The default lumi dir is within Skimmer repo and placing the file there will mark the repo as dirty.
The only way to submit with a clean repo and music_crab3 is to place the dcs file outside the repo and set the --lumi-dir option.
Generally speaking, we should think about putting the configs in a different repository. Makes little sense to "validate" the entire codebase if you just update the config files with the latest working examples.
Dear all, Our current implementation is a bit confusing for lumi input files. Here is an example
A developer finished his work on the skimmer, validated, pushed to master and created a new tag.
A user tries to skim with the latest DCS only json ( because this is what he should do). The default lumi dir is within Skimmer repo and placing the file there will mark the repo as dirty. The only way to submit with a clean repo and music_crab3 is to place the dcs file outside the repo and set the --lumi-dir option.
There should be an easier way.