|
Toolkit |
Included Modules |
|---|---|
|
Coded Microscope |
|
Toolkit |
Included Modules |
|---|---|
|
Coded Microscope |
This module supports manual and coded systems (no motorized systems). By that the status of coded components are displayed in ZEN starter. Additionally, in the Light Path tool, the configuration of the microscope used and the status is displayed.
This extension integrates the ImageJ software into . This enables you to make use of ImageJ's image processing capabilities from within your workflows.
You can send images to ImageJ and retrieve them back into the software with a single click each.
The Single Instance Listener, a feature of ImageJ, is crucial for the ImageJ Extension to work. The Single Instance Listener does not work for the latest ImageJ 2 versions. We recommend to use one of the Fiji Life-Line versions you can find on the Fiji homepage for which the Single Instance Listener does work.
You activate the ImageJ extension via the Extensions Manager and then configure it in the Options dialog.
Configuring the Software
Configuring ImageJ
To configure how ImageJ interacts with the software:
The ImageJ extension of requires ImageJ to be installed and additionally to be configured correctly.
To prepare ImageJ for the use in , perform the following steps:
ImageJ is now correctly installed and prepared to work with the software. If you have several ImageJ installations on your computer, make sure to direct the software to the above installation using the General Options dialog.
The ImageJ workbench enables you to connect with ImageJ. The communication between the two programs is bidirectional. You can use ImageJ to complement the image processing tools available in .
The ImageJ tool enables you to send images to ImageJ or to retrieve images from ImageJ, e.g. after processing them with ImageJ.
Sending an image to ImageJ
To send an image to ImageJ:
Retrieving an image from ImageJ
To retrieve an image from ImageJ:
ImageJ does not support all file types and pixel types that can be used in the software.
In these cases the image must be converted in the software before sending it to ImageJ.
See the tables below for further details.
to ImageJ
|
|
ImageJ |
Comments |
|---|---|---|
|
.tif, .jpg, .bmp, .png, .gif |
Original |
The image is imported unchanged. |
|
.ome.tif |
Original |
The image is imported unchanged. |
|
.czi 2D 8/16 Bit B/W |
32 Bit RGB |
You can change the pixel type back to B/W in ImageJ using the Image > Type command. |
|
.czi 2D 12 Bit B/W |
Not supported |
Convert the image to 16 bit B/W using the Change Pixel Type tool before sending it to ImageJ. |
|
.czi 24/48 Bit RGB |
32 Bit RGB |
|
|
.czi 36/42 Bit RGB |
Not supported |
Convert the image to 24/48 bit RGB using the Change Pixel Type tool before sending it to ImageJ. |
|
MD image |
If necessary, reassign the dimensions in ImageJ using Image > Hyperstacks for example. |
|
Tiled image |
Partially supported |
Only the first tile is imported. |
ImageJ to
|
ImageJ |
|
Comments |
|---|---|---|
|
.tif, .jpg, .bmp, .png, .gif |
Original |
The image is imported unchanged. |
|
.ome.tif |
Original |
The image is imported unchanged. |
|
2D images, B/W or RGB |
.tif, B/W or RGB |
Any 2D image other then the types listed above is received as a .tif-image. |
|
MD image |
All channels or layers are imported into a corresponding multidimensional image. |
|
Tiled image |
Partially supported |
Only the first tile is imported. |