Hi Sarah,
Try using either the DELOBJ Figaro command to delete the AXES values
(assuming this is an NDF file) in a simmilar manner to the erase command
you have tried, or you can try the
HDSTOOLS functions. Open them and use like this:
> HDSTOOLS
> HDELETE myndf.AXES
That should delete the axes extension to the NDF if all else fails.
Cheers,
James
--------------------------------------
Dr. James S. Jenkins
Universidad de Chile
Camino el Observatorio # 1515
Las Condes
Santiago
Chile
Casilla 36-D
Tel: (56-2) 977-1127
Fax: (56-2) 229-3973
--------------------------------------
On Wed, 6 May 2009, James Jenkins wrote:
> Hi Sarah,
>
> Try using either the DELOBJ Figaro command to delete the AXES values
> (assuming this is an NDF file) in a simmilar manner to the erase command you
> have tried, or you can try the HDTOOLS functions. Open them and use like
> this:
>
>> HDSTOOLS
>> HDELETE myndf.AXES
>
> That should delete the axes extension to the NDF if all else fails.
>
> Cheers,
> James
>
> --------------------------------------
> Dr. James S. Jenkins
> Universidad de Chile
> Camino el Observatorio # 1515
> Las Condes
> Santiago
> Chile
> Casilla 36-D
> Tel: (56-2) 977-1127
> Fax: (56-2) 229-3973
> --------------------------------------
>
> On Wed, 6 May 2009, Sarah Casewell wrote:
>
>> Hi,
>> 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.
>> My files were originally fits files, but I don't appear to be able to use
>> iraf to remove any axis parameters either - I just get an error saying I
>> cannot delete them.
>>
>> Does anyone have any ideas?
>> Thanks
>> Sarah
>>
>>
>> --
>> Dr Sarah L Casewell Email: [log in to unmask]
>> Xray and Observational Astronomy Office: S1
>> Department of Physics and Astronomy Phone: +44 (0)116 2523577
>> University of Leicester
>> Leicester
>> LE1 7RH
>> UK
>>
>> On Wed, 6 May 2009, Peter W. Draper wrote:
>>
>>> On Wed, 6 May 2009, Sarah Casewell wrote:
>>>
>>>> I am having some problems using figaro.
>>>> I'm using the latest release of starlink on a SL4 system.
>>>> When I use ystract and enter my start and end parameters (10 and 1000), I
>>>> get errors that read as
>>>>
>>>> !! SUBPAR: 10 is less than the MINIMUM value, 125.647, for parameter
>>>> XSTART.
>>>> ! SUBPAR: Failed constraints check for parameter XSTART
>>>> !! SUBPAR: 1000 is greater than the MAXIMUM value, 125.816, for parameter
>>>> XEND.
>>>> ! SUBPAR: Failed constraints check for parameter XEND
>>>> !! SUBPAR: 10 is greater than the MAXIMUM value, 7.60858, for parameter
>>>> YSTART.
>>>> ! SUBPAR: Failed constraints check for parameter YSTART
>>>> !! SUBPAR: 1000 is greater than the MAXIMUM value, 7.60858, for parameter
>>>> YEND.
>>>> ! SUBPAR: Failed constraints check for parameter YEND
>>>>
>>>> In my sdf file that has a wcs (attatched to it using gaia "fit to star
>>>> positions") the min xstart value is the SFT1_C keyword. I assume this is
>>>> a
>>>> coincindence as the ystart value is close to another crval keyword, but
>>>> not
>>>> the same.
>>>>
>>>> If I run ystract on an image that has no wcs, I also get the same answer
>>>> however.
>>>>
>>>> Does anyone have any idea as to where these values are coming from and
>>>> how I can stop this?
>>>
>>> Hi Sarah,
>>>
>>> since this is figaro these are AXIS coordinate values, so if you want to
>>> set the limits in pixel ranges instead you'll need to remove the AXES
>>> structures from your NDFs:
>>>
>>> % kappa
>>> % erase myndf.AXES ok
>>>
>>> should do it.
>>>
>>> A modern alternative to ystract is the KAPPA application collapse. That
>>> will use the WCS to define the limits, or you can switch to other
>>> coordinate systems:
>>>
>>> % kappa
>>> % wcsframe myndf PIXEL
>>> % collapse myndf outndf 2
>>>
>>> etc.
>>>
>>> Cheers,
>>>
>>> Peter.
>>>
>>
>
|