Fork me on GitHub

Opened 4 years ago

#1470 new Bug

Inconsistency of reading the constituents in jets

Reported by: physwei Owned by:
Priority: critical Milestone:
Component: Delphes code Version: Delphes 3
Keywords: pileup, constituents Cc:

Description

Dear Delphes Experts,

I want to collect the constituents information in jets for my analysis.
I am now using the delphes cards containing Pile-Up module: https://github.com/physwei/mine/blob/main/Phase1_PU.tcl
But when I tried to analysis the constituents just as what Example3.C did, there are many unnatural constituents appear.

My code for doing the analysis: https://github.com/physwei/mine/blob/main/ReadCon.C
Take the first jet in event 59 for example, I would have the following output

Event: 59
	Jet ID: 0
	Jet Eta: 0.598167, Phi:  0.25752, PT: 173.934
			    	Eta 	Phi 	PT
			Track: 0.245222 0.417082 0.986932
			Track: 0.408004 -0.0727779 0.764108
			Track: 1.90811 1.73767 0.680793
			Tower: -4.75821 0.232558 0.687901
			Track: 1.86033 1.35919 0.508102
			Tower: 0.856965 0.395502 7.01609
			Track: 0.814268 0.121829 3.54285
			Tower: 4.07237 1.53389 2.27872
			Track: 0.808913 0.142568 3.22003
			Track: 0.839334 0.306118 4.36746
			Track: 0.563875 0.011135 2.93563
			Track: 0.39865 0.0672844 1.24138
			Track: 0.548672 0.035585 0.916644
			Tower: 4.02643 -3.06126 1.34896
			Track: 0.044262 1.90452 0.644657
			Track: 0.629721 0.120887 5.36694
			Tower: 3.37522 2.16905 2.72275
			Track: 0.518644 0.519124 1.64658
			Track: 2.30687 -2.48965 0.518431
			Track: 2.04966 -1.13611 1.94719
			Track: 0.549516 0.467099 2.33789
			NULL
			NULL
			Track: 1.89153 2.56912 1.04446
			Tower: 2.15248 -0.651266 2.32272
			Track: 2.29251 -2.93717 0.451199
			Tower: 0.93107 2.80353 5.20706
			Track: 0.473904 0.352376 7.38676
			Track: 0.50112 0.36816 6.90915
			Track: 0.553567 0.275286 4.88225
			Track: 0.55576 0.291162 7.63721
			Tower: 4.01444 -0.558368 1.7521
			Track: 0.554935 0.323364 5.97301
			Track: 0.515639 0.304039 6.53981
			NULL
			Track: 0.524969 0.34136 14.1512
			Track: 0.520682 0.325347 33.7557

We can see there are some towers or tracks are supposed not to be included in the jet due the high Delta R.
But if I only read the 59th event instead of looping over the entries (https://github.com/physwei/mine/blob/main/ReadCon_single.C), I will get the following result.

Event: 59
	Jet ID: 0
	Jet Eta: 0.598167, Phi:  0.25752, PT: 173.934
			    	Eta 	Phi 	PT
			Track: 0.245222 0.417082 0.986932
			Track: 0.408004 -0.0727779 0.764108
			NULL
			NULL
			NULL
			Tower: 0.856965 0.395502 7.01609
			Track: 0.814268 0.121829 3.54285
			NULL
			Track: 0.808913 0.142568 3.22003
			Track: 0.839334 0.306118 4.36746
			Track: 0.563875 0.011135 2.93563
			Track: 0.39865 0.0672844 1.24138
			Track: 0.548672 0.035585 0.916644
			NULL
			NULL
			Track: 0.629721 0.120887 5.36694
			NULL
			Track: 0.518644 0.519124 1.64658
			NULL
			NULL
			Track: 0.549516 0.467099 2.33789
			NULL
			NULL
			NULL
			NULL
			NULL
			NULL
			Track: 0.473904 0.352376 7.38676
			Track: 0.50112 0.36816 6.90915
			Track: 0.553567 0.275286 4.88225
			Track: 0.55576 0.291162 7.63721
			NULL
			Track: 0.554935 0.323364 5.97301
			Track: 0.515639 0.304039 6.53981
			NULL
			Track: 0.524969 0.34136 14.1512
			Track: 0.520682 0.325347 33.7557

Now the weird constituents all disappear.

This inconsistency also occurred if I set MeanPileUp 50.
But it didn't occur if I use the default delphes card.

The only difference between these two codes is merely the existence of the for loop.
Is this have something to do with the configuration card or the analysis code?

Every advice or suggestion is highly appreciated. Many thanks.

Best Regards,
physwei

Change History (0)

Note: See TracTickets for help on using tickets.