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

Removed asserts preventing fast re-recoes a la ECALELF #6556

Closed
wants to merge 1 commit into from

Conversation

shervin86
Copy link
Contributor

The removal of asserts should not hurt, but prevents fast re-recoes
@lgray and cms-phys-conveners-EGM should probably double check ad approve

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @shervin86 for CMSSW_7_3_X.

Removed asserts preventing fast re-recoes a la ECALELF

It involves the following packages:

DataFormats/EgammaCandidates

@cmsbuild, @nclopezo, @StoyanStoynev, @slava77 can you please review it and eventually sign? Thanks.
@lgray 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.

@slava77
Copy link
Contributor

slava77 commented Nov 22, 2014

@Sam-Harper
Sam, you should also get yourself added to the list of watchers of the egamma-related packages
you can do it at https://github.com/cms-sw/cmssw/issues/new

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

assert(ctfInfo.ctfTrack==(GsfElectron::core()->ctfTrack())) ;
assert(ctfInfo.shFracInnerHits==(GsfElectron::core()->ctfGsfOverlap())) ;
// assert(ctfInfo.ctfTrack==(GsfElectron::core()->ctfTrack())) ;
// assert(ctfInfo.shFracInnerHits==(GsfElectron::core()->ctfGsfOverlap())) ;
Copy link
Contributor

Choose a reason for hiding this comment

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

You should really "remove" them if this is the decision, not commenting them out.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

If I receive the green light I can do another pull request removing the lines.

                        Shervin

On Sun, 23 Nov 2014, StoyanStoynev wrote:

Date: Sun, 23 Nov 2014 02:00:00 -0800
From: StoyanStoynev notifications@github.com
Reply-To: cms-sw/cmssw
<reply+0045c225c004a1e368e80fd5885cca6f92c6443a95aab3cc92cf000000011089722
092a170ce013cd2ca@reply.github.com>
To: cms-sw/cmssw cmssw@noreply.github.com
Cc: shervin86 shervin@cern.ch
Subject: Re: [cmssw] Removed asserts preventing fast re-recoes a la ECALELF
(#6556)

@@ -42,8 +42,8 @@ GsfElectron::GsfElectron
setVertex(math::XYZPoint(te.positionAtVtx.x(),te.positionAtVtx.y(),te.positionAtVtx.z())) ;
setPdgId(-11_charge) ;
/if (ecalDrivenSeed())*/ corrections.correctedEcalEnergy = superCluster()->energy() ;

  • assert(ctfInfo.ctfTrack==(GsfElectron::core()->ctfTrack())) ;
  • assert(ctfInfo.shFracInnerHits==(GsfElectron::core()->ctfGsfOverlap())) ;
  • // assert(ctfInfo.ctfTrack==(GsfElectron::core()->ctfTrack())) ;
  • // assert(ctfInfo.shFracInnerHits==(GsfElectron::core()->ctfGsfOverlap())) ;

You should really "remove" them if this is the decision, not commenting them out.


Reply to this email directly or view it on GitHub:
https://github.com/cms-sw/cmssw/pull/6556/files#r20763338

Copy link
Contributor

Choose a reason for hiding this comment

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

I don't get it - what is the point of another PR?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ok, let me know if/what to do.

                        Shervin

On Mon, 24 Nov 2014, StoyanStoynev wrote:

Date: Mon, 24 Nov 2014 01:59:15 -0800
From: StoyanStoynev notifications@github.com
Reply-To: cms-sw/cmssw
<reply+0045c225d1ad8dbf71e46d0c9e820fecb03c52472fc680f692cf00000001108ac37
392a170ce013d16c9@reply.github.com>
To: cms-sw/cmssw cmssw@noreply.github.com
Cc: shervin86 shervin@cern.ch
Subject: Re: [cmssw] Removed asserts preventing fast re-recoes a la ECALELF
(#6556)

@@ -42,8 +42,8 @@ GsfElectron::GsfElectron
setVertex(math::XYZPoint(te.positionAtVtx.x(),te.positionAtVtx.y(),te.positionAtVtx.z())) ;
setPdgId(-11_charge) ;
/if (ecalDrivenSeed())*/ corrections.correctedEcalEnergy = superCluster()->energy() ;

  • assert(ctfInfo.ctfTrack==(GsfElectron::core()->ctfTrack())) ;
  • assert(ctfInfo.shFracInnerHits==(GsfElectron::core()->ctfGsfOverlap())) ;
  • // assert(ctfInfo.ctfTrack==(GsfElectron::core()->ctfTrack())) ;
  • // assert(ctfInfo.shFracInnerHits==(GsfElectron::core()->ctfGsfOverlap())) ;

I don't get it - what is the point of another PR?


Reply to this email directly or view it on GitHub:
https://github.com/cms-sw/cmssw/pull/6556/files#r20780745

@Sam-Harper
Copy link
Contributor

I'm still a little confused about this. Surely this is just checking you have the right core and if you dont, well bad things can happen. Why is it causing problems? Is the fast re-reco not fully making things?

@StoyanStoynev
Copy link
Contributor

I expect the question by Sam to be answered (I expected @lgray to comment earlier but he was likely busy).

@lgray
Copy link
Contributor

lgray commented Nov 25, 2014

@StoyanStoynev Yes, Monday was interesting. Anyway, this questions definitely needs to be answered since it is a basic sanity check in the normal reconstruction.

@StoyanStoynev
Copy link
Contributor

Is there any progress in addressing the question(s) raised?

@StoyanStoynev
Copy link
Contributor

ping

@shervin86
Copy link
Contributor Author

Sorry for the late answer.
I removed those asserts in my private code 2 years ago and always patched the GsfElectron module since then. I don't remember exactly why.
In any case this is not relevant. There is no reason to have asserts in the code, these are not protections but used only for debugging purpose. In any case they cause the crash in production...
I wonder why are we waiting for particular approval of this pull request.

                        Shervin

On Fri, 5 Dec 2014, StoyanStoynev wrote:

Date: Fri, 5 Dec 2014 09:02:00 -0800
From: StoyanStoynev notifications@github.com
Reply-To: cms-sw/cmssw
<reply+0045c225b24de175c5e77802ec9ea675f521a419a3059eaa92cf000000011099a70
892a169ce02f7a518@reply.github.com>
To: cms-sw/cmssw cmssw@noreply.github.com
Cc: shervin86 shervin@cern.ch
Subject: Re: [cmssw] Removed asserts preventing fast re-recoes a la ECALELF
(#6556)

ping


Reply to this email directly or view it on GitHub:
#6556 (comment)

@StoyanStoynev
Copy link
Contributor

On the reco part we were waiting the POG convener and RECO coordinator questions to be answered. That is - why this is causing problems at all? Even if you resolve the crash you may be hiding another problem because the crash can not be explained by this part of the code itself (as Lindsay said these were sanity checks).

@StoyanStoynev
Copy link
Contributor

@lgray @Sam-Harper Can this be discussed in one of the POG meetings and decide what to do?

@davidlange6
Copy link
Contributor

Closing this as it is definitely for 74x at this point

@shervin86 shervin86 deleted the GsfElectronFix branch February 25, 2015 09:26
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

7 participants