!) is given for the UNITS parameter, then the NDF’s UNITS component will be erased.
There is also an option to modify the pixel values within the NDF to reflect the change in units (see Parameter MODIFY).
TRUEvalue is supplied, then the pixel values in the DATA and VARIANCE components of the NDF will be modified to reflect the change in units. For this to be possible, both the original Units value in the NDF and the new Units value must both correspond to the format for units strings described in the FITS WCS standard (see
"Representations of world coordinates in FITS", Greisen & Calabretta, 2002, A&A - available at (http://www.aoc.nrao.edu/egreisen/wcs_AA.ps.gz) If either of the two units strings are not of this form, or if it is not possible to find a transformation between them (for instance, because they represent different quantities), an error is reported.
"count/s"). This value may later be used by other applications for labelling graphs and other forms of display where the NDF’s data values are shown. The suggested default is the current value.
"count/s". The pixel values are not changed.
"J/(m2Angstroms)". The pixel values are not changed.
!), this example erases any previous value of the UNITS component in the NDF structure datafile. The pixel values are not changed.
"MJy". If possible, the pixel values are changed from their old units to the new units. For instance, if the UNITS component of the NDF was original
"J/(m2sGHz)", the DATA values will be multiplied by 1.0E11, and the variance values by 1.0E22. However, if the original UNITS component was (say)
"K"(Kelvin) then an error would be reported since there is no direct conversion from Kelvin to Megajansky.