Context: The surface registration process
This page describes technical aspects of the "template" file type used in the FreeSurfer pipeline as part of the process of coregistering the surfaces of individual subjects. If you are unfamiliar with this process and the programs involved, please see this overview: SurfaceRegAndTemplates.
Template data grid
A template contains curvature-related data as an array of data items that pertain to a grid of points on the sphere -- but which grid? Is it a specific surface mesh supplied with FreeSurfer? A standard "icosahedron" such as ic7.tri with an even distribution of 327680 triangles?
As it turns out, it's a grid defined in spherical coordinates:BR
- theta (0..2*pi in 512 steps)
phi (0..pi in 256 steps)BR
... the two parameters of the so-called "surface parameterization" (elsewhere known as u and v).
So, for any single data item, we can expect an array(256 * 512) numbers.
Template data items
The various programs involved have some flexibility in what size and shape of template to work with, but here I will describe the standard ?h.average.curvature.filled.buckner40.tif.
The registration process does not simply attempt to match a subject and template based on a single variable. Instead it works with several variables, and statistics about those variables.
Here's what I think is in the standard template:
sulc (ie: convexity)
Notes:[[BR]] 1. "inflated.H" is likely "mean curvature" of the inflated surface, that is the per-vertex value (kmin+kmax)/2.BR 2. I'm not certain on the measure in the 3rd row because in the mris_register source code it's calculated on the fly, and hard to tell which options cause it to do what.BR 3. Inspecting the actual data in the standard template, the Degrees-of-freedom data seems to be zero.
So, we expect that the standard template contains nine arrays of (256 * 512) numbers.
Template data storage format; What's with this tif business anyway?
In several areas throughout FreeSurfer, non-obvious choices have been made regarding persisting (saving to disk for later use) various kinds of data, and this is the case for templates.
The FreeSurfer code includes a library that is suitable for handling 2-D images (ie: pictures), which already knows how to work with 2-D arrays of pixels, including keeping track of the type of data at each pixel, rows and columns and so on. In addition, it is able to save and load various image formats. As it happens, the TIFF format is able to do two useful things in this regard: save multiple images, and apply compression.
So, the template's (256 * 512) arrays are handled in memory data structures as though they are picture images, and loaded and saved using TIFF functions.
By way of closure, here is lh.average.curvature.filled.buckner40.tif as seen in an image viewer:
Several points to note:
- Dimensions are 256 x 512, so theta 0..2*pi in 512 steps vertically, and phi 0..pi in 256 steps horizontally.
- The image viewer is set to 32 bits per pixel floating point.
This is image 3, counting from zero, of a total of 9 images. This is the second row in the table above, first statistic, so the variable shown is: BRsurface: smoothwm;BRvariable: convexity (ie: sulc);BRstatistic: mean value across the reference subjects (ie: mean of sulc value at this location across subject).
- Values for this image vary from about -2.8 to +3.3.
Relationship of template to subject pattern
Given that this is the template to which sample subject bert's data is registered, we should be able to see some resemblance between the two. Here is bert's sulc (convexity) pattern:
... snd here is the template sulc pattern, the same data as shown above but now rotated, flipped and colored green-to-red:
You can probably see the resemblance, especially in the "equatorial regions". The resemblance won't be exact, because the bert image shows bert's sulc intensity, whereas the template image shows the aggregation of sulc data from the reference subjects.
The template is distorted relative to the spherical version, in the manner of a "Mercator projection", as described here [http://en.wikipedia.org/wiki/Map_projection Map projection]:
Creating a template
Templates are created using mris_make_template, in a process described here SurfaceRegAndTemplates.
Extracting template data
Supposing one wanted to extract data from a template, for example to inspect the pattern, and perhaps display it in color on a sphere. The extraction is possible using ["mrisp_paint"] which samples the template to a target surface and produces a "curv" format file which can be displayed in tksurfer.