CORRECTION DUNE-PRISM MEETING FEBRUARY 28 TH , 2019 Cristvo Vilela - - PowerPoint PPT Presentation

β–Ά
correction
SMART_READER_LITE
LIVE PREVIEW

CORRECTION DUNE-PRISM MEETING FEBRUARY 28 TH , 2019 Cristvo Vilela - - PowerPoint PPT Presentation

DATA-DRIVEN EFFICIENCY CORRECTION DUNE-PRISM MEETING FEBRUARY 28 TH , 2019 Cristvo Vilela INTRODUCTION Want to make a far detector prediction from near detector data, relying as little as possible on neutrino interaction model.


slide-1
SLIDE 1

DATA-DRIVEN EFFICIENCY CORRECTION

DUNE-PRISM MEETING FEBRUARY 28TH, 2019

CristΓ³vΓ£o Vilela

slide-2
SLIDE 2

INTRODUCTION

  • Want to make a far detector prediction from near

detector data, relying as little as possible on neutrino interaction model.

  • Near detector is much smaller than far detector and will

have limited efficiency for events with high hadronic energy.

  • Using MC to estimate near detector hadronic containment

efficiency introduces model dependence.

  • Try to calculate efficiency correction for selected events

at the near detector using the event geometry.

  • Ignoring lepton side of the event for now.

February 28 2019 DUNE-PRISM meeting 2

slide-3
SLIDE 3

GEOMETRIC EFFICIENCY CORRECTION

  • Start out with a selected event at the near detector.
  • Non-primary-lepton energy deposits in the LAr shown.

February 28 2019 DUNE-PRISM meeting 3

slide-4
SLIDE 4

GEOMETRIC EFFICIENCY CORRECTION

February 28 2019 DUNE-PRISM meeting 4

  • Randomly translate event within FV (blue) and rotate wrt average neutrino direction.
  • In this case, keeping x constant.
  • Not a good idea if we expect efficiency to change ~rapidly within a DUNE-PRISM OA slice and if

statistics are limited.

  • In future randomize x within OA slices and use all MC.
slide-5
SLIDE 5

GEOMETRIC EFFICIENCY CORRECTION

February 28 2019 DUNE-PRISM meeting 5

  • Repeat N times.
  • N = 1000
  • A little slow, but doable.
slide-6
SLIDE 6

GEOMETRIC EFFICIENCY CORRECTION

February 28 2019 DUNE-PRISM meeting 6

  • Efficiency for the event is:

π‘‚π‘žπ‘π‘‘π‘‘ π‘‘π‘π‘œπ‘’π‘π‘—π‘œπ‘›π‘“π‘œπ‘’ 𝑑𝑣𝑒

π‘’β„Žπ‘ π‘π‘₯𝑑

π‘‚π‘’β„Žπ‘ π‘π‘₯𝑑

slide-7
SLIDE 7

GEOMETRIC EFFICIENCY CORRECTION

February 28 2019 DUNE-PRISM meeting 7

  • Test method on on-axis near

detector events.

  • Works reasonably well.
  • Differences at high energy

probably from events that are never seen at the near detector.

  • For DUNE-PRISM prediction

will use far detector MC events to make up for those.

slide-8
SLIDE 8

GEOMETRIC EFFICIENCY CORRECTION

February 28 2019 DUNE-PRISM meeting 8

  • Efficiency correction

seems a little worse at edges of detector.

  • Need to verify with

more MC.

  • Might need to tighten

FV.

  • Or improve method.
slide-9
SLIDE 9

GEOMETRIC EFFICIENCY CORRECTION

February 28 2019 DUNE-PRISM meeting 9

  • Efficiency correction

seems a little worse at edges of detector.

  • Need to verify with

more MC.

  • Might need to tighten

FV.

  • Or improve method.

πΉπœ‰

𝑒𝑠𝑣𝑓 < 2 π»π‘“π‘Š

slide-10
SLIDE 10

WHAT NEXT

  • To figure out which far detector MC events need to be added to the

data-driven prediction, want to use the same method on far detector MC events:

  • Place far detector event randomly in imaginary near detector FV.
  • Throw translations and rotations to measure β€œnear detector geometric efficiency”

for each far detector event.

  • Then, when building the prediction loop over, near detector data events

and far detector MC events:

  • If near detector geometric efficiency > threshold, use near detector data event
  • else use far detector MC event.
  • Need to flesh out details, but I think basic idea should work.
  • Found way of accessing true energy deposits in the far detector MC

files.

  • Currently writing an art module to calculate β€œnear detector geometric

efficiency” for far detector events.

February 28 2019 DUNE-PRISM meeting 10