{'fraction_non_alphanumeric': 0.027115858668857847, 'fraction_numerical': 0.004108463434675432, 'mean_word_length': 5.7292817679558015, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Clinical time OSEM3D: infrastructure issues

In previous work we compared two parallel algorithms for calculating 3D forward and backprojection on a distributed-memory cluster computer. These two methods were used to develop an implementation of fully three-dimensional ordered subset expectation maximization iterative reconstruction for emission tomography (OSEM3D). It is, however, necessary to embed these computational kernels in an environment that supports efficient data movement and other infrastructural operations, such as process management. Here we briefly describe two particular components of the infrastructure: the I/O subsystem and the service demon. For the I/O subsystem, a fortuitous relationship between the traditional representation of the fully three-dimensional sinogram S/sub 4DO/(/spl theta/,z,/spl phi/,r) and the distributed representation for image space decomposition permits an efficient solution involving minimal data movement. The service demon is similar to others, but contains additional recovery-oriented mechanisms for minimizing mean time to repair. We conclude with performance benchmarks for fully 3D reconstruction for a scanner that produces a significant volume of data.