|Message: Any example (in G4 or from some user out there) for custom G4VSolid subclass?||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)|
I have a situation in my geometry which has managed to kill both visualization and tracking :-) We have a multistage cryostat with detectors and electronics at the center. To get all of the readout and control cables out to room temperature, we will have more than 200 holes and feedthroughs on the lid of the 4K stage (see the attached picture).
I would like to model this detailed structure explicitly, in order to do thermal studies tracking how IR photons get through the holes to the low temperature stages. The obvious (and horribly wrong) solution is to subtract each hole from the cylindrical can of the cryostat. When I do this, both visualization and tracking hang up in a lovely 250-deep calling stack as "DistanceToIn()" calls down through all of the nested boolean solids.
To replace this, I suspect that writing a custom G4VSolid subclass (maybe even a G4Tubs subclass?) is a much better approach. Then the coded in hole positions could be used to determine in vs. out, normals, etc. This was mentioned in a similar posting several years ago (http://hypernews.slac.stanford.edu:5090/HyperNews/geant4/get/geometry/1146/1.html). My question is whether anyone out there has an example of how to properly write a solid subclass, which they would be willing to share. I don't believe any of the G4 examples have one.
-- Michael Kelsey
|Inline Depth:||Outline Depth:||Add message:|