3x1x1 root parser v3 december 4 2017
play

3x1x1 ROOT parser: v3 (December 4, 2017) Metadata (one entry per - PDF document

3x1x1 ROOT parser: v3 (December 4, 2017) Metadata (one entry per event): Run: run number Subrun: sub run number Event: event number in sub run (0-334) EventTimeSeconds: in Unix time EventTimeNanoseconds: nanoseconds elapsed


  1. 3x1x1 ROOT parser: v3 (December 4, 2017) Metadata (one entry per event): • Run: run number • Subrun: sub run number • Event: event number in sub run (0-334) • EventTimeSeconds: in Unix time • EventTimeNanoseconds: nanoseconds elapsed since ”EventTimeSeconds” • IsData: 1 for data, 0 for MC Hit variables: • NumberOfHits: number of hits per event (one entry per event) The following variables have one entry per hit and are stored in an array. Length of array = ”NumberOfHits”. • Hit TPC: TPC in which hit was found (always 0 for 3x1x1) • Hit View: view in which hit was found (view 0: 320 3m long channels, view 1: 960 1m long channels) • Hit Channel: channel in which hit was found (view 0: channel 0-319, view 1: channel 320 - 1279) • Hit PeakTime: peak time of the fitted hit (in ticks) • Hit ChargeSummedADC: ADC sum of the hit from first tick to last tick (both inclusive, in ADC · ticks) • Hit ChargeIntegral: Integral of the fitted hit from −∞ to + ∞ (in ADC · ticks) • !!! Bug: ”Hit ChargeSummedADC” and ”Hit ChargeIntegral” are both the integral of the fitted hit and thus have the same values for now !!! • Hit PeakHeight: height of the fitted hit (in ADC counts) • Hit StartTime: first tick of the hit (in ticks) • Hit EndTime: last tick of the hit (in ticks) � � � • Hit Width: FWHM/ 2 · 2 · ln (2) FWHM: Full width at half maximum of the fitted hit • Hit GoodnessOfFit: proportional to χ 2 /NDF of the fitted hit (absolute number to be checked) • Hit Multiplicity: Number of hits in that were fitted together with this hit • Hit TrackID: ID of the track to which the hit was assigned to (-1: not assigned to a track) • Hit ClusterID: ID of the cluster to which the hit was assigned to (-1: not assigned to a cluster) 1

  2. Cluster variables: • NumberOfClusters: number of clusters (one entry per event) The following variables have one entry per cluster and are stored in an array. Length of array = ”NumberOfClusters”. • ClusterID: ID of the cluster (first cluster: 1) • Cluster NumberOfHits: number of hits assigned to this cluster (sorted by cluster ID) • Cluster View: View in which cluster was found (view 0: 320 3m long channels, view 1: 960 1m long channels) • Cluster ChargeIntegral: Sum of all ”Hit ChargeIntegral” of the hits assigned to this cluster • Cluster ChargeIntegralAveragePerHit: ”Cluster ChargeIntegral”/”Cluster NumberOfHits fHits” • Cluster StartChannel: Channel in which the cluster hast its first hit (view 0: channel 0-319, view 1: channel 320 - 1279) • Cluster StartTick: ”PeakTime” of the first hit of the cluster (in ticks) • Cluster EndChannel: Channel in which the cluster hast its last hit (view 0: channel 0-319, view 1: channel 320 - 1279) • Cluster EndTick: ”PeakTime” of the last hit of the cluster (in ticks) • Cluster StartCharge: ”Hit ChargeIntegral” of the first hit of the cluster (in ADC · ticks) • Cluster StartAngle: angle at the start of the cluster for the view it was found in (in radian, from − π/ 2 to + π/ 2). 0: parallel to the charge readout plane (CRP), π/ 2: pointing downwards (negative drift direction), − π/ 2: pointing upwards (drift direction). • Cluster EndCharge: ”Hit ChargeIntegral” of the last hit of the cluster (in ADC · ticks) • Cluster EndAngle: angle at the end of the cluster for the view it was found in (in radian, from − π to + π ). 0: parallel to the charge readout plane (CRP), π/ 2: pointing downwards (negative drift direction), − π/ 2: pointing upwards (drift direction). 2

  3. Track variables: • NumberOfTracks: number of tracks (one entry per event) The following variables have one entry per track and are stored in an array. Length of array = ”NumberOfTracks”. • TrackID: ID of the track (first track: 0) • Track StartX: x position of the start point of the track • Track StartY: y position of the start point of the track • Track StartZ: z position of the start point of the track • Track StartDistanceToBoundary: Distance between start point of the track and to the closest active volume boundary • Track EndX: x position of the end point of the track • Track EndY: y position of the end point of the track • Track EndZ: z position of the end point of the track • Track EndDistanceToBoundary: Distance between end point of the track and to the closest active volume boundary • Track Theta: angle at the start of the track with respect to the z-axis (in radian, from 0 to + π , z-axis is parallel to the 3 meter long channels). 0 is in +z direction, π/ 2 perpendicular to z-axis, − π in -z direction. • Track Phi: angle at the start of the track in x-y plane (in radian, from − π to + π ). 0 is in +x direction (up), π/ 2 in +y direction and + π in -x direction (down). For negative angles, tracks point in -y direction. The y-axis is parallel to the 1 meter long channels. • Track Length: length of the track (in cm) The following variables have one entry per track and view and are stored in an array. Length of array = ”NumberOfTracks”*2. • Track PitchInViews: track pitch in both views (first view 0, then view 1, (in radian, from 0 to + π ) ) • Track NumberOfHitsPerView: number of hits in each view that are assigned to this track (first view 0, then view 1) The following variables have one entry per hit and are stored in an array. Length of array = ”NumberOfHits”. The array is sorted by ”Hit TrackID” and ”Hit View”. If a hit was not assigned to a track, the respective value is set to 0 by default. These hits are stored at the end of the array. • Track dEdx: dE/dx for each hit in the track (first for hits in view 0, then in view 1) (not calibrated yet!) • Track dQdx: dQ/dx for each hit in the track using the ”Hit ChargeIntegral” and correcting for the inclination of the track (first for hits in view 0, then in view 1) • Track HitX: position in x of each hit in the track (first for hits in view 0, then in view 1) • Track HitY: position in y of each hit in the track (first for hits in view 0, then in view 1) • Track HitZ: position in z of each hit in the track (first for hits in view 0, then in view 1) 3

  4. 3x1x1 geometry in LArSoft: 4

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend