You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default way that RMsynth_3D should read frequency information is from the FITS header. An externally supplied frequency list should be provided as a non-default option, since it is always preferable to get key metadata from the data object. In particular RMsynth_3D should provide support for the -TAB convention, in which an irregularly gridded axis has an associated FITS extension table giving the frequencies (for instance) corresponding to each channel. See Greisen et al (2006) DOI: 10.1051/0004-6361:20053818.
The text was updated successfully, but these errors were encountered:
The default way that RMsynth_3D should read frequency information is from the FITS header. An externally supplied frequency list should be provided as a non-default option, since it is always preferable to get key metadata from the data object. In particular RMsynth_3D should provide support for the -TAB convention, in which an irregularly gridded axis has an associated FITS extension table giving the frequencies (for instance) corresponding to each channel. See Greisen et al (2006) DOI: 10.1051/0004-6361:20053818.
The text was updated successfully, but these errors were encountered: