|Message: NaN values in energy dose deposit (dicom.out) for GeneralParticleSource in 4.9.6||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've come across a problem (bug?) in GeneralParticleSource. When running the DICOM example of my 4.9.6p01 build with a GPS, a small spare of voxels will show a -nan value in the energy deposit "dicom.out" file. The amount of voxels with NaN depends on the actual number of shot gammas. The longer I simulate (in terms of total events in /run/beamOn) the more NaNs I get - of course because more voxels are hit, but the relative amount of nan voxels/total voxels is also increasing.
I just tested again with the original G4ParticleGun - no NaNs at all. Now, is there anybody out there who encountered the same problem? Is this a known bug in my release? Maybe one could test whether this is fixed in a more recent release by just using GPS and shooting 1e6 gammas with GPS on the phantom.
Any help highly appreciated - thanks!