Updated on reconstruction of ProtoDUNE DP data Vyacheslav Galymov - - PowerPoint PPT Presentation

updated on reconstruction of protodune dp data
SMART_READER_LITE
LIVE PREVIEW

Updated on reconstruction of ProtoDUNE DP data Vyacheslav Galymov - - PowerPoint PPT Presentation

Updated on reconstruction of ProtoDUNE DP data Vyacheslav Galymov IP2I Lyon Matching in 3D problem Have been using the proper PDDP geometry, i.e., with the drift along Y and 3D matching was not failing completely (0 matchted


slide-1
SLIDE 1

Updated on reconstruction of ProtoDUNE – DP data

Vyacheslav Galymov IP2I Lyon

slide-2
SLIDE 2

Matching in 3D problem

  • Have been using the “proper” PDDP geometry, i.e., with the drift along

Y and 3D matching was not failing completely (0 matchted clusters between views)

  • Switched to rotated PDDP geometry (drift along X) and the 3D

matching started to work

  • Matching in 3D relies on the drift coordinate, which is X for SP, while it

is Y for DP with normal drift orientation

  • This is most likely the cause of failure of generating 3D tracks. The drift

coordinate is not correct unless the rotated geometry of ProtoDUNE DP is used (with drift in X)

  • Updated the “rotated” geometry to take into account the actual CRP

numbering (Geometry/gdml/generate_protodunedphase_v2.pl)

2

slide-3
SLIDE 3

Rotated geometry

3

e drift along is along X which is horizontal axis

Cryogenics Entrance DOOR HV FT 1 10

CRP1 CRP2 CRP4 (anodes 2x2)

1 2 3 4 5 6 7 8 9 10 10 11 11 12 12

Z Origin Y is up

slide-4
SLIDE 4

Event example

Many trajectories are broken up (missing hits, LEM borders … ) Visually could identify a number

  • f mismatches (a segment of
  • ne track in one view is

assigned to the wrong track in the other)  To be optimized

4

slide-5
SLIDE 5

LEM border effects

View X View Z These channels would be masked by ChannelStatus, but there would also be a gap on otherwise active channels in the

  • ther view due to the track crossing the

dead space

𝝂±

5

slide-6
SLIDE 6

Track breaks at LEM border

6

These channels are masked by channel status service In this view, the gap is too large and the track is broken

slide-7
SLIDE 7

Conclusions

  • For reconstruction to work still need to use rotated DP geometry

(drift along X)

  • The track reconstruction requires tuning to deal with LEM border

effects

  • Even at the level of a single events see a number of mismatches

between views

  • Needs to be fixed if one wants to get dQ/dx for example to look at

LEM gain

  • Ideally should be done with MC as well, but LEM borders were

never part of the simulation

  • Also the field map of the current PDDP drift field configuration is not

implemented

7