A problem with a G4 runtime

Hi:

Dear experts recently I had a small problem when running the program, while running I emitted 50 particles. During the run, the terminal keeps outputting messages and it looks like the program is working properly, but after less than a minute the program stops and the terminal shows that the program is killed.

I first thought it was a problem with my program, so I ran the B5 example directly and fired 50 particles as well, at which point the same problem occurred as mentioned earlier.

So I would like to ask you experts if this problem is related to the configuration of the computer, and if it is also related to the visualization of the program that I have enabled when I run it.

Thank you, experts, your replies will be very helpful to me.

Hi Jodie

Can you tell us what the messages are? Also, what Operating System and Geant4 version number?

When you say " I emitted 50 particles", I assume you mean you type /run/beamOn 50 on the Geant4 session input line.

If you type /vis/disable before /run/beamOn does it run OK?

If you are writing lots of output, the Qt GUI can become overloaded - is that, perhaps, the problem?

John

Hi:

Thanks for your reply, I am using G411.0 and as you said I am using/run/beamOn 50.
I’m running the program on VMware using a Linux system.

The main information I output is the position of the particle, and the x, y ,z of the particle in SD is output in the terminal.

The following is my output information:

G4WT3 >  x = 0.127487 y = 0.182981 z = 10.6057
G4WT0 >  x = -0.175801 y = -0.109594 z = 6.015
G4WT3 > -------DicomSD::ProcessHits-------
G4WT0 > -------DicomSD::ProcessHits-------
G4WT3 >  x = 0.127127 y = 0.183145 z = 10.5283
G4WT0 >  x = -0.175801 y = -0.109593 z = 6.01544
G4WT3 > -------DicomSD::ProcessHits-------
G4WT0 > -------DicomSD::ProcessHits-------
G4WT3 >  x = 0.12743 y = 0.183521 z = 10.5284
G4WT0 >  x = -0.175738 y = -0.109563 z = 6.06495
G4WT3 > -------DicomSD::ProcessHits-------
G4WT0 > -------DicomSD::ProcessHits-------
G4WT3 >  x = 0.127614 y = 0.184201 z = 10.5285
G4WT0 >  x = -0.17567 y = -0.10928 z = 6.19402
G4WT3 > -------DicomSD::ProcessHits-------
G4WT0 > -------DicomSD::ProcessHits-------
G4WT3 >  x = 0.127614 y = 0.184201 z = 10.5285
G4WT0 >  x = -0.17568 y = -0.109327 z = 6.24132
G4WT3 > -------DicomSD::ProcessHits-------
G4WT0 > -------DicomSD::ProcessHits-------
G4WT3 >  x = 0.12743 y = 0.183521 z = 10.5284
G4WT0 >  x = -0.175692 y = -0.109422 z = 6.29009
G4WT3 > -------DicomSD::ProcessHits-------
G4WT0 > -------DicomSD::ProcessHits-------
G4WT3 >  x = 0.128161 y = 0.183292 z = 10.5286
G4WT0 >  x = -0.175695 y = -0.109458 z = 6.32934
G4WT3 > -------DicomSD::ProcessHits-------
G4WT0 > -------DicomSD::ProcessHits-------
G4WT3 >  x = 0.128161 y = 0.183292 z = 10.5286
G4WT0 >  x = -0.175276 y = -0.109431 z = 6.49982
G4WT3 > -------DicomSD::ProcessHits-------
G4WT0 > -------DicomSD::ProcessHits-------
G4WT3 >  x = 0.126086 y = 0.183238 z = 10.3807
G4WT0 >  x = -0.17512 y = -0.109771 z = 6.60785
G4WT3 > -------DicomSD::ProcessHits-------
G4WT0 > -------DicomSD::ProcessHits-------
G4WT3 >  x = 0.125415 y = 0.183125 z = 10.2821
G4WT0 >  x = -0.175083 y = -0.109911 z = 6.64319
G4WT3 > -------DicomSD::ProcessHits-------
G4WT0 > -------DicomSD::ProcessHits-------
G4WT3 >  x = 0.113904 y = 0.182214 z = 10.2869
G4WT0 >  x = -0.175076 y = -0.109927 z = 6.64717
G4WT3 > -------DicomSD::ProcessHits-------
G4WT0 > -------DicomSD::ProcessHits-------
G4WT3 >  x = 0.0851866 y = 0.149547 z = 10.3211
G4WT0 >  x = -0.17499 y = -0.110102 z = 6.68715

I only intercepted part of the output because the output of these messages is normal until the program crashes, all similar to these messages I posted here.

When the program crashes this message will appear.

G4WT1 >  x = -1.14739 y = -1.84515 z = 12.6843
G4WT2 >  x = -0.268086 y = -0.0491451 z = 14.5333
G4WT3 > -------DicomSD::ProcessHits-------
G4WT0 >  x = -0.182013 y = -0.137419 z = 9.56238
G4WT1 > -------DicomSD::ProcessHits-------
G4WT2 > -------DicomSD::ProcessHits-------
G4WT3 >  x = -0.609542 y = 0.156716 z = 15.6547
killed

This time I also turned on the visualization and used the QT GUI tool.

Thanks again for your reply.

Hi Jodie

I take it the output was obtained with vis disabled?

Anyway, that could be an awful lot of output and, as I said, it could overwhelm the Qt GUI. Or it could be the VMware system that’s being overwhelmed.

Perhaps to nail this issue, you could try running your app without Qt and without a GUI - see How to Set Up an Interactive Session — Book For Application Developers 11.0 documentation.

John

Hi Allison
Thanks for your reply, I think you might be right, because this problem also occurs when I test the sample code. This should indicate that it is not a code issue.