Last changed: $generalUtil.formatDateTime( $blog.lastModificationDate ) by
eduardo
Johan, Luca B, Eduardo, Philippe
This shift
- Some runs from previous night were causing phasing errors. The assumption is that it could be external trigger rates and high rate. Could this be caused by high rate triggers only too. What if that happens when we are on orbit? Must understand and Ric is worried.
- Validate timing settings of CAL and TKR in baseline run BT1 . Eduardo's timing diagram and baseline data taking settings from LAT Integration runs B2 (flight Config) indicate values that have been blessed by Eric Grove and Martin Kocian too. This will be used to determine run BT2 flight config and self triggering)
- Understand why CAL_HI is not triggering with 5GeV electrons using BT1 configuration
- Align ACD with TKR, CAL and external trigger (beam)
- Did not have time to investigate that Francesco reported crashes in the pipeline too. Runs
- In the CU_BT.xml schema file the register for CAL GCFE Config 1 is set to 0x7 and this means (see CAL 0 = cand autorange when you launch end-to-end BT the register is overwritten to 0x3 and CAL_HI can not fire eventhough the it is enabled. The problem is in intE2EConfigLib.py line 797 to 799 INT-0166.05 v1.70.
Runs 813 , 815-816 and 819-820 are electrons and were labeled pions
Johan,Luca B and Eduardo trying to understand why CAL_HI is not firing in 5 GeV run with the BT1 run
Run 700000820 ~ 48K events
100 Hz with CAL_HI enabled , BT1 and nominal settings for CU timing as described in the trigger alignment page.
Run 700000821 : we turn the CU 90 degrees and shoot the beam in the 3 CALs, in order to see the CAL_HI firing...and it works, we have a very nice peak of CAL_HI treq in the Trigger Time distribution. We now want to change a little bit the ext_delay to see the whole distribution and aline CAL_LO and CAL_HI
Run 700000822 : we turn the CU 90 degreeand and
Modfied trigger external delay to ox4 instead of 0x8 to , becasue the CAL_HI did not seem to be aligned.
We see two bumps in the CAL_HI distribution of Condition Arrival Times. (maybe from tower 2 and 3?) since we are shooting from the side?
Run 700000823
Table is at O and take pions at the edge of tower 2
Modify beam settings for negative pions @ 5GeV for ACD calibrations
Owl Shift
Luca B., Eduardo, Philippe, Alex
Will calibrate ACD and check alignment between detectors
Run 700000825
Many packet errors (597/164930) at a rate of an average of 500 Hz and instant rate of 3kHz.
- Latest_hitmap_delayGARC16.xml values are
- hitmap width 15
- hitmap delay 6
- hitmap_deadtime 0
- hold_delay 34
- veto_width 5
- veto_delay 0
Run crashed ! But Detectors seem to be aligned
Run 700000826
Still packet errors.
- Latest_hitmap_delayGARC16.xml values are
- hitmap width 15
- hitmap delay 6
- hitmap_deadtime 0
- hold_delay 34
- veto_width 5
- veto_delay 16
Run did not crash but ACD seem NOT to be aligned.
- ACD 0 - PMT 13 Signal is bigger becasue it is a small tile
- ACD 1 - PMT 11 Signal is bigger becasue it is a small tile
- ACD 2 - PMT 9
- ACD 3 - PMT 15 , 17
- ACD 4 - PMT 7 ~ signal 800
ACD Calibrations
High Voltage Set to 809
Created BT12 which is same as BT1 but with Zero suppression off for Alex to see pedestals. See configuration for details.
Run 700000829 BT12 ACD pedestal run Tile 4 far from the table - this pedestal reference run
Run 700000830 BT12 ACD run Tile 4 according to calibration setting
Run 700000831 BT12 ACD run Tile 3 according to calibration setting has 10% packet errors
Run 700000832 BT12 ACD run Tile 2 according to calibration setting has 30% packet errors
Run 700000833 BT12 ACD run Tile 1 according to calibration setting has 30% packet errors
Run 700000834 BT12 ACD run Tile 0 according to calibration setting has 30% packet errors
High Voltage Set to 760 - too high pulse heights from tiles 0 and 1
Created BT12 which is same as BT1 but with Zero suppression off for Alex to see pedestals. See configuration for details.
These are calibration runs for ACD tiles*: *
Run 700000837 BT12 ACD run Tile 4 according to calibration setting
Run 700000838 BT12 ACD run Tile 3 according to calibration setting has 10% packet errors
Run 700000839 BT12 ACD run Tile 2 according to calibration setting has 30% packet errors
Run 700000840 BT12 ACD run Tile 1 according to calibration setting has 30% packet errors
Run 700000841 BT12 ACD run Tile 0 according to calibration setting has 30% packet errors
Luca is generating ACD calibrations ACDpedestals.py
Instructions for Next Shift
- Inform pipeline manager that SVAC ntiuples are failing
- Analyze data from ACD to confirm if ACD settings are correct
- Understand packet errors which were present in ACD calibrations and BT1 configurations
- Verfiy timing for all BT configurations.
- Try to reproduce BT1 configuration without packet errors with nominal settings. Maybe the problem is high rate
- Educate shifters on usage of this logbool
2006/07/28
