DAQ Meeting/20180524

From PREX Wiki
Revision as of 22:34, 24 May 2018 by Cameronc (Talk | contribs) (Minutes)

Jump to: navigation, search

Back to Main Page >> DAQ_Meeting

previous meeting << >> following meeting

Logistic information

 BlueJeans calling instructions:
 Toll-Free Number (U.S.&  Canada):  888-240-2560
 International toll number:         408-740-7256
 Bluejeans CODE:                  475 839 391
 Bluejeans link: https://bluejeans.com/475839391


  • Chandan, Tyler, Cameron : Verify signals coming into counting house Helicity DAQ are all what we expect
  • Bob : Set up RHRS DAQ and add to TS
  • Bob : Set up LHRS DAQ, add QWeak ADCs, connect to RHRS, and add to TS (should be harder)
  • Long-range plan :
    • Finish setting up all DAQ components to Trigger Supervisor Control (TSC) and verify all components work as intended
    • PAN, post-PAN and PAN-guin (Parity Analyze software) should all be rewritten, primarily to bring its functionality into the current group's control.


  • Morning - 9AM - Chandan, Tyler, Cameron : Verify signals coming into counting house Helicity DAQ are all what we expect.
    • We checked the signals coming out of the 4 modules in the Helicity DAQ (documented in the Helicity Control Board User’s Guide - Draft 2) and they behaved as expected (see figures 5 and beyond in the guide for visualization).
    • There are 4 separate signals (from left to right).
      • Pattern Sync (previously called, and currently labelled as QRT/Quartet, also called T_Stable): Logic spike for the duration of the first window of each helicity quartet. This signal can also be called T_Stable since when it is not true the Pockels Cell is stable.
      • T_Settle (previously called, and currently labelled as MPS/Master Pulse): Narrow spikes at the beginning of each individual helicity window. Indicates the time the DAQs will not collect data allowing for the Pockels Cell to settle. This signal goes to the users.
      • HEL (the delayed helicity signal, not the helicity signal sent to Pockels cell): Logic spike signal indicating the actual helicity state.
      • Pair Sync: On, off, on, off cycling logic spikes which cycle matching time with the helicity window and which tell you whether you are in the first or second window of any given pair (and consequently the position in a quartet, since quartets are just a pair and its converse in sequence). This signal toggle between 0 and 1, other wise it looks like the helicity signal. It is used to make T_Stable (the integration window). It goes to the users.
  • Morning - 10AM - Bob : Run RHRS .crl in CODA and see what happens.
    • It doesn't work, so we need to go see what is happening with the wires and crates on the RHRS itself.