Finally  gotten used to the software a little bit.  Main program is 
analyzeTime, which has a function for integrating energy detected from 
some cutoff time, where t=0 at particle creation, to the end of the 
event. 

Because we want to try and find an algorithm for a more accurate time of 
impact, we have to analyze the effect that changing the initial time of 
impact to after the first detected impact has on our measurement of the 
total energy.  From this first look, it seems there is a bit of 
flexibility in choosing a cutoff time.

I hope to build upon this function for use as a general time window 
energy integrator.

I will use this along with a function that creates a time window 
starting on initial particle detection and ending when most energy has 
been detected.  For use in non-MC simulations, this will have to be 
changed to one that finds an end with either a differential cutoff 
(rather than percentage of total incoming energy detected), or a cutoff based 
on percentage of detectable energy (energy detected over all time); once 
a negligble amount of energy is detected from one cycle to the next, the 
time window closes.

This automatic time window generation will be useful for looking at the 
entire set of events and allow us to understand how our various time 
cutoffs/subwindows effect particle detection, rather than the 
qualitatitive information gained from looking at only one event.

This will all be used together to create a program that represents a 
moving time window that tries to follow the particle through its path.

There is also a simplistic algorithm for finding the corrected time of 
impact, but I need to talk to Hans about geometry; this one finds the 
detector cell closest to the last point seen by the tracker and calls 
that the impact point.  The particle is moving on a curve, however, so 
this understandably produces poor results.