... | @@ -2,9 +2,9 @@ |
... | @@ -2,9 +2,9 @@ |
|
|
|
|
|
DESCRIPTION:
|
|
DESCRIPTION:
|
|
|
|
|
|
Reads Siemens raw .dat file from VB/VD MRI raw data. The raw data can be obtained by calling e.g. twix.image() or for squeezed data twix.image{''} (the '' are needed due to a limitation of matlab's overloading capabilities). Slicing is supported as well, e.g. twix_obj.image(:,:,1,:) will return only the first line of the full data set (all later dimensions are squeezed into one). Thus, slicing of the "memory-mapped" data objects works exactly the same as regular matlab array slicing - with one exception: The keyword 'end' is not supported.
|
|
Reads Siemens raw .dat file from VB/VD MRI raw data. The raw data can be obtained by calling e.g. `twix.image()` or for squeezed `data twix.image{''}` (the '' are needed due to a limitation of matlab's overloading capabilities). Slicing is supported as well, e.g. `twix_obj.image(:,:,1,:)` will return only the first line of the full data set (all later dimensions are squeezed into one). Thus, slicing of the "memory-mapped" data objects works exactly the same as regular matlab array slicing - with one exception: The keyword 'end' is not supported.
|
|
|
|
|
|
Overloading of the '()' and '{}' operators works by overloading matlab's built-in 'subsref' function. Matlab calls subsref whenever the operators '()', '{}', or '.' are called. In the latter case, the overloaded subsref just calls the built-in subsref function since we don't want to change the behaviour for '.'-calls. However, this has one minor consequence: There's no way (afaik) to know whether the original call was terminated with a semicolon. Thus, a call to e.g. twix.image.NLin will produce no output with or without semicolon termination. 'a = twix.image.NLin' will however produce the expected result.
|
|
Overloading of the '()' and '{}' operators works by overloading matlab's built-in 'subsref' function. Matlab calls subsref whenever the operators '()', '{}', or '.' are called. In the latter case, the overloaded subsref just calls the built-in subsref function since we don't want to change the behaviour for '.'-calls. However, this has one minor consequence: There's no way (afaik) to know whether the original call was terminated with a semicolon. Thus, a call to e.g. twix.image.NLin will produce no output with or without semicolon termination. `a = twix.image.NLin` will however produce the expected result.
|
|
|
|
|
|
Author: Philipp Ehses (philipp.ehses@tuebingen.mpg.de)
|
|
Author: Philipp Ehses (philipp.ehses@tuebingen.mpg.de)
|
|
|
|
|
... | | ... | |