Difference between revisions of "Development Period - February 9-10"
Jump to navigation
Jump to search
Line 20: | Line 20: | ||
:* [[media:Delayed_Ana.pdf]] [[media:Delayed_Ana.pptx]] | :* [[media:Delayed_Ana.pdf]] [[media:Delayed_Ana.pptx]] | ||
:* A dump of first 10000 events from Run 8218 [[media:Hel_8218_0.txt]] shows that S1 helicity is lacking FADC by 0 to a few events. FADC helicity is correct because it is read event by event in the same module at the same time. | :* A dump of first 10000 events from Run 8218 [[media:Hel_8218_0.txt]] shows that S1 helicity is lacking FADC by 0 to a few events. FADC helicity is correct because it is read event by event in the same module at the same time. | ||
− | :* For the time being we will not run in delayed helicity mode | + | :* For the time being we will not run in delayed helicity mode because we cannot rely on S1. To use FADC helicity in delayed mode, decoder software development is required. |
==Test FADC time-of-flight readout and new Mott DAQ Configurations (2 hour)== | ==Test FADC time-of-flight readout and new Mott DAQ Configurations (2 hour)== |
Revision as of 15:16, 12 February 2015
Listed in order of suggested priority...
Re-measure emittance in order to analyze Run 1 conditions (3 hours)
- February 9, 2015:
- Identified parameters and details for a procedure
- Measured emittance and Twiss for 6.3 MeV/c setup
- Started emittance and Twiss for 5.5 MeV/c but harp is stuck so test deferred for now
Test hardware TOF veto at 31MHz (4 hours)
- Runs 8210 - 8217 with 0.225 um gold foil
Test background as a function of target ladder position on large target foil (0 hours)
- February 9, 2015:
- Deferred until re-doing emittance measurement at 5.5 MeV/c to try for smaller spot size with 5 or 10 mm rings too
Test Mott delayed operation (1 hour):
- Set of 6 runs while changing between No Delay and Delay=8
- Runs 8218 - 8223 with 1.0 um gold foil
- media:Delayed_Ana.pdf media:Delayed_Ana.pptx
- A dump of first 10000 events from Run 8218 media:Hel_8218_0.txt shows that S1 helicity is lacking FADC by 0 to a few events. FADC helicity is correct because it is read event by event in the same module at the same time.
- For the time being we will not run in delayed helicity mode because we cannot rely on S1. To use FADC helicity in delayed mode, decoder software development is required.
Test FADC time-of-flight readout and new Mott DAQ Configurations (2 hour)
- February 4, 2015:
- Added two more laser timing signals to FADC. From Disc 708, OUT signal was connected to FADC Ch10 and OUT_bar was connected to Ch12. The original laser timing signal is still connected to Ch9.
- Run 8224 with 1.0 um gold foil and Mott_SemiInt configuration
- Measure deadtime with 2.2 uA on 1 um gold foil:
- Run 8225: Mott_SemiInt configuration (FADC+TDC+Scalers), Deadtime = 28% at 5.1 kHz.
- Run 8227: SemiIntFast configuration (only readout of FADC, Blocklevel = 1) , Deadtime = 17% at 5.1 kHz.
- Run 8228: SemiIntBlock configuration (only readout of FADC, Blocklevel = 50) , Deadtime = 1% at 5.1 kHz.
- Mott DAQ Speed: media:DAQ_Speed_Feb2015.pdf media:DAQ_Speed_Feb2015.pptx