T0 Scan
This page presents the tests that were performed on the T0 Scan. In the Göttingen lab an USBpix system was used as a ROD and an alternating plot behavior was seen. See also
here
for a summary presentation at the DAQ meeting. The code can be found in the following branch: /user/jmellent/PixelDAQ-02-05-00_T0
Changes in PixModuleGroup::endT0Set(...)
- Distinction between PixScan::TIMEWALK and PixScan::SCURVE_MEAN was removed. Now always PixScan::SCURVE_MEAN is chosen
- For test purposes conv[ife] is set to 1
- For dummy values of double a = (*hTime)(col, row); and double b = (*hTime1)(col, row); the alternating plot behavior occurs still
- ((ConfFloat &)((*fe)->config()["Misc"]["DelayCalib"])).m_value is always 1 for conv[ife] = 1 and for a non fixed calibration it increases with every scan
Changes in PixModuleGroup::writeConfig(...)
- Added check to see if PlsrldacRamp is set correctly
Checks in USBPixController::writeScanConfig(...)
- scn.getStrobeLVL1DelayOverride() is always 1
- reduce_lvl1delay is always 0
- scn.getStrobeLVL1Delay() has the same values as reg_data[3] and a range from 56 to 58
- These values are also identical for multiple scans
- Changed reg_data[3] = (scn.getStrobeLVL1Delay() - reduce_lvl1delay); to reg_data[3] = (unsigned char) (scn.getStrobeLVL1Delay() - reduce_lvl1delay);
Suspects for the alternating plot behavior
- Inside USBPixController
- Or USBpix code called from there (top suspect)
- Inside post-loop histogram processing (would also affect IBL RODs)
--
JohannesDonatusMellenthin - 2017-01-17
Topic revision: r2 - 2017-01-17
- unknown