2015-11-02T13:32:12Z

Misiak: Created page with "== Windows == '''Notice:''' The ImageJ directory path depends on your ImageJ installation. Following, we assume that the ImageJ home directory is set up to ''C:\Program Fil..."

== Windows ==

 '''Notice:''' The ImageJ directory path depends on your ImageJ installation. Following, we assume that the ImageJ home directory is set up to ''C:\Program Files\ImageJ\''.<br\> 

==== Use MiToBo with an existing ImageJ installation ====

For installing MiToBo into an existing ImageJ installation perform the following steps:

# go to the '''MiToBo-bin\plugins\''' directory
#* copy the ''Mi_To_Bo.jar'' to your ''..\ImageJ\plugins\'' directory
#* copy all jars from ''MiToBo-bin\plugins\jars\'' to your ''..\ImageJ\plugins\jars\'' directory except the ij.jar and jars already existing ('''Notice:''' MiToBo requires explicite versions of some jars, other versions may not work probably, see [[downloads|requirements]].) 
# go to the '''MiToBo-bin\macros\toolsets\''' directory
#* copy the ''MiToBo_Runner.txt'' to your ''..\ImageJ\macros\toolsets\'' directory 

==== Native libraries ====

Some operators of MiToBo use native code via the Java Native Interface (JNI). 
The 'lib/' directory in the zip file provides precompiled JNI-libraries for 32-Bit (lib/libwin32) Windows systems. 
At the moment, JNI-libraries for Windows are only available for 32-Bit architectures, but can also be used with an 64-Bit architecture (see below). 
For using the native code add the libraries to the library path. 
The path to the native libraries must be available to any java application which uses MiToBo operators that depend on these libraries. 

===== 32-Bit architecture =====

# go to the '''MiToBo-bin\lib\''' directory
#* copy the ''libwin32'' directory to your ''..\ImageJ\'' directory 
# configurate your ImageJ startup
#* edit ImageJ configuration file ''..\ImageJ\ImageJ.cfg'' and add the library path '''-Djava.library.path="C:\Program Files\ImageJ\libwin32"''' Example of an ImageJ.cfg file:
C:\Program Files\ImageJ\
C:\Program Files\Java\jre6\bin\javaw.exe
-Djava.library.path="C:\Program Files\ImageJ\libwin32" -Xmx1024m -cp "C:\Program Files\ImageJ\ij.jar" ij.ImageJ
 
::* as an alternative you can start ImageJ from command line
:::* open your Windows command line
:::* move to the ''..\ImageJ\'' directoy
:::* type the following command:
java -Djava.library.path="C:\Program Files\ImageJ\libwin32" -Xmx1024m -cp "C:\Program Files\ImageJ\ij.jar" ij.ImageJ

===== 64-Bit architecture =====

Using a 64-Bit architecture requires a 32-Bit Java installed on the system to use the 32-Bit JNI-libraries. 
Perform the following steps to run MiToBo on a 64-Bit architecture:

# go to the '''MiToBo-bin\lib\''' directory
#* copy the ''libwin32'' directory to your ''..\ImageJ\'' directory 
# configurate your ImageJ startup
#* edit ImageJ configuration file ''..\ImageJ\ImageJ.cfg'' and add the library path '''-Djava.library.path="C:\Program Files (x86)\ImageJ\libwin32"''' Example of an ImageJ.cfg file:
C:\Program Files (x86)\ImageJ\
C:\Program Files (x86)\Java\jre6\bin\javaw.exe
-Djava.library.path="C:\Program Files (x86)\ImageJ\libwin32" -Xmx1024m -cp "C:\Program Files (x86)\ImageJ\ij.jar" ij.ImageJ
 
::* as an alternative you can start ImageJ from command line
:::* open your Windows command line
:::* move to the ''..\ImageJ\'' directoy
:::* type the following command:
C:\Program Files (x86)\Java\jre6\bin\javaw.exe -Djava.library.path="C:\Program Files (x86)\ImageJ\libwin32" -Xmx1024m -cp "C:\Program Files (x86)\ImageJ\ij.jar" ij.ImageJ

 '''Notice:''' The ''-Xmx1024m'' variable sets the maximum memory heap size of Java to 1024 MB. This value can be increased, depending on your installed system memory and architecture.<br\>

Installation/Linux

2015-11-02T13:30:36Z

Misiak:

== Using MiToBo with ImageJ on Linux ==

==== Use MiToBo as shipped ====
Extract the zip file to a directory of your choice. 
You can use MiToBo right away using the ''run.sh'' and ''oprunner.sh'' scripts. 
Make sure that they have the 'x'-bit set before executing the scripts, i.e. do 'chmod u+x run.sh' and 'chmod u+x oprunner.sh' first. 
If an '''UnsatisfiedLinkError''' occurs, please read the '''Native libraries''' section below.

==== Use MiToBo with an existing ImageJ installation ====

To use MiToBo with an existing ImageJ installation perform the following steps:

# copy the ''Mi_To_Bo.jar'' to be found in the 'plugins/' folder of the MiToBo zip file to your 'ImageJ/plugins/' directory
# copy all jars in 'plugins/jars/' of the MiToBo zip file to your 'ImageJ/plugins/jars/' except the ij.jar and any jars already existing in your 'ImageJ/plugins/jars/' directory ('''Notice:''' MiToBo requires explicit versions of some jars, other versions may not work properly, see [[downloads|requirements]].)
# copy the ''MiToBo_Runner.txt'' from the 'macros/toolsets/' directory in the MiToBo zip file to your 'ImageJ/macros/toolsets/' directory; then you can select the MiToBo toolset from the list of available sets by clicking on the arrows button on the right side of the ImageJ standard toolbar
# Make the native libraries in lib/ of the MiToBo zip file available to Java (see the '''Native libraries''' section below)

You can still use the ''run.sh'' and ''oprunner.sh'' scripts if you copy them to your 'ImageJ/' directory.

==== Native libraries ====

Some operators of MiToBo use native code via the Java Native Interface (JNI). 
The 'lib/' directory in the zip file provides precompiled JNI-libraries for 32- (lib/lib32) and 64-Bit (lib/lib64) Linux systems. 
For using the native code add the libraries appropriate for your system to the library path. 
The path to the native libraries must be available to any java application which uses MiToBo operators that depend on these libraries. 

* The ''run.sh'' and ''oprunner.sh'' scripts both add the 'lib/lib32' or 'lib/lib64' directory (depending on your architecture) to the LD_LIBRARY_PATH, thus, you do not have to configure the LD_LIBRARY_PATH manually.
* If you run ImageJ with MiToBo or the OpRunner in another way, the directories of native libraries can be passed to Java in any of the following two ways:
:* The LD_LIBRARY_PATH environment variable must contain the path to the native libraries used
:* The call to Java has to be augmented with an option to tell where native libraries reside:
java -Djava.library.path=/path/to/libs1:/path/to/libs2[:...] ...
:: For example, you can run ImageJ with MiToBo on a 32-Bit system with the unzipped MiToBo structure, but not the ''run.sh'' script, with the following command:
java -Djava.library.path=lib/lib32:/usr/lib -cp plugins/jars/ij.jar ij.ImageJ
:Configuring the LD_LIBRARY_PATH and running java with the -Djava.library.path option are equivalent.

* '''Building of MiToBo's native libraries:'''
: MiToBo ships with precompiled native libraries for 32- and 64-Bit Linux. If you encounter problems with the Linux libraries you might try to compile MiToBo's native libraries by yourself:
: 1. Download the zip file containing the sources of MiToBo and unpack the file to a directory of your choice.
: 2. Go to the 'native/export' directory in MiToBo's directory structure.
: 3. Edit ''Makefile.rules'' if necessary (defaults are predefined):
::* Set the variable MITOBO_HOME which should point to your MiToBo installation directory.
::* Set the path to your java installation which includes the JNI-header files.
::* Set the path to the CGAL libraries.
::* Set the path to the CGAL headers.
: 4. Run ''make install'', which will build MiToBo's native libraries for your architecture and move them into the lib/lib32 or lib/lib64 directory. Note that this will overwrite the libraries in 'lib/lib32' and 'lib/lib64', respectively.

:Note that when using these libraries also the CGAL libraries have to be available on the LD_LIBRARY_PATH upon execution of MiToBo operators.

Installation/Linux

2015-11-02T13:30:13Z

Misiak:

== Using MiToBo with ImageJ on Linux ==

==== Use MiToBo as shipped ====
Extract the zip file to a directory of your choice. 
You can use MiToBo right away using the ''run.sh'' and ''oprunner.sh'' scripts. 
Make sure that they have the 'x'-bit set before executing the scripts, i.e. do 'chmod u+x run.sh' and 'chmod u+x oprunner.sh' first. 
If an '''UnsatisfiedLinkError''' occurs, please read the '''Native libraries''' section below.

=== Use MiToBo with an existing ImageJ installation ===

To use MiToBo with an existing ImageJ installation perform the following steps:

# copy the ''Mi_To_Bo.jar'' to be found in the 'plugins/' folder of the MiToBo zip file to your 'ImageJ/plugins/' directory
# copy all jars in 'plugins/jars/' of the MiToBo zip file to your 'ImageJ/plugins/jars/' except the ij.jar and any jars already existing in your 'ImageJ/plugins/jars/' directory ('''Notice:''' MiToBo requires explicit versions of some jars, other versions may not work properly, see [[downloads|requirements]].)
# copy the ''MiToBo_Runner.txt'' from the 'macros/toolsets/' directory in the MiToBo zip file to your 'ImageJ/macros/toolsets/' directory; then you can select the MiToBo toolset from the list of available sets by clicking on the arrows button on the right side of the ImageJ standard toolbar
# Make the native libraries in lib/ of the MiToBo zip file available to Java (see the '''Native libraries''' section below)

You can still use the ''run.sh'' and ''oprunner.sh'' scripts if you copy them to your 'ImageJ/' directory.

=== Native libraries ===

Some operators of MiToBo use native code via the Java Native Interface (JNI). 
The 'lib/' directory in the zip file provides precompiled JNI-libraries for 32- (lib/lib32) and 64-Bit (lib/lib64) Linux systems. 
For using the native code add the libraries appropriate for your system to the library path. 
The path to the native libraries must be available to any java application which uses MiToBo operators that depend on these libraries. 

* The ''run.sh'' and ''oprunner.sh'' scripts both add the 'lib/lib32' or 'lib/lib64' directory (depending on your architecture) to the LD_LIBRARY_PATH, thus, you do not have to configure the LD_LIBRARY_PATH manually.
* If you run ImageJ with MiToBo or the OpRunner in another way, the directories of native libraries can be passed to Java in any of the following two ways:
:* The LD_LIBRARY_PATH environment variable must contain the path to the native libraries used
:* The call to Java has to be augmented with an option to tell where native libraries reside:
java -Djava.library.path=/path/to/libs1:/path/to/libs2[:...] ...
:: For example, you can run ImageJ with MiToBo on a 32-Bit system with the unzipped MiToBo structure, but not the ''run.sh'' script, with the following command:
java -Djava.library.path=lib/lib32:/usr/lib -cp plugins/jars/ij.jar ij.ImageJ
:Configuring the LD_LIBRARY_PATH and running java with the -Djava.library.path option are equivalent.

* '''Building of MiToBo's native libraries:'''
: MiToBo ships with precompiled native libraries for 32- and 64-Bit Linux. If you encounter problems with the Linux libraries you might try to compile MiToBo's native libraries by yourself:
: 1. Download the zip file containing the sources of MiToBo and unpack the file to a directory of your choice.
: 2. Go to the 'native/export' directory in MiToBo's directory structure.
: 3. Edit ''Makefile.rules'' if necessary (defaults are predefined):
::* Set the variable MITOBO_HOME which should point to your MiToBo installation directory.
::* Set the path to your java installation which includes the JNI-header files.
::* Set the path to the CGAL libraries.
::* Set the path to the CGAL headers.
: 4. Run ''make install'', which will build MiToBo's native libraries for your architecture and move them into the lib/lib32 or lib/lib64 directory. Note that this will overwrite the libraries in 'lib/lib32' and 'lib/lib64', respectively.

:Note that when using these libraries also the CGAL libraries have to be available on the LD_LIBRARY_PATH upon execution of MiToBo operators.

Installation/Linux

2015-11-02T13:29:44Z

Misiak:

== Using MiToBo with ImageJ on Linux ==

=== Use MiToBo as shipped ===
Extract the zip file to a directory of your choice. 
You can use MiToBo right away using the ''run.sh'' and ''oprunner.sh'' scripts. 
Make sure that they have the 'x'-bit set before executing the scripts, i.e. do 'chmod u+x run.sh' and 'chmod u+x oprunner.sh' first. 
If an '''UnsatisfiedLinkError''' occurs, please read the '''Native libraries''' section below.

=== Use MiToBo with an existing ImageJ installation ===

To use MiToBo with an existing ImageJ installation perform the following steps:

# copy the ''Mi_To_Bo.jar'' to be found in the 'plugins/' folder of the MiToBo zip file to your 'ImageJ/plugins/' directory
# copy all jars in 'plugins/jars/' of the MiToBo zip file to your 'ImageJ/plugins/jars/' except the ij.jar and any jars already existing in your 'ImageJ/plugins/jars/' directory ('''Notice:''' MiToBo requires explicit versions of some jars, other versions may not work properly, see [[downloads|requirements]].)
# copy the ''MiToBo_Runner.txt'' from the 'macros/toolsets/' directory in the MiToBo zip file to your 'ImageJ/macros/toolsets/' directory; then you can select the MiToBo toolset from the list of available sets by clicking on the arrows button on the right side of the ImageJ standard toolbar
# Make the native libraries in lib/ of the MiToBo zip file available to Java (see the '''Native libraries''' section below)

You can still use the ''run.sh'' and ''oprunner.sh'' scripts if you copy them to your 'ImageJ/' directory.

=== Native libraries ===

Some operators of MiToBo use native code via the Java Native Interface (JNI). 
The 'lib/' directory in the zip file provides precompiled JNI-libraries for 32- (lib/lib32) and 64-Bit (lib/lib64) Linux systems. 
For using the native code add the libraries appropriate for your system to the library path. 
The path to the native libraries must be available to any java application which uses MiToBo operators that depend on these libraries. 

* The ''run.sh'' and ''oprunner.sh'' scripts both add the 'lib/lib32' or 'lib/lib64' directory (depending on your architecture) to the LD_LIBRARY_PATH, thus, you do not have to configure the LD_LIBRARY_PATH manually.
* If you run ImageJ with MiToBo or the OpRunner in another way, the directories of native libraries can be passed to Java in any of the following two ways:
:* The LD_LIBRARY_PATH environment variable must contain the path to the native libraries used
:* The call to Java has to be augmented with an option to tell where native libraries reside:
java -Djava.library.path=/path/to/libs1:/path/to/libs2[:...] ...
:: For example, you can run ImageJ with MiToBo on a 32-Bit system with the unzipped MiToBo structure, but not the ''run.sh'' script, with the following command:
java -Djava.library.path=lib/lib32:/usr/lib -cp plugins/jars/ij.jar ij.ImageJ
:Configuring the LD_LIBRARY_PATH and running java with the -Djava.library.path option are equivalent.

* '''Building of MiToBo's native libraries:'''
: MiToBo ships with precompiled native libraries for 32- and 64-Bit Linux. If you encounter problems with the Linux libraries you might try to compile MiToBo's native libraries by yourself:
: 1. Download the zip file containing the sources of MiToBo and unpack the file to a directory of your choice.
: 2. Go to the 'native/export' directory in MiToBo's directory structure.
: 3. Edit ''Makefile.rules'' if necessary (defaults are predefined):
::* Set the variable MITOBO_HOME which should point to your MiToBo installation directory.
::* Set the path to your java installation which includes the JNI-header files.
::* Set the path to the CGAL libraries.
::* Set the path to the CGAL headers.
: 4. Run ''make install'', which will build MiToBo's native libraries for your architecture and move them into the lib/lib32 or lib/lib64 directory. Note that this will overwrite the libraries in 'lib/lib32' and 'lib/lib64', respectively.

:Note that when using these libraries also the CGAL libraries have to be available on the LD_LIBRARY_PATH upon execution of MiToBo operators.

2013-02-28T12:59:50Z

Misiak: /* Native libraries */

== General remarks ==

There are two common ways to work with MiToBo:
<ul>
<li> just using the operators included in MiToBo for improving your work and easing image processing tasks
<li> using the MiToBo API to write operators, plugins and other image analysis applications on your own
</ul>
Irrespective of which way you intend to go the first thing to is always to download the binary zip file containing the current release of MiToBo. The actual installation instructions differ in some parts depending on which way you choose. Below we will first provide some notes regarding the binary zip file, and then outline more details about the installation steps required
for simply using MiToBo's operators. Finally we will present some details for using MiToBo's API with your own code.

== The [[downloads|MiToBo Binary]] Zip File ==

To get the current release of MiToBo download and extract the [[downloads|MiToBo Binary zip file]]. You will find the following structure of directories and files:
* lib - includes nesessary libaries for Linux and Windows
* licences - includes MiToBo license and licences for other software used by MiToBo
* macros - includes the MiToBo macro toolset
* plugins - includes MiToBo jar and other jars used by MiToBo
* testimages - some sample images
* ''MiToBo-Guide-1.0.pdf'' - the user and programmer guide for MiToBo
* ''oprunner.sh'' - shell script to run MiToBo operators from commandline (Linux only)
* ''run.sh'' - shell script to run ImageJ with MiToBo (Linux only)
* ''README'' - with basic information

== Using MiToBo with ImageJ ==

'''Important Note:''' These instructions refer to ImageJ 1 only, instructions for ImageJ 2.0 will follow soon.

 

=== Linux ===

==== Use MiToBo as shipped ====
Extract the zip file to a directory of your choice. 
You can use MiToBo right away using the ''run.sh'' and ''oprunner.sh'' scripts. 
Make sure that they have the 'x'-bit set before executing the scripts, i.e. do 'chmod u+x run.sh' and 'chmod u+x oprunner.sh' first. 
If an '''UnsatisfiedLinkError''' occurs, please read the '''Native libraries''' section below.

==== Use MiToBo with an existing ImageJ installation ====

To use MiToBo with an existing ImageJ installation perform the following steps:

# copy the ''Mi_To_Bo.jar'' to be found in the 'plugins/' folder of the MiToBo zip-file to your 'ImageJ/plugins/' directory
# copy all jars in 'plugins/jars/' of the MiToBo zip-file to your 'ImageJ/plugins/jars/' except the ij.jar and any jars already existing in your 'ImageJ/plugins/jars/' directory ('''Notice:''' MiToBo requires explicit versions of some jars, other versions may not work properly, see [[downloads|requirements]].)
# copy the ''MiToBo_Runner.txt'' from the 'macros/toolsets/' directory in the MiToBo zip-file to your 'ImageJ/macros/toolsets/' directory; then you can select the MiToBo toolset from the list of available sets by clicking on the arrows button on the right side of the ImageJ standard toolbar
# Make the native libraries in lib/ of the MiToBo zip-file available to Java (see the '''Native libraries''' section below)

You can still use the ''run.sh'' and ''oprunner.sh'' scripts if you copy them to your 'ImageJ/' directory.

==== Native libraries ====

Some operators of MiToBo use native code via the Java Native Interface (JNI). 
The 'lib/' directory in the zip-file provides precompiled JNI-libraries for 32- (lib/lib32) and 64-Bit (lib/lib64) Linux systems. 
For using the native code add the libraries appropriate for your system to the library path. 
The path to the native libraries must be available to any java application which uses MiToBo operators that depend on these libraries. 

* The ''run.sh'' and ''oprunner.sh'' scripts both add the 'lib/lib32' or 'lib/lib64' directory (depending on your architecture) to the LD_LIBRARY_PATH, thus, you do not have to configure the LD_LIBRARY_PATH manually.
* If you run ImageJ with MiToBo or the OpRunner in another way, the directories of native libraries can be passed to Java in any of the following two ways:
:* The LD_LIBRARY_PATH environment variable must contain the path to the native libraries used
:* The call to Java has to be augmented with an option to tell where native libraries reside:
java -Djava.library.path=/path/to/libs1:/path/to/libs2[:...] ...
:: For example, you can run ImageJ with MiToBo on a 32-Bit system with the unzipped MiToBo structure, but not the ''run.sh'' script, with the following command:
java -Djava.library.path=lib/lib32:/usr/lib -cp plugins/jars/ij.jar ij.ImageJ
:Configuring the LD_LIBRARY_PATH and running java with the -Djava.library.path option are equivalent.

* '''Building of MiToBo's native libraries:'''
: MiToBo ships with precompiled native libraries for 32- and 64-Bit Linux. If you encounter problems with the Linux libraries you might try to compile MiToBo's native libraries by yourself:
: 1. Download the zip file containing the sources of MiToBo and unpack the file to a directory of your choice.
: 2. Go to the 'native/export' directory in MiToBo's directory structure.
: 3. Edit ''Makefile.rules'' if necessary (defaults are predefined):
::* Set the variable MITOBO_HOME which should point to your MiToBo installation directory.
::* Set the path to your java installation which includes the JNI-header files.
::* Set the path to the CGAL libraries.
::* Set the path to the CGAL headers.
: 4. Run ''make install'', which will build MiToBo's native libraries for your architecture and move them into the lib/lib32 or lib/lib64 directory. Note that this will overwrite the libraries in 'lib/lib32' and 'lib/lib64', respectively.

:Note that when using these libraries also the CGAL libraries have to be available on the LD_LIBRARY_PATH upon execution of MiToBo operators.

 

=== Windows ===

 '''Notice:''' The ImageJ directory path depends on your ImageJ installation. Following, we assume that the ImageJ home directory is set up to ''C:\Program Files\ImageJ\''.<br\> 

==== Use MiToBo with an existing ImageJ installation ====

For installing MiToBo into an existing ImageJ installation perform the following steps:

# go to the '''MiToBo-bin\plugins\''' directory
#* copy the ''Mi_To_Bo.jar'' to your ''..\ImageJ\plugins\'' directory
#* copy all jars from ''MiToBo-bin\plugins\jars\'' to your ''..\ImageJ\plugins\jars\'' directory except the ij.jar and jars already existing ('''Notice:''' MiToBo requires explicite versions of some jars, other versions may not work probably, see [[downloads|requirements]].) 
# go to the '''MiToBo-bin\macros\toolsets\''' directory
#* copy the ''MiToBo_Runner.txt'' to your ''..\ImageJ\macros\toolsets\'' directory 

==== Native libraries ====

Some operators of MiToBo use native code via the Java Native Interface (JNI). 
The 'lib/' directory in the zip-file provides precompiled JNI-libraries for 32-Bit (lib/libwin32) Windows systems. 
At the moment, JNI-libraries for Windows are only available for 32-Bit architectures, but can also be used with an 64-Bit architecture (see below). 
For using the native code add the libraries to the library path. 
The path to the native libraries must be available to any java application which uses MiToBo operators that depend on these libraries. 

===== 32-Bit architecture =====

# go to the '''MiToBo-bin\lib\''' directory
#* copy the ''libwin32'' directory to your ''..\ImageJ\'' directory 
# configurate your ImageJ startup
#* edit ImageJ configuration file ''..\ImageJ\ImageJ.cfg'' and add the library path '''-Djava.library.path="C:\Program Files\ImageJ\libwin32"''' Example of an ImageJ.cfg file:
C:\Program Files\ImageJ\
C:\Program Files\Java\jre6\bin\javaw.exe
-Djava.library.path="C:\Program Files\ImageJ\libwin32" -Xmx1024m -cp "C:\Program Files\ImageJ\ij.jar" ij.ImageJ
 
::* as an alternative you can start ImageJ from command line
:::* open your Windows command line
:::* move to the ''..\ImageJ\'' directoy
:::* type the following command:
java -Djava.library.path="C:\Program Files\ImageJ\libwin32" -Xmx1024m -cp "C:\Program Files\ImageJ\ij.jar" ij.ImageJ

===== 64-Bit architecture =====

Using a 64-Bit architecture requires a 32-Bit Java installed on the system to use the 32-Bit JNI-libraries. 
Perform the following steps to run MiToBo on a 64-Bit architecture:

# go to the '''MiToBo-bin\lib\''' directory
#* copy the ''libwin32'' directory to your ''..\ImageJ\'' directory 
# configurate your ImageJ startup
#* edit ImageJ configuration file ''..\ImageJ\ImageJ.cfg'' and add the library path '''-Djava.library.path="C:\Program Files (x86)\ImageJ\libwin32"''' Example of an ImageJ.cfg file:
C:\Program Files (x86)\ImageJ\
C:\Program Files (x86)\Java\jre6\bin\javaw.exe
-Djava.library.path="C:\Program Files (x86)\ImageJ\libwin32" -Xmx1024m -cp "C:\Program Files (x86)\ImageJ\ij.jar" ij.ImageJ
 
::* as an alternative you can start ImageJ from command line
:::* open your Windows command line
:::* move to the ''..\ImageJ\'' directoy
:::* type the following command:
C:\Program Files (x86)\Java\jre6\bin\javaw.exe -Djava.library.path="C:\Program Files (x86)\ImageJ\libwin32" -Xmx1024m -cp "C:\Program Files (x86)\ImageJ\ij.jar" ij.ImageJ

 '''Notice:''' The ''-Xmx1024m'' variable sets the maximum memory heap size of Java to 1024 MB. This value can be increased, depending on your installed system memory.<br\> 

== Using MiToBo's APIs ==
To use the API of MiToBo and benefit from MiToBo's functionality in your own code you just need to make the jar archive to be found in the zip file available on your classpath. In addition, make sure that all jar archives MiToBo depends on and which are listed on the [[downloads|Download page]] are also in your classpath. Note that the jars are also included in the MiToBo's binary zip file, thus, you don't need to download them manually.