Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |
xff [2010/07/06 02:11] – typo fix jochen | xff [2011/03/31 21:01] (current) – typos jochen |
---|
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'); |