Developments for the GeoModelXMLDumper - The first nail in AGDD's coffin

Hi everybody,

this is the first prototype of the GeoModelXML dumper conversion programme. The idea behind it is to take any kind of GeoModel plugin and to dump it into a XML file that can be interpreted by the generic GeoModelXML plugin. E.g.

dumpGeoXML -p ../install/lib/libToroidPlugin.so \
           -o ${run_dir}/dumpedXML.xml

As indicated in the description, the first & major use case will be the trans ToroidPlugin which is based on AGDD. If that translation is successful and correct, then we can say tschuuuuuus AGDD and press on its delete button.

A long the line, I introduced a couple of functions which can be of wider use, but I'm not certain whether we should put them into the GeoModelKernel itself. Hence, I opened the package GeoModelFuncSnippets

• dump the transformations to screen
• Comparison operators of GeoShapes, GeoTrf::Transform3D and GeoPhysVol. Eventhough, the objects are not the same, these operators allow to classify two distinct objects as equivalent if all of their defining parameters are the same within a certain precision. Usually that's in the order of microns.
• GeoShapeUtils: Helper functions to retrieve the operands of the boolean volumes or to collapse a concatination of GeoShapeShifts into a single GeoShapeShift object. Standard way to print a GeoShape to screen.
• defineWorld(): I've seen that the world node is reimplemented over and over again at lots of different places. I've created a createGeoWorld() function for this.
• getChildrenWithRef (). Retrieves all children from the GeoVPhysVol together with the associated transformation. If the child volume is the same as the previous child and it's in kind of a regular pattern, then this volume is not added to the list but the copy number is incremented instead.
• The Euler angles are already described in !244 (merged)

Last but not least, I've added a new feature to GeoModelXML itself. The <shapeshift> XML tag will create a GeoShapeShift from a previously registered shape.

Tagging: @boudreau, @rbianchi, @dellacqu, @tsulaia, @mbandier, @nstyles, @smeriano, @todorova, @ncalace, @asalzbur, @goblirsc

changed title from Draft: Developments for the GeoModelXMLDumper - The first nails in AGDD's coffin to Draft: Developments for the GeoModelXMLDumper - The first nail in AGDD's coffin

added 2 commits

• 91ffbd12 - Fill the define world with life
• eb806026 - Dump the shapes

Compare with previous version

added 2 commits

• a1b1ef4e - More developments
• a9b85ce2 - Albetrtus.... Please clap the switch

Compare with previous version

added 1 commit

• 4f4ce9f2 - Does this fix the CI?

Compare with previous version

added 1 commit

• 4ac175e9 - Introduce geoshapeshift routine

Compare with previous version

changed the description

This is quite interesting but before you say tschuß AGDD there are a couple of things you may wish to consider:

1. is the XML file you come up with readable and understandable (by a human being, I mean). It might well be that one may wish to change things here and there and the resulting file(s) might be so cryptic that this will not be possible (especially since all formulae will be expanded to numbers, which is what made the Georgian blurbs unusable, at the end of the day)
2. the present description of the toroids and related shit is overkill (if not plain wrong) and I would suggesting going through the existing stuff and simplify, rather than translating shit into different shit.

Future you should then be aware that the envelope for the muon system (chambers) and the envelope for the toroids and other paraphernalia will be largely superimposed and future you will have to figure out a way to make these to coexist.

added 1 commit

• 0f0a2be6 - Make world dimensions as arguments

Compare with previous version

changed the description

added 8 commits

• d3d7257c - Ensure that transformations are unique
• 3eb0226b - Dump the top volumes into separate XMLs
• 2541835f - Implement standard dtd copy mechanism. Put the published top nodes into subdirectories
• 89252b87 - Material fiele
• 5ca8b9f1 - Removed unused duplicated class
• 98bf74ba - Material manager update
• 4da30dee - What's the difference between transofmr and transformation'
• ca47258a - Now I got the difference

Compare with previous version

added 2 commits

• 9aaec46c - Mimimimi a multicopy needs to be in an assembly... Mimimimimimi
• 49e6bd76 - convert angular variables into degrees

Compare with previous version

added 37 commits

• 49e6bd76...5262cef7 - 9 commits from branch main
• 5262cef7...e515a6f6 - 18 earlier commits
• bde2f209 - Implement standard dtd copy mechanism. Put the published top nodes into subdirectories
• 3ed4ee09 - Material fiele
• ee159d8e - Removed unused duplicated class
• 6eb45f06 - Material manager update
• fde6a33d - What's the difference between transofmr and transformation'
• e5c5a41f - Now I got the difference
• ab89ee64 - Mimimimi a multicopy needs to be in an assembly... Mimimimimimi
• d76be694 - convert angular variables into degrees
• 0c6c031c - Take the fact whether a child is a full physical volume into accoutn
• cc573f61 - No need to dump the material map

Compare with previous version

mentioned in merge request !249 (merged)

added 1 commit

• cbdede37 - Add method to extract Euler angles from a rotation matrix

Compare with previous version

added 5 commits

• cbdede37...1eccc850 - 4 commits from branch main
• f03e395a - Fix merge conflicts

Compare with previous version

added 14 commits

• f03e395a...6a3140fc - 13 commits from branch main
• 73ec7e91 - Merge with main

Compare with previous version

added 7 commits

• 73ec7e91...816cea94 - 6 commits from branch main
• fc29f661 - Fix merge conflicts

Compare with previous version