[MINC-development] MINC2 file with floating-point voxels and slice normalization

[Andrew Janke]

Hi John,

I went looking for an example of this in the Register/Display code but
it seems to use the valid min/max of a file (not the per slice values
even if they are present). Yes, the per slice values are used while
reading and normalised by volume_io but not in register/Display
themselves.

In our MINC2 based web viewer for large histology (TissueStack) we use
the valid min/max as a starting guess. We also normalise during
conversion to its own internal fast format but that's another story.

Do you have an example of this behaviour? I didn't get to looking far
into postf to see what it does, I ask as while I see this as being
useful for discrete data types I don't see the point for float/double
given that they are "normalised" already and thus a file min/max
should be a decent approximation.

Storing a min/max for each slice is also only going to work for
viewing in a particular orientation.

ta


a


On 19 January 2013 01:46, John G. Sled <jgsled at phenogenomics.ca> wrote:
> Since we are voting ... I vote for keeping Peter's design where the slice
> min / max is maintained for informational purposes when the underlying data
> type is float.  This allows visualization tools to make a sensible initial
> choice for the window and level.