 Fri May 22 16:19:01 2020, Andrey Starodumov, Software, Change in MoreWeb GradingParameters.cfg
|
Xray noise:
grade B moved from 300e to 400e
grade C moved from 400e to 500e |
|
Fri May 22 17:09:37 2020, Andrey Starodumov, FTs for ETHZ, Module list1
|
[COLOR=green]green[/COLOR]: correct in Total production overview
black: to remove old entries/raws
[COLOR=red]red[/COLOR]: many failures at one or both temperatures
|
|
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 |
|
Mon May 25 17:24:05 2020, Andrey Starodumov, Software, Change in MoreWeb ColumnUniformityPerColumn.py
|
In file
~/L1_SW/MoReWeb/Analyse/TestResultClasses/CMSPixel/QualificationGroup/XRayHRQualification$ emacs Chips/Chip/ColumnUniformityPerColumn/ColumnUniformityPerColumn.py
the high and low rates at which double column uniformity is checked are hard coded. Rates for L2 was there. Now correction is added:
|
|
Thu May 28 14:38:43 2020, Andrey Starodumov, Module transfer, 18 Modules shipped to ETHZ
|
1536, 1537, 1539, 1540, 1541,
1543, 1545, 1547, 1548, 1550,
1551, 1552, 1553, 1554, 1565,
|
|
Thu May 28 14:40:57 2020, Andrey Starodumov, Module transfer, 8 modules shipped to PSI
|
Quick check: Leakage current, set Vana, VthrCompCalDel and PixelAlive
Module Current@-150V Programmable Readout
[COLOR=red]M1555 -6.000uA OK OK Current is rising up to 11uA with time after PixelAlive is done at +22C !!![/COLOR]
|
|
Fri May 29 13:56:35 2020, Andrey Starodumov, Re-grading, M1630
|
In ROC1 of M1630 gain calibration failed massively (3883 pixels) at +10C with CtrlReg 9.
A special test of M1630 only at +10C and with CtrlReg 17 showed no problem.
p10_1 from ~/L1_DATA/ExtraTests_ToBeKept/M1630_FullTestp10_2020-04-17_15h54m_1587131688/000_Fulltest_p10
|
|
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 May 29 15:41:40 2020, Andrey Starodumov, General, M1546 
|
ROC10 of M1546 has 107 pixels with trimming problems:
in a VCal threshold scan after trimming 81 has a threshold underflow, means <0, and 26 pixels are outside 40-60VCal window (around Vcal 50) at +10C only.
Trimbit distribution looks reasonable.
|
|
Fri May 29 15:56:27 2020, Andrey Starodumov, FTs for ETHZ, Module list2
|
[COLOR=green]green:[/COLOR] correct in Total production overview
black: to remove old entries/rows
[COLOR=red]red:[/COLOR] many failures at one or both temperatures
|
|
Thu Jun 4 15:32:50 2020, Andrey Starodumov, Module transfer, 18 Modules shipped to PSI
|
Quick check: Leakage current, set Vana, VthrCompCalDel and PixelAlive
T=+24C
|
|
Fri Jun 5 13:47:11 2020, Andrey Starodumov, Module grading, M1613
|
FT of this modules has been done twice: March 23 and March 25, in both cases with the final test SW. On March 23 module was graded C due to many trim bit
failures. That is why it was retested. But after failure in trimbits were excluded from the grading, FT of Mar 23 looks better then later FT of Mar25.
That is why FT of Mar 23 is kept. |
|
Fri Jun 5 16:22:19 2020, Andrey Starodumov, General, Cleaning L1_DATA directory
|
To be able to analyse Xray data and keep Total Production overview in a proper state we need to clean L1_DATA directory.
Reasons:
1) if one analyse Xray test results with flag -new, then all deleted with -d flag tests will be analysed again and Total production overview will have |
|
Mon Jun 15 10:36:45 2020, Andrey Starodumov, FTs for ETHZ, Module list 3
|
M1596 2020-04-28
M1597 2020-04-30
M1598 2020-05-04
|
|
Fri Aug 14 13:47:26 2020, Andrey Starodumov, General, new PH optimisation test and Total Overview
|
New PH optimisation is done at -20C as a FT, hence the results of this test are added to "DB" file as the second m20_1 test.
If there are more than one result per test in the DB file the total production overview is corrupted in a way that for such
modules # of defects is not calculated (due to ambiguity) and hence these modules are not rank according to the number of defects.
|
|
Fri Aug 28 11:13:33 2020, Andrey Starodumov, Module grading, M1615
|
M1615: one pixel in ROC10 unmaskable hence should be graded C. Otherwise the module is of grade A
To be checked! |
|
Fri Aug 28 11:53:23 2020, Andrey Starodumov, PhQualification, M1555
|
There is no new PH optimisation for this module?!
To be checked! |
|
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??? |
|
Fri Aug 28 14:07:24 2020, Andrey Starodumov, PhQualification, M1539
|
There is no new PH optimisation for this module?!
To be checked! |
|
Fri Sep 18 15:45:21 2020, Andrey Starodumov, Other, M2211 and M2122
|
I made a mistake and instead M2122 used ID M2211 in the .ini file.
Hence now we do not have entry for M2122 but have 2 entries for M2211: one is of Sept 18 and another one called old of Sep 17).
Test results of Sep 17 are for 2211
|