| Getting Started | Documentation | Glish | Learn More | Programming | Contact Us |
| Version 1.9 Build 803 |
|
Presently, there is capability to
im := imagefromfits('x.app', 'X.FITS') # Convert from FITS
im.view() # Display
#
im2 := imagefromfits(infile='X.FITS') # Output Image tool is virtual
im2.view()
In the second example, we didn't write the AIPS++ image out - it's stored in memory. This is called a virtual image (see below).
im := image('X.FITS') # Native FITS access
im.view() # Display
This example shows how the image constructor can also be used to gain native access to the FITS file. No format conversions occur and the data are sourced directly from the FITS file. Performance will be good unless you start to try to access the data in non-native order. For example, if with the Viewer, you reordered the display axes from their native order, performance would be poorer. Always convert to an AIPS++ image if you need to do this.
im := image('hcn.mir') # Native Miriad access
im.view() # Display
The same comments above about native FITS file performance apply here as well.
im := imagefromforeign('hcn.app', 'hcn', package='gipsy')
im.view() # Display
This constructor relies on the nominated package being installed. It is used to write out a temporary FITS file which is then converted to AIPS++ format.