tomoscan issueshttps://gitlab.esrf.fr/tomotools/tomoscan/-/issues2021-08-30T13:44:47+02:00https://gitlab.esrf.fr/tomotools/tomoscan/-/issues/16Adapt to XRD-CT scans2021-08-30T13:44:47+02:00paynoAdapt to XRD-CT scansWe should be able to manage tomoscan to XRD-CT scans.
Should at least give access to diode information ?
Might need to create an other TomoBase object or only adapt to `HDF5TomoScan` object.We should be able to manage tomoscan to XRD-CT scans.
Should at least give access to diode information ?
Might need to create an other TomoBase object or only adapt to `HDF5TomoScan` object.0.6https://gitlab.esrf.fr/tomotools/tomoscan/-/issues/29MockHDF5: add field of view and estimated_cor_frm_motor2021-06-22T15:23:39+02:00paynoMockHDF5: add field of view and estimated_cor_frm_motor0.6https://gitlab.esrf.fr/tomotools/tomoscan/-/issues/28add unit test for `check_virtual_sources_exist`2021-05-18T11:19:52+02:00paynoadd unit test for `check_virtual_sources_exist`0.6https://gitlab.esrf.fr/tomotools/tomoscan/-/issues/24hdf5 - tomo_n2021-05-03T14:32:21+02:00paynohdf5 - tomo_nfor now for HDF5TomoScan the `tomo_n` attribute is obtain from the len(projection) when it should be the parameter registered on the hdf5 file. This also need to be integrated in nxtomomill: https://gitlab.esrf.fr/tomotools/nxtomomill/-/...for now for HDF5TomoScan the `tomo_n` attribute is obtain from the len(projection) when it should be the parameter registered on the hdf5 file. This also need to be integrated in nxtomomill: https://gitlab.esrf.fr/tomotools/nxtomomill/-/issues/600.6