[Kst] more healpix/matrix discussion

[Rick Chern]

On Mon, 2005-06-13 at 18:12 -0700, Theodore Kisner wrote:
> 
> 2.  Currently, KstRVector is the only object that calls readField for a 
> datasource.  KstMatrix is a "high level" object, in the sense that it 
> inherits from KstDataObject, and hence contains vectors/scalars as members.  
> So KstMatrix is NOT a direct analogue to KstVector.
> 
> Do we want KstMatrix to contain a bare flat-packed matrix of doubles similar 
> to KstVector::_v ?  Do we want KstMatrix to be able to read directly from a 
> datasource with readFieldMatrix (e.g. using a new constructor that contains 
> the field to read)? 
> 
> My naive thoughts are that it would make more sense if KstMatrix inherited 
> from KstObject and was exactly analogous to KstVector.  There would also be a 
> KstRMatrix (that calls readFieldMatrix), and then KstDataObject would 
> contain:
> 
> KstMatrixMap _inputMatrices;
> KstMatrixMap _outputMatrices;
> 
> Then KstImage would be just like KstBaseCurve, in that it uses the members of 
> the underlying KstDataObject, rather than needing an extra "KstMatrixPtr 
> _matrix;" member.
> 

I think this makes sense too in that some data objects (like CSDs) might
want to output slave matrices, so it would be useful to be able to
create matrices that do not use vectors, and have KstMatrixMap
_outputMatrices.