On Fri, 9 Jan 2004, Tim Jenness wrote:
> Is the AXIS information in an NDF meant to be thought of as a part of the
> WCS information when viewing an NDF as an NDX (in, say, treeview)?
It ought to be, but the NDF handler doesn't currently implement it
properly, so an AXIS component is not correctly incorporated into
the WCS.
> Currently treeview displays the AXIS information as a separate node that
> implies it is not part of the core NDX specification even though the AXIS
> frame is included in the WCS section as an option.
>
> I suppose what I'm really suggesting is that the AXIS information should
> not be shown when the NDX view of an NDF is displayed, only when the NDF
> is treated as an NDF.
I believe this is what already happens:
% treeview -text -ndf mars_3pos.sdf | grep '^....[^ ]'
+ [NDF] mars_3pos.sdf (1+68,1+65)
- [HDS] TITLE <_CHAR*132>"mars"
- [HDS] UNITS <_CHAR*5>"Volts"
+ [ARY] DATA_ARRAY (1+68,1+65) <_REAL>
+ [ARY] VARIANCE (1+68,1+65) <_REAL>
+ [ARY] QUALITY (1+68,1+65) <_UBYTE>
+ [WCS] WCS 3 frames; current domain "AXIS"
- [HIS] HISTORY (8)
+ [HDS] AXIS (2) <AXIS>
+ [HDS] MORE <EXT>
% treeview -text -ndx mars_3pos.sdf | grep '^....[^ ]'
+ [NDX] mars_3pos.sdf (1+68,1+65)
- [SCA] Title <string>"mars"
- [NDA] image (1+68,1+65) <float>
- [NDA] variance (1+68,1+65) <float>
- [NDA] quality (1+68,1+65) <byte>
- [SCA] BadBits <int>0x1
+ [WCS] WCS 2 frames; current domain "PIXEL"
+ [ELE] <etc>
(the greps are just to eliminate nodes deeper than first level in the tree).
The AXIS component turns up as an HDS node in the NDF view, but
is not shown at all in the NDX view.
I agree with all David's comments on this too.
Mark
--
Mark Taylor Starlink Programmer Physics, Bristol University, UK
[log in to unmask] +44-117-928-8776 http://www.star.bris.ac.uk/~mbt/
|