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

add MET receipe #6994

Merged
merged 6 commits into from Jan 14, 2015
Merged

add MET receipe #6994

merged 6 commits into from Jan 14, 2015

Conversation

TaiSakuma
Copy link
Contributor

The MET group is planning to close the MET recipe by integrating it into either the CMSSW releases or the PAT recipes [https://github.com/cms-met/issues/1].

This PR contains the commits in the current MET recipe. With this PR in the CMSSW, we can close the MET recipe for 5_3_X.

The commit TaiSakuma@ac3814e?diff=split edits a file under DataFormats/METReco but doesn't change the data format. It only adds friend operators and won't require to update the checksum. I am not sure if that is ok.

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @TaiSakuma (Tai Sakuma) for CMSSW_5_3_X.

add MET receipe

It involves the following packages:

DataFormats/METReco
JetMETCorrections/Type1MET
RecoMET/METFilters

@nclopezo, @monttj, @cmsbuild, @StoyanStoynev, @slava77, @vadler can you please review it and eventually sign? Thanks.
@rappoccio, @ahinzmann, @mmarionncern, @nhanvtran, @schoef, @mariadalfonso this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
@smuzaffar you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

@slava77
Copy link
Contributor

slava77 commented Dec 23, 2014

It would help to rebase on top of the latest release/IB in 53X.

the first commit on the list is in 53X since Feb, with #2402

@cmsbuild
Copy link
Contributor

@slava77
Copy link
Contributor

slava77 commented Dec 25, 2014

about
JetMETCorrections/Type1MET/plugins/CorrectedCaloMETProducer2.cc and JetMETCorrections/Type1MET/plugins/CorrectedPFMETProducer2.cc:
are the equivalents present in 74X release?
I see something similar in AddCorrectionsToCaloMET and AddCorrectionsToPFMET in 74X.
Are these *2 names just historical specific for 53X?

significance=0.;
CorrMETData(const CorrMETData& corr) : mex(corr.mex), mey(corr.mey), sumet(corr.sumet), significance(corr.significance) { }

CorrMETData& operator+=(const CorrMETData& rhs)
Copy link
Contributor

Choose a reason for hiding this comment

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

these have a pretty long history
https://hypernews.cern.ch/HyperNews/CMS/get/pkgAnnounce/137777.html
We've integrated quite a bit of analysis level code in 53X since then; I guess that was a bad timing back in Feb 2013.

@monttj
Copy link
Contributor

monttj commented Jan 13, 2015

+1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_5_3_X IBs unless changes (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar, @ktf

@davidlange6
Copy link
Contributor

+1

@TaiSakuma
Copy link
Contributor Author

This PR has been merged. But I will write the answer to the question about these two files for the record.

JetMETCorrections/Type1MET/plugins/CorrectedCaloMETProducer2.cc
JetMETCorrections/Type1MET/plugins/CorrectedPFMETProducer2.cc

These two files were originally merged to CMSSW_6_2_0_pre5. The addition of these two files were published in CmsTC and approved in March 2013. This was the task generalize MET correction (1st step) described on CMS.METDevelopmentPlan.

Later in CMSSW_7_0_0_pre11, these two files were renamed respectively

JetMETCorrections/Type1MET/plugins/AddCorrectionsToCaloMET
JetMETCorrections/Type1MET/plugins/AddCorrectionsToPFMET

with the PR #1823.

This PR used the original names because this branch has been being used by many users and renaming them would break many configuration files already being used.

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