-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Puppi isolation electrons mini aod rebased v2 #15722
Puppi isolation electrons mini aod rebased v2 #15722
Conversation
fix indentation
A new Pull Request was created by @ishvetso (Ivan Shvetsov) for CMSSW_8_1_X. It involves the following packages: DataFormats/PatCandidates @cmsbuild, @cvuosalo, @slava77, @monttj, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
@cmsbuild please test |
The tests are being triggered in jenkins. |
-1 Tested at: 293ba88 You can see the results of the tests here: I found follow errors while testing this PR Failed tests: UnitTests AddOn
I found errors in the following unit tests: ---> test runtestTqafExamples had ERRORS
I found errors in the following addon tests: cmsRun /build/cmsbuild/jenkins-workarea/workspace/ib-any-integration/CMSSW_8_1_X_2016-09-04-2300/src/PhysicsTools/PatAlgos/test/IntegrationTest_cfg.py : FAILED - time: date Mon Sep 5 03:58:41 2016-date Mon Sep 5 03:58:00 2016 s - exit: 16640 |
Shouldn't it be the same as the input for PAT Photon? process.egmPhotonPUPPIIsolation.srcToIsolate = cms.InputTag("reducedEgamma","reducedGedPhotons") The input for PAT photons is "gedPhotons" collection while the input for the value map is "reducedEgamma:reducedGedPhotons". Same for electrons. Regards, |
I also thought that it should be gedPhotons, but I have checked the dump of the miniAOD configuration and there reducedEgamma collection is the actual input source collection. |
@slava77 I'm trying to rebase -i as you requested to remove some irrelevant commits. I have started a new area and did and I'm getting some conflicts for some reason ...: When you have resolved this problem, run "git rebase --continue". should I fix that? I don't quite understand why this happens. |
On 9/5/16 8:29 AM, Ivan Shvetsov wrote:
try to follow the instructions, in case it's just for one or two commits. Given the long history of minor commits, which doesn't really describe
|
superseded by #15741 |
this is a rebase of #15628