You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we import czi files from the LZ1 and choose resave as hdf5, the tiles are correctly placed and the stack sizes are fixed.
I we do the very same procedure and ask to keep the raw data for the dataset.xml file, all images are at position 0,0,0 and have the same number of slices...
Any help where this problem lies would be appreciated. I could create a pull request myself once I know where to look.
Best
Oli
The text was updated successfully, but these errors were encountered:
I just checked with some example .czi files we have lying around here and could replicate the same z-size stack bug. That was working before but might have broken during one of the last updates. I will look into this with the files I have.
I could not reproduce the poosition (0,0,0) bug - could you maybe create a very small dataset (only a few planes) where it occurs and send it to us?
Just a short update:
I found the reason why the stack sizes were not corrected, it should be fixed with c5ce4c2 and will be included in the next release in Fiji.
(I'm responsible for this breaking, as I had introduced a missing-exclamation-mark "typo-bug" in some refactoring done in 1142041. Sorry for that).
When we import czi files from the LZ1 and choose resave as hdf5, the tiles are correctly placed and the stack sizes are fixed.
I we do the very same procedure and ask to keep the raw data for the dataset.xml file, all images are at position 0,0,0 and have the same number of slices...
Any help where this problem lies would be appreciated. I could create a pull request myself once I know where to look.
Best
Oli
The text was updated successfully, but these errors were encountered: