Created attachment 400 [details] This is the output from running run1.mac, run2.mac and the manual stuff described above, I separate them with "OUTPUT FROM ..." where ... is run1.mac, run2.mac, or MANUAL I started example B3a in interactive mode. Then I ran the following commands: /vis/disable /run/initialize /run/beamOn 1000000 The output dose was insane: G4WT1 > --------------------End of Local Run------------------------ G4WT1 > The run was 499444 F18; Nb of 'good' e+ annihilations: 64456 G4WT1 > Total dose in patient : 14.5659 nanoGy G4WT1 > ------------------------------------------------------------ G4WT1 > G4WT0 > Thread-local run terminated. G4WT0 > Run Summary G4WT0 > Number of events processed : 500556 G4WT0 > User=104.78s Real=52.45s Sys=0.01s G4WT0 > Go to merge parameters G4WT0 > G4WT0 > --------------------End of Local Run------------------------ G4WT0 > The run was 500556 F18; Nb of 'good' e+ annihilations: 64614 G4WT0 > Total dose in patient : 1.45725e+17 Gy G4WT0 > ------------------------------------------------------------ G4WT0 > Run terminated. Run Summary Number of events processed : 1000000 User=104.8s Real=52.47s Sys=0.03s --------------------End of Global Run----------------------- The run was 1000000 events ; Nb of 'good' e+ annihilations: 129070 Total dose in patient : 1.45725e+17 Gy ------------------------------------------------------------ As you can see, one worker thread has a sane does, the other is insane. 145PetaGreys would vaporize (with prejudice) any material that received such a dose. There is no way that a mere 1,000,000 positrons and 2,000,000 511 keV photons could give that dose. This effect scales, running "/run/beamOn 2000000" yields: G4WT0 > --------------------End of Local Run------------------------ G4WT0 > The run was 1001000 F18; Nb of 'good' e+ annihilations: 129484 G4WT0 > Total dose in patient : 2.91575e+17 Gy G4WT0 > ------------------------------------------------------------ G4WT0 > G4WT1 > Thread-local run terminated. G4WT1 > Run Summary G4WT1 > Number of events processed : 999000 G4WT1 > User=215.26s Real=107.73s Sys=0.05s G4WT1 > Go to merge parameters G4WT1 > G4WT1 > --------------------End of Local Run------------------------ G4WT1 > The run was 999000 F18; Nb of 'good' e+ annihilations: 128768 G4WT1 > Total dose in patient : 29.1472 nanoGy G4WT1 > ------------------------------------------------------------ G4WT1 > Run terminated. Run Summary Number of events processed : 2000000 User=215.27s Real=107.73s Sys=0.05s --------------------End of Global Run----------------------- The run was 2000000 events ; Nb of 'good' e+ annihilations: 258252 Total dose in patient : 2.91575e+17 Gy ------------------------------------------------------------ When run in batch mode on run1.mac and run2.mac, it yields good results for run1.mac but does this insane behavior in run2.mac
Hi Ivana, it looks like the problem is the new G4Parameter stuff. Thread 0 seems to have a correct initialization value, but not thread 1... Andrea P.S. The reports come from our tutorial
The problem was in the initialization of the hits collections IDs in B3aEventAction. It is now fixed in the development version and the fix will be included in the next patch to the 10.2 release.
