Acquisition
Sample stage rotation
The stage is assumed to perform a rotation around its axis during the scan, resulting in a circular sample trajectory. Other trajectories can be modelled using drifts, especially drifts of the stage geometry parameters. For example, a helix scan can be modelled by starting with a standard circular trajectory of several rotations (as described in the following), and an additional drift of the stage center’s position. If the scan trajectory is completely described by drifts, the stage rotation described here should be deactivated by setting both "start_angle"
and "stop_angle"
to 0
.
For a circular CT scan, the start and stop angle of the sample stage are defined in this section. An angle of 0
refers to the orientation of the stage as defined in the geometry section (for frame 0). All other angles express a rotation around the axis of the stage. The direction of rotation must be mathematically positive in the case of counter-clockwise acquisition direction ("CCW"
), and mathematically negative in the case of clockwise acquisition direction ("CW"
). The stage reaches the start and stop angle by rotating in the given "direction"
around its normal axis (Fig. 4). This means that the "direction"
parameter affects both the positions of start and stop angle, as well as the direction of rotation in which the CT scan is performed. It also means that the start angle must always be less than (or equal to) the stop angle. However, negative angular positions and positions greater than 360° are allowed, as well as an angular coverage of more than a full circle, e.g. to perform multiple rotations during one scan.
329"start_angle": {"value": 0, "unit": "deg"},
330"stop_angle": {"value": 320, "unit": "deg"}
The direction of the sample stage rotation can be counter-clockwise ("CCW"
, mathematically positive) or clockwise ("CW"
, mathematically negative) around the axis:
331"direction": "CW",
332"direction": "CCW"
The parameter "scan_mode"
defines if the rotation stops while a projection is taken, or if it runs continuously.
332"scan_mode": "stop+go",
333"scan_mode": "continuous"
The property for scan speed should only be used for continuous-motion scans. If undefined, it may be calculated from the detector’s integration and dead time.
333"scan_speed": {"value": 360, "unit": "deg/h"}
For stop&go scans, it should be set to null
:
333"scan_speed": null
Frames and projections
Number of projections
The "number_of_projections"
is also given in the acquisition section.
334"number_of_projections": 2001
Beginning from the start angle, the necessary number of angular steps is performed (in the case of a stop&go scan). It is assumed that a frame is taken before each step (starting with the first frame at the start angle). The parameter "include_final_angle"
can be set to true
if the last projection should be taken after the stop angle has been reached, or to false
if it is meant to be taken at the last step before the stop angle is reached.
335"include_final_angle": true
Frame averaging
The number of frames to be averaged for one projection image can be specified:
336"frame_average": 3
Dark field and flat field acquisition and correction
If dark field and flat field images are acquired along with the projections, their numbers and frame averages can be specified. An "ideal"
image means that the simulation of noise is to be omitted by the simulation software, possibly in contrast to the noise specification in the detector section. The parameter "correction"
tells whether the projection images already come in a corrected form as a result of the scan (true
) or if they are taken as uncorrected files (false
).
337"dark_field": {
338 "number": 1,
339 "frame_average": 1,
340 "ideal": true,
341 "correction": false
342},
343"flat_field": {
344 "number": 3,
345 "frame_average": 20,
346 "ideal": false,
347 "correction": false
348}
Pixel binning
The number of pixels to bin in directions and of the detector:
349"pixel_binning": {"u": 1, "v": 1}
The binning operation is not described here and left to the software.
Scattering
This parameter specifies if X-ray scattering should be simulated or not.
350"scattering": false