2009 cascade filter proposal - desy · high disk memory high space consumption of 7 tb : for one...

2009 Cascade Filter Proposal

Eike Middell and Sebastian Panknin

DESY Zeuthenand Humboldt University of Berlin

2008-12-05 / Group Meeting

Eike Middell and Sebastian Panknin (DESY and HU) 2009 Cascade Filter Proposal Group Meeting 1 / 17

Outline

1 Filter Proposal Time at DesyDesign of the filterOrganisation at DesyFeature Extractor Settings

2 Cascade Filter 2009Filter IdeaOptimized Settings


The Pole Filter Script

JEBJoint Event Builder

Script Design at the PoleEvents may be interesting for many filters and some filters will usesimilar variables:

all modules run over all eventsa module may refuse a specific event (precondition not fulfilled)the filter modules tag the events, if they pass the filterevents without any tag are rejected

different filters can use same modules (in different ways)it is helpful to have the whole filter script


Requirements for a Proposal

TFT Board RequestAll filter proposal have to fulfill certain standards:

show data, MC agreement for IC40show cut variables for IC60decide between different settings and variablescalculate performance for IC60bandwidth estimation

same (retriggered) datasets for most groupssimilar script to calculate variablessome settings are the same (Feature Extractor)


Organisation

CooperationLet’s work together, because:

same data sets neededsame scripts can be usedeasier to compare results

The OFU people are also interested in a online filter study.

Eike Sebastian Robert F. and Anna F.

processing retriggering cut variables

study cascade filter FE threshold OFU


Resource UsageBatch SystemAbout 500 CPUh were used forvariable calculation:

High Disk MemoryHigh space consumption of7 TB:

for one setting: about500 GB

datasets: about 100 GBoutput files:

I hdf files: 700 MBI root files: 2 GBI i3 files: 97 GB

very full i3 filesbetter save than sorry

Space will be given free starting next week.


Used Datasets

DatasetsMinimal triggered IC80 simulation (V02-02-09):

dataset (IC40): 111310single muon corsika: 1516double muon corsika: 1511triple muon corsika: 1550νe MC: 1568νµ MC: 1560

each 100 up to 200 files available in Zeuthenretriggered to IC40 and IC60


What is the ADCThreshold

threshold is used for chargecalculationfor multi peak reconstructionthreshold of 1 corresponds to thehardware discriminator

old setting was 0.4new (proposed) setting is 1.0

A scratch of two pulses:the 0.25 PE pulse

defines the 1.0 FEthreshold.


Effect on Pulse Charge

Charge per Pulse:only for the 1.0 threshold clear peak at 1.

many pulses are split with lower threshold.Eike Middell and Sebastian Panknin (DESY and HU) 2009 Cascade Filter Proposal Group Meeting 9 / 17

Effect on Nsth

number of pulses Nhit:very sensitive on settingtotal charge of event Qevent:quite robustnumber of channels Nchan:per definition (number of DOMlaunches) independentnumber of modules withpulses NOM:a small dependence onthresholds


Cascade Filter 2009


Cascade Filter 2008: ToI EvalRatio > 0.12 and LineFit Velocity < 0.13 Sebastian's IC40 Test: 1204.3 Hz 17.7 Hz → BG passing: 1.5%, nue E2 passing: 70.3 %

Cascade Filter 2009: 16 (+ 3) additional strings adjust filter to keep rate at about 17 Hz (eventually include some track fit zenith)

Overview Cascade Fiter

New Settings FeatureExtractor

ADCThreshold 0.4 1.0 (influence on NHits)→ NewDiscThreshold: True

(use new routine to estimate discriminator threshold,data run has to be processed with False)

LineFit: use only FirstLeadingEdge

LineFit doesn't weight DOM with charge but with #pulses reduce influence of Nhits

ToI: Loose Nchannel > 8 to consider StringTrigger events?

Use coincified pulses in LineFit and ToI?

ADCThreshold

no impact on nchannel small impact on charge huge influence on #pulses 1.0 setting physically preferred (histogram of pulse

charges peaked at 1pe Sebastian's Wikipage)→

influence on final efficiency not totally understood

FilterVariables (2008 Filter Settings)

ToI Evalratio

Left: without DiscThreshold Right: with DiscThreshold

Linefit Vel.


FilterVariables (2008 Filter Settings)

FilterVariables

Gulliver TrackFit Zenith


Rates IC40

Last year: 1140.7 Hz Corsika: 1107 Hz Data: 1076 Hz

IC60 Corsika: 1611 Hz

Last year after filter: 17 Hz

2009 Goal: Suppress Background to 1 %

Reco Success percentages(IC60) (preliminary):

nue ToI: 78% Linefit 99 % Trackfit 78 %

Corsika: ToI: 45 % Linefit: 97 % Trackfit: 53 % (Nchan > 10)

2009 Filter Optimization

use max. LineFit velocity and min. ToI evalratio determine 1% contour line in corsika passing rate

plot on this search for maximum E→ 2 passing rate along

Nue E2 passing corsika passing

IC60 - Old ToI and LineFit Settings (+coincify, +NewDiscThreshold, ADCTh 1.0)

down to 1% background at 69% E2 signal is feasible with old settings

New ToI and LineFit Settings (+coincify, +NewDiscThreshold, ADCTh 1.0)

losen the nchannel cut in ToI more →StringTrigger events to achieve the →same BG supression only get 62.6% E2 signal

New ToI and LineFit Settings (+no coincify, +NewDiscThreshold, ADCTh 1.0)

Without coincify and with StringTrigger Events slightly better:63.8% E2 signal

Energy Efficiency

Energy Dependence of the Cut:low efficiency below 1 TeV


Resulting numbers

Optimal Cuts:This are the choosen cut values and the resultig efficiencies:

LineFit vel ToI evalIC40(old) 0.130 0.120IC60 0.086 0.046

Sample Efficiency [%]BG MC 1νe E−1 89νe E−2 69

Resource requirementsThe following properties were calculated:

bandwidth s = 6020 Mbd

filter rate f = 16.1 Hz

low calculation time (below 0.2 ms per event and module)


Summary

2009 Filter Proposals:I good collaborations with OFU peopleI high resource consumptionI Feature Extractor threshold of 1 physically preferred

Cascade FilterI LineFit and Tensor of Inertia as cut variablesI 1 % background (16 Hz, 6 Gb

d )I 69 % E−2-signal efficiency

OutlookI fast clean up of unused dataI answering open questions on request


2009 cascade filter proposal - desy · high disk memory high space consumption of 7 tb : for one...

Documents