Masking error
The masking written in the chip configuration file does not correspond to the mask from the relative scan. The number of masked pixels is the same in the two files, however the pixels masked in the chip configuration file are scattered all over the place with some pattern.
YARR devel
branch at commit cfdb33b4
is affected. Tag v1.3.1
seems not to be affected.
See the figures below for example. These were obtained from the output files of an analog scan on two RD53B chips from a quad. Note that the analog scan has been run after a digital -m 1
scan, which did not mask anything. Here one can notice the difference between the fully enabled .json.before
, the EnMask.json
with clustered disabled pixels and the .json.after
with scattered disabled pixels. Other modules and scans show the same issue.
Chip 2 configuration file before the analog scan, all pixels are enabled:
Chip 2 EnMask file from the analog scan, showing two disabled columns plus two other pixels (770 in total):
Chip 2 configuration file after the analog scan, showing 770 scattered disabled pixels:
Chip 3 configuration file before the analog scan, all pixels are enabled:
Chip 3 EnMask file from the analog scan, showing a cluster of 19 disabled pixels:
Chip 3 configuration file after the analog scan, showing 19 scattered disabled pixels: