assigned to @cpeng
I added the script to CI since if we are using an anti-pattern (even where misguided) we might as well make sure the output is consistent for as long as we are using it... So, IMO, removing the script from CI should only happen when the design is fully implemented as a dd4hep plugin.
I plan to modify the script so it reads the xml instead of writing to it. The writing part was to make the first version of that xml file, and it will be moved to a separate function.
It may complicate the maintenance or development if the detector information is stored in a separate python script.
!127 (merged), will add back a similar CI job as a placement check that reads the xml file
closed