Message: Re: MuonMinusCaptureAtRest and decay products Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Feedback Re: MuonMinusCaptureAtRest and decay products 

Forum: Event and Track Management
Re: None MuonMinusCaptureAtRest and decay products (Matthew T)
Date: 26 Apr, 2013
From: Gumplinger Peter <Gumplinger Peter>

Dear Matt,

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

 Add Message Add Message
to: "Re: MuonMinusCaptureAtRest and decay products"

 Subscribe Subscribe

This site runs SLAC HyperNews version 1.11-slac-98, derived from the original HyperNews

[ Geant 4 Home | Geant 4 HyperNews | Search | Request New Forum | Feedback ]