Difference between revisions of "New Delayed Helicity Readout Scheme for Physics Events Trigger"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
* '''On Pattern Start:''' | * '''On Pattern Start:''' | ||
# Increment pattern counter | # Increment pattern counter | ||
| − | # Grab | + | # Grab reported helicity |
# Push onto running seed (30-bit) | # Push onto running seed (30-bit) | ||
# Clear pattern phase counter | # Clear pattern phase counter | ||
| Line 19: | Line 19: | ||
# Report current seed value | # Report current seed value | ||
# report current pattern phase | # report current pattern phase | ||
| − | # Report current pattern and T_Settle | + | # Report current pattern and T_Settle counters |
Latest revision as of 12:53, 20 May 2015
Paul King has this outline for a new scheme to readout the delayed helicity for Physics Events Trigger (instead of using Scalers RingBuffer):
Running in background:
- On Pattern Start:
- Increment pattern counter
- Grab reported helicity
- Push onto running seed (30-bit)
- Clear pattern phase counter
- On T_Settle Transition:
- Increment pattern phase counter
- Increment T_Settle counter
Then, when a physics event triggers DAQ:
- On CODA Event:
- Report current seed value
- report current pattern phase
- Report current pattern and T_Settle counters