DAQ Testing/20181102
From PREX Wiki
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
November 5th, 2018 Testers: Cameron
Goals
- Measuring ET bridge paradigm analyzer deadtime
- Check that forced blocking deadtime actually affects DAQ readouts
- Check that -nb, -n, -s, -q, and chunk size can or cannot help
Tests
- Run 4556 - non-blocking - simple analysis - 961.524 Hz set rate - 28.7829 % deadtime in analyzer - 0 % deadtime in DAQ
- Run 4558 - non-blocking - 200 us delay ana - 961.524 Hz set rate - 76.0947 % deadtime in analyzer - 0 % deadtime in DAQ
- Run 4561 - switching to blocking mode to see if the TI board cares about CODA
- Run 4561 - blocking - 200 us delay ana - 961.524 Hz set rate - 0 % deadtime in analyzer - 0 % deadtime in DAQ
- Run 4561 - blocking - 2,000 us delay ana - 961.524 Hz set rate - 51 % deadtime in analyzer - 0 % deadtime in DAQ
- Run 4561 - blocking - 20,000 us delay ana - 961.524 Hz set rate - 82.1063 % deadtime in analyzer - 0.38 % deadtime in DAQ (after the run the ROC complains that "interrupt: Ev#172055: VQWK 0 timed out with timer=-200.logTask: 201 log messages lost." for a large number of events, probably the ones that were held up)
- Run 4561 - blocking - 200,000 us delay ana - 961.524 Hz set rate - 98.5522 % deadtime in analyzer - 0.101346 % deadtime in DAQ
- Run 4561 - blocking - 2,000,000 us delay ana - 961.524 Hz set rate - 99.949 % deadtime in analyzer - 0.0 % deadtime in DAQ
- Run 4562 - blocking - swapped the TI busy to ADC read signal and got no scaler incrementing for any time delays
- Run 4563 - blocking - restored it... maybe deadtime is differnent? (Ask Ed or Carl?)
