Problem with Nuclear Secondaries from Muon Capture

Help: Forums, postings and threads

Forums, postings and threads

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.

Layout of the posting thread(s)

The posting threads can be shown with/without the text of the postings ("Inline depth"). In addition the depth of the thread can be controlled ("Outline depth"). For both cases several values are provided, which can be toggled. Note that the displayed values are those, which can be chosen, they do not correspond to the actual display status of the thread(s).

Add message

Add a new posting thread to this Forum

Show subscribers

Click "Show subscribers" to get the List of all subscribers, who receive e-mail from postings to this Forum, if they have not explictly unsubscribed from a posting thread. This includes:

Subscribers to the forum
Explicit subscribers to the posting or any of its ancestors
The author of the posting (if he has not unsubscribed)
The authors of any ancestor posting (if they have not unsubscribed)

Some browsers display old pages from the cache

Some browsers (e.g. Firefox) display a page from the cache even though the page has been updated. As a result, one may not get the latest messages in the forum's outline or the logon ID of the previous session appears on the upper right corner. If one suspects that he or she does not get the latest content of a page, try clearing up the personal data from the browser's cache as the following:

Tools -> Clear Private Data -> Clear Private Data (from browser Firefox)

Tools -> Delete Private Data (from browser Opera)

then reflesh the current page to get the latest content.

Details on "Inline depth" and "Outline depth"

Threads and the follow-up messages are numbered. There is one line per posting, normally starting with the posting number. The URLs of a posting and its responses reflect the depth of the follow-up postings. Watch the URLs to see how this is done. Depending on the chosen display options, the thread-display may be incomplete; the number of messages at the next level is, however, displayed, e.g. "…3 message(s)". You may not see all contributors unless you choose "All".

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.

Argument Default value Alternative Comment

1 0 1 no text / full text of posting

2 1 All text for level 1 only / text for All postings

Argument	Default value	Alternative		Comment
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.

Argument Default value Alternative Comment

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)

Argument	Default value	Alternative	Comment
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 am having a problem understanding how to use the G4MuonMinusCaptureAtRest process, similar to an issue from a few years back that was unfortunately never answered: http://hypernews.slac.stanford.edu:5090/HyperNews/geant4/get/phys-list/287.html

Following information in the forum and in the examples, I add the capture process to my muon physics list:

  G4VProcess* mucap = new G4MuonMinusCaptureAtRest;
  pmanager -> AddRestProcess(mucap);

When the secondaries list of the process includes a nucleus, (it doesn't seem to matter what type!), the CPU becomes pegged at 100%, and memory use grows until the process is killed for eating the entire memory of the machine. If I set /tracking/verbose 2, I see the following in the output:

    :----- List of 2ndaries - #SpawnInStep= 18(Rest=18,Along= 0,Post= 0), #Spawn
Total= 18 ---------------
    :      0 fm      0 fm  -11.3 cm   4.14 MeV     alpha
snipped
    :      0 fm      0 fm  -11.3 cm   1.28 MeV     gamma
    :      0 fm      0 fm  -11.3 cm   1.38 MeV Ne22[0.0]
    :      0 fm      0 fm  -11.3 cm     12 eV      gamma
snipped

The output for that nucleus displays the problem:

********************************************************************************
*************************
* G4Track Information:   Particle = Ne22[0.0],   Track ID = 7,   Parent ID = 1
********************************************************************************
*************************

Step#      X         Y         Z        KineE    dEStep   StepLeng  TrakLeng    
Volume     Process
    0      0 fm      0 fm  -11.3 cm   1.38 MeV     0 eV      0 fm      0 fm     
 housing    initStep
    1      0 fm      0 fm  -11.3 cm   1.38 MeV     0 eV 5.83e+288 pc 5.83e+288 p
c      housing   UserLimit
    2      0 fm      0 fm  -11.3 cm   1.38 MeV     0 eV 5.83e+288 pc    inf pc  
    housing   UserLimit
    3      0 fm      0 fm  -11.3 cm   1.38 MeV     0 eV 5.83e+288 pc    inf pc  
    housing   UserLimit

The last line of which continues forever.

The interesting thing to me is that this is the output of the advanced optical physics example LXe, although my code produces the same garbage (Mg26 from Al, in my case).

I'm guessing that I've left something out ... following the examples, I only define the following particles:

  G4MuonMinus::MuonMinusDefinition();
  G4NeutrinoMu::NeutrinoMuDefinition();
  G4MuonPlus::MuonPlusDefinition();
  G4AntiNeutrinoMu::AntiNeutrinoMuDefinition();

  G4Electron::ElectronDefinition();
  G4NeutrinoE::NeutrinoEDefinition();
  G4Positron::PositronDefinition();
  G4AntiNeutrinoE::AntiNeutrinoEDefinition();

  G4Gamma::GammaDefinition();

Is the issue that I'm not defining all the possible secondaries? Or could I be doing something else wrong? Is there (blaphemy!) a bug in the implementation of the capture process?

I'm using 4.9.2.p1 compiled with gcc 4.3.6 on a few different x86_64 Linux systems. Any pointers you can give me would be greatly appreciated...