Add reader and writer for NXTomo files #939
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds ability to read and write the NXTomo format.
Reader was modified from this code
Writer makes use of this code
Addresses the first part of #744
I copied over all methods from the original reader code, but I am unsure whether the following are needed:
get_acquisition_data_subset
,get_acquisition_data_batch
andget_acquisition_data_subset
- the same thing can be achieved by using slicing withget_acquisition_data
if thedimensions
are set.get_acquisition_data_whole
- the same thing is returned if you just useget_acquisition_data
withoutdimensions
setFrom the NXTomo documentation, the data is of shape [nFrames, xSize, ySize], however in the previous code and by visualising NXTomo datasets from EPAC, it is seen that the data is in the order (angles, vertical, horizontal), which is the default for CIL acquisition data.
Another point is I am wondering if we should have some way for the user to specify which integer type they would like to write to the file. By default the NEXUSDataWriter writes out as float32 but the NXTomo format expects the data as "any representation of an integer number". I have set it to uint32, but say for example I have a uint16 dataset that I read in and want to write out again then it will double in size!