http://imagej.273.s1.nabble.com/FIJI-thinks-my-greyscale-image-stack-is-a-coloured-image-tp5009051p5009057.html
caveat that disabling SCIFIO is a temporary workaround. These bugs should
> Hi,
>
> On Wed, 6 Aug 2014, Mr_Sonky wrote:
>
> > Hi all, I've got a simple question. Why does FIJI open my stack of
> > grayscale images as a colour image?? I know it does this because of the
> > letter "c" in place of the "play" button when we want to scroll between
> > slices in a stack. Also it does this annoying thing where it colour
> > codes i.e. Slice #1: Red, Slice #2: Green..etc.. this goes on to Slice
> > #6: Yellow.. and Slice 7 onwards to Slice 361 remains gray (its original
> > colour). All images are acquired by a monochromatic sensor so I know the
> > colour is not real.
> >
> > When I apply a 'Grays' LUT, it either doesn't save or I wants me to
> > convert to 8-bits first. But doing so doesnt solve the problem of the
> > "c" slider. In addition, I found that when the "c" slider is present, I
> > can't adjust the Brightness/Contrast for all slices whereas before I
> > normally could with a standard greyscale stack. *When I tried opening
> > the SAME image file using ImageJ, it opens normally* without the
> > pseudo-colouring the first 6 slices. Everyhting else also works when
> > opened in ImageJ (as opposed to FIJI)
> >
> > <
http://imagej.1557.x6.nabble.com/file/n5009051/Sample_image.png>
> >
> > The image on the right and left essentially the same opened in different
> > programs.. Would really appreciate if someine can explain to me how to
> stop
> > this annoying behaviour!
>
> First of all, I understand your frustration. It still would be a good idea
> to be a little gentler if you want somebody else to fix the problem for
> you.
>
> Further, as John pointed out, this might be caused by SCIFIO reading
> images now. Remember, we are in the process of future-proofing ImageJ and
> part of that is to switch to a new image file input/output layer: SCIFIO.
>
> The best way to make sure that your grayscale images are read correctly is
> to be friendly to the people who you ask to work for you, free of cost,
> and follow the excellent instructions provided here:
>
http://imagej.net/Bug_reporting_best_practices>
> In particular, I'd like to point out the second bullet point here:
> "Provide a minimal, complete, verifiable example." This is crucial. In
> other words, write out a *minimal* grayscale stack that you expected to be
> read back as grayscale, and then attach it to the bug report.
>
> Hopefully this helps,
> Johannes
>
> --
> ImageJ mailing list:
http://imagej.nih.gov/ij/list.html>