next up previous contents index
Next: SET SPECTRUM Up: SET Previous: SET SCAN

SET SELECTION

 

        CLIC\SET SELECTION mode band subband-range  [FREQ  freqout]  /WINDOW
    fmin fmax [fmin2 fmax2 ...]

    Choose the type of data selection to be done  by  command  TABLE,  which
    creates a UV data Table for mapping software.

    - The first argument 'mode' may be CONTINUUM or LINE, to prepare  single
    channel or multiple channel maps.

    - The second argument is the sideband to be used,  UPPER  or  LOWER,  or
    DSB.   DSB  may be used in conjunction with CONTINUUM: in this case, two
    separate visibility points are written, one for each sideband. DSB  used
    in  conjunction  with  LINE means that the side band will be selected to
    match the desired frequency range (as given in the command TABLE),  thus
    allowing  to  mix  in the same table data from USB and LSB, if different
    frequency setups have been used in different configurations.

    - The third argument is a subband range as for SET SUBBANDS command.  In
    Continuum mode subbands are averaged, in spectral mode they are combined
    to produce a single spectrum.  The default is : SET SELECTION CONTINUUM,
    DSB, L01 L02 L03 L04 L05

    Arguments "FREQ freqout" are  used  only  for  CONTINUUM  tables.   They
    define  the  frequency (in MHz) used for mapping purposes.  U and V (for
    each side band in DSB mode) will be scaled to this frequency.   This  is
    intended  to  combine  maps  obtained in continuum at slightly different
    frequencies.  The default for  freqout  will  be  the  actual  observing
    frequency,  or  the frequency used for previous data if data is appended
    to a previously existing table by the TABLE command.

    Option /WINDOW  is  used  to  avoid  spectral  lines  when  producing  a
    continuum  table  from  spectral  correlator  data.  The  first two rest
    frequencies (in MHz) give the first frequency window in which data is to
    be used, the next two give the second frequency window, ... etc.


lucas@iram.fr