Difference between revisions of "New Delayed Helicity Readout Scheme for Physics Events Trigger"
Jump to navigation
Jump to search
Line 3: | Line 3: | ||
Running in background: | Running in background: | ||
− | * '''On Pattern Start''' | + | * '''On Pattern Start:''' |
# Increment pattern counter | # Increment pattern counter | ||
# Grab Reported Helicity | # Grab Reported Helicity | ||
Line 9: | Line 9: | ||
# Clear pattern phase counter | # Clear pattern phase counter | ||
− | * '''On T_Settle Transition''' | + | * '''On T_Settle Transition:''' |
# Increment pattern phase counter | # Increment pattern phase counter | ||
# Increment T_Settle counter | # Increment T_Settle counter | ||
Line 16: | Line 16: | ||
Then, when a physics event triggers DAQ: | Then, when a physics event triggers DAQ: | ||
− | * '''On CODA Event''' | + | * '''On CODA Event:''' |
# Report current seed value | # Report current seed value | ||
# report current pattern phase | # report current pattern phase | ||
# Report current pattern and T_Settle counter | # Report current pattern and T_Settle counter |
Revision as of 12:50, 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 counter