|
217 | 217 | /// |
218 | 218 | /// * **gdml**: Bound the generator to a certain gdml component. No need to define size |
219 | 219 | /// and position. Needs another "from" parameter. If the "from" parameter is defined, |
220 | | -/// we can omit `shape="gdml"` parameter. |
| 220 | +/// we can omit `shape="gdml"` parameter. In the case that the gdml volume has daughters, |
| 221 | +/// the particles will be generated excluding the daughter volumes. |
221 | 222 | /// \code |
222 | 223 | /// // We launch particles from random positions inside the vessel volume defined in our GDML geometry |
223 | 224 | /// <generator type="volume" from="vessel" > ... </generator> |
|
543 | 544 | /// the GDML geometry. If an event did not produce an energy deposit in the |
544 | 545 | /// sensitiveVolume, the event will not be stored at all. Therefore, the |
545 | 546 | /// sensitive volume will serve as a trigger volume to decide when an event |
546 | | -/// should be stored. For the moment we can only define a single sensitive |
547 | | -/// volume, but it might be desirable to introduce boolean operations with |
548 | | -/// different geometry volumes. |
| 547 | +/// should be stored. Multiple sensitive volumes can be defined by using |
| 548 | +/// different `<volume>` definitions with the parameter `sensitive="true"`. |
| 549 | +/// When multiple sensitive volumes are defined, the event will be stored |
| 550 | +/// if an energy deposit is produced in any of these sensitive volumes. |
| 551 | +/// You can also use a logical volume as sensitive volume, in this case |
| 552 | +/// all the physical volumes corresponding to that logical volume will be |
| 553 | +/// set as sensitive volumes. Furthermore, you can use regular expressions |
| 554 | +/// (at the parameter `name` of the `<volume>` definition) to define |
| 555 | +/// multiple sensitive volumes matching a certain pattern. |
549 | 556 | /// |
550 | 557 | /// We can define the energy range we are interested in by defining the |
551 | 558 | /// parameter energyRange. The event will be written to disk only if the |
|
629 | 636 | /// \endcode |
630 | 637 | /// |
631 | 638 | /// The option `removeUnwantedTracks` can optionally be enabled inside detector section: |
632 | | -/// |
| 639 | +/// \code |
633 | 640 | /// <detector><removeUnwantedTracks enabled="true" keepZeroEnergyTracks="true"/></detector> |
| 641 | +/// \endcode |
634 | 642 | /// |
635 | 643 | /// This option will remove all tracks that do not deposit energy in any of the sensitive volumes or in any of |
636 | 644 | /// the volumes marked as 'keepTracks' (for instance <volume name="veto" keepTracks="true" />). |
|
0 commit comments