ed - rtmda65/talks/seededrtcut_brussels_muon.pdfmatthias danninger september 22, 2010 brussels...

L2-Hitcleaning

Matthias Danninger

- ed - RT -

Matthias Danninger September 22, 2010 Brussels Collaboration Meeting 2

Overview

SeededRTCut x-check http://icecube.wisc.edu/~mda65/IC79/studies/seededRTCut.htm

→ what was done and how → choice of seed → choice of cut → choice of iterations → results corsika polygonato → results atm. neutrinos


Hitcleaning x-check

not all MCHits result in a DOMLaunch

number of physics hits, compared to MCTruth, in the InIceRawData is not 100%

more like 93% which is also taken as the possible 100% reference for the evaluation of the performance of the seededRTCut-cleaning

Two main variables for this x-check:

* physics ratio: number of physics-launches in selected seededRTCut-series

total amount of physics hits

* purity: number of physics-launches in selected seededRTCut-series

total number of launches in selected seededRTCut-series


ConfigurationsDatasets:

spice1 corsika dataset-4418the spice1 atm. neutrino dataset, numu-4337 (E ¹⁻ ) [too much high-E bias], and the quite outdated atm. neutrino dataset, numu-2488 (E ²) [better energy range]. ⁻

Seeds:COG of all HLC hits [used in online filtering L1]→every HLC hitCOG of the RT-cleaned HLC hits

Cuts:radius of distance-cut on the IceCube strings, R [fixed to 150m]

length of time window for launches on IceCube strings, T [1000ns or 2000ns]

radius of distance-cut on DeepCore strings, RDC [80m, 120m, 160m]

length of time window for launches on DeepCore strings, TDC [1000ns or 2000ns]

Iterations:

how often this RT cut should be applied if a new hit is found within the limits [2, 3, 4, 5]

The current online L1 settings: R=150m, T=1000ns, 2 iterations(seed = COG of all HLC hits).


Results (1/9)

Number of selected HLC

Number of selected DOMLaunches

Corsika polygonatoIncl. coincident µ


Results (2/9)Corsika polygonatoIncl. coincident µ


animation from Antonia H. talk



HLCcore All-HLC


Results (6/9) atm. neutrino (E ¹)⁻


Hitcleaning x-check – summaryseededRTCut-cleaning selects about 20-25% more physics hits than the so far used HLC-only series

the selected launch-series is of very high purity (~98-99%)

the COG as a seed (used so far) seems to be the least best choice

allHLC or HLCcore perform much better, but are also more time intensive for high-NChan events. For events of NChan<~40 should be no noticable difference

BUT it doesn't select 100% of the physics launches. These missed physics-launches could be(are) crucial for a veto like the DeepCore veto

there is of course still room for improvement in the method, but this cleaning clearly improves the selection of physics hits of an event

change for L2-processing some parameters (e.g. number of iterations), maybe(definately) the seed to COG of RT-cleaned HLC or allHLC?

as the numu E-1 dataset shows (as well as coincident corsika events) this cleaning also improves the physics selection for very high-NChan events

it is yet to be determined how this influences the llh-reconstruction (my guess is positive or not much at all)


We should decide together on L2-settings

The current online L1 settings: R=150m, T=1000ns, 2 iterations(seed = COG of all HLC hits).

Proposed L2 settings: R=150m, T=1000ns, 2/3 iter.(seed = HLCcore of HLC hits)DeepCore (same RT values)

Proposed L2 settings: FIRST: standard TW-cut (150/1000)

SECOND: R=150m, T=1000ns, 1 iter.

(seed = allHLC hits)DeepCore (same RT values)

Thank you

ed - rtmda65/talks/seededrtcut_brussels_muon.pdfmatthias danninger september 22, 2010 brussels...

Documents