<casaxml xsi:schemaLocation="http://casa.nrao.edu/schema/casa.xsd file:///opt/casa/code/xmlcasa/xml/casa.xsd" xmlns="http://casa.nrao.edu/schema/psetTypes.html" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<task type="function" name="importuvfits" category="import/export">
<shortdescription>Convert a UVFITS file to a CASA visibility data set</shortdescription>
<description>Convert a UVITS file to a CASA visiblity data set.
Don\'t forget to flag autocorrelations using taskname flagdata, autocorr = true
<param type="path" mustexist="true" name="fitsfile"><shortdescription>Name of input UV FITS file</shortdescription><description>Name of input UV FITS file</description>
<param type="string" name="vis"><shortdescription>Name of output visibility file (MS)</shortdescription><description>Name of output visibility file (MS)</description>
<param type="string" name="antnamescheme"><shortdescription>VLA/EVLA/CARMA only; \'new\' or \'old\'; \'VA04\' or \'04\' for VLA ant 4</shortdescription><description>VLA/EVLA/CARMA only; \'new\' or \'old\'; \'VA04\' or \'04\' for VLA ant 4</description>
Convert a UVFITS file to a CASA visibility data set:
fitsfile -- Name of input UV FITS file
default = none; example='3C273XC1.fits'
vis -- Name of output visibility file (MS)
default = none; example: vis='3C273XC1.ms'
antnamescheme -- Naming scheme for VLA/JVLA/CARMA antennas
old: Antenna name is a number, '04'
This option exists for backwards compatibility
but can lead to ambiguous results when antenna
indices are used for data selection.
new: Antenna name is not a number, e.g., 'VA04' or 'EA04'
With this scheme, data selection via
antenna names and indices is non-ambiguous.
Note: Don't forget to flag autocorrections using
taskname flagdata, autocorr = true
<returns>void</returns></task>