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

From Ciswikidb
Jump to navigation Jump to search
Line 1: Line 1:
Paul King has this outline for a new scheme to readout the delayed helicity for Physics Event Triggers instead of using Scalers RingBuffer:
+
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:
 
  Running in background:
Line 14: Line 14:
  
  
  Then, when a physics event triggers DAQ
+
  Then, when a physics event triggers DAQ:
  
 
* '''On CODA Event'''
 
* '''On CODA Event'''

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
  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 counter