> so I'm surprised that people have not come across this interaction of ATOOLS
> and CONVERT earlier (or not, depending on how popular you believe ATOOLS to
We have come across accidental format conversion, however, I don't
recall it with the ORAC-DR distortion correction
(_DEFINE_DISTORTION_TRANSFORMATION_).
> ORAC-DR could delete the relevant environment variable at startup if that was
> the only way to handle it.
Wouldn't you have to restore the environment upon completion to avoid
annoying users in another way?
>> 2. Change the files the recipes/primtives read/write to have an extension
>> (say .lis or .tmp or .anything) that does NOT try to get automagically
>> converted.
>
> that would also seem to work. The opening lines of
> _DEFINE_DISTORTION_TRANSFORMATION_ do use a .lis suffix.
We can certainly change those file extensions for relevant primitives.
> There is an option #4 which is what we should be using now:
>
> 4. Do all the frameset manipulation natively in the primitive using the
> Starlink::AST perl module.
Do you have some examples? I only found one primitive
(SCUBA2/_GET_PIXEL_SCALE_) that uses Starlink::AST. We need to consult
SUN/211, the C interface to get the correct method names.
> This has the advantage of being less complicated
By less complicated do you mean that avoids the intermediate external
files and just deals with objects?
> and significantly more efficient than the atools version.
Agreed.
Malcolm
|