> > > First - without new features.
> >
> > With no new features, pretty minimal to keep it ticking over. If you
> > want me to put in the new SpecFrame stuff, I don't know. I'm not sure
> > how it's all integrated or how much change would be needed.
>
> I've just had a quick grep through the datacube source files, and it looks
> like all the handling of AST Frames is done within KAPPA. Is this right?
> The only bit of fortran which uses AST seems to be putaxis which shouldn't
> need to know anything about the nature of the frame, and so should not
> need any change.
*nod*
The PUTAXIS task is for when I have to use FIGARO to handle spectral
fitting.
> 1) Getting a suitable SpecFrame into the NDF WCS component (you can use
> kappa:wcsadd for this).
>
> 2) Controlling the attributes of the SpecFrame (e.g. deciding whether
> the spectralaxis should be annotoated in freq, wavelen, etc.). This can be
> done with kappa:wcsattrib, or by using the STYLE parameter for things
> like LINPLOT.
Okay, that doesn't sound too bad.
I've had a fiddle and it looks like a lot of the pre-SpecFrame problems
I had work arounds for might now be easier (at least for SpecFrame'd stuff
like JAC will be generating).
The actual code looks fairly easy to manage at this point, I'd balk at
updating the documentation though. Especially SC/16, I don't really have
a good enough handle on the current state of play to re-write the cookbook.
If I do the software, perhaps JAC would volunteer to update the
documentation!
Al.
|