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.

Sign up for GitHub

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

Jump to bottom

Huge log for phase2 workflows #22582

Closed
boudoul opened this issue Mar 12, 2018 · 16 comments
Closed

Huge log for phase2 workflows #22582

boudoul opened this issue Mar 12, 2018 · 16 comments
Labels
fully-signed reconstruction-approved upgrade-approved

Comments

@boudoul
Copy link
Contributor

boudoul commented Mar 12, 2018

Greetings,
The phase2 workflows (2023D21, 2023D17 etc...) are still exhibiting very long logs which make testing (and actually scrutinizing the logs ) very complicated . There is below a copy paste of a (small) fraction of the logs - Looks like it is on thePFTrackProducer:pfTrack . Could someone investigate if those are harmless and eventually fix or take actions ? I seem to remember a previous open issue on this but I'm not sure (and can't find it actually) .

Reducing the phase2 logs would be very appreciated . Thank you.

%MSG-w PFTrackTransformer: PFTrackProducer:pfTrack 12-Mar-2018 01:16:30 CET Run: 1 Event: 10
KF TRACK Reco track charge = 1, type = 1, Pt = 8.37763, P = 97.0849
R0 = 0.010947 Z0 = -1.50682
number of tracker measurements = 0
number of points total = 4
Traj point id = -1, layer = 0, Eta,Phi = -5.61786,-2.32022, X,Y = -0.00745722,-0.0080141, R,Z = 0.010947,-1.50682, E,Pt = 97.0849,8.37763
Traj point id = -1, layer = 1, Eta,Phi = -3.19199,-0.756139, X,Y = 1.81873,-1.71529, R,Z = 2.5,-30.3697, E,Pt = 97.085,8.37763
Traj point id = -1, layer = -1, Eta,Phi = 0,0, X,Y = 0,0, R,Z = 0,0, E,Pt = 0,0
Traj point id = -1, layer = -1, Eta,Phi = 0,0, X,Y = 0,0, R,Z = 0,0, E,Pt = 0,0
PROPAGATION TO THE ECAL HAS FAILED
%MSG
%MSG-w PFTrackTransformer: PFTrackProducer:pfTrack 12-Mar-2018 01:16:30 CET Run: 1 Event: 10
KF TRACK Reco track charge = 1, type = 1, Pt = 8.37763, P = 97.0849
R0 = 0.010947 Z0 = -1.50682
number of tracker measurements = 0
number of points total = 6
Traj point id = -1, layer = 0, Eta,Phi = -5.61786,-2.32022, X,Y = -0.00745722,-0.0080141, R,Z = 0.010947,-1.50682, E,Pt = 97.0849,8.37763
Traj point id = -1, layer = 1, Eta,Phi = -3.19199,-0.756139, X,Y = 1.81873,-1.71529, R,Z = 2.5,-30.3697, E,Pt = 97.085,8.37763
Traj point id = -1, layer = -1, Eta,Phi = 0,0, X,Y = 0,0, R,Z = 0,0, E,Pt = 0,0
Traj point id = -1, layer = -1, Eta,Phi = 0,0, X,Y = 0,0, R,Z = 0,0, E,Pt = 0,0
Traj point id = -1, layer = -1, Eta,Phi = 0,0, X,Y = 0,0, R,Z = 0,0, E,Pt = 0,0
Traj point id = -1, layer = -1, Eta,Phi = 0,0, X,Y = 0,0, R,Z = 0,0, E,Pt = 0,0
PROPAGATION TO THE HCAL ENTRANCE HAS FAILED
%MSG
%MSG-w PFTrackTransformer: PFTrackProducer:pfTrack 12-Mar-2018 01:16:30 CET Run: 1 Event: 10
KF TRACK Reco track charge = 1, type = 1, Pt = 5.51758, P = 66.1883
R0 = 0.0027203 Z0 = -1.56612
number of tracker measurements = 0
number of points total = 4
Traj point id = -1, layer = 0, Eta,Phi = -7.04876,-0.363833, X,Y = 0.00254223,-0.000968043, R,Z = 0.0027203,-1.56612, E,Pt = 66.1883,5.51758
Traj point id = -1, layer = 1, Eta,Phi = -3.22687,1.20216, X,Y = 0.900848,2.33205, R,Z = 2.5,-31.4513, E,Pt = 66.1884,5.51758
Traj point id = -1, layer = -1, Eta,Phi = 0,0, X,Y = 0,0, R,Z = 0,0, E,Pt = 0,0
Traj point id = -1, layer = -1, Eta,Phi = 0,0, X,Y = 0,0, R,Z = 0,0, E,Pt = 0,0
PROPAGATION TO THE ECAL HAS FAILED
%MSG
%MSG-w PFTrackTransformer: PFTrackProducer:pfTrack 12-Mar-2018 01:16:30 CET Run: 1 Event: 10
KF TRACK Reco track charge = 1, type = 1, Pt = 5.51758, P = 66.1883
R0 = 0.0027203 Z0 = -1.56612
number of tracker measurements = 0
number of points total = 6
Traj point id = -1, layer = 0, Eta,Phi = -7.04876,-0.363833, X,Y = 0.00254223,-0.000968043, R,Z = 0.0027203,-1.56612, E,Pt = 66.1883,5.51758
Traj point id = -1, layer = 1, Eta,Phi = -3.22687,1.20216, X,Y = 0.900848,2.33205, R,Z = 2.5,-31.4513, E,Pt = 66.1884,5.51758
Traj point id = -1, layer = -1, Eta,Phi = 0,0, X,Y = 0,0, R,Z = 0,0, E,Pt = 0,0
Traj point id = -1, layer = -1, Eta,Phi = 0,0, X,Y = 0,0, R,Z = 0,0, E,Pt = 0,0
Traj point id = -1, layer = -1, Eta,Phi = 0,0, X,Y = 0,0, R,Z = 0,0, E,Pt = 0,0
Traj point id = -1, layer = -1, Eta,Phi = 0,0, X,Y = 0,0, R,Z = 0,0, E,Pt = 0,0
PROPAGATION TO THE HCAL ENTRANCE HAS FAILED
%MSG
%MSG-w PFTrackTransformer: PFTrackProducer:uncleanedOnlyPfTrack 12-Mar-2018 01:16:30 CET Run: 1 Event: 10
KF TRACK Reco track charge = 1, type = 1, Pt = 8.37763, P = 97.0849
R0 = 0.010947 Z0 = -1.50682
number of tracker measurements = 0
number of points total = 4
Traj point id = -1, layer = 0, Eta,Phi = -5.61786,-2.32022, X,Y = -0.00745722,-0.0080141, R,Z = 0.010947,-1.50682, E,Pt = 97.0849,8.37763
Traj point id = -1, layer = 1, Eta,Phi = -3.19199,-0.756139, X,Y = 1.81873,-1.71529, R,Z = 2.5,-30.3697, E,Pt = 97.085,8.37763
Traj point id = -1, layer = -1, Eta,Phi = 0,0, X,Y = 0,0, R,Z = 0,0, E,Pt = 0,0
Traj point id = -1, layer = -1, Eta,Phi = 0,0, X,Y = 0,0, R,Z = 0,0, E,Pt = 0,0
PROPAGATION TO THE ECAL HAS FAILED
%MSG
%MSG-w PFTrackTransformer: PFTrackProducer:uncleanedOnlyPfTrack 12-Mar-2018 01:16:30 CET Run: 1 Event: 10
KF TRACK Reco track charge = 1, type = 1, Pt = 8.37763, P = 97.0849
R0 = 0.010947 Z0 = -1.50682
number of tracker measurements = 0
number of points total = 6
Traj point id = -1, layer = 0, Eta,Phi = -5.61786,-2.32022, X,Y = -0.00745722,-0.0080141, R,Z = 0.010947,-1.50682, E,Pt = 97.0849,8.37763
Traj point id = -1, layer = 1, Eta,Phi = -3.19199,-0.756139, X,Y = 1.81873,-1.71529, R,Z = 2.5,-30.3697, E,Pt = 97.085,8.37763
Traj point id = -1, layer = -1, Eta,Phi = 0,0, X,Y = 0,0, R,Z = 0,0, E,Pt = 0,0
Traj point id = -1, layer = -1, Eta,Phi = 0,0, X,Y = 0,0, R,Z = 0,0, E,Pt = 0,0
Traj point id = -1, layer = -1, Eta,Phi = 0,0, X,Y = 0,0, R,Z = 0,0, E,Pt = 0,0
Traj point id = -1, layer = -1, Eta,Phi = 0,0, X,Y = 0,0, R,Z = 0,0, E,Pt = 0,0
PROPAGATION TO THE HCAL ENTRANCE HAS FAILED
%MSG
%MSG-w PFTrackTransformer: PFTrackProducer:uncleanedOnlyPfTrack 12-Mar-2018 01:16:30 CET Run: 1 Event: 10
@cmsbuild
Copy link
Contributor

A new Issue was created by @boudoul boudoul.

@davidlange6, @Dr15Jones, @smuzaffar, @fabiocos can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

@Dr15Jones
Copy link
Contributor

assign reconstruction, upgrade

@cmsbuild
Copy link
Contributor

New categories assigned: upgrade,reconstruction

@slava77,@perrotta,@kpedro88 you have been requested to review this Pull request/Issue and eventually sign? Thanks

@kpedro88
Copy link
Contributor

These messages have been there forever. I suspect the underlying problem is the lack of effort to adapt ParticleFlow to the extended tracker and HGCal. This is an ongoing area of concern, so I am reluctant just to disable the messages and ignore the problem.

For private runs, you could suppress the messages in your config, following https://twiki.cern.ch/twiki/bin/view/CMSPublic/SWGuideMessageLoggerSetupExamples#Suppressing_Messages_From_Specif.

@VinInn
Copy link
Contributor

VinInn commented Mar 18, 2018

maybe it can be shorted to just
PROPAGATION TO THE E/HCAL ENTRANCE HAS FAILED
the rest of the information seems pretty redundant at this point...

@hatakeyamak
Copy link
Contributor

hatakeyamak commented Jul 18, 2019 •
edited
Loading

#27131
should have addressed this, which is merged in CMSSW_11_0_0_preX, so this can be closed?

@kpedro88
Copy link
Contributor

kpedro88 commented Jul 18, 2019 •
edited
Loading

@hatakeyamak thanks! To make sure I'm clear, your PR does two separate things:

  1. reduces the warning messages from PF
  2. allows (but does not enable) propagation to HF

Is that correct?

@hatakeyamak
Copy link
Contributor

Yes, for 1.

For 2, now we can get extrapolation of tracks to HF surface, but we are not enabling links of tracks and HF clusters yet. Such PR is still in progress. Stay tuned.

@kpedro88
Copy link
Contributor

kpedro88 commented Jul 18, 2019 •
edited
Loading

(signature removed based on comment below)

@hatakeyamak
Copy link
Contributor

hatakeyamak commented Aug 15, 2019 •
edited
Loading

Actually, we still have to deal with:

%MSG-e PFEGammaProducer: PFEGammaProducer:particleFlowEGamma 13-Aug-2019 11:13:22 CDT Run: 1 Event: 1
PFBLOCKALGO BUG!!!! Found a SuperCluster in a block by itself!
%MSG

so we can keep this issue alive for now. I think it comes from SC from HGCAL, but the fact that HGCAL's PFClusters don't go into PFBlocks cause this message. If this can be confirmed, I think this can be addressed by (1) suppress this message when such SC comes from HGCAL, or (2) prevent SC from HGCAL from going into PFBlocks.

@bendavid @guitargeek @jpata

@hatakeyamak hatakeyamak mentioned this issue Aug 15, 2019
Merged
@hatakeyamak
Copy link
Contributor

With the convergence of the above PR #27785 I think we can consider this issue is resolved.

@hatakeyamak
Copy link
Contributor

Not sure who needs to sign it off to make it closed..

@kpedro88
Copy link
Contributor

kpedro88 commented Sep 6, 2019

+upgrade

@hatakeyamak
Copy link
Contributor

I guess reco also needs to sign it off.

@slava77
Copy link
Contributor

slava77 commented Sep 6, 2019

+1

I checked PU200 wf 20634.0 (D41 ttbar): before this PR [in CMSSW_11_0_X_2019-09-04-1100] there are about 120 warnings per event PFBLOCKALGO BUG!!!! Found a SuperCluster in a block by itself!. After this PR [in CMSSW_11_0_0_pre7] these warnings are gone.
There are no PF-related reco warnings based on a pattern.

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 6, 2019

This issue is fully signed and ready to be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
fully-signed reconstruction-approved upgrade-approved
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@Dr15Jones @smuzaffar @VinInn @cmsbuild @kpedro88 @slava77 @boudoul @hatakeyamak