Z Projections

[Knecht, David]

I looking for an explanation of the math behind Nearest Point vs. brighest point projections and the influence of the various opacity setttings in 3D project.  It would be nice if this were explained in detail somewhere with example images.  
From documentation:
Surface Depth-Cueing and Interior Depth-Cueing. Sur- face Depth-Cueing works only on nearest-point projections and the nearest-point component of other projections with opacity turned on. Interior Depth-Cueing works only on brightest-point projections. For both kinds, depth-cueing is turned off when set to zero (i.e. 100% of intensity in back to 100% of intensity in front) and is on when set at 0 <n 100 (i.e. (100−n)% of intensity in back to 100% intensity in front). Having independent depth-cueing for surface (nearest-point) and interior (brightest-point) allows for more visualization possibilities.

  For interior cueing with brightest point, given a ray trace through a volume, is the pixel value of each pixel reduced by a different % depending on its depth and then the values are compared for brightest?


Dr. David Knecht    
Department of Molecular and Cell Biology
Co-head Flow Cytometry and Confocal Microscopy Facility
U-3125
91 N. Eagleville Rd.
University of Connecticut
Storrs, CT 06269
860-486-2200
860-486-4331 (fax)

[Du, Guanghua]

Dear list,
can anybody explain me the basic concept of the following terms used in
the image processing:
what is exactly an Imageplus and an Imageprocessor,what's the difference?
what is the difference between an Imageplus holding 3D images and an
Imagestack?

is an ImageProcessor just a class which contains array of pixels(of
different datatype (Byte,Float....) and the methods packed? but
Imageplus is a container at a top level which implements the
communication with the OP or draws the imageprocessors to the monitor?


Sorry for this quite basic questions, but I realy need to udnerstand
these concept clear.

PS, If I declare an ImageStack object (using "new Imagestack(w,h,z), do
i need initialize each slice using (Imagestack.addslice("",imageprocessor)?

best regards..

GDu

[Michael Schmid]

Hi Guanghua,

to put it simple:

ImageProcessor contains the data of a 2D image and provides some  
basic methods to manipulate it.

An ImageStack is a list of ImageProcessors of same type and size.
   new ImageStack(w,h,z) does not create any ImageProcessors - and it  
can't: It cannot be determined whether it should be filled with Byte,  
Short, Float or ColorProcessors.
In case of doubt, my usual approach is looking at the source code on  
the ImageJ web site.

ImagePlus can contain a 2D image, stack, composite image and also  
includes metadata (spatial calibration, possibly directory/file where  
it was read from, sometimes other data read from the file...)

Michael
________________________________________________________________

On 16 Mar 2010, at 10:07, Guanghua Du wrote:

> Dear list,
> can anybody explain me the basic concept of the following terms  
> used in the image processing:
> what is exactly an Imageplus and an Imageprocessor,what's the  
> difference?
> what is the difference between an Imageplus holding 3D images and  
> an Imagestack?
>
> is an ImageProcessor just a class which contains array of pixels(of  
> different datatype (Byte,Float....) and the methods packed? but  
> Imageplus is a container at a top level which implements the  
> communication with the OP or draws the imageprocessors to the monitor?
>
>
> Sorry for this quite basic questions, but I realy need to  
> udnerstand these concept clear.
>
> PS, If I declare an ImageStack object (using "new Imagestack
> (w,h,z), do i need initialize each slice using (Imagestack.addslice
> ("",imageprocessor)?
>
> best regards..
>
> GDu

[Albert Cardona-2]

Hi GDu,

See this tutorial:

http://albert.rierol.net/imagej_programming_tutorials.html#ImageJ
programming basics

Hope that helped.

Albert
--
http://albert.rierol.net

[Du, Guanghua]

Hi, Michael and Albert,
Thanks a lot for the response. I am now a little bit more clear about
their use and difference.

Imageplus is the "image" object which one see in the imageJ window, so
if you want to show something, you have to declare/generate an Imageplus
object. each Imageplus contains one image processor (certain image type)
or more processors (for stacks, in this way, stack looks also like an
imageprocessor contains an array of image processors). you can
manipulate the pixel data in the image processor. somehow Imageplus is
the virtual image you see, imageprocessor is the data in the virtual
image...

GDU

Albert Cardona wrote:

> Hi GDu,
>
> See this tutorial:
>
> http://albert.rierol.net/imagej_programming_tutorials.html#ImageJ
> programming basics
>
> Hope that helped.
>
> Albert

-

[Burger Wilhelm]

Guanghua,

you may also want to have a look at the illustration in our Short Reference (Fig. C.2 on page 472),
http://www.imagingbook.com/fileadmin/en/material1/BurgerBurgeEn20071104_IJreference_Letter.pdf ,
which tries to show how the different data structures relate to each other.

--Wilhelm

> -----Original Message-----
> From: ImageJ Interest Group [mailto:[hidden email]] On Behalf Of
> Guanghua Du
> Sent: Tuesday, March 16, 2010 3:27 PM
> To: [hidden email]
> Subject: Re: concept ImagePlus ImageProcessor ImageStack
>
> Hi, Michael and Albert,
> Thanks a lot for the response. I am now a little bit more clear about
> their use and difference.
>
> Imageplus is the "image" object which one see in the imageJ window, so
> if you want to show something, you have to declare/generate an
> Imageplus
> object. each Imageplus contains one image processor (certain image
> type)
> or more processors (for stacks, in this way, stack looks also like an
> imageprocessor contains an array of image processors). you can
> manipulate the pixel data in the image processor. somehow Imageplus is
> the virtual image you see, imageprocessor is the data in the virtual
> image...
>
> GDU
>
> Albert Cardona wrote:
> > Hi GDu,
> >
> > See this tutorial:
> >
> > http://albert.rierol.net/imagej_programming_tutorials.html#ImageJ
> > programming basics
> >
> > Hope that helped.
> >
> > Albert
>
> -