1. IC59 muon Level3 investigations Mike Baker Muon call April 12, 2010

2. I've got the sample scripts for Muon L3 in the folder here:
They work with the same framework as Andreas's L2 scripts. Read/Write and other services are imported from L2 scripts.
muonL3_Master.py – mostly copied from the L2 master script
level3_MuonReco.py – has blocks of reconstruction modules, also a few extra Python modules to help with conditional execution.
jobSubmitter_ic59mul3test.pl and scriptSubmit_npx2-uwa.sh are useful tools for throwing things onto a Condor cluster (NPX3, UW Analysis cluster)

3. LineFit, SPE8+MPE, Photorec, MuE
Muon things run at L2:
LineFit, SPE8+MPE, Photorec, MuE
Things we need at L3:
Track resolution (paraboloid, Cramer-Rao)
Downgoing rejection (Bayesian fits, noise++ fit)
Coincident rejection (TT, split fits, noise++ fit, coincident fits?)
Things I know less about but may also be interesting(DirectWalk, SuperLineFit)

4. -Timing within t of muon crossing time
Topological trigger (TT) uses these criteria to determine whether pulses are connected:
-Timing within t of muon crossing time
-XY separation less than r meters
-Z spacing of less than z DOMs
If two pulses pass ALL of these criteria, they are topologically connected, and put into the same sub-event.
Being connected is transitive.
Sub-events are required to have 5 pulses within 4 μs.
CPU – TT takes roughly half much at CPU time as a single Llh fit.
Split fits will take ~8*2 LlhFits, but can only be applied to upgoing events

5. TT can return up to 3 sub-events
~95% of upgoing events get >=1 sub-event
~11% of upgoing events get >=2 sub-events
~0.5% of upgoing events get 3 sub-events
Of course, this depends somewhat on the input parameters.

6. ~1-2% of signal neutrinos are cut
I've been playing with the settings parameters for TT, the effect of tightening cuts is not very strong. I'd like to see if anything weird happens at very tight parameter values.
Coincident looks the same as for data (shown), with much lower statistics.
~1-2% of signal neutrinos are cut
Further plots use the maroon line for TT settings

7. Black – all upgoing, mufilter events
Blue – apply Topological Trigger (TT zenith>90)
Red- apply split fit cuts (min geo-split zenith>80)
Split fits cut away lots of low Nch events due to one of the split events not having sufficient hit DOMs for a successful Gulliver fit

8. TT and Split fits applied to coincident corsika

9. TT and Split fits applied to data

10. TT saves many more low NCh events compared to the split fits, but are they good events?
I still need to see how well TT works in conjunction with other cuts, and how much the ~10% of events with 2 sub-events can improve background rejection.