DAQ Testing/20181127

Back to Main Page >> DAQ Documentation Portal >> DAQ Testing >> DAQ Commissioning Notes

Previous Day of Testing << >> Next Day of Testing

November 27th, 2018 Testers: Bob, Cameron

See Today's Meeting Notes

Goals

• Verify the NIM-TTL level translator is not bad and that the real issue with DAQ_Meeting/20181127 was improper signal termination in the scope
• Scan Helicity readback from scalers as a function of delay time
  • Likely the readout instance is marginally close to the LNE delayed signal timing)
  • It is important to verify that the FLEXIO is functioning as advertised in the FLEXIO manual
• Add Helicity information to the scalers of interest
  • Find their data in the output data-stream to allow for unambiguously determining the relative timing of the scaler vs. vqwk vs. control bit readouts
• Update timing diagrams (include the 1us between start of T_settle and Helicity flipping, don't show multiple helicity flips if subsequent T_settle's aren't shown too)
• Work with Ed Jastrzembski to implement/verify the synchronization of the TS between Counting House and Injector
• Understand how to monitor data transfer in ET system using monitorGui
  • Understand DAQ deadtime implications
  • Figure out the parameters to be tweaked to allow data to flow unobstructed
  • If this doesn't yield an obvious solution, explore a homemade data buffer solution that allows for DAQ vs. online analysis decoupling
• Incorporate Helicity sequence monitor into deadtime testing and scaler testing

Work

TS Timing

Bob emailed Ed Jastrzembski asking for his support in evaluating the TS synchronization. We will likely tour the Counting House and Injector at a time convenient for Ed soon.

Helicity Sequence Monitor

Bob siphoned off the helicity sequence predictor code from the QWeak analyzer and made a standalone code that can be used to verify that no events are skipped in the data stream (offline analysis)

Next:

• Cameron should implement this in his ~/et-12.0/src/cameron/ etclient program that tests for deadtime online
• Cameron should consider utilizing the on or offline versions of this to verify that scalers reading helicity information are reading the correct relative events ** Just eyeballing it is sufficient for our purposes, but using this and calculating the helicity sequence offset for each copy of the sequence would be valuable as well