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

Revert new cpe #5581

Merged
merged 2 commits into from Sep 28, 2014
Merged

Revert new cpe #5581

merged 2 commits into from Sep 28, 2014

Conversation

nickmccoll
Copy link
Contributor

This PR fixes the issues described here: https://hypernews.cern.ch/HyperNews/CMS/get/relval/3159/18/1.html

It changes the default strip CPE to the original version due to an unexpected drop in tracking efficiency.

Nickolas added 2 commits September 26, 2014 06:29
…NewCPE

Conflicts:
	RecoLocalTracker/SiStripRecHitConverter/python/StripCPEfromTrackAngle_cfi.py
@cmsbuild
Copy link
Contributor

A new Pull Request was created by @nickmccoll for CMSSW_7_2_X.

Revert new cpe

It involves the following packages:

RecoLocalTracker/SiStripRecHitConverter

@cmsbuild, @nclopezo, @StoyanStoynev, @slava77 can you please review it and eventually sign? Thanks.
@forthommel, @yduhm, @GiacomoSguazzoni, @gbenelli, @rovere, @VinInn, @jlagram, @gpetruc, @cerati, @threus, @venturia 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.
@nclopezo you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

@cerati
Copy link
Contributor

cerati commented Sep 26, 2014

This PR fixes the issues described here: https://hypernews.cern.ch/HyperNews/CMS/get/relval/3159/18/1.html

@StoyanStoynev
Copy link
Contributor

@nickmccoll please provide a proper description to the PR.

@cerati
Copy link
Contributor

cerati commented Sep 26, 2014

Hi @StoyanStoynev, which other information do you need? This PR just reverts one parameter that is responsible for the differences spotted in validation of pre6 (see link above)

@StoyanStoynev
Copy link
Contributor

@cerati You are not saying the current description which is "No description provided." is the proper one, are you? We need these for documentation purposes (at least). One can refer to the PR that is reverted and give link to the reasoning (the one in the comment). It is good to actually summarize the reasoning and to say what the expected effect from the PR is.

@cerati
Copy link
Contributor

cerati commented Sep 26, 2014

I guess only Nick has access to the description field, if this is what is needed. This PR reverts 5151 (keeping the code in release, it will be used later on, after more tests/developments are done). Please start the review process.

@StoyanStoynev
Copy link
Contributor

I am trying to merge this PR with the latest IB, CMSSW_7_2_X_2014-09-26-0800, and I get
450 files changed, 20362 insertions(+), 66485 deletions(-)
Certainly not right. What is the PR based on, can you try yourself with the latest (available) IB?

@cmsbuild
Copy link
Contributor

@slava77
Copy link
Contributor

slava77 commented Sep 26, 2014

@VinInn @cerati @rovere
sigh.
How did it happen that the incremental prevalidation was showing an improvement without a loss in efficiency?

Were there any other changes (like to the MTV that would make the validation/signal association sensitive to the hit uncertainties)?

@VinInn
Copy link
Contributor

VinInn commented Sep 26, 2014

On 26 Sep, 2014, at 4:55 PM, Slava Krutelyov notifications@github.com wrote:

@VinInn @cerati @rovere
sigh.
How did it happen that the incremental prevalidation was showing an improvement without a loss in efficiency?
nobody looked at qcd3TeV

@slava77
Copy link
Contributor

slava77 commented Sep 26, 2014

@Martin-Grunewald
Martin, after all, what is the current selection in the HLT configurations for this parameter?
Was it all left to use the legacy?
(at some point I got a feeling that one of the last changes in pre7 was going to start using it).
Please clarify

@slava77
Copy link
Contributor

slava77 commented Sep 26, 2014

I guess I learned my lesson: better follow the policy of no tracking changes in the last open pre.

@slava77
Copy link
Contributor

slava77 commented Sep 27, 2014

+1

for #5581 fd72d91

tested in CMSSW_7_2_X_2014-09-24-1400 (test area test5581; it was more convenient to test in an older area)

This seems like a case of Le mieux est l'ennemi du bien.
So, reverting to the good old setup sounds more appropriate for 72X.

What are we going to do in 73X?
I could guess that we should keep the new CPE in 73X and try to improve downstream, in places where the problems for efficiency arise.

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_2_X IBs unless changes (tests are also fine). @nclopezo can you please take care of it?

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_2_X IBs unless changes (tests are also fine). @nclopezo can you please take care of it?

davidlange6 added a commit that referenced this pull request Sep 28, 2014
@davidlange6 davidlange6 merged commit bf5a6f3 into cms-sw:CMSSW_7_2_X Sep 28, 2014
@nickmccoll nickmccoll deleted the revertNewCPE branch February 1, 2015 17:32
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

8 participants