Message: Any way to modify physics list after passing into Run Manager? Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Question Any way to modify physics list after passing into Run Manager? 

Forum: Run Management
Date: 14 Mar, 2017
From: Michael H. Kelsey <Michael H. Kelsey>

I have a fairly complex simulation with a vast array of user configuration commands, including allowing users to modify the physics list while in the PreInit state. One option my users have is to select some "new" physics constructor to attach to the physics list.

One of the available constructors includes a non-empty ConstructParticle() function which creates particles which are not normally part of the simulation. What I have discovered is that if a "basic" physics list is registered (via G4RunManager::SetUserInitialization()), and we go back after that to add this new physics, the job aborts during /run/initialize. The abort happens because the new particles don't have process managers attached to them.

Is there an approved way for the RunManager to be told to call ConstructParticle() (which I guess means calling SetupPhysics()) a second time? Or should I set up my own simulation code to make that call when the user make an "add physics" request?

   -- Michael Kelsey

 Add Message Add Message
to: "Any way to modify physics list after passing into Run Manager?"

 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 ]