IC40 Physics Run Preparations

1. IC40 Physics Run Preparations Erik Blaufuss – University of Maryland IceCube Science Advisory Committee May 5-6, 2008

2. The TFT board • TFT is a working committee within the collaboration charged with determining: • Trigger and DAQ settings for physics data taking • Online filters deployed to Pole and their settings. • TDRSS satellite bandwidth allocations. • Review allocations of non-physics data detector allocations to support run coordinator • Determine allocations of CPU resources at Pole • TFT board members drawn from • Run coordinator • Subsystem experts (DAQ, online filtering) • Several experts from physics analysis and simulation

3. The TFT board • Physics working groups submit proposals for triggers, filters, satellite bandwidth • Reviewed by TFT • TFT works to generate DAQ/filter settings • Tuning filters based on information provided in proposals • TFT has an established filter evaluation criteria, taking into account: • Matches physics goals of IceCube • Amount of resources being requested • Filter maturity • Results from previous years requests • No physics filter has had to be rejected to date • A handful of filters this season tuned down somewhat to accommodate satellite bandwidth constraints. • Small impact on physics signal in each case.

4. IC40 Filtering • IC40 physics run has already started. • Began collecting data in IC40 configuration: • April 11, Run 110811 • All request trigger and DAQ settings implemented • I3DAQ and TWR DAQ events being merged and taped • Filters for IC40 deployed • April 17, Run 110847 • TDRSS bandwidth allocation well-filled. • Total: 37 GB/day • Slightly in excess of our goal of 35 GB/day but TDRSS seems to be routinely delivering. • CPU at pole ~85% loaded under normal rate

5. IC40 new triggers • In addition to majority triggers used in previous years, this year has two new triggers: • 5 of 7 String trigger – Low energy muons • ULEE trigger – 3 of 4 string trigger w/ large veto • Experimental trigger/filter – very small rates. • Aims to collect tracks ~10 GeV neutrinos

6. IC40 Filters – Upgoing muons • Upgoing muon filter – single largest filter • Select upgoing events based on log-likelihood reconstruction zenith angle using I3-only data • Fully efficient at ~1 TeV. • Aimed at use in ATM neutrino, Point source searches, and diffuse neutrino searches

7. IC40 Filters – Low Energy muons • Three filters compliment standard muon • Aim for filter efficiency at or below 100 GeV • Two use merged I3+TWR data • Low energy atmospheric neutrinos, WIMPs • Low-up filter –any LE event, I3+TWR, I3-only • JAMS filter – I3+TWR events with few I3 hits • Low energy contained filter – vertical tracks from I3 string triggers. Low Up filter signal efficiency

8. IC40 Filters – Cascades • Two cascade filters, both select events based on event topology • I3 Cascade filter – higher energy cascades in I3 DAQ data. • LE Cascade filter – lower energy cascade sensitivity in region around denser AMANDA

9. IC40 Filters - Others • EHE filter • Aimed at GZK neutrinos, tau neutrino searches, exotic particle searches. • Selects any event with ~600 pe total charge • GRB filter • Searching for neutrino (muon or cascade) signal coincident with GCN alerts • Obtain raw data from 2 hour window around GRB time, apply special filters

10. IC40 Filters - Others • Moon filter • Select cosmic ray events in region near moon • Use moon shadow to verify ability to see point sources • Downgoing contained filters • 2 filters: use upper/outer strings as active veto to search Southern sky for neutrino sources • I3+TWR: seach for starting tracks near denser AMANDA region, using I3 as veto • I3-only: use deep portions of central strings as fiducial volume – Study for Deep Core • DST • Record small event summary for all triggered events • Collect high statistics sample of cosmic ray events, search for anisotropy, seasonal variations…

11. IC40 Filters – By the Numbers. • IC40 trigger rate (I3+TWR) : 1340 Hz • IC40 filter rate: ~80 Hz, 6% (no moon) http://internal.icecube.wisc.edu/status/detector-summary.xml

12. IC40 Filters – By the Numbers. GB/day Total: 32.5 GB/day

13. IC60 Planning • Preparations for next seasons physics run are now just underway. • “IC60” represents first year with a more incremental upgrade. • # of strings not doubling • Online systems more mature • Much more advanced and capable simulation. • Expect similar start to physics run • Run IC40 filters until April 1, 2009 • Earlier deadlines for IC60 TFT requests • September 1 : DAQ and trigger proposals • November 1 : Filter and bandwidth proposals

14. Future filtering • Looking for ways to do filtering better, and considering several approaches. • For more mature analyses, do more data reduction online and return smaller fraction of data from Pole • Move higher level reduction steps to online filters • Point source/upgoing neutrinos for example • Tool to identify and tag/remove common atmospheric muon background. • Evolve to Level 1 filter for all neutrino filters • More advanced algorithms now useable online on smaller fraction of data. • Needs collaboration-wide effort.