|Message: Bug in scorer?||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)|
Using Geant4.9.1.p02 on fedora 8
While trying to get the meshBox scorer to work I have found a couple of problems:-
* digits_hits/utils/src/G4ScoringBox.cc Class G4ScoringBox::SetupGeometry() The last argument in the call to G4PVDivision( .... , fSize/fSegment*2.) is the width of the mesh box (as in the call to G4PVReplica) and should be 0.0, the offset of the mesh. This is the same for all the calls to G4PVDivision in this file. The result is that an extra box is added to the mesh in one direction which can be easily verified by creating a meshBox of 2x2x2. The resulting box is 2x2x3. I use Inventor (OIX) for the visualisation and the meshBox can be seen and verified in it.
* digits_hits/utils/src/G4VScoreWriter.cc Class G4VScoreWriter::GetIndex() This took a while to figure out but the index x + y*fNMeshSegments + z*fNMeshSegments *fNMeshSegments is constructed differently to where the data is stored in each of files digits_hits/scorer/src/ 4PS*3D.cc where the index is contructed as i*fNj*fNk+j*fNk+k. I suggest that the index in the writer should be z + y*fNMeshSegments + x*fNMeshSegments *fNMeshSegments. After changing it I can now read in (using imagej) the flux, energy, etc as a 3D image and they make a lot more sense.
I hope this makes sense and is helpful. I have noticed that the beta version 4.9.2 contains the same code.