CamiTK

CamiTK develop

Wed, 25 Mar 2026 00:00:00 +0000

Current version

This page is generated automatically from the gitlab activity and is will not be edited by a human until the next release.

Python Extensions

Mon, 01 Jan 0001 00:00:00 +0000

Develop Python Extensions for CamiTK

Use Python to create Actions, Components, or Viewers with CamiTK’s Python API.

Getting Started with Python Extensions

Python extensions are ideal for rapid prototyping, machine learning integration, and scripting. DevStudio generates a Python file for each action for you to complete.

Steps to Create a Python Extension:

Open DevStudio from the CamiTK menu.
Define your extension's name, package requirements (if any), parameters, and input components.
DevStudio generates the boilerplate code: a .py for each action for you to edit and a .camitk containing the metadata of your extension.
As shown in the devstudio video click on Initialize to generate the boilerplate code for first time and then on Register to integrate it in CamiTK (it will then be automatically available in the corresponding Action menu).
Complete the process function in the generated Python file.

Python Action code template

When DevStudio generates the template code of an action, you will find four functions in the corresponding Python file. Some Python code is generated when DevStudio creates your action to show you an example of what is expected (see devstudio video). It is now up to you to modify the four functions/methods:

C++ Extensions

Mon, 01 Jan 0001 00:00:00 +0000

Develop C++ Extensions for CamiTK

Use C++ for high-performance extensions, such as computationally intensive tasks.

Getting Started with C++ Extensions

C++ extensions are ideal for performance-critical tasks. DevStudio generates all the files required to add your extension into CamiTK.

Steps to Create a C++ Extension:

Open DevStudio from the CamiTK menu.
Define your extension's name, parameters, and input components.
Choose between Hotplug or Standard extension types.
DevStudio generates the boilerplate code: one C++ files per action for you to complete, a .camitk file containing the metadata of your extension, and a CMakeLists.txt ready to build your code.
As shown in the devstudio video click on Initialize to automatically build your extension for the first time and then on Register to integrate it in CamiTK (it will then be automatically available in the corresponding Action menu).
Complete the generated C++ classes and rebuild to modify your extension.

C++ Action code template

When DevStudio generates the template code of an action, it generates a class derived from CamiTK Action in the corresponding .cpp files (the header file is generated, if you need to add fields to your class use the DevStudio UI or edit the .camitk directly). There are four methods you will need to complete. Some C++ code is generated when DevStudio creates your action for the first time to show you an example of what is expected. It is now up to you to modify the four methods:

Migration guide from CamiTK 3.x to CamiTK 4.0

Mon, 01 Jan 0001 00:00:00 +0000

This page explains how to modify your CamiTK 3.x code to work on the 4.x version. The CamiTK team tried to do its best to make sure that there are not a lot of changes to make to your CEP source code. Here it a complete step by step.

Prerequisite

First of all, make sure you have compiled and installed CamiTK 4.0 or up on your computer. Please follow the setup guide of this wiki.

Migration guide from CamiTK 4.0 to CamiTK 4.1

Mon, 01 Jan 0001 00:00:00 +0000

The main objective of the CamiTK 4.0 was to ensure that CamiTK will stay up to date with its basic dependencies. Qt4, VTK5 and CMake version 2 became obsolete. CamiTK 4.0 had therefore to ensure compatibility with Qt5, VTK6 and CMake version 3.

CamiTK 4.1 is the first stable release of the 4.x family. It removes all the 3.x deprecated methods and clean up a lot of obsolete Core library API methods.

C++ Tutorials

Mon, 01 Jan 0001 00:00:00 +0000

Tutorials source code

The tutorials CEP is one of the CEP of CamiTK Community Edition. It contains some examples that could help you develop your own extension. You can find all the tutorial source code in the tutorials subdirectory of CamiTK Community Edition.

Support Policy

Mon, 01 Jan 0001 00:00:00 +0000

This document lists the toolchain and dependencies currently supported (and recommended) for building CamiTK 6.0.0 and CamiTK develop.

CamiTK develop continuous integration status

Supported Operating Systems

The CamiTK project team is currently using the following OS during continuous integration:

Debian testing

Debian 14 Forky

Debian is the base of many distributions.

Using Debian Testing allows the CamiTK team to make sure the most recent version of Linux packages are supported.

Migration guide from CamiTK 4.1 to CamiTK 5.0

Mon, 01 Jan 0001 00:00:00 +0000

CamiTK 5 fixes a lot of bugs (see the Release Notes) and introduces one big new feature: the viewer extension (ability to define plugins that provides new viewers, see the viewer extension documentation for more information). Viewer extensions are now a first class type of extension, and are as easy to create and integrate as action and component extensions. They also makes applications easier to build and test.

The methods in the Component class that used a pointer to a Viewer in the previous versions of CamiTK are now using a QString to name the required viewer. This ensures safety and modularity to access a specific viewer (e.g., to manage the case where the corresponding viewer extension is not currently loaded).

Migration guide from CamiTK 5.0 to CamiTK 5.2

Mon, 01 Jan 0001 00:00:00 +0000

CamiTK 5.2 fixes a lot of bugs (see the Release Notes) and introduces one big new feature: the viewer extension (ability to define plugins that provides new viewers, see the viewer extension documentation for more information). Viewer extensions are now a first class type of extension, and are as easy to create and integrate as action and component extensions. They also makes applications easier to build and test.

Migration guide from CamiTK 5.2 to CamiTK 6.0

Mon, 01 Jan 0001 00:00:00 +0000

Frames and geometrical Transformations

If your extension manages frames of components and geometrical transformations between them, you will need to port your code to the new framework.

Here is a short preview:

Previously, components had a Component::get/setParentFrame() and a transformation to it that you could set using Component::setTransform() and other helper functions.
Now Frames and Transformations are managed by the TransformationManager (see API), so that multiple components can use the same frame.
When you load or create a MeshComponent, a new Frame is created for it.
When you load an ImageComponent, it comes with three frames: the Data Frame (were the voxels are defined), the main Frame (which is usually the coordinates system of the imaging machine, e.g. CT scanner) and an arbitrary frame to manage the position and orientation of the arbitrary slice that CamiTK can display.
Ownership: you need to be careful about the ownership of Frames and Transformations: When you use frames and transformation to process coordinates, you do not need to own the Frames and Transformations. This is why Component::getFrame(), ImageComponent::getDataFrame() return raw, non owning pointer.
If you really need ownership of a Frame, usually because you want to set the Frame of a new Component, you can either use myNewMesh->setFrameFrom(myOldMesh), or the more explicit myNewMesh->setFrame( TransformationManager::getFrameOwnership(myOldMesh->getFrame()) )
If your extension creates a new Component, please set its Frame in a logical way: if the data is expressed in the same Frame as the input component, just set the Frame of your output component to the Frame of the input Component
If you know the transformation between two Components, you can add a Transformation between their Frames using TransformationManager::addTransformation

New extensions

You should use DevStudio to create new extensions instead of the wizard. The code will be simpler, and Python extensions are supported as well.

CamiTK Programming Guidelines

Mon, 01 Jan 0001 00:00:00 +0000

The programming guidelines are available in PDF.

If you intend to develop long term and reusable CEP or a CEP that you would like us to include in the CamiTK Community Edition, please read and conform to these guidelines.

Manual segmentation action extension

Mon, 01 Jan 0001 00:00:00 +0000

CamiTK is a great tool that brings you the visualization power of VTK, image processing power of ITK and GUI handling capabilities of Qt, but simplifies it so that you can concentrate on your work. There are many ways to go about implementing what you need in CamiTK. In this tutorial, you will be presented with on such way: development in increments.

For this tutorial, let’s create a segmentation tool that lets you manually segment an image by drawing along the contours of the objects of interest similar to the ITK-SNAP tool¹ using the polygon mode.

Creating your own specific application

Mon, 01 Jan 0001 00:00:00 +0000

Creating your own CamiTK application is probably not what you want to do first. It is also not what you need to do either (at least in 95% of the use cases that we have seen so far in the projects that use CamiTK).

The already provided CamiTK imp application is highly customizable, features a lot of use cases that you will need to replicate (menu, history recording, preference settings, …), and can also be customizable thanks to the fact that all the viewers are in docks (that you can move or remove as you see fit).

Internationalization of CamiTK GUI

Mon, 01 Jan 0001 00:00:00 +0000

Warning

Internationalization is not officially supported by the CamiTK team, although it may work!

Change user interface language in CamiTK imp

start camitk-imp application.
in the “Help menu” do “Change Language” and choose a new language.
close camiTK imp application.
settings are modified and you can start your camiTK application with this new language.

At the moment, only a few strings are translated from English, but do feel free to contact us if you would like to help translate CamiTK in another language!

CamiTK testing framework technical overview

Mon, 01 Jan 0001 00:00:00 +0000

CamiTK provides some tools to test your code at different granularity levels. In this wiki page you will find information about our testing process, what we test and how you can use our already defined tests.

Introduction

Testing a software code is always a good practice to make sure that the code behave accordingly to the specification, to detect bugs and errors and regression. It can also be very helpful to check that code integration is operational. Several types of tests exist depending on the granularity level of the tests. There are classically three categories of tests:

How to ask for help

Mon, 01 Jan 0001 00:00:00 +0000

If you are facing a difficulty while developing in CamiTK, you may want to ask more experimented users for help. Here is explained how to do so.

First, make sure your question is not already answered somewhere

Here is a list of website or resources you need to check first.

Online documentation

Just go to the “Search this site” field on the top right corner of this page.

Issue board on Gitlab

The issue board contains the (recent) history of all the issues that developers or users have face.

Using VTKWidget (interactive widget in 3D)

Mon, 01 Jan 0001 00:00:00 +0000

VTK widgets are useful for 3D interactive actions. They can be easily added in CamiTK actions. This page gives you a step by step to add an interactive VTK widget in the default 3D viewer in an action.

The first step is the creation of a class for the VTK widget. This class must inherit from the vtkCommand class.

Example with a vtkImplicitPlaneWidget :

DLL import and export on Windows

Mon, 01 Jan 0001 00:00:00 +0000

This page explains how to take care of DLL symbol export and import easily. This is required on Windows to reuse an extension or library into an other extension. For Linux or Mac developers, this is required if you want your extension to work on Windows, although you don’t need it if you restrict yourself to your own platform.

Introduction

A dynamic library (.dll, .so, .dylib, named DLL in the following explanation) contains C++ compiled functions which might be called by another program using this DLL at runtime. When programming, as a developer you may want to reuse some classes or functions already defined and compiled in a dynamic library, or, on the other hand, you would like to make some classes / functions available within a dynamic library (for other developments).

Interactive display the results of a VTK pipeline in 3D

Mon, 01 Jan 0001 00:00:00 +0000

How to temporarily display the output of a vtk filter

This method avoid the creation of a new Component : the output of a vtk filter can be displayed by only changing the data connection of the initial Component.

The Geometry service getDataPort() and setDataConnection() allow you to temporarily connect the VTK pipeline between the original data and the visualization. The VTK pipeline is added without modifying the initial mesh data, but its results will be seen in the 3D viewers.

Using OpenCV in a CamiTK extension project

Mon, 01 Jan 0001 00:00:00 +0000

Although CamiTK Community Edition does not depends on OpenCV, if your extension requires OpenCV, this page presents the correct way of setting up, install and use OpenCV for a flawless integration.

Setup and install OpenCV

On Linux

On Ubuntu, Debian or derivatives, just install the dev package (typically using sudo apt install libopencv-dev).

For other Linux distribution, please check that a package is available. Otherwise just refer to the OpenCV documentation or get inspired by the windows setup below. As OpenCV is also using CMake, it is a easy step.

Deploy CamiTK with your extensions

Mon, 01 Jan 0001 00:00:00 +0000

Once your extension has reached a stable state, the next step is often to give it to another user or developer so that it can test it. This is what we call “distribute and deploy your CamiTK extensions”.

The dependency chain might be quite fragile when it comes to C++ where there is not (yet) an official package manager, especially on Windows.

This page provides a recipe to easily get all you need to run CamiTK and your extensions (called mycep henceforward) on another computer (called the target computer henceforward) than the one you used to develop (called the developer computer henceforward).

CamiTK 6.0.0

Tue, 24 Mar 2026 00:00:00 +0000

CamiTK 6.0.0 is Here!

This major release introduces three groundbreaking features, significant bug fixes, and internal improvements.

CamiTK 5.2.0

Tue, 20 Feb 2024 00:00:00 +0000

This is the release notes for CamiTK 5.2.0.

CamiTK 5.2.0 comes with a main new feature and important bug fixes.

2 new features
- Users can save and load a workspace in a .camitk file. The workspace includes opened components, image contrast (LUT), mesh colors, geometrical transformations between components and more.
- Image registration using Elastix (needs elastix command available)
5 bugs fixed
- Fancy viewer application segfaults (closes #168)
- IMP and ActionStateMachine requires linking to specific viewers - caused a crash in previous packages (closes #133)
- Printing debug information using F2 key does not crash (closes #171)
- Action viewer’s search panel now correctly filters actions (closes #173)
- Arbitrary Slice does not crash with 2D images (closes #176)
UI improvements

CamiTK 5.1.0

Fri, 28 Jul 2023 00:00:00 +0000

This is the release notes for CamiTK 5.1.0.

CamiTK 5.1.0 comes with few new features but a lot of important bug fixes, especially in its support of medical image and mesh.

4 new features
- CamiTK now supports VTK 9 and ITK 5.2 (the recommended versions)
- Anti-aliasing in 3D viewer (FXAA) is now on by default in the 3D viewer
- A color can be attributed to each vertex of a mesh
- More customizable tube representation in 3D (through the API)
4 bugs fixed

CNRS opens a permanent research engineer position for CamiTK

Wed, 15 Jun 2022 00:00:00 +0000

The French National Centre for Scientific Research (CNRS in French) is opening a position to support the development of CamiTK.

Ingénieur(e) de recherche expert(e) ingénierie logicielle

Le laboratoire TIMC recrute un⋅e ingénieur⋅e de recherche chef⋅fe de projet ou expert⋅e en ingénierie logicielle par concours externe des ingénieurs et techniciens du CNRS.

Contexte

Situé à Grenoble, le laboratoire de recherche Translationnelle et Innovation en Médecine et Complexité (TIMC) réunit scientifiques et cliniciens autour de l’utilisation de l’informatique et des mathématiques appliquées pour la compréhension et le contrôle des processus normaux et pathologiques en biologie et santé. Dans le domaine des technologies médicales, la mise au point d’un nouveau dispositif médical fait intervenir plusieurs disciplines scientifiques et différents acteurs (chercheurs, ingénieurs, cliniciens et entreprises).

Windows setup, OpenCV and deploy your CEP documentation update

Tue, 13 Jul 2021 00:00:00 +0000

Three new documentation updates were published today

The Windows setup documentation page was updated to remove some misprints (thanks to Hatem Younes)
an article on how to install and use OpenCV in a CamiTK extension project was added to development advanced topics (thanks to Hatem again!)
A new documentation page on how to distribute and deploy CamiTK with your extension(s) was added (with CamiTK 5.0 deploying became fairly, easy even on Windows).

Second open science french government plan

Wed, 07 Jul 2021 00:00:00 +0000

The second “open science” plan of the french government was publish last week. I encourage you to read the full document (in french). You will note that, along with other axis that cover access to publication and management and promotion of open data, there is a specific axis called “Ouvrir et promouvoir les codes sources produits par la recherche” (open and promote the source code produced by research) with the following actions:

CamiTK 5.0.2

Fri, 30 Apr 2021 00:00:00 +0000

This is the release notes for CamiTK 5.0.2

CamiTK 5.0.2 comes with

a brand new web site (click here for all the details)
13 new features: viewer extension framework, slice arbitrary orientation, mesh projection, and more… (click here for all the details)
10 code quality and devops improvements: updated dependencies and toolchain, improved continuous integration, multi-architecture support, improved quality, and more… (click here for all the details)
and over 11 bug fixed

Note

CamiTK 5.0 is our first Long Term Support release. It will be updated with patches, but no new features will be added for a while as we are busy with a completely new version. CamiTK 5.0 therefore offers stability for the next three years.

New CamiTK website

Mon, 18 Jan 2021 00:00:00 +0000

The new CamiTK website is generated thanks to the Docsy theme of Hugo.

The Docsy Hugo theme lets project maintainers and contributors focus on content, not on reinventing a website infrastructure from scratch. That’s really similar to the way the CamiTK team feel about prototyping software!

New beginning for the CamiTK website. Look around, you're in it!

The big advantages of using docsy are:

CamiTK 4.1.2 (burgundy)

Sun, 15 Jul 2018 00:00:00 +0000

CamiTK Community Edition

Starting with CamiTK 4.1, all the open-source supported code is now named/branded "CamiTK Community Edition" (CamiTK CE)
CamiTK Community Edition is now available on the gitlab server of Univ. Grenoble Alpes
New continuous integration test system implemented directly into Gitlab with the power of Docker for all supported OS.
Bug and feature requests should now be submitted directly to our gitlab issue board
All CamiTK 3.x deprecated API removed. See the migration guides for more information: 3.x → 4.0 and 4.0 → 4.1
Better support for operating failures of used libraries (itk, vtk, etc.) through the use of exception handling.

Code quality improvement

More flexibility and robustness:

A lot of code consolidation, performance improvement, code cleaning and compilation messages cleaned.
CamiTK CE code is now compliant to C++ 11 standard (thanks to clang-tidy).
The "Report Bug" action (that allows you to report a bug directly from the camitk-imp interface) has been updated.
Test coverage results are now published on CDash Dashboard.
New option at configuration time to build with the Include What You Use system.

CamiTK 4.0.4 (red)

Thu, 01 Dec 2016 00:00:00 +0000

Packaging ready version

Fix issues on vtk filter on some actions.
Fix internal compilation mode to taking into account C++11 standard.

Bug fixed

CamiTK hotfix version 4.0.4 fixes bugs: 184

4.0.3

29 September 2016

Packaging ready version

Fix package problem.
Fix parallel build issues due to dependencies to SDK targets.
Fix some spelling and copyright mistakes.
Fix space in CEP name bug.

4.0.2

22 July 2016

VTK et CamiTK 3D viewer

Wizard updated to generate a CamiTK 4.0 compliant CEP.
Migration guide from 3.5 to 4.0 is available.
CamiTK 4.0.2 dependencies are:
- Qt 5.3 and above on Linux and Qt 5.6 on Windows
- VTK 6.3 and above (VTK 7 should work)
On Windows, there is a VTK bug that prevent the installation of VTK 6 or VTK 7 debug version.

Bug fixed

CamiTK hotfix version 4.0.2 fixes bugs: 181

CamiTK 3.5.0 (teal)

Fri, 29 Jan 2016 00:00:00 +0000

No libxml2 dependency anymore!

CamiTK used libxml2, essentially for parsing XML in the modeling CEP. We now use XSD to describe our XML structures.

Bug fixed

CamiTK version 3.5.0 fixes bugs: 116, 118, 127, 128, 133, 134, 135, 146, 150, 155, 156, 158, 163, 172, 179.

New frame policy!

When creating a new component thanks to an action, you have the choice of the frame policy to apply: keep the parent component's frame, only the relation as a parent frame or no one at all. The choice is up to you. Edit this preference in the CamiTK IMP Edit->Preference menu.

CamiTK 3.4.0 (iris)

Fri, 31 Oct 2014 00:00:00 +0000

New images orientations!

CamiTK now considers the translation, rotation and orientation of images. Images acquired by scanner are now faithfully represented in 3D spaces. Axial, coronal and sagittal viewers no longer display wrong slices since each image orientation is taken into account at read time.

New service: Frames!

CamiTK provides a new service to any component: Frames. Frames stands for the capacity of any component to be positioned relatively to any other component in a 3D space. This feature is major and is really useful for describing component's position, especially with subcomponents. For instance, this feature is already used on projects involving robots components, positioning themselves relatively to other (part of) robots. A new frame explorer has been added in order to view the opened component frames's hierarchy. Also, a simple action is available to change a component's frame.

CamiTK 3.3.2 (indigo)

Tue, 06 May 2014 00:00:00 +0000

Version 3.3.2 (indigo)

6 May 2014

Bug fixed

CamiTK version 3.3.2 fixes bug: remove non DFSG compliant file (swf with no sources) and unused video files.

Version 3.3.1 (indigo)

7 April 2014

Bug fixed

CamiTK version 3.3.1 fixes bug ID11 and others not reported.

Version 3.3.0 (indigo)

4 March 2014

New Wizard application

The Wizard application is the best application to start working with CamiTK : it allows you to create your CamiTK Extension Project (CEP) and add Actions and Components extensions to it. The wizard generate your CEP's files and the skeleton of your C++ classes of your extensions. Do not hesitate to take a look at the CamiTK wiki documentation on how yo uses the new Wizard in order to work with it. You may also use take a look at its implementation with the technical documentation.

CamiTK 3.2.0 (azure)

Wed, 26 Jun 2013 00:00:00 +0000

CamiTK Extension Project

CamiTK Extension Projects (CEP) are a brand new way of organizing CamiTK plugins (extensions) of a same project. More than gathering together plugins of a same project, CEP organisation provides reliable tools such as packaging and dependencies handling between CEPs. Learn more about CEP in the Wiki documentation.

New project organisation (CEP wise)

CamiTK open source code is now separated into 3 parts : the sdk and the imaging and modeling CEPs. The SDK provides the core of CamiTK with several basic extensions, required to run or install any other CEP using CamiTK. The imaging and modeling are optional CEPs featuring, respectivaly image processing and biomechanical extensions. Both requires the SDK to be used. Learn more about this new camitk-opensource code organisation in the Wiki documentation.

CamiTK 3.1.0 (sapphire)

Fri, 01 Mar 2013 00:00:00 +0000

New application : Action State Machine

The new application "Action State Machine" allows you to easily process actions on images step by step. Actions are processed throught a pipeline (discribed in an xml file), displaying and requesting the least information possible. This application is really useful for end users willing to easily test a prototype.

New software project management

The CamiTK team follows the SCRUM agile sotware development rules. This organisation improves productivity and greatly reduces regressions.
CamiTK also features continuous integration with a CDash dashboard. This tool provides the developpers willing to contribute to reduce compilation and testing issues on several platforms (Windows, Linux, MacOsX).

CamiTK 3.0.0 (blue)

Sat, 07 Jul 2012 00:00:00 +0000

New application actions

New application actions are automatically available in any CamiTK application. Right clicking on a component pops-up an actions contextual menu which allows you to select them.

Volume rendering action

Easily render any 2D image (acquired from a scanner for instance) into a volumic colored mesh.

Improved Picking action

Multi-Pixel picking action has been added to the framework, featuring pixels information in a history. Useful !

Search Results

Mon, 01 Jan 0001 00:00:00 +0000

CamiTK

CamiTK develop

Python Extensions

Getting Started with Python Extensions

Steps to Create a Python Extension:

Python Action code template

C++ Extensions

Getting Started with C++ Extensions

Steps to Create a C++ Extension:

C++ Action code template

Migration guide from CamiTK 3.x to CamiTK 4.0

Prerequisite

Migration guide from CamiTK 4.0 to CamiTK 4.1

C++ Tutorials

Tutorials source code

Support Policy

CamiTK develop continuous integration status

Supported Operating Systems

Debian 14 Forky

Migration guide from CamiTK 4.1 to CamiTK 5.0

Migration guide from CamiTK 5.0 to CamiTK 5.2

Migration guide from CamiTK 5.2 to CamiTK 6.0

Frames and geometrical Transformations

New extensions

CamiTK Programming Guidelines

Manual segmentation action extension

Creating your own specific application

Internationalization of CamiTK GUI

Change user interface language in CamiTK imp

CamiTK testing framework technical overview

Introduction

How to ask for help

First, make sure your question is not already answered somewhere

Online documentation

Issue board on Gitlab

Using VTKWidget (interactive widget in 3D)

Creating a class for your widget

DLL import and export on Windows

Introduction

Interactive display the results of a VTK pipeline in 3D

How to temporarily display the output of a vtk filter

Using OpenCV in a CamiTK extension project

Setup and install OpenCV

On Linux

Deploy CamiTK with your extensions

CamiTK 6.0.0

CamiTK 5.2.0

CamiTK 5.1.0

CNRS opens a permanent research engineer position for CamiTK

Ingénieur(e) de recherche expert(e) ingénierie logicielle

Contexte

Windows setup, OpenCV and deploy your CEP documentation update

Second open science french government plan

CamiTK 5.0.2

New CamiTK website

CamiTK 4.1.2 (burgundy)

CamiTK Community Edition

Code quality improvement

CamiTK 4.0.4 (red)

Packaging ready version

Bug fixed

4.0.3

29 September 2016

Packaging ready version

4.0.2

22 July 2016

VTK et CamiTK 3D viewer

Bug fixed

CamiTK 3.5.0 (teal)

No libxml2 dependency anymore!

Bug fixed

New frame policy!

CamiTK 3.4.0 (iris)

New images orientations!

New service: Frames!

CamiTK 3.3.2 (indigo)

Version 3.3.2 (indigo)

6 May 2014

Bug fixed

Version 3.3.1 (indigo)