Ignore:
Timestamp:
Dec 16, 2009, 12:14:47 PM (15 years ago)
Author:
garnier
Message:

CVS update

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/UserActions/optionalActions.xml

    r904 r1222  
    2727<literal>G4RunManager</literal>.
    2828</para>
     29
     30<!-- ******************* Section (Level#2) ****************** -->
     31<sect2 id="sect.OptUAct.Usage">
     32<title>
     33Usage of User Actions
     34</title>
    2935
    3036<!-- ******* Bridgehead ******* -->
     
    401407</para>
    402408
    403 
     409</sect2>
     410
     411<!-- ******************* Section (Level#2) ****************** -->
     412<sect2 id="sect.OptUAct.EngyConsv">
     413<title>
     414Killing Tracks in User Actions and Energy Conservation
     415</title>
     416
     417<para>
     418In either of user action classes described in the previous section,
     419the user can implement an unnatural/unphysical action. A typical
     420example is to kill a track, which is under the simulation, in the
     421user stepping action. In this case the user have to be cautious of
     422the total energy conservation. The user stepping action itself does
     423not take care the energy or any physics quantity associated with
     424the killed track. Therefore if the user want to keep the total
     425energy of an event in this case, the lost track energy need to be
     426recorded by the user.
     427</para>
     428
     429<para>
     430The same is true for user stacking or tracking actions. If the
     431user has killed a track in these actions the all physics information
     432associated with it would be lost and, for example, the total energy
     433conservation be broken. 
     434</para>
     435
     436<para>
     437If the user wants the Geant4 kernel to take care the total energy
     438conservation automatically when he/she has killed artificially
     439a track, the user has to use a killer process. For example if the
     440user uses G4UserLimits and G4UserSpecialCuts process, energy of
     441the killed track is added to the total energy deposit.
     442</para>
     443
     444
     445</sect2>
    404446</sect1>
Note: See TracChangeset for help on using the changeset viewer.