 Fri May 15 17:15:34 2020, Andrey Starodumov, XRay HR tests, Analysis of HRT: M1630, M1632, M1636, M1638
|
Krunal proved test result of four modules and Dinko analised them.
M1630: Grade A, VCal calibration: Slope=43.5e-/Vcal, Offset=-145.4e-
M1632: Grade A, VCal calibration: Slope=45.4e-/Vcal, Offset=-290.8e-
|
|
Fri May 22 16:06:43 2020, Andrey Starodumov, XRay HR tests, Analysis of HRT: M1623, M1632, M1634, M1636-M1639,M1640
|
Module HRtest VCal calibration Grade
#defects max #noisy pix
ColdBox XRay
|
|
Mon May 25 16:58:23 2020, Andrey Starodumov, XRay HR tests, a few commments
|
These is just to record the information:
1. measured hit rates at which Efficiency and Xray hits Maps are taken are 40-50% of the 50-400MHz/cm2 that in the titles of corresponding plots
2. in 2016 the maximum rate was 400MHz/cm2 but with such rate (or better corresponding settings of HV and current of Xray tube) in double columns of certain |
|
Fri May 29 15:04:04 2020, Andrey Starodumov, XRay HR tests, Analysis of HRT: M1555-M1561 and M1564
|
Module HRtest VCal calibration Grade
#defects max #noisy pix
ColdBox XRay
|
|
Fri Aug 28 12:02:48 2020, Andrey Starodumov, XRay HR tests, M1599
|
| ROC5 has eff=93.65% and should be graded C. Somehow efficiency was not taken into account for HR test grading??? |
|
Tue Aug 6 16:01:17 2019, Matej Roguljic, Software, Wrong dac settings - elComandante
|
If it seems that elComandante is taking wrong dac settings for tests like Reception test or full qualification, one should remember that it does NOT read
values from module specific folders like "M1523", but rather from tbm-specific folders like "tbm10d". The folders from which the dacs are taken are listed
in "elComandante.config", the lines which look like "tbm10d:tbm10d". |
|
Thu Sep 26 15:51:30 2019, Dinko Ferencek, Software, pXar code updated
|
pXar code in /home/l_tester/L1_SW/pxar/ on the lab PC was updated yesterday from [URL=https://github.com/psi46/pxar/tree/15b956255afb6590931763fd07ed454fb9837fc0]https://github.com/psi46/pxar/tree/15b956255afb6590931763fd07ed454fb9837fc0[/URL]
to the latest version [URL=https://github.com/psi46/pxar/tree/e17df08c7bbeb8472e8f56ccd2b9d69a113ccdc3]https://github.com/psi46/pxar/tree/e17df08c7bbeb8472e8f56ccd2b9d69a113ccdc3[/URL]
which among other things contains updated DAC settings for ROCs.
|
|
Thu Sep 26 22:09:14 2019, Dinko Ferencek, Software, DAC configuration update
|
In accordance with the agreement made in an email thread initiated by Danek, the following changes to DAC settings for ROCs
vsh: 30 -> 8
|
|
Wed Oct 2 12:50:52 2019, Dinko Ferencek, Software, Problem with elComandante Keithley client during full qualification
|
Full qualification was attempted for M1532 on Oct. 1. After the second Fulltest at -20 C finished, the Keitley client crashed with the following error
[CODE]
|
 Sat Oct 5 22:59:58 2019, Dinko Ferencek, Software, Problem with elComandante Keithley client during full qualification
|
A new attempt to run the full qualification for M1532 was made on Friday, Oct. 4, but the Keithely client crashed with the same error message. This time
we managed to see from log files that the crash happened after the first IV measurement at -20 C was complete and Keithley was reset to -150 V. Unfortunately,
the log files were now saved for the test on Tuesday so we couldn't confirm that the crash occurred at the same point. |
|
Mon Oct 28 17:01:05 2019, Matej Roguljic, Software, Investigating the bug with the Keithley client
|
We took module 1529 and tried recreating the issue observed in the beginning of October. To do this in a reasonable amount of time, a "shorttest" procedure
was defined which consists only of pretest and pixelalive. Three runs were taken
|
|
Tue Oct 29 16:38:32 2019, Matej Roguljic, Software, Investigating the bug with the Keithley client
|
[quote="Matej Roguljic"]We took module 1529 and tried recreating the issue observed in the beginning of October. To do this in a reasonable amount of time,
a "shorttest" procedure was defined which consists only of pretest and pixelalive. Three runs were taken
|
|
Wed Oct 30 16:54:58 2019, Matej Roguljic, Software, Investigating the bug with the Keithley client
|
[quote="Matej Roguljic"][quote="Matej Roguljic"]We took module 1529 and tried recreating the issue observed in the beginning of October. To do this in a
reasonable amount of time, a "shorttest" procedure was defined which consists only of pretest and pixelalive. Three runs were taken
|
|
Wed Nov 27 18:25:08 2019, Dinko Ferencek, Software, pXar code updated
|
pXar code in /home/l_tester/L1_SW/pxar/ on the lab PC was updated on Monday, Nov. 25 from [URL=https://github.com/psi46/pxar/tree/e17df08c7bbeb8472e8f56ccd2b9d69a113ccdc3]https://github.com/psi46/pxar/tree/e17df08c7bbeb8472e8f56ccd2b9d69a113ccdc3[/URL]
to [URL=https://github.com/psi46/pxar/tree/9c3b81791738e1b8ec7dd9f0d1b68f8800f8416c]https://github.com/psi46/pxar/tree/9c3b81791738e1b8ec7dd9f0d1b68f8800f8416c[/URL]
which pulled in the latest updates to the pulse height optimization test. Today a few remaining updates were pulled in by going to the current HEAD of |
|
Wed Nov 27 21:50:02 2019, Dinko Ferencek, Software, Reorganized pXar configuration files for pixel modules
|
Due to different DAC settings needed for PROC V3 and V4, a single folder containing module configuration files cannot cover both ROC types. To address this
problem, the existing folder 'tbm10d' in /home/l_tester/L1_SW/pxar/data/ containing configuration for PROC V4 was renamed to 'tbm10d_procv4' and a new
folder for PROC V3, 'tbm10d_procv3', was created. For backward compatibility, a symbolic link 'tbm10d' was created that points to 'tbm10d_procv4'.
|
|
Thu Nov 28 18:23:31 2019, Dinko Ferencek, Software, Reorganized pXar configuration files for pixel modules
|
[quote="Dinko Ferencek"]Due to different DAC settings needed for PROC V3 and V4, a single folder containing module configuration files cannot cover both
ROC types. To address this problem, the existing folder 'tbm10d' in /home/l_tester/L1_SW/pxar/data/ containing configuration for PROC V4 was renamed to
'tbm10d_procv4' and a new folder for PROC V3, 'tbm10d_procv3', was created. For backward compatibility, a symbolic link 'tbm10d' was created that points |
|
Thu Nov 28 18:34:00 2019, Dinko Ferencek, Software, pXar code updated
|
[quote="Dinko Ferencek"]pXar code in /home/l_tester/L1_SW/pxar/ on the lab PC was updated on Monday, Nov. 25 from [URL=https://github.com/psi46/pxar/tree/e17df08c7bbeb8472e8f56ccd2b9d69a113ccdc3]https://github.com/psi46/pxar/tree/e17df08c7bbeb8472e8f56ccd2b9d69a113ccdc3[/URL]
to [URL=https://github.com/psi46/pxar/tree/9c3b81791738e1b8ec7dd9f0d1b68f8800f8416c]https://github.com/psi46/pxar/tree/9c3b81791738e1b8ec7dd9f0d1b68f8800f8416c[/URL]
which pulled in the latest updates to the pulse height optimization test. Today a few remaining updates were pulled in by going to the current HEAD of |
|
Thu Nov 28 18:58:30 2019, Dinko Ferencek, Software, Updated Fulltest configuration
|
The Fulltest definition used on the lab PC and stored in /home/l_tester/L1_SW/elComandante/config/tests/Fulltest had the following content
pretest
|
|
Mon Jan 20 13:47:33 2020, Dinko Ferencek, Software, pXar code updated
|
[quote="Dinko Ferencek"][quote="Dinko Ferencek"]pXar code in /home/l_tester/L1_SW/pxar/ on the lab PC was updated on Monday, Nov. 25 from [URL=https://github.com/psi46/pxar/tree/e17df08c7bbeb8472e8f56ccd2b9d69a113ccdc3]https://github.com/psi46/pxar/tree/e17df08c7bbeb8472e8f56ccd2b9d69a113ccdc3[/URL]
to [URL=https://github.com/psi46/pxar/tree/9c3b81791738e1b8ec7dd9f0d1b68f8800f8416c]https://github.com/psi46/pxar/tree/9c3b81791738e1b8ec7dd9f0d1b68f8800f8416c[/URL]
which pulled in the latest updates to the pulse height optimization test. Today a few remaining updates were pulled in by going to the current HEAD of |
|
Wed Jan 22 11:39:48 2020, Dinko Ferencek, Software, BB2 configuration
|
When attempting to run the FullQualification this morning, pXar crashed while running the BB2 test. After some investigation, we realized the source of
the problem was the BB2 configuration missing from testParameters.dat. The configuration is available in moreTestParameters.dat but by default the mkConfig
script does not put it in testParameters.dat. Since we run BB2 in the FullQualification, the configuration needs to be copied by hand every time the configuration |