Page History

...

Note that all the CTB variables have been redefined based on their definition found in the workbook. N.B for variables such as XtalRmsTkrCoreDoca, TkrSHRCalAngle, and TkrCalTrackDoca which are based on the merit variable CalTrackDoca in Pass8 this variable is for the first cluster and not the uber one. While the CalEdgeEnergy variable (which is also used to define CalEdgeEnergyRatio) is for the uber cluster, therefore there is a inconsistency for the Pass8 selection. We have looked into creating the CalEdgeEnergy variable for the first cluster and stumbled across the issue that the getEnergy() method from recon is different from that in the CalValsTool. The variables used for the BackSeal veto (i.e. Cal67Sum and Cal67Diff and CalLLRms ) are for the first cluster, the variable CalLLRms also used in the BackSeal veto is for the uber cluster therefore this condition needs to be fixed in order to make it consistent. And finally also CTBBestEnergy in Pass8 is for the first cluster.

...

veto TkrSideSeal: (CalDeltaEdgeEnergy < .75 || (CalDeltaEdgeEnergy < .95 - (30./(CalEdgeEnergy+20))^2 & CalEdgeEnergy < 300)) && CalDeltaEdgeEnergy < (1.1 - CalEdgeEnergy/200)

CTBCPFGamProb>0

filter nTkrFront: TkrNumTracks > 1 && Tkr1FirstLayer < 5 && (CTBTkrCoreCalDoca<40.56 || (CalXtalRatio<0.105 & EvtECalTransRms<3.45))

...

I took the recon files and created the CalEdgeEnergy variable for the first cluster to see if there was any impact on the selection. Unfortunately the recon files for v20r3p4 were somehow corrupt therefore in order to try this out I needed to use the recon files for the v19r4p1gr14 series. Below are the distributions for the Pass7 and Pass8. The statistics are limited (there are only 100 recon files available) thus it is hard to say anything however it looks like there is no substantial difference. I applied the same precuts as described above except the CTBCPFGamProb>0 because it removed too many background events and I wanted to see the overall effect of using the first cluster was.