DAQ Testing/20190204

From PREX Wiki
Revision as of 11:57, 4 February 2019 by Cameronc (talk | contribs) (Created page with "Back to Main Page >> DAQ Documentation Portal >> DAQ Testing >> DAQ Commissioning Notes DAQ_Tes...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

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

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

February 4th, 2019 Testers: Cameron Clarke, Devi Adhikari

Goals

  • Restore Helicity Control Board in CH crate
  • Establish standard DAQ procedure
  • Establish standard data analysis procedure
  • Take pedestal noise floor calibration runs for updated SAM cabling configuration

Restore Helicity Control Board in CH crate

We took the fiber translator board and put it back in.

Importantly we noticed that the vqwk_1 and _4 were improperly inserted into the CH VME crate and we properly inserted them

  • Run 1193 - checks that this fixed vqwk_1_channels that weren't working to work now hopefully
    • Result:

Establish Standard DAQ Procedure

Steps to utilize the Parity DAQ in a healthy and collaborative fashion. The "DAQ" here refers to the CODA system and its attached processes, which must be run from within the "apar" user account on the "adaq" computer system. We prefer to use "adaq3" computer for parasitic testing purposes, but when PREX/CREX runs we will switch over to the new "adaq1" machine instead. We should be careful to utilize the "parity-daq" channel of the PREX collaboration Slack Channel to alert other users to intended DAQ operations and availability. For optimal collaboration the DAQ should be run only from the MCC building for injector studies or the 1st or 2nd floor of the counting house (or the HRS laptops for on the fly testing).

  • Log into apar@adaq3 (later adaq1):
ssh -Y apar@adaq3