PC 180112 MAUSRun etc » History » Revision 6

« Previous | Revision 6/9 (diff) | Next »
Rogers, Chris, 18 January 2012 13:56

PC 180112 MAUSRun etc

Globals handling:

Issue 1:
In e.g. Geant4 setup, I need access to a whole load of configuration information in quite low level classes. For example, I need access to MiceModules in order to set up the G4 geometry. At the moment this "global" type information is stored in the MICERun. Initialisation is left up to individual developers (e.g. simulation initialises it's own MiceModules and puts them on the MICERun). That's okay but a bit hacky - what if more than one user wants to access this configuration information?

Issue 2:
Some stuff needs to be set up per run, some stuff needs to be set up per code execution. e.g. MiceModules needs to be reinitialised every run because the magnet currents may change from one run to the next. Need a way to handle run reinitialisation. Ideally, we don't really want to reinitialise the whole code as this can be slow. Other things in this list are:
  • Calibrations
  • Cabling
  • Fields
  • Geometries

Issue 3:
We would like to write out some data every code execution and some data every run.

Updated by Rogers, Chris almost 10 years ago · 6 revisions