1 / 6

P0D Reconstruction Systematic Error Estimation

P0D Reconstruction Systematic Error Estimation. Norm Buchanan, David Connick , Eric Conrad, Fahmida Khana m. First Draft of Plan.

althea
Download Presentation

P0D Reconstruction Systematic Error Estimation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. P0D Reconstruction Systematic Error Estimation Norm Buchanan, David Connick, Eric Conrad, Fahmida Khanam

  2. First Draft of Plan Time is of the essence so we want to get reasonable estimates of trackand shower reconstruction systematic uncertainties as well as systematics for particle identification. This purpose of this presentation is to throw out ideas and get feedback – our timescale won’t allow fishing expeditions so we have to make our effort count! Approach for track and shower systematics • Identify subset of reconstruction parameters that contribute measurably to analysis • Determine what level of “smearing” of parameters is reasonable • Adjust parameters of interest and look at effect on MC/data difference after reprocessing (running p0dRecon). Question: what sample size is reasonable? Approach for PID systematics • Want to determine the effect of likelihood parameter variation on outputs (defined in OAAnalysis DST – so less overhead to study) • Were studies like this performed when constructing likelihoods?

  3. Reconstruction Parameters < p0dRecon.Cycle.MinCycleHits = 10 > Minimum hits for a cycle to be saved < p0dRecon.Cycle.TimeWindow = 30 ns > Minimum Hits must be in a time window < p0dRecon.Cycle.MinCleanHits = 5 > Minimum number of cleaned hits < p0dRecon.Clean.TimeCut = 30.0 ns > < p0dRecon.Clean.DistCut = 10.0 cm > < p0dRecon.Clean.LowQDistCut = 3.5 cm >< p0dRecon.Clean.HighQThreshold = 15.0 > < p0dRecon.Clean.LowQThreshold = 7.0 > < p0dRecon.Tracking.MinimumHits = 4 > Minimum hits in a track. < p0dRecon.Tracking.MinimumLength = 69 mm > Minimum length of a track. < p0dRecon.Tracking.RoadFollowing = 1 > Road following if non-zero < p0dRecon.Tracking.RoadWidth = 60 mm > The width of the road. < p0dRecon.Tracking.RoadAngle = 0.15 rad > The width of the road. < p0dRecon.Tracking.LayerHitSeparation = 40 mm > < p0dRecon.Tracking.MaxCollectedHits = 3 > Max hits out of road added to layer < p0dRecon.Tracking.ExtensionLength = 4 > < p0dRecon.Tracking.ExtensionWidth = 40 mm > < p0dRecon.Tracking.SaveSeeds = 1 > Debug seed tracks if non zero. < p0dRecon.Tracking.Hough.MinimumHits = 4 > Minimum hits collected by Hough. < p0dRecon.Tracking.Hough.AngularBinSize = 1.8 deg > < p0dRecon.Tracking.Hough.AngularOversampling = 2 > < p0dRecon.Tracking.Hough.RadialBinSize = 25 mm > < p0dRecon.Tracking.Hough.RadialOversampling = 3 >

  4. Reconstruction Parameters <p0dRecon.TrackFit.Select.LowP0DuleCountCut = 4 > < p0dRecon.TrackFit.Select.HighP0DuleCountCut = 8 > < p0dRecon.TrackFit.Select.HitsInP0Dule2D = 6 > < p0dRecon.TrackFit.Kalman.ProcessNoise = 700 > < p0dRecon.TrackFit.Parametric.FitWindowLength = 25 cm > Fit window length < p0dRecon.TrackFit.Parametric.FitHits = 10 > Minimum hits in fit window. < p0dRecon.Expand.Merging.ConeAngle = 0.2 rad > < p0dRecon.Expand.Merging.ConeFraction = 0.5 > < p0dRecon.Expand.Merging.Separation = 100 mm > < p0dRecon.Expand.Merging.MaxNodes = 7 > < p0dRecon.Expand.AddHits.SideSeparation = 40 mm > < p0dRecon.Expand.AddHits.ProjectionLength = 200 mm > < p0dRecon.Expand.AddHits.ProjectionResidual = 40 mm > < p0dRecon.Attenuation.LongComponent = 508.1 cm > < p0dRecon.Attenuation.LongFraction = 0.69 > < p0dRecon.Attenuation.ShortComponent = 51.8 cm > < p0dRecon.Attenuation.Reflectivity = 0.80 > < p0dRecon.ChargedPart.Neighborhood = 8.0 cm > < p0dRecon.Vertex.MaxTimeDiff = 40 ns > Max time between tracks in a vertex < p0dRecon.Vertex.MaxXYSigma = 50 cm > Max uncertainty in a pairwise vertex < p0dRecon.Vertex.MaxZSigma = 50 cm > Max uncertainty in a pairwise vertex < p0dRecon.Vertex.MaxSeparation = 20 cm > Max distance between combined vertices < p0dRecon.Shower.Cluster.LineSpacing = 1.7 cm > < p0dRecon.Shower.Cluster.Weighting = 0.25 > < p0dRecon.Shower.Cluster.Oversampling = 4 > < p0dRecon.Shower.Cluster.MinimumPoints = 5 >

  5. Reconstruction Parameters < p0dRecon.Shower.Vertex.ConstraintLength = 100 cm > < p0dRecon.Shower.Vertex.ConstraintClose = 10 cm > < p0dRecon.Shower.Vertex.ConstraintFar = 20 cm > < p0dRecon.MuonDecayTag.TimeCut = 100.0 ns > < p0dRecon.MuonDecayTag.XYCut = 30.0 cm > < p0dRecon.MuonDecayTag.ZCut = 30.0 cm > < p0dRecon.FullSpill.NumberOfBunches = 15 > < p0dRecon.FullSpill.BunchLength = 58.0 ns > < p0dRecon.FullSpill.BunchWindow = 100.0 ns > < p0dRecon.FullSpill.BunchSeparation = 350.0 ns > < p0dRecon.FullSpill.NumberOfCycles = 23 > < p0dRecon.FullSpill.IntegrationWindow = 241.0 ns > < p0dRecon.FullSpill.ResetTime = 50.0 ns > < p0dRecon.FullSpill.CycleLength = 291.0 ns > < p0dRecon.Control.ChargedShowerSeparation = 1 > < p0dRecon.Control.ShowerVertexReconstruction = 1 > < p0dRecon.VetoForTPC.MinimumHits = 4 > < p0dRecon.VetoForTPC.TimeWindow = 100 ns > < p0dRecon.VetoForTPC.ChargeCut = 7 > < p0dRecon.PID.PDFVersion = p0dRecon-v7r3 >

  6. Status Machinery in Place We are using p0dRecon v7r5 for our studies Samples Data: equivalent set of Run1+Run2 data to Glenn’s list (~4E19 POT) MC: MCP4 Spin B neut MC (water) reco files (100 files or ~5E19 POT) Questions/Comments 1. It would be very helpful to know how parameters were chosen – no P0D reco technical write-up currently exists. Is there any information on how parameters were chosen? 2. Are the parameters chosen so far reasonable – have we missed any obvious choices? Any and all suggestions are welcomed!

More Related