SUSY branches on CMSSW 9_4_7 (not backward compatible with 940) #16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This gets the SUSY code to work on CMSSW947, addressing the NanoAOD changes to the LeptonMVA. When working in CMSSW947, the corresponding LeptonMVA training is automatically loaded (i.e. we always take the LeptonMVA training from the NanoAOD configuration)
The commit "updated for TTHMVA in 947" is not backward compatible with CMSSW940, so it might be safer to have a new branch (CMSSW_9_4_7) in the central repository.
This is because the 940 IsoValueMapProducer.cc code does not create a PFIsoAll04 variable.
This commit includes the commit from my previous PR (#14), since that one has not been merged yet