[ Identification | Description | Input parameters | Links ]

The Union_abs_logger_nD_scintillator Component

Identification

• Author: Milán Klausz, derived from Union_abs_logger_nD by Mads Bertelsen
• Origin: ESS
• Date: 23.09.26

Description

Part of the Union components, a set of components that work together and thus
separates geometry and physics within McStas.
The use of this component requires other components to be used.

1) One specifies a number of processes using process components
2) These are gathered into material definitions using Union_make_material
3) Geometries are placed using Union_box/cylinder/sphere, assigned a material
4) Logger and conditional components can be placed which will record what happens
5) A Union_master component placed after all of the above

Only in step 5 will any simulation happen, and per default all geometries
defined before this master, but after the previous will be simulated here.

There is a dedicated manual available for the Union_components

This component is an absorption logger, and thus placed in point 4) above.

An absorption logger will log something for each absorption event happening
in the geometry or geometries on which it is attached. These are specified
in the target_geometry string. By leaving it blank, all geometries are
logged, even the ones not defined at this point in the instrument file.
Multiple geometries are specified as a comma separated list.

This absorption logger stores absorption as events, with position, velocity,
time and weight. The Monitor_nD libraries are used to write the event files.
This version is a close copy of Monitor_nD, having the same interface, though
the user must be aware that no propagation happens for rays to hit the
detector pixels, instead it uses the position where the ray was absorbed.
Values must still be set for xwidth and yheight: they do not select which
absorptions are recorded, that is decided by the Union geometry named in
target_geometry, but a monitor with zero area is deactivated by Monitor_nD.

This absorption logger needs to be placed in space, the position and velocity
is recorded in the coordinate system of the logger component.

It is possible to attach one or more conditional components to this absorption
logger. Such a conditional component would impose a condition on the state of
the neutron after the Union_master component that executes the simulation,
and the absorption logger will only record the event if this condition is true.

To use the logger_conditional_extend function, set it to some integer value n
and make and extend section to the master component that runs the geometry.
In this extend function, logger_conditional_extend[n] is 1 if the conditional
stack evaluated to true, 0 if not. This way one can check what rays is logged
using regular McStas monitors. Only works if a conditional is applied to this
logger.

This is a scintillator variant of Union_abs_logger_nD, designed for a specific
position sensitive scintillator detector: a GS20 converter layer read out by
a multi-anode photomultiplier tube (MAPMT). The logger is placed in the
converter layer, and represents the physics from the neutron conversion up to
a detection event being triggered in one of the MAPMT pixels.

Instead of logging each absorption at its own position, it converts it into up
to five weighted detection events: the MAPMT pixel facing the absorption
position and its four neighbours. The weights are tabulated position
dependent detection efficiencies, read from the text files
true/up/down/left/right_pixel_hit_efficiency[_high_resolution].txt (must be
present in the working directory). They answer the question "given that a
neutron is absorbed at this position in the converter, what is the
probability that a detection event is recorded in each MAPMT pixel", and were
produced by a separate Geant4 simulation of the scintillation light, applying
a detection threshold per pixel. That threshold suppresses events whose light
is shared between neighbouring pixels and would otherwise be counted twice.
Two MAPMT pixel sizes are supported, each with its own set of tables.

Note that the detector geometry is hard coded to match the tabulated
efficiency files, and is not derived from xwidth and yheight: the tables are
read as a 100 x 100 grid of 0.5 mm bins covering a 50 x 50 mm converter tile,
read out by a MAPMT pixel grid spanning the central 48.5 x 48.5 mm of that
tile. Absorptions outside that map are clamped to its edge bins rather than
rejected, so attaching this logger to a geometry of a different size silently
gives meaningless efficiencies. Using it for another detector means replacing
the efficiency files and adjusting these hard coded values together.

The real MAPMT pixels are not actually all the same size: the outermost ring
of pixels is 0.25 mm larger than the rest (3.25 mm vs 3 mm for the high
resolution grid, 6.25 mm vs 6 mm for the low resolution one). Monitor_nD only
supports a uniform pixel size, so it cannot represent that directly. The
trick used here is to build the Monitor_nD pixel grid at the regular
(smaller) pixel size, spanning the central 48 x 48 mm, and to treat the 0.25
mm wide band just outside it as still belonging to the perimeter pixels: an
absorption position that falls in that band is shifted inward by 0.25 mm -
onto the strip of the grid that Monitor_nD considers part of the
corresponding (undersized) perimeter pixel - before the position is handed to
Monitor_nD, so that Monitor_nD bins the resulting detection event into the
correct perimeter pixel. This repositioning is done purely for pixel
assignment, after the pixel-hit detection efficiencies have already been
looked up for the true, unshifted absorption position (see
compute_scintillator_pixel_hit_probabilities and
move_perimeter_det_event_inside_monitor_limits below).

Input parameters

Links

• Source code for Union_abs_logger_nD_scintillator.comp.
• See also the Monitor_nD mcdoc page"

[ Identification | Description | Examples | Input parameters | Links ]