|Message: Re: MuonMinusCaptureAtRest and decay products||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 am not the expert with MuonMinusCaptureAtRest and perhaps you'd be more successful getting the answer you deserve in the 'Hadronic Physics Forum'.
I also left on vacation shortly after reading your post. That said, I am really curious how your issue resolves. Maybe, you can debug the code in:
> Is this caused by a bug in the invocation of certain processes in my > physics list (pManager->AddProcess(new G4MuonMinusCaptureAtRest(), > 0,-1,-1);)?
I doubt it but perhaps you can employ one of the provided PhysicsLists, for example, QGSP_BERT or FTFP_BERT, that use G4StoppingPhysics and in turn, G4MuonMinusCaptureAtRest.
> Does G4MuonMinusCaptureAtRest actually kill the muon after > capture like it should, or does the muon capture and then stick around > until it decays?
It seems the muon is killed as one would expect:
> Or do the extra particles eventually get killed at some > time other than tracking time?
No, this is not done. All secondaries that are produced are being tracked unless, you - the user, decides otherwise in StackingAction.
If you have access to the G4 source, you can debug both G4MuonMinusCaptureAtRest and G4Decay and find out where all these secondaries come from in the same step.
Hope this helps, Peter