Proposals:VectorImage: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
No edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
ITK: Vector Image | ITK: Vector Image | ||
Create a templated n-dimensional vector image class. | |||
This class differs from Image in that it is intended to represent multiple images. Each pixel represents \e k measurements, each of datatype \e TPixel. The memory organization of the resulting image is as follows: | |||
... Pi0 Pi1 Pi2 Pi3 P(i+1)0 P(i+1)1 P(i+1)2 P(i+1)3 P(i+2)0 ... | |||
where Pi0 represents the 0th measurement of the pixel at index i. | |||
Conceptually, a <tt>VectorImage< double, 3 ></tt> is the same as a <tt>Image< Array< double >, 3 ></tt>. The difference lies in the memory organization. The latter results in a fragmented organization with each location in the Image holding a pointer to an \c Array holding the actual pixel. The former stores the \e k pixels instead of a pointer reference. The parameter \e k can be set at run time. | |||
Revision as of 14:21, 1 August 2005
ITK: Vector Image
Create a templated n-dimensional vector image class.
This class differs from Image in that it is intended to represent multiple images. Each pixel represents \e k measurements, each of datatype \e TPixel. The memory organization of the resulting image is as follows:
... Pi0 Pi1 Pi2 Pi3 P(i+1)0 P(i+1)1 P(i+1)2 P(i+1)3 P(i+2)0 ...
where Pi0 represents the 0th measurement of the pixel at index i.
Conceptually, a VectorImage< double, 3 > is the same as a Image< Array< double >, 3 >. The difference lies in the memory organization. The latter results in a fragmented organization with each location in the Image holding a pointer to an \c Array holding the actual pixel. The former stores the \e k pixels instead of a pointer reference. The parameter \e k can be set at run time.
