DAQ To-Do List
Back to Main Page >> DAQ Documentation Portal >> DAQ Testing >>
DAQ To-Do List - for more information see DAQ Doc Portal
See testing day-by-day to do lists in DAQ Testing/To-Do-Lists
August 3rd
Cameron and Chandan visited for a week and a half again in late July/early August
Accomplished Recently
- Revive all crates.
- Deploy all ADCs needed and test each channel.
- Build various DAQ configs with subsets of the DAQ crates.
- RS485 cable between HRS to build full system.
List
1. Timing diagram, check timing of external signals and readout.
2. Test rate limit, ensure deadtime zero.
3. Ensure that ET system is fast enough for feedback.
4. Revive the synchronization-check system.
5. Add a scaler to R-HRS crate.
6. Implement Bank structure.
7. Eliminate the so-called "dirty trick" if we can (clean up CRL)
8. Check the 7200 scaler setup at injector, find a spare 7200.
9. Pedestal studies, aka cross-talk.
10. Green Monster maintenance.
11. Test spares. (I will have Ye Tian start this.)
12. Document everything. Circuit diagrams, cable map, "how to".
13. Test new analysis software as it becomes available.
14. Online software, a bit undefined since software is changing. Some ideas here:
- automatic production of run-dependent database
- alarms like end-of-run voice
- feedback
- coil-pulsing aka modulation aka dithering
- panguin (GUI showing real-time plots)
- prompt analysis
- e-logbook entries
- archiving EPICs data
July 30th
Preparing for Cameron and Chandan's second visit to JLab in Summer 2018
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. Bank structure
11. Pedestal studies, aka cross-talk
12. Green Monster maintenance
13. Online software, a bit undefined since software is changing. Some ideas here:
- automatic production of run-dependent database
- alarms like end-run voice
- feedback
- coil-pulsing
- panguin (GUI showing real-time plots)
- prompt analysis
- e-logbook entries
- archiving EPICs data
Email from July 3rd
Things to try to do in that week:
- Test each ADC and scaler with signals. (add scaler to R-HRS ?)
- Possibly test new software if its available (otherwise use old software)
- Learn how to set up and adjust timing (flip rate, etc).
- Test the rate limit, measure deadtime, ensure it is zero.
- Ensure that the ET system is fast enough for feedback.
- Implement the synchronization-check system.
- Bank Structure
Lower priority:
- Test spare electronics.
- Archive EPICS data (final solution can wait until just before we run)
- Automatic e-logbook entries ( ditto )
Things we accomplished on Cameron and Chandan's first visit:
- Revive the two spectrometer VME crates.
- Deploy all ADCs needed for the experiment.
- Build various DAQ configs including the full system.
- Fix the RS485 cable between spectrometers.
Then there is a host of items to do once the new software is settled, like archiving a run-dependent database, the feedback software, coil pulsing, a GUI to show real-time plots, prompt analysis. Kent probably has a better overview of that.
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
Accomplished 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