On Thu, Jun 28, 2012 at 4:24 AM, David Berry <[log in to unmask]> wrote:
> Hi Andy,
> I think Tim is right that the behaviour you are seeing
> is what is intended. I suppose there could be a case for an option
> that completely eradicates all memory of the third axis from the NDF,
> but at the moment that's not what happens - instead, as you've seen,
> the original 3D Frame is retained in case it is needed again, and a
> new 2D Frame is added and made current.
>
> However, I think Tim may be wrong about the TRIM=FALSE TRIMWCS=TRUE
> issue. If TRIM is FALSE, then TRIMWCS is not used - in effect a value
> of FALSE is always used for TRIMWCS if TRIM is FALSE. So I think you
> must be loosing the WCS axis somewhere else.
>
Thanks for the explanation.
> Looking at the history from "broken.sdf" I see that at step 12)
> NDFCOPY TRIM=TRUE TRIMWCS=TRUE is used, thus removing the 3rd axis
> (both pixel and wcs). But then at step 14)
>
> setbound gs20120627_6_850_foc1(,,1:1)
>
> is used, thus re-introducing a 3rd pixel axis, but no 3rd wcs axis.
>
Aha. So it's deliberate. The NDF fix sounds like it's all that is needed.
--
Tim Jenness
|