Closed pieterdavid closed 6 years ago
Build triggered. sha1 is merged.
Build started sha1 is merged.
Build finished.
Build triggered. sha1 is merged.
Build started sha1 is merged.
Build finished.
I went through the diffs...
For unit_tests_data.py
the differences are minor: all scale factors gone (I removed them), electron_expectedMissingInnerHits
, (fat)jet_pfDeepCSVJetTags_probcc
(it seems not to be there in this version of the deepcsv) and muon_isMedium2016
. The former and latter will probably be needed still, so I can put them back easily. There are also differences in jet_pfDeepCSVJetTags_probc
(maybe the merged probc
and probcc
?), and in the electron IDs because I removed them... maybe in hindsight I shouldn't have.
For unit_test_mc_with_db.py
the same, plus the PU weights which I also removed.
For unit_test_mc.py
there are more differences... I turned off the electron smearing and regression (the recipes changed, see this twiki, I didn't get to implementing that).
Also the jet, jet systematic variation and MET branches changed. For the former two I suppose that would be because we pick up newer calibrations/recipes somehow, for the MET I'm reasonably certain (I saw code changes that needed the config to be adjusted). Does that make sense?
the updateremotes
script is just perfect :) thanks for the other fixes !
Do you know why Jenkins fails ? Is it just the outdated ref trees ?
I changed the definition of the target branch, so reopening as a new PR, https://github.com/cp3-llbb/Framework/pull/284
I checked out the Framework in CMSSW_9_4_9, removed everything that said 80X or 'Moriond17' etc., and tried to make things run... so there will be differences, and I may have been too enthusiastically removing things in some places - my main aim was to provide a "clean" starting point, but feel free to point out if something doesn't make sense.
Anticipating a few questions:
cms.Task
to be associated with the process or path for eachedm::EDProducer
. This required quite a bit of trial-and-error with redoJEC etc., but the tests should run now