Stack label bug?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Stack label bug?

Glen MacDonald-2
Hello,
If a range of slices is selected to apply stack labels (Image>Stacks>Label...>Range) the label is applied to all slices regardless of the slice range.  This occurs with overlay and non-overlay labels.  Mac 10.6.3, ImageJ 1.44c.  

Regards,
Glen


Glen MacDonald
Core for Communication Research
Virginia Merrill Bloedel Hearing Research Center
Box 357923
University of Washington
Seattle, WA 98195-7923  USA
(206) 616-4156
[hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Stack label bug?

Rasband, Wayne (NIH/NIMH) [E]
On Jul 1, 2010, at 8:33 PM, Glen MacDonald wrote:

> Hello,
> If a range of slices is selected to apply stack labels (Image>Stacks>Label...>Range) the label is applied to all slices regardless of the slice range.  This occurs with overlay and non-overlay labels.  Mac 10.6.3, ImageJ 1.44c.  

This bug is fixed in the 1.44d14 daily build. Note that virtual stacks and hyperstacks can only have overlay labels.

-wayne
Reply | Threaded
Open this post in threaded view
|

Re: Stack label bug?

ChrisH
Bug in hyperstack overlay?
As pointed out in the last note on this topic from Wayne, hyperstacks can use overlay labels. However, when the labelled hyperstacks are opened (from tiff) the overlay contents are no longer assigned uniquely to the slices they were on prior to saving - they all are overposted on every slice.
The Overlay label -> save tiff -> load tiff -> show overlay process works perfectly with normal stacks, with each overlay label (in my case a textRoi) showing uniquely on the appropriate slice.
I'm wondering whether this indicates a problem with the hyperstack save / load, or with the overlay for the hyperstack, or with something else I have overlooked?
The only work-around I can think of at present is to de-interleave and save each component stack (one per channel) and then recombine them into the hyperstack after loading in the next work session. That seems inelegant at best, so any better suggestions are welcome!

Thanks


Chris H