Skip to content

MuonAlignmentCondAlg - Allow for duplicated channels

Johannes Junggeburth requested to merge jojungge/athena:FixAlignCrash into 23.0

Hi everybody,

in !64287 (merged), I cleaned up the A&B line data flow and also introduced a more rigorous check on the duplicated channels in the container. I was not aware that the current data23 alignment has BIS78 in the endcap and barrel folder

04:03:54 MuonAlignmentCondAlg                                   0     0 WARNING More than one (A-line) entry in folder /MUONALIGN/MDT/ENDCAP/SIDEA for  BIS at Jzz/Jff 7/1 --- keep the latest one
04:03:54 MuonAlignmentCondAlg                                   0     0 WARNING More than one (B-line) entry in folder /MUONALIGN/MDT/ENDCAP/SIDEA for  BIS at Jzz/Jff 7/1 --- keep the latest one
04:03:54 MuonAlignmentCondAlg                                   0     0 WARNING More than one (A-line) entry in folder /MUONALIGN/MDT/ENDCAP/SIDEA for  BIS at Jzz/Jff 7/2 --- keep the latest one
04:03:54 MuonAlignmentCondAlg                                   0     0 WARNING More than one (B-line) entry in folder /MUONALIGN/MDT/ENDCAP/SIDEA for  BIS at Jzz/Jff 7/2 --- keep the latest one
04:03:54 MuonAlignmentCondAlg                                   0     0 WARNING More than one (A-line) entry in folder /MUONALIGN/MDT/ENDCAP/SIDEA for  BIS at Jzz/Jff 7/3 --- keep the latest one
04:03:54 MuonAlignmentCondAlg                                   0     0 WARNING More than one (B-line) entry in folder /MUONALIGN/MDT/ENDCAP/SIDEA for  BIS at Jzz/Jff 7/3 --- keep the latest one
04:03:54 MuonAlignmentCondAlg                                   0     0 WARNING More than one (A-line) entry in folder /MUONALIGN/MDT/ENDCAP/SIDEA for  BIS at Jzz/Jff 7/4 --- keep the latest one
04:03:54 MuonAlignmentCondAlg                                   0     0 WARNING More than one (B-line) entry in folder /MUONALIGN/MDT/ENDCAP/SIDEA for  BIS at Jzz/Jff 7/4 --- keep the latest one
04:03:54 MuonAlignmentCondAlg                                   0     0 WARNING More than one (A-line) entry in folder /MUONALIGN/MDT/ENDCAP/SIDEA for  BIS at Jzz/Jff 7/5 --- keep the latest one
04:03:54 MuonAlignmentCondAlg                                   0     0 WARNING More than one (B-line) entry in folder /MUONALIGN/MDT/ENDCAP/SIDEA for  BIS at Jzz/Jff 7/5 --- keep the latest one
04:03:54 MuonAlignmentCondAlg                                   0     0 WARNING More than one (A-line) entry in folder /MUONALIGN/MDT/ENDCAP/SIDEA for  BIS at Jzz/Jff 7/6 --- keep the latest one
04:03:54 MuonAlignmentCondAlg                                   0     0 WARNING More than one (B-line) entry in folder /MUONALIGN/MDT/ENDCAP/SIDEA for  BIS at Jzz/Jff 7/6 --- keep the latest one
04:03:54 MuonAlignmentCondAlg                                   0     0 WARNING More than one (A-line) entry in folder /MUONALIGN/MDT/ENDCAP/SIDEA for  BIS at Jzz/Jff 7/7 --- keep the latest one
04:03:54 MuonAlignmentCondAlg                                   0     0 WARNING More than one (B-line) entry in folder /MUONALIGN/MDT/ENDCAP/SIDEA for  BIS at Jzz/Jff 7/7 --- keep the latest one
04:03:54 MuonAlignmentCondAlg                                   0     0 WARNING More than one (A-line) entry in folder /MUONALIGN/MDT/ENDCAP/SIDEA for  BIS at Jzz/Jff 7/8 --- keep the latest one
04:03:54 MuonAlignmentCondAlg                                   0     0 WARNING More than one (B-line) entry in folder /MUONALIGN/MDT/ENDCAP/SIDEA for  BIS at Jzz/Jff 7/8 --- keep the latest one

On a longer time scale, we'd need new alignment conditions tag (Tagging: @amelung and @giraudpf). For the moment, I disabled the duplication check. Tagging @wlampl, @jmaurer

Merge request reports