> After being reminded of the dimensions, I figured that my ndfcopy
> command should also include the first two axes, like so:
>
> ndfcopy in='330-360_fullres_central_toedit(0,0,-200.0:200.0)'
> out=SLS_fullres_central_342882_9_MHz_window.sdf
Correct. I had suspected that might be the case.
> Which works!
In case you had a 1x1xN array, that would need the commas in the NDF
section to specify +/-200.0 limits to the third axis, I had tried the
NDFCOPY as you did applied to a 1x1xN spectrum from HARP to see how the
NDF slicing would behave. There was no problem. LINPLOT also displayed
some data. Hence I thought we'd better find out more about the WCS in
your NDF. Later I tried "(-200.0,200.0) section on some other HARP data
and saw the AST_MAPREGION error you found. At least asking for the
NDFTRACE output lead you to the solution.
Malcolm
--
Scanned by iCritical.
----
Starlink User Support list
For list configuration, including subscribing to and unsubscribing from the list, see
https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=STARLINK
|