_Date_ | _Kinematic_ | _He runs_ | _H2 runs_ | _Nitrogen Runs_ | _Empty_ | _Carbon_ | _Runs Replayed_ |
3/24/06 | Kin 3a | 3342-3347 | 3334-3341 | ||||
3/25/06 | Kin 3a | 3348-3355, 3371-3379, 3382-3383 | 3362-3366, 3368-3370 | 3360-3361 | 3356-3359 | ||
3/26/06 | Kin 3a | 3384-3387, 3389-3400, 3401-3409, 3411 | |||||
3/27/06 | Kin 3a | 3413-3423, 3433-3434, 3436, 3438-3449 | 3424-3427, 3430-3432 | ||||
3/28/06 | Kin 3a | 3450-3464, 3467, 3469, 3471-3473 | 3465-3466 | 3470 | |||
3/29/06 | Kin 3a | 3480. 3485-3486 | 3474-3479, 3484, 3490-3491 | 3481-3482, 3487-3489 |
This isn't very illuminating as it is copying information that can be found in the runlist found in http://hallaweb.jlab.org/experiment/E02-013/mtg/2007aug22/kelleher/, this information being in an excell spreadsheet is also clearer to see and use.
We do run into some issues on database days, as perhaps half the day will have the right database and half the day won't. This is a product of our database scheme.
_Dates_ | _Kinematic_ | _Runs Replayed_ | _Runs to be Replayed_ | ||||
3/01/06 - 3/08/06 | Kin 1 | BH DB to be done | |||||
3/09/06 - 3/12/06 | Kin 1 | can use prev. BH DB | |||||
3/13/06 - 3/14/06 | Kin 2a | BH DB to be done? (ignore) | |||||
3/15/06 - 3/15/06 | Kin 2a | BH DB to be done | |||||
3/16/06 - 3/16/06 | Kin 2a | can use prev. BH DB | |||||
3/17/06 - 3/17/06 | Kin 2a | can use prev. BH DB | |||||
3/18/06 - 3/18/06 | Kin 2a | can use prev. BH DB | |||||
3/19/06 - 3/21/06 | Kin 2a | can use prev. BH DB | |||||
3/22/06 - 3/22/06 | Kin 2a | BH DB to be done? | |||||
3/23/06 - 3/23/06 | Kin 3a | No He runs | |||||
3/24/06 - 3/26/06 | Kin 3a | 3364, 3372-3379, 3382-3387, 3389-3400, 3402-3407, 3409 | |||||
3/27/06 - 3/29/06 | Kin 3a | 3413-3423, 3438-3460, 3462-3464, 3467, 3469 | |||||
3/30/06 - 4/03/06 | Kin 3a | 3494-3509, 3517-3518, 3520-3529, 3531, 3533-3534, 3538-3548, 3551-3554, 3556-3562, 3566-3570, 3579-3586, 3589-3594, 3597-3599, 3602-3608, 3610-3615, 3618, 3620, 3623-3627, 3630-3635 | |||||
4/04/06 - 4/04/06 | Kin 3a | 3641-3646, 3648-3649, 3668-3674 | |||||
4/05/06 - 4/10/06 | Kin 3a | 3687-3699, 3716-3732, 3736-3756, 3761-3780, 3784-3790, 3792-3793, 3795-3812, 3814-3825 | 3675-3686, 3700-3715 | ||||
4/11/06 - 4/17/06 | Kin 3a | 3832-3838, 3875-3876, 3888-3892, 3894-3903, 3905-3909, 3922-3940, 3945-3976, 3978-3981, 3983-3988 , 3995-4009 | 3877, 3910-3913, 3915-3917, 3941-3944, 3990-3992 | ||||
4/18/06 - 4/18/06 | Kin 2b | BH DB to be done? (ignore) | |||||
4/19/06 - 4/23/06 | Kin 2b | BH DB to be done | |||||
4/24/06 - 4/27/06 | Kin 3b (Kin 2b in 4/24/06) | BH DB to be done | |||||
4/28/06 - 4/30/06 | Kin 3b | can use prev. DB | |||||
5/01/06 - 5/01/06 | Kin 3b/Kin 4 | BH DB to be done? (ignore) | |||||
5/02/06 - 5/10/06 | Kin 4 | 4419-4436 4440-4441, 4444-4507, 4511-4528, 4530-4532, 4534-4536, 4538-4539, 4541-4542, 4544-4551, 4572-4578, 4581-4584, 4586-4597 | 4442, 4510, 4529, 4533, 4537, 4540, 4543, 4552-4571, 4579-4580, 4585 | ||||
5/11/06 - | Kin 4 |
Using std cuts to select quasi-elastic events, certain runs were investigated to see if the virtual photon momentum vector could be reconstructed and the hadron momentum vector could be reconstructed.
This was done for run 3898 (for both the X component and Y component):
and run 4490 (for both the X component and Y component):