> This is a known deficiency in the java NDF handling - it doesn't
> handle NDF AXIS components, which is how BBODY stores its coordinate
> information. It can only cope with WCS components.
I had a session with Steve earlier concluded that you needed a WCS
component for Treeview and SPLAT. LINPLOT and SPLOT, being vintage
code, generate the desired axes.
There are lots of old data out there that pre-date the WCS, and made
heavy use of the AXIS structure, so I think we should support it in
Treeview and SPLAT.
> You can get round this by getting KAPPA to generate a WCS component from
> the AXIS one. If your NDF is called blackbod.sdf, then
>
> wcsadd blackbod axis wavelength unit
>
> should do the trick.
Yes I tried WCSFRAME, NDF2FITS/FITS2NDF, and WCSADD to attempt to copy
the axis to WCS. The last two worked.
> Your next question will probably be: "why does SPLAT/Treeview display
> 'Angstrom' rather than 'log10(10**-3*micron)' for the units?".
It was.
> I don't know - I *think* this is probably something Peter or David
The NDF2FITS then FITS2NDF approach also propagates the units string
successfully, SPLAT still ignores it and uses Angstrom. BTW,
NDFTRACE only gives the first fifteen characters of the Units.
Malcolm
|