Difference between revisions of "July 13, 2015"
From GlueXWiki
Line 9: | Line 9: | ||
:* Read out path (scintillator sub-detectors, PS/PSC, TAGM, ) | :* Read out path (scintillator sub-detectors, PS/PSC, TAGM, ) | ||
− | :* Pedestals | + | ::* Pedestals |
− | ::: - Report the sum of N samples ( N = 4, 8, 16) computed at the beginning of the readout window | + | :::: - Report the sum of N samples ( N = 4, 8, 16) computed at the beginning of the readout window |
− | ::: - Number of samples N - programmable | + | :::: - Number of samples N - programmable |
− | ::: - Energy range 0 - 255, report 0xFF if underflow or overflow occures. The number of bits required - 8 + 4 = 12 | + | :::: - Energy range 0 - 255, report 0xFF if underflow or overflow occures. The number of bits required - 8 + 4 = 12 |
− | :* - Fix NSb to 5 | + | ::* - Fix NSb to 5 |
:* Scalers | :* Scalers |
Revision as of 09:15, 13 July 2015
- Addendum to specifications for fadc250 firmware
- Trigger path
- - Energy transfer
- Fix Nsb to 5
- - Hit-bit pattern
- Trigger threshold - no pedestal subtraction for both energy and hit-bit (firmware version 90E)
- - Energy transfer
- Read out path (scintillator sub-detectors, PS/PSC, TAGM, )
- Pedestals
- - Report the sum of N samples ( N = 4, 8, 16) computed at the beginning of the readout window
- - Number of samples N - programmable
- - Energy range 0 - 255, report 0xFF if underflow or overflow occures. The number of bits required - 8 + 4 = 12
- - Fix NSb to 5
- Scalers
- FCAL MIPs efficiency
- Adjusting pedestals during the run (pedestal stability check)
- Implementing trigger scalers (gtp, ssp, )
- - add scalers to the data stream
- Hardware/trigger performance during the beam test
- - Reproduce trigger thresholds with recorded data (features with FCAL ST algorithm)
- additional checks in read out lists
- - Non-uniform occupancies with TOF trigger
- - use PlayBack for comprehensive system checks.
- High-rate performance checking