WIP: Module flexible chip id numbering
With this change one can modify the chip_id map in the module definition on a chip basis. Thus the same module type can be used even though chips have different chip ids for different chip types. (e.g. [13, 14, 15, 12] in case of ITkPixV1)
Fixes #504 (closed)
Edited by Yannick Manuel Dieter
Merge request reports
Activity
added Bug label
assigned to @kmauer
mentioned in issue #504 (closed)
The chip IDs for the common RD53A quad are still wrong, should be 1-4 and not 0-3
Edited by Thomas Christian Sengeradded 54 commits
-
1d76a623...3379a842 - 47 commits from branch
development
- 5b5f0b6c - ENH: Allows to use chip ids 1 to 4
- e08793dd - ENH: set arbitrary chip ids per chip
- 0879690d - FIX: codestyle
- 70b1af47 - FIX: Typo
- c595d8ca - ENH: better chip_id map in module_types
- 8b509c8d - FIX: wrong shape of chip id map
- dea8096b - ENH: simplification of extend_maps
Toggle commit list-
1d76a623...3379a842 - 47 commits from branch
added 9 commits
-
dea8096b...5e931229 - 2 commits from branch
development
- ab419abd - ENH: Allows to use chip ids 1 to 4
- 27c5281a - ENH: set arbitrary chip ids per chip
- 14b06f3b - FIX: codestyle
- cfbd706a - FIX: Typo
- 64b309b5 - ENH: better chip_id map in module_types
- e06ce2de - FIX: wrong shape of chip id map
- cf6ebb5f - ENH: simplification of extend_maps
Toggle commit list-
dea8096b...5e931229 - 2 commits from branch
enabled an automatic merge when the pipeline for 22ee8c92 succeeds
Please register or sign in to reply