1.2.3

Changes

• Option to create post-processing Python scripts for combined flat-field correction and creation of reconstruction configuration files using the CTSimU toolbox.
• Updated to metadata file format version 1.2.
• Projection matrices: code simplification, minor speedup.

1.2.2

New options

• Option to skip the simulation and only create metadata and reconstruction configurations.
• Quick scenario loading: certain time-consuming computations can be deactivated when a scenario is loaded. A warning is displayed during the simulation of a partly loaded scenario and the metadata file includes information about which features have been excluded from the simulation.
• Option to always include the run number in file names, even for single runs.
• Contact name for metadata files can be specified in settings.
• Reconstruction config files can be generated for uncorrected projection images (instead of corrected ones that are assumed to be corrected by the CTSimU toolbox). This is especially useful in combination with VGSTUDIO and OpenCT, where the flat-field correction is done by the reconstruction software in this case.

OpenCT config files

• Option to use absolute paths in config files instead of relative paths.
• Correction images (bright, dark) are included in OpenCT config if JSON loader is instructed to create a config file for uncorrected projections.
• Circular trajectory variant of the file format can be enforced. Only meant for ideal circular trajectories (see README in the main git repository).
• Updated to full OpenCT file format version 1.0.0, but still includes legacy keys for compatibility.

Extended metadata files

• Two metadata files are created: one for projections, one for reconstruction.
• Reconstruction metadata includes information about the tomogram volume to be reconstructed.
• All metadata files include some aRTist-specific simulation information and the complete scenario JSON that has been simulated.

Bug fixes

• Run number is now included in flat-field correction filenames (for multiple runs, or when this behavior is enforced in the settings).
• Flat-field correction is turned off while taking the dark image. (Only applicable for scenarios where flat-field correction is done by aRTist during the simulation.)
• Projection matrices: if no image/volume coordinate system is given, a default one is created automatically.
• Drifts imply their parent parameter's unit if they don't have their own unit specified in the scenario (as required by the CTSimU file format).

Minor changes (only relevant for developers)

• Prepared native unit for angular velocity (deg/s) to be on the same level as the toolbox. Angular velocities still do not play any role in a CTSimU simulation in aRTist.

1.2.1

Changes

• Bug fix: projection counter error for more than one ideal flat field.

1.2.0

News

• General support for file format version 1.0, 1.1 and 1.2
• Parameter drifts are supported
• Scatter images can be kept for a user-defined number of frames, instead of calculating a new scatter image for each frame.
• Option to restart aRTist after each batch run. (To free memory.)
• New supported JSON features:
  • new geometrical deviations (translations and rotations along arbitrary axes or pivot points)
  • source: spot images
  • detector: MTF
  • detector: quantum efficiency
  • detector: external noise characteristics files
  • known_to_reconstruction parameter for geometrical deviations and drifts is obeyed when calculating projection matrices.

0.8.18

Changes

• Fix in CERA reconstruction config files: the Datatype parameter is now inactive (made into a comment), only OutputDatatype left as valid parameter for the volume data type.

0.8.17

Changes

• Small updates and fixes in reconstruction config file outputs.

0.8.16

Changes

• Added aRTist-specific JSON option to create primary intensity images (as an alternative to primary energy images).

0.8.15

Changes

• Minor bug fix: Parts not loaded centered at (0,0,0) since version 0.7.10 due to a spelling mistake. This bug had no impact on part placement: centering parts after loading is not necessary and has therefore been fully removed in this version.

0.8.14

Notable Changes

• Removed iSRb correction scaling factor of 0.6830822016 (for aRTist 2.12+).
• Added aRTist-specific JSON option to create primary energy images.

0.8.13

Notable Changes

• Added options for recon volume data type (uint16, float32).
• Cleaned up VGI output.
• Physical pixel size is used in factor/offset detector grey value method, instead of iSRb-scaled pixel area from the DetectorCalc module.