L3FIP filters on the impact parameter significance of the tracks returned by the tool L3TIPTracker. It can filter on multiple tracks with the same
ip significance as well as total hits and SMT hits in XY and Z.
|
L3FPhysIP applies impact parameter significance cuts to a muon in the event. As input it takes 2 FILTERS - L3FIP and L3FMuon (central matched). The filter matches the track associated with the muon with one of the L3IPTrackPhysicsResults that has passed L3FIP. By applying IP cuts to the L3FIP filter that is input to the L3FPhysIP filter we can cut on the impact parameter significance of the muon. The reason for the obscure name is because eventually it could be applied to different physics objects including electron, jets etc.
|
L3FInvMass is an invariant mass filter. At present it only does 2 object invariant mass and takes 2 FILTERS as input.. It is a versatile filter and has 2 main modes of operation.
If "DoOppositeSign" is set to false:
if mass flags are set to zero - uses only the physics object variables
if mass flags are non zero - uses physics object kinematic variables and supplied masses
If "DoOppositeSign" is set to true:
MUST be L3TrackPhysicsResults or L3MuonPhysicsResults
MUST have masses non zero
if both threshold values are set to zero then it returns all opposite sign masses
Below are two plots to show L3FInvMass in action. It is used to find Phis so we do opposite sign and enter the kaon mass for the tracks. Looking at the data plot, we can estimate a loose mass window at 0.98->1.06, or a window of 0.08 centred on the Phi mass.
|
Below is a set of plots for the certification of p16. All rejections are wrt the trigger MT3_L2M0_MM3. To obtain these plots, I ran trigsim over run 188676 and selected events that passed MT3_L2M0_MM3. I also ran over a set of Bs->Dspi MC and selected MT3_L2M0_MM3. Data are the black points. MC are the red points. It is hoped that some of these triggers will run unprescaled at 60E30 which corresponds to a rejection of around 40 wrt MM3
|