Refactor the propagation of tau ID WPs

[ktht]

Right now, we just propagate the tau ID WP of the tight tau collection to the analysis, but it leaves the tau ID WPs of fakeable / loose tau collections unchanged. This causes problems, if the user wants to switch to a different tau ID altogether. The solution is to define clear-cut list of tau ID WPs which are modifiable in tthAnalyzeRun/hhAnalyzeRun submission scripts: for each tau collection, the tau ID WP must be defined explicitly. There already is some code in place that makes the task a bit easier, but it's still relatively substantial task.

[ktht]

Summary in no particular order:

• loose had tau selector removed;
• correct data/MC SFs are now applied in case the tau discriminant is relaxed below the nominal fakeable WP;
• hardcoded references to any had tau discriminant is removed from the C++ and Python code;
• support for DeepTau ID fully implemented:
  • if the user requests to run the analysis using the DeepTau ID discriminator, then the loosest WPs of anti-e and anti-mu DeepTau ID discriminators are automatically applied;
  • fakeable had tau selector by default uses dR03mvaVLoose WP but it can be easily changed to VVVLoose of DeepTau ID by setting tauId to TauID::DeepTau2017v2VSjet: https://github.com/HEP-KBFI/tth-htt/blob/85ec2368fbfacb2beeaa5444cb6fe5e562f4701c/src/RecoHadTauCollectionSelectorFakeable.cc#L12-L23
  • fakeable had tau selector has the option to "relax" the WP or switch to a different tau ID as described in this comment: https://github.com/HEP-KBFI/tth-htt/blob/85ec2368fbfacb2beeaa5444cb6fe5e562f4701c/src/RecoHadTauSelectorBase.cc#L178-L186
  • the functionality described in this comment is verified with a set of unit tests (test/unittests/test_hadTauSelection.cc);
  • it's possible to change the tau ID discriminant with -t/--tau-id option which takes either of the two values: dR03mva or deepVSj; example:

    ./test/tthAnalyzeRun_2lss_1tau.py -e 2017 -v 2019Sep06 -m default -t deepVSj

  • this functionality is facilitated by WP maps like these: https://github.com/HEP-KBFI/tth-htt/blob/85ec2368fbfacb2beeaa5444cb6fe5e562f4701c/test/tthAnalyzeRun_2lss_1tau.py#L77-L87
  • currently, the WPs are the same for both discriminant, but they can be easily changed in these maps;
  • the default WP still is dR03mva but can be easily changed here: https://github.com/HEP-KBFI/tth-htt/blob/85ec2368fbfacb2beeaa5444cb6fe5e562f4701c/python/runConfig.py#L179
  • changing the DeepTau ID here basically has the effect that all WPs corresponding to deepVSj key enter the python config files;
• jet->tau FR submission script is more robust:
  • one of the the following WPs has to be selected for the denominator: https://github.com/HEP-KBFI/tth-htt/blob/85ec2368fbfacb2beeaa5444cb6fe5e562f4701c/test/tthAnalyzeRun_jetToTauFakeRate.py#L20
  • numerators are automatically determined from a given denominator: https://github.com/HEP-KBFI/tth-htt/blob/85ec2368fbfacb2beeaa5444cb6fe5e562f4701c/test/tthAnalyzeRun_jetToTauFakeRate.py#L66-L71
• functionality tested by generating Python config files (C++ code already covered by the unit tests);
• all changes are implemented in ttH and HH repositories.