On Wed, 6 May 2009, Sarah Casewell wrote:
> Thanks for the advice Peter, Unfortunately I am still having no joy with
> the data. I have used erase test.axis ok but although kappa gives no
> errors, nothing seems to happen. If I look at the header in gaia, the
> naxis etc keywords are still there.
>> % kappa
>> % erase myndf.AXES ok
Sorry that should be:
% erase myndf.AXIS ok
Have a look in your NDF:
% hdstrace myndf
MYNDF <NDF>
DATA_ARRAY <ARRAY> {structure}
ORIGIN(2) <_INTEGER> 1,1
DATA(353,353) <_REAL> 3580,3580,3754,3754,3754,3754,3667,
... 3634,3634,3634,3634,3720,3720,3720
BAD_PIXEL <_LOGICAL> FALSE
MORE <EXT> {structure}
FITS(121) <_CHAR*80> 'SIMPLE = T /FIT...'
... 'PC002002= 9.9940228527557...','END'
TITLE <_CHAR*7> 'ngc1275'
AXIS(2) <AXIS> {array of structures}
Contents of AXIS(1)
DATA_ARRAY <ARRAY> {structure}
ORIGIN(1) <_INTEGER> 1
DATA(353) <_DOUBLE> -2.8931497883572,-2.8931497883572,
... -2.8931497883572,-2.8931497883572
LABEL <_CHAR*100> 'Right ascension'
UNITS <_CHAR*100> 'hh:mm:ss.s'
WCS <WCS> {structure}
DATA(175) <_CHAR*32> ' Begin FrameSet',' Nframe = 4',' Cu...'
... ' E...',' End CmpMap',' End
FrameSet'
End of Trace.
It's that "AXIS(2)" structure that erase should delete.
I may be confused about what you are doing. If you're passing FITS data
directly to ystract (using on-the-fly conversion) then none of this will
work as the AXIS structure will be re-created from the WCS each time. The
only way to avoid that is to run fits2ndf, erase and then ystract. Of
course you could just use the axis coordinate values instead of pixel
positions to define the range.
Peter.
|