This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
xff [2010/05/29 03:38] jochen created |
xff [2011/03/31 23:01] (current) jochen typos |
||
---|---|---|---|
Line 3: | Line 3: | ||
===== Motivation ===== | ===== Motivation ===== | ||
Neuroimaging data comes in various formats, among of the more prominent ones are | Neuroimaging data comes in various formats, among of the more prominent ones are | ||
- | * Analyze/NIftI (e.g. used in the [[http://www.fil.ion.ucl.ac.uk/spm/|SPM]] series | + | * Analyze/NIftI (e.g. used in the [[http://www.fil.ion.ucl.ac.uk/spm/|SPM]] series) |
* DICOM (a format that several scanners use to store/transport imaging data) | * DICOM (a format that several scanners use to store/transport imaging data) | ||
* PAR/REC (a Philips proprietary, text and binary compound file format) | * PAR/REC (a Philips proprietary, text and binary compound file format) | ||
Line 227: | Line 227: | ||
3 | srf | /Applications/NeuroElf/NeuroElf_v09a/_files/colin/colin_RH_SPH.srf | 3 | srf | /Applications/NeuroElf/NeuroElf_v09a/_files/colin/colin_RH_SPH.srf | ||
-------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- | ||
- | Total MB occupied: 165.793</code> | + | Total MB occupied: 165.793</file> |
To access one of these objects, this ROOT object offers the ''.Documents'' method: | To access one of these objects, this ROOT object offers the ''.Documents'' method: | ||
Line 259: | Line 259: | ||
sliceddata = vtc(:, :, :, 20);</code> | sliceddata = vtc(:, :, :, 20);</code> | ||
- | Matlab automatically refuses this syntax for objects with a default property or in case the variable (vtc) is, in itself, not of size 1x1. | + | Matlab automatically refuses this syntax for objects without a default property or in case the variable (vtc) is, in itself, not of size 1x1. |
=== Storing additional information === | === Storing additional information === | ||
- | In addition to pre-defined fields, it is also possible to store arbitrary information (text, variables, contrast definitions, etc.) with xff objects by creating new fields in the .RunTimeVars field. This data is **not** automatically saved when the object is written to disk, but only so upon calling the **''.SaveRunTimeVars''** method. Then, all fields therein will be saved into a file with the same name but the ".mat" extension. If several xff-accessible files share the same name (e.g. for PRT/SDM/VTC combinations of BrainVoyager projects), each object has its own "sub-space" in the .mat-file, so information will not be overwritten by using the .RunTimeVars concept in more than one of these objects! Here is an example: | + | In addition to pre-defined fields, it is also possible to store arbitrary information (text, variables, contrast definitions, etc.) with xff objects by creating new fields in the .RunTimeVars field. This data is **not** automatically saved when the object is written to disk, but only so upon calling the **''.SaveRunTimeVars''** method. Then, all fields therein will be saved into a file with the same name but the ".rtv" extension (in fact a MAT-file). If several xff-accessible files share the same name (e.g. for PRT/SDM/VTC combinations of BrainVoyager projects), each object has its own "sub-space" in the .rtv-file, so information will not be overwritten by using the .RunTimeVars concept in more than one of these objects! Here is an example: |
<code matlab>vmr = BVQXfile('subject_01.vmr'); | <code matlab>vmr = BVQXfile('subject_01.vmr'); |