[MINC-users] Display.globals options was: Re: Visualizing data with high dynamic range

Gabriel A. Devenyi gdevenyi at gmail.com
Wed Aug 5 16:42:04 EDT 2015


Bert,

Are there docs somewhere on what we can specify for Display.globals?

-- 
Gabriel A. Devenyi B.Eng. Ph.D.
Research Computing Associate
Computational Brain Anatomy Laboratory
Cerebral Imaging Center
Douglas Mental Health University Institute
McGill University
t: 514.761.6131x4781
e: gdevenyi at gmail.com

On Wed, Aug 5, 2015 at 10:45 AM, Robert D. Vincent <
robert.d.vincent at mcgill.ca> wrote:

> Hi Andrew,
>
> Display should be able to handle high dynamic range data. There is a global
> variable "Convert_volumes_to_byte" which is true by default, but which can
> be overridden either on the command line or the Display.globals
> initialization file. You can set it either by specifying:
>
> Display -global Convert_volumes_to_byte false <input.mnc>
>
> or by adding the line:
>
> Convert_volumes_to_byte=False;
>
> to a file named Display.globals in your home directory.
>
> Register has similar functionality, but it was added fairly recently, so I
> don't believe it is widely available. The code checked into Github supports
> two globals, Volume_voxel_type and Volume_voxel_signed, that control the
> conversion of loaded volumes.
>
> Hope this helps. I intend to change the default behavior in future versions
> of Display, but I haven't made the change yet.
>
>     -bert
>
> On Wed, Aug 5, 2015 at 9:41 AM, Andrew Wood <andrew at biospective.com>
> wrote:
>
> > Hi all,
> >
> > I'm having trouble visualizing a volume containing float data with a high
> > dynamic range. Both register and Display discretize the signal (down to
> > byte precision?), which is not workable for these volumes.
> >
> > The only solution I have right now is to explode the data into new
> volumes
> > by sliding a reduced range over the signal, clamping away data that
> > register and Display can't handle.
> >
> > Does anyone have experience visualizing high dynamic range data? Is
> there a
> > tool that can do this, or just a better workaround?
> >
> > Thanks,
> > Andrew
> > _______________________________________________
> > MINC-users at bic.mni.mcgill.ca
> > http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-users
> >
> _______________________________________________
> MINC-users at bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-users
>


More information about the MINC-users mailing list