Adam Blake, University of Utah Overview As of 8/4/2008, my search for events in the HiRes data with abnormal speed results in 8 events making it past my cuts. Of those 8, only 1 has a speed that significantly (meaning 5 or more standard deviations from the speed of light from both HiRes 1 and HiRes 2) differs from the speed of light. Cuts Data Processing CutsMy Cuts Both detectors must pass plane fits Minimum PE per tube: 1.0 Minimum Tubes per event: 6 Minimum Average PE per tube per event: 15.0 Maximum Track Length: Hr1 36.0, Hr2 57.0 Minimum Track Length: Hr1 3, Hr2 6 Cut if event crossing planes or tube binning 10 > Opening Angle 170 < Opening Angle Bootstrap >.0012 m/ns Hr1 adjusted tubes < 3 Hr2 adjusted tubes < 6 Track Length < 8 degrees Tubes in 1 mirror > 170 > 120 Plog < 2.0 Rp < 4km from either site Speed difference to Error difference ratio* April 6 th, 2003 EventRp Hr1Rp Hr2Opening Angle Track Length Hr1 Track Length Hr1 m Track Length Hr2 Track Length Hr2 m Shower Time Slope Hr1Good Tubes Hr1 Slope Hr2Good Tubes Hr Various Speed Fits Speeds:m/ns shower_speed sab_plane_fit shower_speed/Origin Hires_soft/Mathematica Hires_Soft/Mathematica No weight No Correction, No weight Shower_speed is speed fit by my program sab_plane_fit is speed fit after refitting the plane using a plane fitter I wrote Shower_speed/Origin is speed fit by Origin based on points from shower_speed Hires_Soft/Mathematica is the HiRes plane fit used with Mathematica to correct tube times then fit in Origin Hires_Soft/Mathematica no weight is the HiRes plane fit used with mathematica to correct tube times then fit in Mathematica with no additional weighting No Correction, No weight is a fit performed straight on HiRes raw data with no corrections. This is the data straight from Bills reconstruction without further changes. Bills is used instead of Zhens because Zhen uses timing in his reconstruction and Bill does not. Stereo Reconstruction Data Stereo Reconstruction of Event (Bills Reconstruction) VariableHiRes 1 rp psi theta32.48 phi-61.73 VariableHiRes 2 rp psi theta32.48 phi-61.73 HiRes 1 HiRes 2 Various shower profiles collected from different sources. There are 2 sets from Utah, shwa and shwb referring to the banks I pulled fits from. There is currently only the one from Rutgers. Ive included both individual and overlay graphs where possible. Npart graphs refer to particles vs slant depth generally in units of 10e9 particles. Photons refer to NPE. Shower Profiles HiRes 2 Npart - shwa HiRes 1 Npart - shwa Overlapped Npart - shwa HiRes 1 photons shwa HiRes 2 photons - swha Overlapped photons shwa Redone Profiles - shwb HiRes 2 NPE Profile - shwb HiRes 1 NPE Profile - shwb Overlapped Profiles - shwb Rutgers Profile This is Rutgers HR2 mono reconstruction of this event. Note that all values here assume the speed of light. Rutgers Reconstruction of Event Dumps from Rutgers DST RUFPLN bank (FADC cluster plane fit) Number of tubes = 141 Number of tubes in plane fit = 44 Seed for track = 23 Normal vector to plane: Norm vect err matrix: Run start: jday Event start: Angular extent = 22.9 Duration = Angular RMS = 12.6, 0.4 Stream = 3 Dumps from Rutgers DST RUFTFT bank (FADC cluster time fits) Status: 3 Linear Fit: t0 = Slope = Chi2 = Cov = 3.30e e e e-03 Vertical Tangent Fit: r0 = t0 = Chi2 = 35.8 Cov = 4.58e e e e+00 Tangent Fit: r0 = Psi = t0 = Chi2 = 36.7 Cov = 1.25e e e e e e e e e+02 Rutgers DST Parameters RUSPGF bank (Simultaneuous profile-geometry fit) Status: 1 RpPsit0XmaxNmaxEnergy Fit Values: E E+19 Errors(dn): E E+17 (up): E E+17 FADC traces This section includes some of the calculations that I have done on the event. My Work on Event Event Profile Stereo Planes My Fit Plane Routine Routine is simple to reduce possible sources of error. Takes a point at every tube that fired and made it through reconstruction. Draws a line from that tube, putting additional points at every 1 km interval. Fits the new set of expanded points using the standard equation of a plane and a type of least squares fit. Does not at any point in time assume stereo geometry. Planes for each detector are fit in a vacuum so to speak. Plane Fit Comparisons Plane VectorsHr1_XHr1_yHr1_z Reconstructed My fit Hr2_xHr2_yHr2_z Reconstructed My fit Rutgers Comparison for plane vectors done by various fitting Rutgers and HiRes mono planes use relative timing to aide in plane fitting. My fit describes a plane fitting routine that I wrote to check planes. Parameter Comparison Comparison TableMineReconstruction Impact X Impact Y rp HR rp HR phi theta psi HR psi HR Comparison for various parameters. Mine refers to parameters calculated using my planes and Mathematica Reconstruction are values pulled from reconstruction. Line Fits Line Fits show the depth along shower from rp in meters vs. the corrected time as measured by HiRes. Red points are those tubes that were removed by either reconstruction or my fitting routine. Most are removed by reconstruction Fit Parameters are given in the box in the upper right hand corner on each graph. Line Fits HiRes 1HiRes 2 Line Fit: HiRes 1 Line Fit: HiRes 2 Wiggling Plane HR1 Theta Direction This movie shows the process of moving the HR1 plane and recalculating speed assuming HR2 plane remains fixed. Click on picture to see movie. State of Detector There is a bit of confusion between the logs. HiRes 2 runners claimed good weather run, HiRes 1 runners claimed poor weather run. So checking various systematics like flashers to see what weather was like. HR1 log Hal Log y2003m04d06 (SS,CO,CCJ) =========================== Executive Summary: hours of poor data. Most of the run was cloudy but were told by HR2 runners that it was clear. Cloudcam seems to be having problems; has pink stripes once in a while. Did Ctrl C on hr1sls and hr2sls accidentally, started and shut it down (please look below). Problem Summary: Were there any garage door problems??? No Any other problems or jobs which need to be done??? Weat computer is still down. HR1 log (continued) Detectors: BiG H run? Y HiRes-2 FADC run? Y Atmos. Lasers: [HR1SLS] run? Y [HR2SLS] run? Y Hours Good Data: Hours Poor Data: 5.5 Hours Test Data: Sunset Weather: Cloudy, some snow Run Weather: Mainly cloudy on DPG Flashers seen: Intersite: Y Which others?: hr2sls seen: South side of Bigh:Y North Side of Bigh: Y hr3vls seen: (Terra Laser) Vertical Tracks in M19: Y hr1sls Problems: none hr2sls Problems: none hr3vls Problems: none !!! HR2 log HR2 Log y2003m04d06 (rem cmh) =========================== Executive Summary: snow during day, but cleared by data time; 5 h good data; clouds moved in at end Hardware: Software: Data Issues: Weather: Sunset: high clouds; high humidity; hires1 visible Run: clouds low on horizon; clear above; high humidity Runtime: (from dark output) Dark period: 05:35 (run night!) from: (moon set) 2003 Apr 6 05:58 to: (begin twilight) 2003 Apr 6 11:34 HR2 log (continued) Problem Summary: Mirror did not come on during Boot2. Tried again and failed. then tried "