Changeset 1222 for trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/UserActions/optionalActions.xml
- Timestamp:
- Dec 16, 2009, 12:14:47 PM (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/UserActions/optionalActions.xml
r904 r1222 27 27 <literal>G4RunManager</literal>. 28 28 </para> 29 30 <!-- ******************* Section (Level#2) ****************** --> 31 <sect2 id="sect.OptUAct.Usage"> 32 <title> 33 Usage of User Actions 34 </title> 29 35 30 36 <!-- ******* Bridgehead ******* --> … … 401 407 </para> 402 408 403 409 </sect2> 410 411 <!-- ******************* Section (Level#2) ****************** --> 412 <sect2 id="sect.OptUAct.EngyConsv"> 413 <title> 414 Killing Tracks in User Actions and Energy Conservation 415 </title> 416 417 <para> 418 In either of user action classes described in the previous section, 419 the user can implement an unnatural/unphysical action. A typical 420 example is to kill a track, which is under the simulation, in the 421 user stepping action. In this case the user have to be cautious of 422 the total energy conservation. The user stepping action itself does 423 not take care the energy or any physics quantity associated with 424 the killed track. Therefore if the user want to keep the total 425 energy of an event in this case, the lost track energy need to be 426 recorded by the user. 427 </para> 428 429 <para> 430 The same is true for user stacking or tracking actions. If the 431 user has killed a track in these actions the all physics information 432 associated with it would be lost and, for example, the total energy 433 conservation be broken. 434 </para> 435 436 <para> 437 If the user wants the Geant4 kernel to take care the total energy 438 conservation automatically when he/she has killed artificially 439 a track, the user has to use a killer process. For example if the 440 user uses G4UserLimits and G4UserSpecialCuts process, energy of 441 the killed track is added to the total energy deposit. 442 </para> 443 444 445 </sect2> 404 446 </sect1>
Note: See TracChangeset
for help on using the changeset viewer.