ITkPixV1 is hardcoded as module_0
With the new feature of the lane test of rd53b, itkpixv1 has to be defined always as module_0. This should be fixed in order to allow arbitrary module definitions.
With the new feature of the lane test of rd53b, itkpixv1 has to be defined always as module_0. This should be fixed in order to allow arbitrary module definitions.
added Regression label
True, a solution would be to give this info to the chip object during _init_
. The chip object unfortunately does not know about the self.chip_settings
as in scan_base.
Let's nevertheless call it a bug since since it never worked (its a new feature).
This lane test feature is quite quick&dirty...
added Bug label and removed Regression label
Yes true... This was fixed @mstandke?
mentioned in merge request !376 (merged)
Yes, this was fixed in !376 (merged)
closed