Difference between revisions of "DAQ To-Do List"

From PREX Wiki
Jump to navigationJump to search
(Created page with "DAQ To-Do List - for more information see DAQ_Doc_Portal == May 31 2018 == Cameron and Chandan visited Bob for 2 weeks and worked on DAQ related tasks, as well as GEM COD...")
 
Line 1: Line 1:
DAQ To-Do List - for more information see [[DAQ_Doc_Portal]]
+
DAQ To-Do List - for more information see [[DAQ Doc Portal]]
  
 
== May 31 2018 ==
 
== May 31 2018 ==

Revision as of 15:44, 8 August 2018

DAQ To-Do List - for more information see DAQ Doc Portal

May 31 2018

Cameron and Chandan visited Bob for 2 weeks and worked on DAQ related tasks, as well as GEM CODA DAQ for the SBU group

What was Done Recently

During the 2-week visit of Cameron and Chandan to JLab in late May we managed to do items 1, 4, 5, 6, and the "deploy" part of 2 but not the "testing" part. It was a productive visit. We have a fully working DAQ with enough Qweak ADC channels to run; but also HAPPEX ADCs in the HRS and counting room. If another visit happens this summer, we'd do the "testing" part of item 2 and also 7, 8, 9. Testing the rate limit will involve learning how to configure and check the timing. Item 3 (testing spares) can be done in our test stand; it doesn't need access to the hall, so we can postpone it to the Fall.

For the software (item 10) I'll try to have a version of "pan" ready to at least look at raw signals. But I am worried about item 10 being ready for the experiment. With a fully working DAQ we could do parasitic tests this Fall, if desired.

List

1. Revive spectrometer crates. 2. Deploy all ADCs and test them. 3. Obtain and test the spares. 4. Build various DAQ configs with subsets of the DAQ crates. 5. Find / remake the RS485 cable between HRS to build full system. 6. Move our DAQ to new computer. 7. Test rate limit, ensure deadtime zero. 8. Ensure that ET system fast enough for feedback. 9. Revive the synchronization-check system. 10. Online software, a bit undefined since software is changing. Some ideas here:

  • automatic production of run-dependent database
  • feedback
  • coil-pulsing
  • panguin (GUI showing real-time plots)
  • prompt analysis
  • e-logbook entries
  • archiving EPICs data