Home » Blogs » veprbl's blog

Zilong's cones vs Grant's regions cross-check on Run12 pp200 jet trees

Updated on Sat, 2017-02-25 20:46. Originally created by veprbl on 2017-01-01 21:36.

This was resolved here

Grant's tree implementation defines four regions wrt the leading jet: Towards, Away, Plus and Minus. One can realize that these four cover the full phi acceptance (with |eta|<1.0), so we can use that to access most tracks and towers in the event. I've used this to make my own implementation that constructs cone density from the data available in region UE trees. If we compare my result to Zilong's we will see:



We see a clear disagreement.
So let’s consider a printout of a single event.
 
Let:
  • R mean track or tower found in region using my algorithm
  • C mean track or tower from Zilong's trees cone
More specifically:
  • RP - from leading jet “Plus” region
  • RM - “Minus”
  • RT - “Toward”
  • RA - “Away”
  • C0 - Zilong’s “Plus” cone
  • C1 - Zilong’s “Minus” cone
 
Then one event will look like
 
RP track        phi=1.68503     eta=0.0458476   pt=0.245932
C0 track        phi=1.68503     eta=0.0458476   pt=0.245932
// these match

RP track        phi=1.72704     eta=-0.279223   pt=0.345209
C0 track        phi=1.72704     eta=-0.279223   pt=0.345209
// also ok

RP tower        phi=1.38614     eta=-0.225      pt=0.224021
C0 tower        phi=1.3861      eta=0.0310771   pt=0.229605
// eta is different! bad!

RP tower        phi=1.75545     eta=-0.075      pt=0.340511
C0 tower        phi=1.75548     eta=0.181936    pt=0.335894
// eta is different!

RM track        phi=-1.30528    eta=0.32941     pt=0.292396
C1 track        phi=-1.30528    eta=0.32941     pt=0.292396
// ok

RA track        phi=0.853263    eta=0.227293    pt=0.398568
C0 track        phi=0.853263    eta=0.227293    pt=0.398568
// ok
 
C0 tower        phi=0.917588    eta=0.0310761   pt=0.316608
// not found in regions
C1 tower        phi=-1.23191    eta=-0.178944   pt=9.842e-11
// not found in regions

In other printouts at a glance I see

  • tracks and towers from my implementation that are not present in Zilong's
  • tracks and towers present in Zilong's implementation that don't show up in mine
  • towers with pt like 9.81305e-11 in both implementations
»