|Message: Obtaining position vectors relative to local G4PVPlacement||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 everyone. I am working on a geometry that includes a large number of germanium detectors. In G4SteppingAction, I would like to obtain the position of the energy deposition relative to the origin of the germanium detector physical volume, rather than relative to the origin of the world volume. Assuming all germanium detectors are named "Detector001", "Detector002", etc., ideally what I am looking for is to be able to do this: theTrack = theStep->GetTrack(); if( strstr( theTrack->GetVolume()->GetName(), "Detector") ) G4cout << theStep->GetLocalPostStepPoint()->GetPosition.x() << " " << theStep->GetLocalPostStepPoint()->GetPosition.y() << " " << theStep->GetLocalPostStepPoint()->GetPosition.z() << G4endl; where GetLocalPostStepPoint, again, returns the position relative to the origin of the G4PhysicalVolume in which the hit occurred, rather than relative to the origin of the world volume. Does such an implementation exist? Would using a sensitive detector solve this issue, or would I still have to find some way to figure out the G4PhysicalVolume-specific offsets? Given the large number of detectors I'm working with, coupled with no way of knowing a priori where, e.g., Detector001 will actually be (the simulation is built to be highly customizable), I have not been terribly successful in my search for an answer. Perhaps this is covered in one of the examples, and I just haven't recognized it? Thanks for any information or advice. Kareem Kazkaz
|Inline Depth:||Outline Depth:||Add message:|