IceCube Global Trigger:

1
IceCube Global Trigger the First Year Goals
current status
Seon-Hee Seo for PSU
IceCube/AMANDA Collaboration Meeting Uppsala,
Oct. 7-13, 2004
2
Outline
1. Why Global Trigger in IceCube?
2. First Year Goals
3. Global Trigger Inputs
4. Global Trigger Output
5. Global Trigger Timing Diagrams
6. Current Status
2
3
Why Global Trigger?
1. IceCube consists of subdetectors, InIce and
IceTop, each of which will produce triggers
independently.
2. IceCube will use trigger information from
external detectors AMANDA, GRB and SNEWS
detectors etc...
IceCube needs a detector wide trigger, i.e.,
the Global Trigger which can manage all
different sources of triggers and produces one
output to the Event Builder.
3
4
Online
Global Trigger
AMANDA
Experiment Control
IceCube DAQ Architecture
...
DAQ Control
InIce Trigger
IceTop Trigger
...
String Processor
...
DOM Hub Application
DOR Driver
HAL
...
DOMApp
5
IceCube First Year Goals
1. IceCube will have 4 InIce strings (240 DOMs)
and 8 IceTop tanks (16 DOMs) for the first year
(2005).
2. Due to the limited size of the detector (5 of
the complete one), IceCube's main focus for the
first year might be A) to achieve smooth data
flow from DOMs in ice to the northern
hemisphere via satellite under proper operation
of both hardware and software systems. B) to
calibrate the detector flasher board C) to
tune the detector hardware software
parameters D) to do some physics down going
muon, air shower
3. InIce LC, simple majority and calibration
triggers IceTop shower and calibration
triggers
5
6
GT First Year Goals
1. GT will use only InIce and IceTop trigger
inputs. 2. GT will apply extended time window to
issue a GT event size of the extended time
window is determined by trigger types from
InIce and IceTop trigger. 3. GT will handle
both low and high threshold data. 4. GT will
instruct EB to read both InIce and IceTop
even though only InIce or IceTop trigger exists
exception pure calibration
trigger 5. GT will generate random trigger for
monitoring TBD random trigger frequency TBD
random trigger time window
6
7
GT Inputs
1. In GT, there is no merge of two consecutive
triggers from the same sub-detector if they
are close in time, then they should be merged
in sub-detector level.
An example list of GT input trigger primitives
7
8
Global Trigger Output
An example list of GT output trigger primitives
8
9
(A) InIce or IceTop trigger only
InIce (H)
IceTop
GT
InIce
IceTop (H)
GT
InIce (L)
(X)
IceTop
GT
InIce
(X)
IceTop (L)
GT
9
10
(B) InIce IceTop coincidence trigger (I)
InIce (H)
IceTop (H)
GT
InIce (H)
(X)
IceTop (L)
GT
InIce (L)
(X)
IceTop (L)
GT
10
11
(B) InIce IceTop coincidence trigger (II)
InIce (H)
IceTop (H)
2 GT!
InIce (H)
(X)
IceTop (L)
GT
InIce (L)
(X)
IceTop (L)
GT
11
12
(C) Calibration trigger
extended time window!
InIce_calib
IceTop (H)
GT
InIce_calib
(X)
IceTop (L)
GT
InIce_calib
(X)
IceTop (L)
GT
12
13
(D) Topological trigger
Not for the 1st year!
InIce_topol (H.L)
IceTop (H,L)
GT
InIce_topol(H,L)
IceTop (L)
GT
13
14
(E) Random trigger
InIce
IceTop
GT_random
InIce (L)
(x)
IceTop
GT_random
InIce
IceTop (H)
?
GT_random
14
15
Current Status of GT
1. DAQ-independent GT algorithm is ready and
tested w/ fake data. (random trigger has not
been implemented yet.) 2. GT algorithm using the
splicer is ready and tested w/ fake data this
result produced the same result as
DAQ-independent GT algorithm. 3. DAQ-dependent
GT algorithm will be ready by Nov. 1st 2004,
when there is a DAQ-integration meeting at PSL.
15