|Message: Tesselated GDML-structures and transformations (overlaps)||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
Hello, I've used fastrad to convert some cad->step files to GDML.
It works almost smoothly, producing a huge file that will with a a few fixes and minute overlap-corrections from the direct output of fastrad give me a beautiful tesselated structure into G4.
But here is what baffles me: if i apply a affine transformation, such as a rotation, to all my physical volumes, I would from basic linear algebra assume there will be no overlaps if there weren't any before.
But adding in any sort of little rotation will give me a bunch of huge overlaps.
A transformation seemed to go fine, but very little else.
My first thought was there is some bug in the gdml parser. But I wrote some python that parses through the gdml-file and applies the same transformation directly to the coordinates. And the same happens with this as well.
Anyone got any clue where I should look for the problem?
Also, the documentation does not even say which point it exactly is that a tesselated volumes "position" is.
Any input greatly appreciated.