More flexibility and robustness:
CamiTK 4.1 offer better support for automatic test of your CamiTK Extension Project (CEP), see the automatic test documentations. Notably:
The new log system is developer as well as end-user friendly. It is more flexible, versatile and more configurable (level, output to file or console). It can be used at all development stage from prototype development to clinical test. Coming with the new log system, the application console displaying the message has been completely recreated from scratch.
All VTK file point data are now loaded and can be displayed/hidden by the user or programmatically. Norm, first, second, and third component of point or cell vector data can now also be displayed in the 3D viewer. There is also three ways to show vector data in 3D (hedge hog, scaled and unscaled arrows).
(This was submitted as feature request #192 and #162 on the now defunct bugzilla server).
CamiTK version 4.1 fixes the following bugs:
CamiTK version 4.1 implements the following feature requests submitted by our users:
Here is some stats:
CamiTK hotfix version 4.0.4 fixes bugs: 184
CamiTK hotfix version 4.0.3 fixes bugs: 183
CamiTK hotfix version 4.0.2 fixes bugs: 181
CamiTK 4.0.0 does not change its API but works with the new major release versions of its main libraries dependencies.
CamiTK now supports:
CamiTK used libxml2, essentially for parsing XML in the modeling CEP. We now use XSD to describe our XML structures.
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.
Every default actions of a imager (reprensented as the CamiTK component 'ImageAcquisitionComponent') are now available. It's easier then to create a new component to interface a new imager device with CamiTK!
The new action PML Explorer allows one to look into the structure of any PML component. Select any element (point, cells etc.) of the structure in this widget. The element is automatically enlightned!
Note that, in previous versions, within an PML component, each of its element was considered as a CamiTK component. This is not the case anymore, optimizing the resources when loading a PML component in memory!
New action edit frame allows one to completly (and betterly) edit one component's frame. From the translation to the rotation and the parent, you will be able to edit them all!
Note that, since frame are not stored when saving a component as a file, you may export your frame information as a .xml file on your hard drive and load it later!
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. More information on the dedicated page on the wiki.
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.
Mesh components have single and multiple points / cells picking. This allows to select any part of the 3D structure of the mesh. A tab in the property explorer displays information about the current selection. Also, mesh components contain now a generic attribute data which can be used by action on the mesh. This information is displayed in the data tab of the property explorer.
We greatly improved our DICOM component to read volumic images from DICOM standard format. Still based on GDCM open source library, we mixed our 2 previous DICOM components into one. It prompts the user which images to open and read their tags to consider their translation and orientation.
The MSH component has been improved to support .msh file format version 2. Try it out!
We added a new component that aims at helping building a component that acquires images from any devices. If you plan to build a component to get images from a new device, use this one!
Wiki documentation has been refreshed, betterly organised in different sections and categories. You'll find your information easier and faster.
Our automatic tests run on actions and components can now be switched on with a certain level. The higher the level of the test, the better the check are done on the extension. More information on testing levels in CamiTK.
CamiTK translation into several languages is now possible. We use QtLinguist to create several languages version of your CamiTK applications. Check out the wiki documentation to learn more about this new feature!
CamiTK version 3.3.2 fixes bug: remove non DFSG compliant file (swf with no sources) and unused video files.
CamiTK version 3.3.1 fixes bug ID11 and others not reported.
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 API has been exposed to Python using PySide and its wrapper tools. Our goal to achieve is to let the developper works on CamiTK either in C++ or Python, which is simpler, and targets more specifically Matlab users. At the moment, our wrapping of CamiTK allows any developpers to manipulate CamiTK API's objects in Python, and thus, build scripts in Python. Those scripts might be useful to apply many CamiTK actions on several data and then display the result within IMP. Curious or interested in this feature ? Please have a look to this first version in the Wiki documentation.
CamiTK API Documentation has now greatly been improved, with more classes and concepts description. Now following the source code directory tree, the API Documentation aims at presenting each extension concepts featuring the corresponding C++ classes. Do not hesitate to take a look at it.
CamiTK now proposes automatic basic testing of Actions and Components and a simple architecture to create unitarian and functional tests. Please have a look to the documentation on the wiki of the concepts.
CamiTK installation on Windows is now as fast as on Linux systems (really), in some minutes ! We provide automatic installers of CamiTK binaries, source code and all libraries dependencies (such as ITK, VTK, Qt) already compiled. Those installer are proposed in 32bits and 64bits, working for Visual Studio 2013, which we recommend for Windows users. Please learn more with this tutorial on the Wiki documentation.
CamiTK uses the powerful Qt meta-object properties and enhanced them to propose a generic and adaptable new property system. Now, you will be able to specificy in details (type, steps ...) of your Components and Actions' properties. Moreover, CamiTK properties are dynamic and can be set as readonly. Do not hesitate to take a look at the newProperty class..
Have you ever wanted to save in a file the pipeline of the different algorithms applied on your image ? Now, you can save, as an xml file, the history of your actions applied on your components through IMP! A XML file is automatically created and can be played, step by step as an input file for the Action State Machine application! Really useful when you have completed a pipeline of actions and want it to be validated by some end users.
New action to allow to change the grey level voxel value of a volumic image!
New action to subsample a volumic image into a smaller one!
New mesh action to merge two meshes into one. Your output is a single mesh file, store as a CamiTK MeshComponent!
New mesh component, that allows to handle .stl mesh files in CamiTK!
New mesh clipping action allows you to clip a mesh with lots of possible options!
CamiTK version 3.2.2 code source is avaible for Download.
This version fixes bugs 178, 185, 164, 116, 183, 180 and 177.
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
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.
CamiTK has now a special incubator (svn project) for Open-Source projects. The incubator is a new place where CEPs are maturing until they are ready to be integrated into CamiTK open-source code. Learn more about CEP maturing.
Windows Debug and Release DLLs (built using Visual Studio compiler) are known not to be compatible. This causes lots of system PATH issues. We decided to get over this problem by providing a new Windows (Visual Studio) configuration. Debug DLLs and applications are now suffixed with a "-debug" in their name, like Qt does with the "d" suffix, solving any Windows specific configuration issue.
Note, for compatibility purpose, on Windows using Visual Studio you will need to recompile some libraries this way. Take a look at the installation steps to follow (an automatic script is also provided).
CamiTK imaging CEP provides 2 new DICOM components using the GDCM open source library to handle DICOM image (.dcm) and DICOM directory, containing several images.
CamiTK SDK and modeling CEP provide new meshes actions: ICP registration, invert mesh, smooth filter, mesh to image stencil, extract edges, grid topology (2D and 1D). Feel free to use them!
New mesh quality action has been added. Featuring several distance, this action allows users to determines the quality, regarding the selected distance of each cell of a mesh.
camitk-config is a new console configuration utility for CamiTK. This application allows you to get information about the location and the installed plugins of your CamiTK installation. This tool is also used for configuring new CEP.
CamiTK is now C++11 compliant, and thus can be compiled using gcc 4.8 and MSVC 2010.
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.
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).
New components have been developped in order to support new file extensions : .off meshes format and analyse formats (.hdr.gz, .nifti and .nii)
New applications to make statistics easier in order to compare biomechanical models have been released. Using the MML format, ConvertMML will output statistics on CSV format or as plots to display the results.
Volume rendering actions is now optimized for image volume image. Any volume image component can be rendered in 3D as a subcomponent!
CamiTK applications running on Microsoft Windows proposes default file association with the current running CamiTK application (camitk-imp or any other). File association is done each time the application loads a new component extension, extending its files handling capabilities.
And of courses, a lot of bug fixes, making CamiTK more and more reliable in the Cami world! ;-)
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.
Easily render any 2D image (acquired from a scanner for instance) into a volumic colored mesh.
Multi-Pixel picking action has been added to the framework, featuring pixels information in a history. Useful !
Action creation is more generic and a lot easier. User now has a default customizable action widget to handle his action properties. This one can be replaced any other more sophisticated widget (created by Qt Designer for instance).
New drag and drop functionality to open images and better icons improve the global CamiTK applications ergonomy.
Now applications automatically load their last used components and actions at start-up, thanks to this feature! Less time wasted !
This component allows you to handle .msh file : tetra, hexa, prsim, pramid quad and triangle geometries are supported at the moment.
A new action to easily create spheres and grid topology is available.
And of courses, a lot of bug fixes, making CamiTK more and more reliable in the Cami world!