Update digitizer_and_detector_modeling.rst

OpenGATE · Sep 18, 2024 · f0942d6 · f0942d6
1 parent 46bbfc9
commit f0942d6
Showing 1 changed file with 5 additions and 2 deletions.
diff --git a/docs/digitizer_and_detector_modeling.rst b/docs/digitizer_and_detector_modeling.rst
@@ -1181,11 +1181,14 @@ To utilize this digitizer, the cylindricalPET geometry must be configured as fol
 The size of the crystal should be defined at the Submodule level using Air as the material.
 The crystal and layer0 levels should both reflect the crystal size and use the crystal's material.
 This setup allows new virtual IDs for the XYZ axes to be assigned at the Layer, Crystal, and Submodule levels, respectively.
+
 **Commands**
 
-Discretization Control: The digitizer includes commands that enable users to specify which axes require discretization. With "nameAxis".
+*"nameAxis"* Enable users to specify which axes require discretization. The axis selected can be any combination of "XYZ", "XY", "XZ" or "YZ", "X", "Y" or "Z".
+
+*"pitch, pitchX, pitchY, pitchZ"* allow users to specify the desired pitch size for all axis, or specific values for X,Y and Z axis. If no pitch size is provided, the digitizer will use the spatial resolution value to compute the optimal pitch size ensuring that the number of bins, defined as (crystal size)/(pitch), is integer. Note that the spatial resolution must be a single value for each axis; if a the spatial resolution is defined with a distribution and no pitch value is provided, the digitizer will not function correctly.
 
-The commands "pitch, pitchX, pitchY, pitchZ" allow users to specify the desired pitch size for all axis, or specific values for X,Y and Z axis. If no pitch size is provided, the digitizer will use the spatial resolution value to compute the optimal pitch size ensuring that the number of bins, defined as (crystal size)/(pitch), is integer. Note that the spatial resolution must be a single value for each axis; if a the spatial resolution is defined with a distribution and no pitch value is provided, the digitizer will not function correctly.
+*"useMacroGenerator"* boolean flag that determines if the user wants to generate the new geometry macro with the segmentation.
 
 Example::