Skip to content

imaris/ImarisConvertBioformats

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

14 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

ImarisConvertBioformats

ImarisConvertBioformats is a command line program that converts microscopy image files stored in one of the many file formats readable by the Bio-Formats readers into the IMS format used by the Imaris software for visualization and analysis of microscopy images.

ImarisConvertBioformats is simple to use from the command line. It can also be used as a plugin to the ImarisFileConverter program which provides a graphical user interface that makes file conversion very simple.

The open source nature of ImarisConvertBioformats and Bio-Formats and ImarisWriter creates the possibility to easily add new formats for both input and output and it creates the possibility for anyone to easily fix bugs should that be necessary. We hope that this flexibility is beneficial for the microscopy community.

Binary Download

You can download the latest installers for ImarisConvertBioformats for Windows and macOS here: WindowsInstaller, macOSInstaller

Usage

ImarisConvertBioformats is a command line program. To get the arguments list and usage examples:

On Windows

ImarisConvertBioformats.exe --help

On MacOS and Linux

./ImarisConvertBioformats --help

Dependencies

  1. Bio-Formats: download bioformats_package.jar from https://www.openmicroscopy.org/bio-formats/downloads/ and copy it to the existing empty bioformats folder, contained in the Imaris Convert Bioformats top folder.

  2. ImarisWriter: download and extract the source code from https://github.com/imaris/ImarisWriter. Rename the folder containing CMakeLists.txt as ImarisWriter and copy it in the same folder as bioformats, fileiobase, fileiobioformats and ImarisConvertBioformats. It will be automatically built during ImarisConvertBioformats' building process.

  3. hdf5 version >= 1.10.4: https://www.hdfgroup.org/downloads/hdf5/ (compile with default options, only base C module is required)

  4. zlib: https://www.zlib.net/ (compile with default options)

  5. lz4: https://github.com/lz4/lz4 (compile with default options)

  6. FreeImage: version >= 3.17: https://freeimage.sourceforge.io/ (compile with default options)

  7. boost: version >= 1.65 (sucessfully tested with both <1.69 and >=1.69) We suggest cmake version >=3.13 for correctly finding new boost versions (starting from boost 1.69, boost::system became a header only library) On Mac and Windows compile boost with:

    --with-atomic --with-filesystem link=static

    On Linux we link dinamically, we do not need

    link=static

  8. java: tested succesfully with both java8 and java11 (we also need jre, or jre-like functionality from jdk)

Build

In order for CMake to find the thirdparty (custom) installations, some or all of the following CMake path variables should be properly set for your system:

-DHDF5_ROOT -DZLIB_ROOT -DLZ4_ROOT -DBOOST_ROOT -DJAVA_HOME -DJRE_HOME -DFreeImage_ROOT -DFreeImage_LIBRARIES

For most of the above dependencies, default system installation on Mac and Linux will work and in many cases, -D<LibraryName>_ROOT will not be necessary. In case of FreeImage, however, even for system install, one has to define in the cmake command:

-DFreeImage_ROOT

and/or

-DFreeImage_LIBRARIES

-DJRE_HOME should be set to the folder that contains, depending on the system:

lib/server/<dynamic_jvm_library>

or

bin/server/<dynamic_jvm_library>

-DJRE_HOME can point to a separate jre installation, or to a relative path to JAVA_HOME (assuming JAVA_HOME is set to the jdk folder).

In most installations of Java 8, jre is a subfolder of the jdk folder, but that is not (necessarily) the case for java 11. For most Java 11 installations, JRE_HOME could be set to $JAVA_HOME

The cmake command should be run from ImarisConvertBioformats subfolder.

Building example on Windows

Release build using Visual Studio, with custom installation for all dependencies:

cd ImarisConvertBioformats
mkdir build
cd build
cmake -G"Visual Studio 14 Win64" -DHDF5_ROOT="<libs>/hdf5" -DZLIB_ROOT="<libs>/zlib" -DLZ4_ROOT="<libs>/lz4" -DBOOST_ROOT="<libs>/boost" -DJAVA_HOME="<libs>/jdk" -DJRE_HOME="<libs>/jre" -DFreeImage_ROOT="<libs>/FreeImage" ..
devenv.com "ImarisConvertBioformats.sln" /Build "Release|x64" 
devenv.com "ImarisConvertBioformats.sln" /Deploy "Release|x64" /project "INSTALL"

A debug build is similar, one just has to set Debug, instead of Release in the build and install steps. The installation folder is build/<build_type>.

Building example on Linux/MacOS

Release build, with system path installations for all thirdparty dependencies (so <Library_Name>_ROOT not necessary):

cd ImarisConvertBioformats
mkdir build
cd build
cmake .. -DFreeImage_LIBRARIES="<path_to_dynamic_FreeImage_library>" -DJAVA_HOME="<jdk_folder>" -DJRE_HOME="<jre_folder>" -DCMAKE_BUILD_TYPE="Release"
make
make install

For a debug build, one has to set:

-DCMAKE_BUILD_TYPE="Debug"

If CMAKE_BUILD_TYPE is defined, the installation folder is build/{$CMAKE_BUILD_TYPE}, otherwise just build. On some MacOS systems, the build target architecture(s) should be set with

-DCMAKE_OSX_ARCHITECTURES

For example:

-DCMAKE_OSX_ARCHITECTURES=x86_64

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 3

  •  
  •  
  •  

Languages