Skip to content
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

Fix posftix and scheduled mode issue in the runMETUncertainty tool (Copy of the original #14606) #15616

Closed

Conversation

mmarionncern
Copy link

Identical to the original #14606 PR that was messed up when solving conflicts appeared during the holding time.

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @mmarionncern for CMSSW_8_0_X.

It involves the following packages:

PhysicsTools/PatAlgos
PhysicsTools/PatUtils

@cmsbuild, @cvuosalo, @slava77, @montjj, @davidlange6 can you please review it and eventually sign? Thanks.
@TaiSakuma, @imarches, @ahinzmann, @acaudron, @gpetruc, @rappoccio, @jdolen, @nhanvtran, @JyothsnaKomaragiri, @schoef, @ferencek, @mverzett, @mariadalfonso, @pvmulder this is something you requested to watch as well.
@slava77, @smuzaffar you are the release manager for this.

cms-bot commands are list here #13028

@slava77
Copy link
Contributor

slava77 commented Aug 26, 2016

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Aug 26, 2016

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/14749/console

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

@@ -8,7 +8,7 @@
'tauID("decayModeFinding") > 0.5 &'
' tauID("byLooseCombinedIsolationDeltaBetaCorr3Hits") > 0.5 &'
' tauID("againstMuonTight3") > 0.5 &'
' tauID("againstElectronVLooseMVA6") > 0.5'
' tauID("againstElectronVLooseMVA5") > 0.5'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should be switched back to MVA6
see #14596

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mmarionncern
it would be better to git rebase -i and remove the commit that edits this file

@cmsbuild
Copy link
Contributor

Pull request #15616 was updated. @cmsbuild, @cvuosalo, @slava77, @montjj, @davidlange6 can you please check and sign again.

@mariadalfonso
Copy link
Contributor

@slava77 removed the unneeded commit on the tau - config

@slava77
Copy link
Contributor

slava77 commented Aug 28, 2016

@cmsbuild please test
the comparisons got stuck, apparently

@cmsbuild
Copy link
Contributor

cmsbuild commented Aug 28, 2016

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/14785/console

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

@slava77
Copy link
Contributor

slava77 commented Aug 29, 2016

+1

for #15616 b5f0210

@slava77
Copy link
Contributor

slava77 commented Aug 29, 2016

hold

as with the previous (identical) iteration of this PR, there are changes in miniAOD which will go in once the rereco release is built.

@cmsbuild
Copy link
Contributor

Pull request has been put on hold by @slava77
They need to issue an unhold command to remove the hold state or L1 can unhold it for all

@slava77
Copy link
Contributor

slava77 commented Sep 6, 2016

-1
superseded by #15600
@mariadalfonso please double-check

@mariadalfonso
Copy link
Contributor

@slava77 @davidlange6
not sure this is #15616 superseeded by the #15600

@slava77
Copy link
Contributor

slava77 commented Sep 7, 2016

@mariadalfonso
can you check if it is?
Visually, the same code is in #15600
Also, I checked that 81X version of PhysicsTools/PatUtils/python/tools/runMETCorrectionsAndUncertainties.py (the only file modified here) is the same in #15600
This PR has fewer edits.

I see that this PR would have merge conflicts anyways
https://github.com/cms-sw/cmssw/compare/CMSSW_8_0_X...cms-met:MM_Fix_230516_v3_duplicata?expand=1

@mariadalfonso
Copy link
Contributor

@slava77
this PR (#15616) correspond to the #14608 that is in the 81 already
#15600 correspond to the #15565

i will check and solve the conflict (by today RECO meeting)

@slava77
Copy link
Contributor

slava77 commented Sep 7, 2016

On 9/7/16 4:53 AM, mariadalfonso wrote:

@slava77 https://github.com/slava77

this PR (#15616 #15616) correspond
to the #14608 #14608 that is in
the 81 already
#15600 #15600 correspond to the
#15565 #15565

i will check and solve the conflict (by today RECO meeting)

Thanks.

If any non-trivial edits from runMETCorrectionsAndUncertainties.py
are missing,
then something must be wrong, because they would be missing from 81X as well
(see my earlier message about runMETCorrectionsAndUncertainties.py being
the same in 81X and 80X+15600)


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#15616 (comment), or
mute the thread
https://github.com/notifications/unsubscribe-auth/AEdcbo6kV3ZA4-rbgOR7PvdC5pXRk0jMks5qnqWogaJpZM4Jt-UJ.

@mariadalfonso
Copy link
Contributor

@slava77 I confirm that this PR doens't add anything on top of the IB CMSSW_8_0_X_2016-09-07-1100. So good that is already closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants