Difference between revisions of "Off-line analysis"

From PolWiki
Jump to: navigation, search
(List of changes in Run parameter)
(List of changes in Run parameter)
Line 15: Line 15:
 
*24141 - 24242 : we do not have event-mode and scaler data for this period, the address-mapping in header file wasn't correct
 
*24141 - 24242 : we do not have event-mode and scaler data for this period, the address-mapping in header file wasn't correct
 
*24242 ...    : we now have data corresponding to two different PWTL
 
*24242 ...    : we now have data corresponding to two different PWTL
 +
*24296 ...    : updated master board firmware to 0xAA0E, in the previous revision, the accum trigger corresponding to PWTL2 was not clocked at the final output stage, hence those patterns where the overlap between multiple triggers was only one clock wide were lost.
  
 
==How-to==
 
==How-to==

Revision as of 19:32, 7 March 2012

List of changes in Run parameter

Run number range : Event

  • 23211 ...  : accumulation trigger changed from 2-plane to 3-plane
 : kept running with 3-plane accum trigger, all planes unmasked
  • 23677 - 23765 : the laser cycle On:Off period was changed from regular 60:30 to 50:25
  • 23766 - 23773 : beam off, calib input runs
  • 23774 - 23835 : beam off, (LED linearity tests, DAQ tests etc)
  • 23836 - 23913 : transverse regular running
  • 23914 - 23926 : transverse running, I=75, edet trigger Gatewidth scan
  • 23933 ...  : regular longitudinal running , I = 180uA
  • 23939 - 23945 : edet trigger gatewidth scan with changing trigger and mask conditions
  • 23946 ...  : back to 3-plane trigger, all planes including sick channels of plane-4 unmasked
  • 24141 ...  : changed slave firmware to 0x321B, master board firmware to 0xAA0D, has data for two PWTLs but 2nd one not working yet
  • 24175 ...  : masked off plane 2: strip 10 & 41; plane 3: strip 62
  • 24141 - 24242 : we do not have event-mode and scaler data for this period, the address-mapping in header file wasn't correct
  • 24242 ...  : we now have data corresponding to two different PWTL
  • 24296 ...  : updated master board firmware to 0xAA0E, in the previous revision, the accum trigger corresponding to PWTL2 was not clocked at the final output stage, hence those patterns where the overlap between multiple triggers was only one clock wide were lost.

How-to