|Message: Re: Trouble with G4SubtractionSolid -- pipe at angle to wall||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)|
John Allison writes: > Quick reply from a non-expert... > > Some geometry functions don't keep the rotation matrix - only the > pointer. Hi, John. That was my first thought as well; when I tried using a pointer, it made no difference. I then traced the G4SubtractionSolid ctor back through its inheritance. Ultimately, the G4RotationMatrix* is passed into the constructor of G4AffineTransform, which simply copies the data members into its own local table. So the pointer is not saved (even though it is stupidly passed as non-const), and just encourages users to create memory leaks :-( > or use an alternative constructor that takes a G4Transform3D - in that > case it makes its own rotation matrix and keeps it. Ironically, I had started out by using G4Transform3D::inverse(), and that wasn't working, so I switched to trying to build the roation myself. I think I may have discovered the problem, and it is (in my opinion) a bug in CLHEP::HepRotation. Once I confirm it, I'll follow up with a detailed post. -- Mike