source: trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/Run/run.xml @ 904

<!-- ******************************************************** -->
<!--  Docbook Version:  For Toolkit Developers Guide          -->
<!-- ******************************************************** -->

<!-- ******************** Top of Section ******************** -->
<sect1 id="sect.DsgnFuncRun">
<title>
Run
</title>

<!-- ******************* Section (Level#2) ****************** -->
<sect2 id="sect.DsgnFuncRun.DsgPhlsp">
<title>
Design Philosophy
</title>

<para>
The run category manages collections of events that share a common beam and
detector implementation.
</para>

</sect2>

<!-- ******************* Section (Level#2) ****************** -->
<sect2 id="sect.DsgnFuncRun.ClssDsg">
<title>
Class Design
</title>

<para>    
<itemizedlist spacing="compact">
  <listitem><para>
    <emphasis role="bold">G4Run</emphasis> - This class represents a run.  
    An object of this class is constructed and deleted by G4RunManager.
  </para></listitem>
  <listitem><para>
    <emphasis role="bold">G4RunManager</emphasis> - the run controller class.  
    Users must register detector construction, physics list and primary 
    generator action classes to it.  G4RunManager or a derived class must be 
    a singleton.
  </para></listitem>
  <listitem><para>
    <emphasis role="bold">G4RunManagerKernel</emphasis> - provides control of 
    the Geant4 kernel. This class is constructed by G4RunManager.
  </para></listitem>
</itemizedlist>
</para>
 
</sect2>

<!-- ******* Bridgehead ******* -->
<bridgehead role="revisionHistory" renderas='sect4'>
[Status of this chapter]
</bridgehead>

<para>
<simplelist type="var">
   <member>
    28.06.05 - under construction 
  </member>
   <member>
    December 2006 - Converted from latex to Docbook by K. Amako
  </member>
</simplelist>
</para>


</sect1>