Table of Contents
Object stands for all type of data that Anatomist can handle. This software manages volumes (T1, fMRI, ...), meshes, textures (to stick on other objects), structured objects like sulci graphs or ROI graphs. All these objects can be visualized and combined (merging, superimposing...). Some data types and formats are peculiar to Anatomist, like for example meshes (.mesh or .tri), or nomenclature (.hie).
Main objects handled by Anatomist are listed below (the list is not exhaustive because there are also merged objects, volume slices...) :
Table 5.1. Formats managed by Anatomist (non exhaustive list)
| Icon | Format / Extension / Anatomist data type | Description |
|---|---|---|
 |
2D, 3D and 4D volume. |
Formats list, non exhaustive, according to the operating system (linux, windows...) :
|
|
Script (no icon) | .ana | Script to execute a sequence of actions. For example, a script can be a file containing commands to merge two volumes and load a specific palette. |
| Bundles : .bundles Bucket : .bck | Bundles are sets of fibers obtained by tracking. It is handled as a graph. A bucket is a set of points coprresponding for example to a region of interest, ie a voxels list (it is not possible to see the coordinates, only display is managed). |
| Mesh : .tri ou .mesh | Files storing meshes ( 3D mesh of hemispheres, brain, cortex...). |
| FUSION2D Object | Object created by merging objects with Fusion2D method (for example : merging two volumes). |
 | FUSION3D Object Texture : .tex, .val ou .erp | Object created by merging objects with Fusion3D method (for example : merging a volume and a mesh). Texture file, containing data to stick on meshes. |
 | CutMesh object | Object created by merging objects with CutMesh method (for example : merging a volume and a mesh). |
 | Volume Rendering Fusion | See the section called “Objects menu”. |
 | PlanarFusion3D object | Object (textured plan) obtained by merging a mesh slice plan (Planar mesh) and a volume. For example, in a FusionCutMeshMethod fusion between a volume and a mesh, PlanarFusion3D object will be the textured plan of the volume according to the slice plan of the mesh. |
 | Graph : .arg et .data | .arg file is associated to a .data directory, and enables to organize data as a graph (sulci graph, region of interest graph...) |
 | Nomenclature : .hie | File containing a hierarchy of names or label. It enables to do hierarchical selections in a graph : you can select via the nomenclature file .hie the graph nodes that have the same name or label. For example, if you load several sulci graphs that have been labelled with the same reference nomenclature (eg. the file sucal_root_colors.hie), you can do a hierarchical selection with the nomenclature (display of the selected node and its sub-nodes for all labelled sulci graphs). It is also possible in a nomenclature to associate a color to name and label graph attributes. A classical example is to use a nomenclature to visualize sulci labelling (each recognized sulcus is named and the graph is associated to a nomenclature that links each label to a specific color). |