Created attachment 682 [details] Artifact in Setup1 I initially reported a bug to John Apostolakis and Gabriele Cosmo about G4PhantomParameterisation, which seemed to provide artifacts in the code. They told me to run the newest patch to test out these errors. This bug report in on the newest patch 10.07.p01. Simulation Setup 1: (Medical Physics S-value setup) 1) World is a 5 m x 5m x 5m world filled with air, which contains a cubed geometry filled with water at 81mm x 81mm x 81mm. This cubed geometry was voxelized by a voxel volume of 1 mm3 in x,y,z with G4PhantomParameterisation. 2) Created a parallelworld with no mass or radiation physics turned on. This world created the same exact voxelized cubed geometry (utilized G4PhantomParameterisation) in the parallelworld as was used as the scoring volume. 3) Primitive Scorer of G4VPSDoseDeposit was utilized and the radiation physics list used was Penelope with G4DecayPhysics and G4RadioactiveDecayPhysics. A source was placed at the center of the cube with GPS. All deposited dose was scored. 4) The newpatch.png visual illustrates the resulting dose deposits after running 4 million particles. Many particles were killed due to this error shown below: *** Event Must Be Aborted *** G4WT1 > G4Track (0x7ff04e07c9b0) - track ID = 4, parent ID = 1 G4WT1 > Particle type : e- - creator process : RadioactiveDecayBase, creator model : gammaPIXE G4WT1 > Kinetic energy : 961.646 keV - Momentum direction : (0.650302,-0.000215437,0.759676) G4WT1 > Step length : 1 Ang - total energy deposit : 0 eV G4WT1 > Pre-step point : (0.662544,-0.5,1.47516) - Physical volume : PatientRealBoxPV (Water__1.000 g/cm3) G4WT1 > - defined by : ScoringWorld - step status : 3 G4WT1 > Post-step point : (0.662544,-0.5,1.47516) - Physical volume : PatientRealBoxPV (Water__1.000 g/cm3) G4WT1 > - defined by : msc - step status : 7 G4WT1 > *** Note: Step information might not be properly updated. G4WT1 > -------- EEEE -------- G4Exception-END --------- EEEE ------- Simulation Setup 2: The setup was identical to the setup in 1. However, in step one the world was not voxelized by G4PhantomParameterisation. Results here illustrate seemingly accurate results. However, out of 4 million particles 1 event was aborted as above and the warning message below was frequent. -------- WWWW ------- G4Exception-START -------- WWWW ------- *** G4Exception : GeomNav1002 issued by : G4PhantomParameterisation::GetReplicaNo() Corrected the copy number! It was negative or too big LocalPoint: (31.6121,-37.3209,40.5) LocalDir: (0.442871,-0.0938395,-0.891661) Voxel container size: 40.5 40.5 40.5 LocalPoint - wall: -8.88785 -77.8209 0 *** This is just a warning message. *** -------- WWWW -------- G4Exception-END --------- WWWW ------- Please let me know if I need to provide any additional information. Best Regards, Peter
it is the same issue as https://bugzilla-geant4.kek.jp/show_bug.cgi?id=2314 Comment out that warning as mentioned there
*** This problem has been marked as a duplicate of problem 2314 ***
(In reply to Pedro.Arce from comment #1) > it is the same issue as https://bugzilla-geant4.kek.jp/show_bug.cgi?id=2314 > Comment out that warning as mentioned there Hi Pedro, I understand that the warnings may be commented out, but does this fix the inordinate amount of particles killed due to stuck particles when using G4PhantomParameterisation? This is the main problem I was reporting not the warning outputs. The issue for me is less the warning outputs and more the fact that the particles are killed, leading to wrong simulation results. Best, Peter
