New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CellImg VirtualStack support tricky for composite images #83

ctrueden opened this Issue Aug 19, 2014 · 0 comments


None yet
2 participants

ctrueden commented Aug 19, 2014

There is code in place to treat AbstractCellImg based images as ImgLib-derived VirtualStacks. But we include special code for propagating changes to the current plane of an image back to IJ2 (which is more than what IJ1 does since for IJ1 changing slider positions afterwards will invalidate the current planes changes). So we have special code in legacy layer to propagate these changes and as a result IJ2 acts a little differently than IJ1. One consequence is that composite images that look unchanged in IJ1 can look changed in IJ2. This is because we propagate a single plane's changes making composite pixels different. Determine if this is just bad legacy syncing that causes the channel pixels to change or if this type of change is a byproduct of the new approach.

An example:

  • Save Leaf as a png file (using BF Exporter as APNG)
  • Open it in IJ2 (which should now be a (V) virtual stack) [note that you might need to hack DatasetIOPlugin to always open as CellImgs]
  • Run Image Scale (0.5 x & y, curr plane, no new window)
  • Displayed image changes colors
  • The same set of steps (except Import Tiff Virtual Stack instead of open PNG) in IJ1 does not show changes to pixels.


@hinerm hinerm self-assigned this Mar 23, 2015

@hinerm hinerm added this to the m1 milestone Mar 23, 2015

@hinerm hinerm added the bug label Mar 23, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment