MSETUP INPUT

        [MRTCAL\]MSETUP INPUT Keyword Switch

    [MRTCAL\]MSETUP INPUT BAD YES|NO

    Choose if the command READ should read the bad time dumps  (in  addition
    to  the  good  ones) from the backendXXX tables (including the DATA col-
    umn). A bad time dump has a null ISWITCH value, and its associated  data
    (e.g. MJD, INTEGTIM) are not expected to be correct. Default is YES.

    [MRTCAL\]MSETUP INPUT BANDWIDTH Value

    Setup  the  desired reading bandwidth in MHz. The nearest value that al-
    lows the division of the good spectra channels of each chunkset in equal
    virtual chunk sizes will be used. Exceptions are:
      - if value is 0, use the native hardware chunk size (no subdivision),
      - if  value  is larger than the native hardware chunk size, the latter
        is used instead (same as 0),
      - if value is lower than the channel spacing, the latter is  used  in-
        stead (all channels calibrated individually, use with caution).
    Default is native chunk size.

    [MRTCAL\]MSETUP INPUT DATA NONE|ONTRACK|ALL

    Select how Mrtcal should read the DATA column:
      - NONE:  no data is read. Useful to read the other IMB-FITS tables and
        avoiding the DATA column which may be large (save time and/or  memo-
        ry).
      - ONTRACK:  read  only the on-track part of the DATA column, according
        to the subscan start and stop MJDs.
      - ALL: real the whole DATA column, including the off-track parts.
    Default is ONTRACK.

    [MRTCAL\]MSETUP INPUT MJDINTER YES|NO

    Choose if the command READ should intersect the  DATE-OBS  and  DATE-END
    (on-track  range)  of the subscan with the MJD columns in the tables An-
    tenna Slow, Antenna Fast, and Backend Data. It may happen  that  one  of
    these  columns  are  too  short and the data dumps can not be processed.
    Setting YES means that the associated dumps in this missing range  won't
    be considered on-track anymore. Default is NO.

    [MRTCAL\]MSETUP INPUT TOCHUNK YES|NO

    Choose if Mrtcal should map the DATA column into chunksets at read time.
    NO means that you won't be able to do anything but READing the raw  DATA
    into  the  internal  buffers,  and  accessing from the VARIABLEs. YES is
    needed for calibration. This is the default.