Closed tischi closed 4 years ago
...indeed constructing the image like this fixes the bugs:
ImgPlus<T> result = new ImgPlus<>(img, Paths.get(filename, dataset).toString(), new AxisType[]{ Axes.X, Axes.Y, Axes.CHANNEL, Axes.Z, Axes.TIME });
This change will be part of our refactoring branch.
awesome @tischi, thanks for fixing this! It would be great if you can use either one of the "closing" keyword together with this issue number (e.g. fixes @26
) in a commit, or add it to the to the PR description.
Nice catch @tischi. This got fixed in https://github.com/ilastik/ilastik4ij/pull/24
The way you construct the
ImgPlus
in theHdf5DataSetReader
is like this: https://github.com/ilastik/ilastik4ij/blob/master/src/main/java/org/ilastik/ilastik4ij/hdf5/Hdf5DataSetReader.java#L130If I read an image, e.g. like this
And write it again using the
Hdf5DataSetWriter
, I get errors here: https://github.com/ilastik/ilastik4ij/blob/master/src/main/java/org/ilastik/ilastik4ij/hdf5/Hdf5DataSetWriter.java#L275 withdimensionIndex = -1
, indicating that it cannot determine the dimension.My feeling is that in the
Hdf5DataSetReader
you should maybe use another constructor for theImgPlus
, specifying the axes order.