Difference between revisions of "New Delayed Helicity Readout Scheme for Physics Events Trigger"

From Ciswikidb
Jump to navigation Jump to search
 
(One intermediate revision by the same user not shown)
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
 
# Push onto running seed (30-bit)
 
# Push onto running seed (30-bit)
 
# 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 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:
  1. Increment pattern counter
  2. Grab reported helicity
  3. Push onto running seed (30-bit)
  4. Clear pattern phase counter
  • On T_Settle Transition:
  1. Increment pattern phase counter
  2. Increment T_Settle counter


Then, when a physics event triggers DAQ:
  • On CODA Event:
  1. Report current seed value
  2. report current pattern phase
  3. Report current pattern and T_Settle counters