nxtomomill.app.dxfile2nx#

Application to convert from dx file (HDF5) to NXTomo (HDF5) file

usage: nxtomomill dxfile2nx [-h] [--input_entry INPUT_ENTRY] [--output_entry OUTPUT_ENTRY] [--file_extension FILE_EXTENSION] [--scan-range SCAN_RANGE] [--pixel-size PIXEL_SIZE] [--fov FIELD_OF_VIEW]
                            [--distance DISTANCE] [--energy ENERGY] [--overwrite] [--data-copy]
                            input_file output_file

convert acquisition contained in provided dx file to NXTomo entry

positional arguments:
  input_file            master file of the acquisition
  output_file           output .nx or .h5 file

optional arguments:
  -h, --help            show this help message and exit
  --input_entry INPUT_ENTRY
                        h5py group path to be converted
  --output_entry OUTPUT_ENTRY
                        h5py group path to store the NXTomo
  --file_extension FILE_EXTENSION
                        extension of the output file. Valid values are .h5/.hdf5/.nx
  --scan-range SCAN_RANGE
                        scan range of the projections. Dark and flat will always be considered with rotation angle == scan_range[0]
  --pixel-size PIXEL_SIZE
                        pixel size in meter as (x pixel size, y pixel size)
  --fov FIELD_OF_VIEW, --field-of-view FIELD_OF_VIEW
                        field of view. Can be Full or Half
  --distance DISTANCE, --detector-sample-distance DISTANCE
                        sample to detector distance (in meter)
  --energy ENERGY, --incident-beam-energy ENERGY
                        incident beam energy in keV
  --overwrite           Do not ask for user permission to overwrite output files
  --data-copy           Force data duplication of frames. This will permit to have an 'all-embed' file. Otherwise we will have link between the dxfile and the NXTomo.

For a complete tutorial you can have a look at dxfile2nx tutorial

Functions

convert_2elmts__tuple_to_float(input_str)

rtype

tuple

main(argv)