Streamline FT tuning versions
So @kheinick, this is the merge request.
As I wrote via email, at the moment the following tunings are defined:
“Summer2017Optimisation” => the version shown during the LHCb week in Lake Placid (kept for backward compatibility). Taggers are optimized on Run2 data here.
“Summer2017Optimisation_Run1” => taggers optimized on Run1. This is identical to the “Run1” configuration, except for the OSe, which has been updated (new version documented in https://gitlab.cern.ch/lhcb-ft/FT_AnalysisNote_Run1Run2 already). This should be the default on Run1 data. This could be renamed as “Summer2017Optimisation_Run1_v1” if we want to follow “CAMPAIGNNAME_TRAININGDATA_TRAININGVERSION"
“Summer2017Optimisation_Run1_noVeloCharge” => same as above, but with velo charge cuts removed, so that this tuning can be tested on the upgrade. This could be renamed as “Summer2017Optimisation_Run1_v1p1” if we want to follow “CAMPAIGNNAME_TRAININGDATA_TRAININGVERSION"
“Summer2017Optimisation_v2_Run2” => same as Summer2017Optimisation, but with OSe updated to match what is documented in https://gitlab.cern.ch/lhcb-ft/FT_AnalysisNote_Run1Run2 This should be the default on Run2 data. This could be renamed as “Summer2017Optimisation_Run2_v2" if we want to follow “CAMPAIGNNAME_TRAININGDATA_TRAININGVERSION"
“Summer2017Optimisation_v2_Run2_noVeloCharge” => same as above, but with velo charge cuts removed, so that this tuning can be tested on the upgrade. This could be renamed as “Summer2017Optimisation_Run2_v2p1" if we want to follow “CAMPAIGNNAME_TRAININGDATA_TRAININGVERSION"
“Summer2017OptimisationDev” => the development tuning, which for now just points to Summer2017Optimisation_v2_Run2.
Please let me know your opinions/concerns.