integrate nabu multicor values to saaxis
Nabu is expected to handle several cor values. And the idea is to benefit from it.
-
For now
tomwer.core.process.reconstruction.saaxis,saaxis
has arun_slice_reconstruction
function which iterates over the different COR values (375). Refactoring should:- remove the
for
loop (line 375).-
warning: keep the setting of:
- convert from relative position to absolute position. But of the full cor_positions this time qnd set 'reconstruction/rotation_axis_position'
- set 'output/location' and 'output/file_format'
- set 'resources'
- "pipeline" key (line 377-381) can be re,oved. It was used to resume fro, 'sinogram' step ans speed up processing.
-
- remove the
-
_Reconstructor
will be 'removed' and one will be created for saaxis using nabu config file able to handle several cor and a single output.
data_slice
request will be added to tomoscan identifiers so we could have processing like:
volume = self._process_config(...)
for i_cor, cor in enumerate(cor_position):
identifier = copy(volume)
identifier.data_slice = i_cor
results[cor] = identifier
potential issues
nabu and tomwer have different references. Nabu uses absolute COR values when tomwer uses relative.
Edited by Jerome Lesaint