Facilities > VLA > Documentation > Manuals > Guide to Observing with the VLA > Commonly Used Observing Modes

Commonly Used Observing Modes

« Return to page index

1. Spectral Line

The wide bandwidths of the VLA allow users to observe up to 8GHz of bandwidth at a time. All observations with the upgraded VLA are inherently spectral observations, including those intended for continuum science. The VLA's improved sensitivity and wide bandwidths greatly enhance the VLA's functionality for spectral line purposes, enabling simultaneous imaging of multiple spectral lines. The WIDAR correlator is extremely flexible and can act as up to 64 independent correlators with different bandwidths, channel numbers, polarization products, and observing frequencies. The VLA is able to:

  • deliver continuous spectral coverage of up to 8GHz;
  • access 1GHz or 2GHz chunks in each receiver band (called basebands) and place multiple correlator subbands within them;
  • place up to 32, independently tunable subbands within a baseband, up to 64 in total. Each subband can be configured with its own subband bandwidth, number of frequency channels, and polarization products;
  • fine-tune each baseband frequency independently according to an object's line-of-sight velocity with respect to the earth (Doppler Setting); each subband frequency can be set to apply this shift or not.

The detailed capabilities offered for each semester are described in the VLA Observational Status Summary (OSS).


Line Frequencies and Velocity Conventions

Spectral line catalogs available online are useful for selecting targeted line rest frequencies. The recommended catalog for VLA and ALMA observing is Splatalogue which contains molecular line data from sources including the Lovas catalog, the JPL/NASA molecular database, the Cologne Database for Molecular Spectroscopy, as well as radio recombination lines.

Observing Frequency and Velocity Definitions

The sky frequency (ν) at which we must observe a spectral line is derived from the rest frequency of the spectral line (ν0), the line-of-sight velocity of the source (V), and the speed of light (c). The relativistic velocity, or true line-of-sight velocity, is related to the observed and rest frequencies by

[display]V = \frac{\nu^2_0-\nu^2}{\nu^2_0+\nu^2}c[/display]

This equation is a bit cumbersome to use; in astronomy two different approximations are typically used:

  • Optical Velocity [display]V^{optical} = \frac{\lambda-\lambda_0}{\lambda_0}\,\,c = cz [/display] (z is the redshift of the source)
  • Radio Velocity [display]V^{radio} = \frac{\nu_0-\nu}{\nu_0}\,\,c = \frac{\lambda-\lambda_0}{\lambda}\,\,c \neq V^{optical} [/display]

The radio and optical velocities are not identical. Particularly,V optical and V radio diverge for large velocities. Optical velocities are commonly used for (Helio/Barycentric) extragalactic observations; (LSR) radio velocities are typical for Galactic observations.

At high redshifts, it is advisable to place the zero point of the velocity frame into the source via[display]\nu=\frac{\nu_0}{z+1}[/display]

where the redshifted ν can now be used as the input frequency for the observations. This method will appropriately apply the redshift correction to the channel and line widths and the resulting velocities are also intrinsic to the source.

Note that the VLA's natural spectral axis is in frequency. The radio convention will simply be a velocity relabeling to the frequency axis. The optical velocity and redshift, however, will introduce a non-linearity between channel widths and labeling, in particular for large velocity values.

Velocity Reference Frames

The Earth rotates, revolves around the Sun, rotates around the Galaxy, moves within the Local Group, and shows motion against the Cosmic Microwave Background. As for the convention above, any source velocity must therefore also always be specified relative to a reference frame.

Various velocity rest frames are used in the literature. The following table lists their name, the motion that is corrected for, and the maximum amplitude of the velocity correction. Each rest frame correction is incremental to the preceding row:

Table 7.1.1: Velocity Rest Frame Designations
Rest Frame NameRest FrameCorrect forMax. Amplitude (km/s)
Topocentric Telescope Nothing 0
Geocentric Earth Center Earth rotation 0.5
Earth-Moon Barycentric Earth+Moon center of mass Motion around Earth+Moon center of mass 0.013
Heliocentric Center of the Sun Earth orbital motion 30
Barycentric Earth+Sun center of mass Earth+Sun center of mass 0.012
Local Standard of Rest (LSR) Center of Mass of local stars Solar motion relative to nearby stars 20
Galactocentric Center of Milky Way Milky Way Rotation 230
Local Group Barycentric Local Group center of mass Milky Way Motion 100
Virgocentric Center of the Local Virgo supercluster Local Group motion 300
Cosmic Microwave Background CMB Local Supercluster Motion 600

The velocity frame should be chosen based on the science. For most observations, however, one of the following three reference frames is commonly used:

  • Topocentric is the reference frame of the observatory (defining the sky frequency of the observations). Visibilities in a measurement set are typically stored in this frame.
  • Local Standard of Rest is the native output of images in CASA. Note that there are two varieties of LSR: the kinematic LSR (LSRK) and the dynamic (LSRD) definitions for the kinematic and dynamic centers, respectively. In almost all cases LSRK is being used and the less precise name LSR is usually used synonymously with more modern LSRK definition. LSR in the PST and in the OPT means LSRK.
  • Barycentric is a commonly used frame that has virtually replaced the older Heliocentric standard. Given the small difference between the Barycentric and Heliocentric frames, they are frequently used interchangeably.

Doppler Correction

A telescope naturally operates at a fixed sky frequency (Topocentric velocity frame) which can be adjusted to account for the motion of the Earth. The observed frequency of a spectral line will shift during an observing campaign. Within a day, the rotation of the Earth dominates and the line may shift up to ±0.5km/s, depending on the position of the source on the sky (see the table on Velocity Rest Frames above). Observing campaigns that span a year may have spectral lines that shift by up to ±30km/s due to the Earth's motion around the Sun.

As a rule of thumb, 1 MHz in frequency corresponds roughly to x km/s for the line at a wavelength of x in mm. For example, 1 MHz corresponds to about 7 km/s in velocity at a wavelength of 7 mm, and to roughly 210 km/s at the 21 cm line. Using this rule of thumb, a line may shift by up to ±5 MHz in Q-band and by up to ±0.15 MHz in L-band over the course of a year. This shifting needs to be taken into account when setting up the dynamically scheduled observations. Accounting for the frequency shifting can be handled in different ways:

  • use the same fixed sky frequency for all observations, accommodating the line shift (maximum of ±30 km/s) by using a wide enough bandwidth to cover the line at any time in the observing campaign. The data is later regridded in post processing to a common LSRK or BARY velocity frame. The actual sky frequency of a specific spectral line rest frequency can be computed with the Dopset tool for any given time. One may find the LST dates for an observation on the VLA Observing Schedules page.
  • calculate the sky frequency at the beginning of an observing block and keep this fixed for the duration of the scheduling block. This is called Doppler Setting (in contrast to Doppler tracking below). The upgraded VLA supports Doppler setting. Doppler Setting can be specified for each individual baseband in the OPT, removing the burden to do this for each possible observing run by the observer. The line shift during the observation is then reduced to the rotation of the earth (maximum amplitude ±0.5 km/s). This small shift may optionally be corrected in data processing, i.e., if the length of the observing run justifies this correction. Although the absolute sky frequency will be different between observing runs separated in time, Doppler Setting will place the spectral line in the same channel number of each repeated observation.
  • change the sky frequency continuously to keep the line at the same position in the band. This method is called Doppler tracking and was standard for the VLA before the WIDAR correlator was in place. The upgraded VLA does NOT support Doppler tracking. The WIDAR correlator offers enough bandwidth and spectral channels to cover any line shift and post processing regridding needs. Additionally, a non-variable sky frequency may also yield a more robust calibration and overall system stability.

The regridding of the spectrum can be completed during data processing in CASA, either directly during imaging in the task clean or, alternatively, with the task cvel. In AIPS, the task CVEL typically is run after bandpass calibration. Assuming one knows the spectral line width in advance, the regridding works well when the spectral features are sampled with at least 4 channels.


The WIDAR Correlator

The WIDAR correlator is inherently a spectral line correlator in any regular mode. A full description of the current WIDAR capabilities is provided in the WIDAR section of the OSS. The OSS also contains a spectral line configurations section.

There are two important issues when configuring the WIDAR correlator for spectral line observations. One is to set the necessary spectral resolution. This can be achieved by baseline board stacking and/or recirculation. Both are described in the OSS. For observing large instantaneous bandwidths with high spectral resolution, it is recommended to use as wide as bandwidth as possible (i.e., 128, 64 or 32 MHz) and use stacking, possibly in combination with recirculation over the alternative of using many narrow subbands stacked next to each other. This avoids the stitching process described below and provides a much better spectral baseline.

A second issue is the existence of the 128 MHz boundaries. Lines should not be placed across or very near these boundaries since subbands cannot span across a boundary and the sensitivity drops near the boundaries. In particular note that the very center of the baseband always falls on a 128 MHz boundary. The spectral line under consideration should never be placed in the very center of a baseband. Multi-line observations also need to ensure that none of the lines fall on or near a boundary. This can be challenging at times but is usually a solvable problem and the OPT provides some tools to do so. If it is not possible to obtain simultaneous coverage of all of your lines, or if the exact position of the line is unknown (e.g., for line searches), it is possible to observe with two basebands shifted by 10–64 MHz apart. This will ensure that one baseband covers the boundaries of the other baseband with full sensitivity. An example is given in the figures (7.1.1 and 7.1.2) below, where the top figure shows the RMS of a single baseband with the 128 MHz boundaries sticking out as having high noise. The bottom figure shows a combination of two basebands that have been separated by 64MHz. The noise spikes are clearly suppressed by adding, with the appropriate weight, the two basebands, or even by simply replacing the noisy channels of each baseband with data from the other.


Subband 0

The baseband response is suppressed at each side of the spectrum. The largest affected baseband edge is at the highest sky frequency in the baseband when using lower sideband in X and Ku-bands, and at the lowest sky frequency in the baseband when using upper sideband in observing bands other than X and Ku-bands. For upper sideband, this causes reduced sensitivity typically in the lower 20% frequency edge of the first 128 MHz subband and about 5% in the higher frequency edge of the last 128 MHz subband (the reverse is happening for X and Ku-bands). It is typically noticed in subband 0 of a baseband, but other subband numbers are possible as well. This part of the spectrum, the lower ~30 MHz and upper ~8 MHz of each baseband in 4, P, L, S, C, K, Ka, and Q-bands or the lower ~8 MHz and upper ~30 MHz of each baseband in X and Ku-bands, should be avoided for spectral line observing if possible. This effect can readily be seen in the figures 7.1.1 and 7.1.2 above, where the RMS in the subband below 4.6 GHz is significantly increased. See EVLA memo 154 for details.

Data Rate Limits

A high number of subbands, baseline board stacking, recirculation, and time resolution can add up to an extremely high data rate in the correlator. Please see the OSS for the allowable data rates and volumes for each observing semester. The OPT instrument configuration calculates data rates based on the spectral line setup and the sum of data rates and total volume must not exceed the maximum allowed for any observational setup.


Preparing Spectral Line Observations

The Observation Preparation Tool (OPT) is the web-based interface to create scheduling blocks (SBs) for time awarded on the VLA. An SB is the observing schedule used for a single observing run. This consists of at least a start-up scan sequence (see the 8/3-Bit Attenuation and Setup Scans guidelines), a bandpass calibrator, a flux density calibrator, a complex gain calibrator, and target observations. High frequency observations should also include at least two (often more) X band interferometric pointing scans and a corresponding setup scan, whereas 3-bit and multi-frequency band observations add even more required scans to the SB. In the OPT, the observer specifies the sources, scan lengths and order, and correlator setups. A full project may consist of several SBs. To access the OPT, go to my.nrao.edu and click on the Obs Prep tab, followed by Login to the Observation Preparation Tool. Instructions for using the OPT and for selecting appropriate calibrators are provided in the OPT Manual.

Bandpass Setup

All observations with the VLA—even those with the goal of observing continuum—require bandpass calibration. When scheduling the bandpass calibration scans within an SB, the observer should be careful to minimize the number of shadowed antennas, as an antenna without a bandpass determined for it will essentially be flagged in the data for the rest of the observation. A bandpass calibrator should be bright enough, or observed long enough, so that the bandpass calibration does not significantly contribute to the noise in the image. For a given channel width a bandpass calibrator with flux density Scal observed for a time tcal and a science target with flux density Sobj observed for a time tobj,  S_{cal} \sqrt{t_{cal}} should be greater than S_{obj} \sqrt{t_{obj}}. How many times greater will be determined by one's science goals and the practicalities of the observations, but  S_{cal} \sqrt{t_{cal}} should be greater by at least a factor of two. For extremely narrow channels or very weak bandpass calibrators, those typical flux requirements can lead to extremely large integration times. As an alternative one may then choose to reduce the integration time and interpolate in frequency, or to fit a polynomial across all channels in post-processing (bandtype=BPOLY in CASA's bandpass task).

The bandpass calibrator should be a point source or have a well-known model. At low frequencies, the absolute flux density calibrators (3C48, 3C147, or 3C286) are quite strong and can often double as bandpass calibrators. At high frequencies (Ku, K, Ka, and Q-bands), however, these sources have only moderate flux densities of ~0.5–3 Jy, translating into a potentially noisy bandpass solution. A different, stronger bandpass calibrator should then be observed. Naturally, all of the above depends on the channel widths, and for wide channels the standard flux calibrators may be sufficient even at higher frequencies. In turn, extremely narrow channels may require stronger bandpass calibrators at the low frequency end. Additionally, we have shown that one can transfer the bandpass from a wide subband onto a narrow subband if the wide bandpass frequency range covers the narrow one. This may be good to a level of a few percent, but we advise to use that option only when absolutely necessary.

The stability of bandpasses as a function of time is of concern for high-dynamic-range spectral work as well as for weak broad lines. We have found that most antennas show bandpasses that are stable to a few (~2–4) parts in a thousand over a period of several (~4–8) hours. This should be sufficient for most scientific goals but the bandpasses can be observed several times during an observation for extreme calibration accuracy requirements.

A complication can occur when the frequency range of the bandpass is contaminated by other spectral features, such as RFI lines or Galactic HI in absorption or emission. There are two basic options to accommodate that situation:

  • if the feature is narrow, one can simply observe as usual. In post processing, the narrow feature can be flagged and the frequency gap interpolated by values of nearby channels or by fitting a polynomial across the bandpass.
  • for wider contaminating lines, an option is to observe the bandpass at slightly offset frequencies and transfer the bandpass to the target frequency. If a common solution is obtained from two, symmetric offsets, at higher and lower frequencies, the solution can be improved. Depending on the choice of offsets, and also on the position in the receiver frequency range, the error can vary. For 4 MHz offsets close to the HI rest frequency of 1.42 GHz, the error is in the percent range.


Complex Gain Calibration

The complex gain (phase and amplitude gain) calibration is the same for a spectral line observation as for any other observation. Ideally, one should use the same correlator setup for the complex gain calibrator and the science target. For weak calibrators, however, it is possible to use wider bandwidths for the phase calibrator and then transfer the phases to the source. However, there will be a phase offset between them. The phase offset between the narrow and wide subbands can be determined by observing a strong source (e.g. the bandpass calibrator) and applied in post processing from the complex gain calibrator to the target sources. A similar method can be used if the complex gain calibrator is observed at a slightly different frequency, e.g. to avoid a contaminating line feature such as Galactic HI.

2. Polarimetry

Quick Start Guide

There are two components for polarization calibration:

  • Determining the leakage terms (i.e., the polarization impurity between the R and L polarizations).
  • Calibrating the absolute polarization angle.

There are two common approaches to determine the leakage terms:

  • either observe one or more strong calibrators (> 1 Jy) over a wide range (e.g., > 60 degrees) in parallactic angle and through multiple scans,
  • or observe a strong unpolarized (typically less than 1% polarized) calibrator source through at least one scan; see below for more information on determining leakage terms.

To calibrate the absolute polarization angle, observe a calibrator with a well-known polarization angle.

In the following we present detailed information on polarization calibration, including the most common calibrators for this purpose.


For projects requiring imaging in Stokes Q and U, the instrumental polarization can be determined through observations of a bright calibrator source spread over a range in parallactic angle. The phase calibrator chosen for the observations can also double as a polarization calibrator provided it is at a declination where it moves through enough parallactic angle during the observation (roughly Dec 15° to 50° for a few hour track). The minimum condition that will enable accurate polarization calibration from a polarized source (in particular with unknown polarization) is three observations of a bright source spanning at least 60 degrees in parallactic angle (if possible schedule four scans in case one is lost). If a bright unpolarized unresolved source is available (i.e., known to have very low polarization) then a single scan will suffice to determine the leakage terms. The accuracy of polarization calibration is generally better than 0.5% for objects small compared to the antenna beam size. At least one observation of 3C286 or 3C138 is required to fix the absolute position angle of polarized emission. 3C48 also can be used to fix the position angle at wavelengths of 6 cm or shorter. The results of a careful monitoring program of these and other polarization calibrators can be found at http://www.aoc.nrao.edu/~smyers/evlapolcal/polcal_master.html

High sensitivity linear polarization imaging may be limited by time dependent instrumental polarization, which can add low levels of spurious polarization near features seen in total intensity and can scatter flux throughout the polarization image, potentially limiting the dynamic range. Preliminary investigation of the VLA’s new polarizers indicates that these are extremely stable over the duration of any single observation, strongly suggesting that high quality polarimetry over the full bandwidth will be possible.

The accuracy of wide field linear polarization imaging will be limited, likely at the level of a few percent at the antenna half-power width, by angular variations in the antenna polarization response. Algorithms to enable removing this angle-dependent polarization are being tested and observations to determine the antenna polarizations have begun. Circular polarization measurements will be limited by the beam squint, due to the offset secondary focus feeds, which separates the RCP and LCP beams by a few percent of the FWHM. The same algorithms noted above to correct for antenna-induced linear polarization can be applied to correct for the circular beam squint. Measurement of the beam squints, and testing of the algorithms, is ongoing.

Ionospheric Faraday rotation of the astronomical signal is always notable at 20 cm. The typical daily maximum rotation measure under quiet solar conditions is 1 or 2 radians/m2, so the ionospherically-induced rotation of the plane of polarization at these bands is not excessive – 5 degrees at 20 cm. However, under active conditions, this rotation can be many times larger, sufficiently large that polarimetry is impossible at 20 cm with corrrection for this effect. The AIPS program TECOR has been shown to be quite effective in removing large-scale ionospherically induced Faraday Rotation. It uses currently-available data in IONEX format. Please consult the TECOR help file for detailed information. In the future CASA will provide a similar capability. With CASA release 4.7 it is possible to correct Faraday rotation effects using the task gencal with caltype='tecim'. The addition of dispersive delay corrections are under development and will be available in future releases of CASA.


Observing Recommendations

There are several strategies for deriving the Q/U angle calibration:

  • Observation of a primary polarization standard (Category A)
  • Observation of a secondary polarization calibrator (Category B with Note 3) with auxilary monitoring observations to transfer from primary.

This calibration is needed to set the polarization vector angle 0.5*arctan(U/Q) and should be done in all cases.

There are several strategies for deriving the instrumental polarization:

  • Single scan observation of a zero polarization source (Category C)
  • Several scans (minimum of 3 scans over 60 degrees of parallactic angle) of an unknown polarization source. These can be, but are not limited to sources listed in Category B.
  • Two scans of a source of known polarization (Category A or B with transfer)

See Tables 7.4.1-7.4.4 below for Category A-D source catalogs.


Polarization Calibrator Catalog and Selection

The following sources are known to be useable for polarization calibration. These consist of a few "pol standard" sources with known stable polarization (for Q/U angle calibration), plus a number of "bright" sources with "monitored" variable flux densities and polarization. Some of these are seen to have only "moderate variability" and could be used as secondary angle calibrators if you can transfer the angle from the monitoring observations. Assume others (particularly "flat spectrum") are highly variable. There are also a few "bright, low pol" sources available as leakage calibrators (but they can have measurable polarization at high frequencies).

NOTE: Be sure to use the VLA OPT Source catalog to obtain the standard J2000 positions and approximate flux densities.

Calibration Selection Procedure:

  • Select Polarization Standard (to calibrate polarization angle Q/U) - optimally select one Category A source and observe at least one scan. The percentage polarization and angle for the known stable calibrators as a function of frequency is tabulated in Table 7.5.1 below. Alternative: use a "moderately variable" Category B calibrator and use monitoring information (would need to request monitoring observations, and may have to submit your own SB for this) to transfer from a primary.
  • Select Leakage Calibrator (to determine instrumental polarization) - optimally select one Category C low-polarization source or Category B secondary source in optimal Dec range (see the notes of Tables 7.4.2 and 7.4.3) for PA coverage during run (if long enough). Single scans ok for Category C. Alternative: try a Category D CSO if no other options available.


Table 7.4.1: Category A - primary polarization standards
SourceOther nameCommentsNotes
J0137+3309 B0134+329 (3C48) pol standard (>4GHz) A1,A2
J0521+1638 B0518+165 (3C138) pol standard A1
J1331+3030 B1328+307 (3C286) pol standard A1,A3

Table 7.2.1 Notes:

  • A1. Polarized fraction and angle values for these sources is given in Table 7.5.1 below.
  • A2. 3C48 is weak at high frequency and somewhat resolved in larger configurations. Depolarized below 4GHz.
  • A3. 3C286 is our foremost primary calibrator and should be used if available.


Table 7.4.2: Category B - secondary polarization calibrators
SourceOther nameCommentsNotes
J0359+5057 B0355+508 (NRAO150) bright, flat spectrum, monitored upon request, moderate variability B1
J0555+3948 B0552+398 bright, flat spectrum, monitored upon request, moderate variability B1,B2
J0854+2006 B0851+202 bright, flat spectrum, monitored upon request, moderate variability B1
J0927+3902 B0923+392 bright, flat spectrum, monitored upon request, moderate variability B1,B2
J1310+3220 B1308+326 monitored upon request
J2136+0041 B2134+004 bright, flat spectrum, monitored upon request, moderate variability
J2202+4216 B2200+420 (BLLac) bright, flat spectrum, monitored upon request, moderate variability B1
J2253+1608 B2251+158 (3C454.3) bright, flat spectrum, monitored upon request B3

Table 7.2.2 Notes:

  • B1. In optimal Declination range to be used as leakage calibrator with PA coverage. Recommended as calibrators and if necessary can be used as secondary standards with monitoring.
  • B2. Low polarization at low frequencies (L, sometimes S,C), do not use as angle calibrator.
  • B3. Highly variable and interesting in its own right.


Table 7.4.3: Category C - primary low polarization leakage calibrators
SourceOther nameCommentsNotes
J0319+4130 B0316+413 (3C84) low pol, bright, flat spectrum, monitored upon request C1
J0542+4951 B0538+498 (3C147) low pol <10GHz, steep spectrum, resolved C2
J0713+4349 B0710+439 low pol, CSO, monitored upon request C3
J1407+2827 B1404+286 (OQ208) low pol, steep spectrum C4
J2355+4950 B2352+495 low pol, CSO, monitored upon request C3

Table 7.2.3 Notes:

  • C1. Very bright and low polarization (<1%), but variable flux density. Approaches 1% polarized at 43GHz.
  • C2. Steep spectrum and resolved, low polarization below 10GHz (best <4.5GHz). Stable polarization above. See Table 7.5.1 below.
  • C3. Weak at high frequency, but stable flux and very low polarization.
  • C4. Weak at high frequency, bright and low polarization below 9GHz.


The following northern sources are known to be CSO (Compact Symmetric Objects) and are characteristically unpolarized. They can be used over a range of frequencies (Gugliucci, N.E. et al. 2007, ApJ 661, 78) as "low pol" leakage calibrators. CSOs tend to be on the weak side and should be used with care at higher frequencies. We have not used these with the VLA and thus rate them as "secondary" unpolarized calibrators. Let us know if you use these so we can evaluate their performance.

WARNING: the positions given in Table 7.4.4 are B1950, use the Source names in the VLA OPT to get the J2000 positions.


Table 7.4.4: Category D - secondary (unverified) low polarization sources
SourceRA (1950)DEC (1950)B1950 Name'Comments
J0029+3456 00 26 34.8386 34 39 57.586 0026+346 CSO
J0111+3906 01 08 47.2595 38 50 32.691 0108+388 CSO
J0410+7656 04 03 58.60 76 48 54.0 0404+768 CSO
J1035+5628 10 31 55.9562 56 44 18.284 1031+567 CSO
J1148+5924 11 46 10.4160 59 41 36.834 1146+596 CSO
J1400+6210 13 58 58.310 62 25 08.40 1358+624 CSO
J1815+6127 18 15 05.4851 61 26 04.496 1815+614 CSO
J1823+7938 18 26 43.2676 79 36 59.943 1826+796 CSO
J1944+5448 19 43 22.6729 54 40 47.955 1943+546 CSO
J1945+7055 19 46 12.0492 70 48 21.397 1946+708 CSO
J2022+6136 20 21 13.3005 61 27 18.157 2021+614 CSO

Table 7.2.4 Comments:

  • at least one "pol standard" (ideally from Category A) should be included for angle calibration
  • "bright" sources are easily useable as leakage calibrators with PA coverage (and probably good for bandpasses to boot!)
  • "monitored" sources can be found at http://www.vla.nrao.edu/astro/calib/polar/ (for VLA 1999–2009) and http://www.aoc.nrao.edu/~smyers/evlapolcal/polcal_master.html (for VLA 2010-2012)
  • "steep spectrum" sources are likely weak at high frequencies
  • "flat spectrum" sources are likely bright at high frequencies but variable
  • "moderately variable" sources may be useable in a pinch if you can get a nearby (in time) monitoring observation (Table 7.2.5)

Primary Polarization Calibrator Information

At least one observation of 3C286 or 3C138 is recommended to fix the absolute position angle of polarized emission. 3C48 also can be used for this at frequencies of ~3 GHz and higher, or 3C147 at frequencies above ~10 GHz. Table 7.5.1 shows the measured fractional polarization and intrinsic angle for the linearly polarized emission for these four sources in December 2010. Note that 3C138 is variable—the polarization properties are known to be changing significantly over time, most notably at the higher frequencies. See the "Integrated Polarization Properties of 3C48, 3C138, 3C147, and 3C286" (2013, ApJS 206, 2) by Perley and Butler for more details.

Table 7.5.1: Polarization Properties of Four Calibrators
GHz % Deg. % Deg. % Deg. % Deg.
1.05 0.3 25 5.6 −14 <0.05 8.6 33
1.45 0.5 140 7.5 −11 <0.05 9.5 33
1.64 0.7 −5 8.4 −10 <0.04 9.9 33
1.95 0.9 −150 9.0 −10 <0.04 10.1 33
2.45 1.4 −120 10.4 −9 <0.05 10.5 33
2.95 2.0 −100 10.7 −10 <0.05 10.8 33
3.25 2.5 −92 10.0 −10 <0.05 10.9 33
3.75 3.2 −84 <0.04 11.1 33
4.50 3.8 −75 10.0 −11 0.1 −100 11.3 33
5.00 4.2 −72 10.4 −11 0.3 0 11.4 33
6.50 5.2 −68 9.8 −12 0.3 −65 11.6 33
7.25 5.2 −67 10.0 −12 0.6 −39 11.7 33
8.10 5.3 −64 10.4 −10 0.7 −24 11.9 34
8.80 5.4 −62 10.1 −8 0.8 −11 11.9 34
12.8 6.0 −62 8.4 −7 2.2 43 11.9 34
13.7 6.1 −62 7.9 −7 2.4 48 11.9 34
14.6 6.4 −63 7.7 −8 2.7 53 12.1 34
15.5 6.4 −64 7.4 −9 2.9 59 12.2 34
18.1 6.9 −66 6.7 −12 3.4 67 12.5 34
19.0 7.1 −67 6.5 −13 3.5 68 12.5 35
22.4 7.7 −70 6.7 −16 3.8 75 12.6 35
23.3 7.8 −70 6.6 −17 3.8 76 12.6 35
36.5 7.4 −77 6.6 −24 4.4 85 13.1 36
43.5 7.5 −85 6.5 −27 5.2 86 13.2 36

3. Subarrays

The VLA can be split up in subarrays. That is, some of the 27 antennas and corresponding baselines can be ordered to do a completely different and independent program than other antennas. This may be the case when an observer has asked to divide up the array for a single project to observe a source simultaneously in multiple bands, to observe multiple different sources simultaneously that do not need the full array, or when one antenna is split off from the main array for inclusion in a VLBI array by another user (though not currently offered).

The current restrictions for observing with subarrays are:

  • The use of subarrays has to be requested in the proposal and approved by the TAC.
  • Up to 3 subarrays may be used. Note that the array cannot be divided up in three equal subarrays of nine antennas. For instance, three subarrays may be obtained by having 10 antennas in subarray 1, 9 antennas in subarray 2, and 8 antennas in subarray 3. For more information and for other possibilities see the subarray configuration details in the VLA OSS.
  • Until further notice, only 8-bit default NRAO wideband continuum frequency setups may be used for standard interferometric observing (no phasing, binning, etc). Other modes may be offered as RSRO in the call for proposals.
  • The division of pointing directions, frequency bands, polarization products and integration times over subarrays is unrestricted. Some of this freedom may be limited for OTF modes and pointing scans.
  • Only a single scheduling block should be submitted through the OPT, with appropriate comments to the operator. This scheduling block should consist of Subarray Loops, one per subarray in which separate lists of scans are placed for each subarray. Each Subarray Loop defines the antennas used per subarray. Check the OPT manual before you start making the subarray schedule by referring to section 5: "Subarray Observing".
  • The sum of data rates and other restrictions and guidelines for standard (single subarray) observations must be taken into account.
  • All Subarray Loops in a single Scheduling Block are started at the same time.

Please see section 5: "Subarray Observing" in the OPT manual for further information or contact the NRAO Helpdesk.

4. Mosaicking and OTF


This document is intended for observers planning VLA observations using multiple pointing and phase centers to create a "mosaic". A mosaic is an image of a patch of sky that is larger than the field of view of the telescope and thus is made up of more than one observed field. There are two different ways of making up such a patch: one is to combine together fields from individual pointings of the telescope, the other is to combine data that is taken in a 'scanning' mode, where the telescope does not dwell on a position but keeps moving with respect to the sky.

These two different ways are referred to as a discrete or pointed mosaic, and on-the-fly mapping or OTF(M), respectively. The former is typically used for smaller and non-rectangular patterns or when significant time needs to be spent per sky area to obtain sufficient sensitivity and image fidelity, the latter is most useful to scan large rectangular patterns on the sky such as for shallow surveys and transient searches where at least one dimension of the mosaic is many times larger than the primary beam. Each method has their advantages, prerequisites, and limitations which are outlined below. Whether to choose one over the other depends on the science goal and boundary conditions such as sensitivity but also, e.g., data rate.

Important considerations are:

  • size and shape of the area to cover (in primary beams)
  • sensitivity of the observation over the area (amount of integration time required on any single field of the mosaic)
  • image requirements (e.g., uv-coverage and largest angular size)

The VLA supports, through normal observing, mosaics that use a discrete pointing pattern. In this standard mode, the mosaic pointing centers are set up as individual fields to be observed (as if they were just a set of target sources). In data post-processing, the data that come from these groups of mosaic fields are jointly deconvolved taking into account the mosaic patterns.

Since semester 2015A, as part of our Shared Risk Observing (SRO) program, the VLA has been offering the opportunity to use OTF mosaicking to more efficiently scan large areas with small dwell times on each point. This is done by moving the telescopes while taking data (and stepping the phase centers for correlation). Special considerations must be taken in processing data taken with this mode. See the section Considerations for On-The-Fly (OTF) Mosaics below and the OPT Manual section on OTF for more details.


Considerations for Discrete Mosaics

To set up a discrete mosaic for VLA observing, you need to first work out:

  1. What area of sky do you want to cover?
    • Compute the total mosaic area [inline]A_{\rm mos}[/inline] in appropriate solid angle units, e.g. square degrees.
      I want to cover 5 degrees x 5 degrees, so my area is 25 square degrees.
  2. What is the effective primary beam size in your observing band? How many independent "beams" are in the mosaic?
    • Compute the Full-Width Half-Maximum (FWHM) [inline]\theta_p[/inline] of the VLA at a representative frequency [inline]v_{\rm obs}[/inline], usually the center of your observing band, using the formula
      [display]\theta_P \approx 42^\prime \frac{\rm 1 \: GHz}{\nu_{\rm obs}}[/display] (see the Field of View section in the VLA OSS document)
      I am observing in L-band 1-2 GHz, so νobs = 1.5GHz and θP [inline]\approx[/inline] 28'
      (Note that the formula given above for [inline]\theta_P[/inline] is approximate, as the beam is not perfectly linear with frequency. For more accurate beam sizes as a function of frequency, we refer the user to EVLA Memo 195 by R. Perley (2016) for the Karl G. Jansky VLA. For beam sizes for the original VLA, we refer the user to VLA Test Memo 134 by Napier & Rots (1982) )
    • Compute the mosaic beam area ΩB from the FWHM, using the formula (see the Gaussian Beam Pattern Sensitivity subsection below for more details) [display]\Omega_B = 0.5665 \theta^2_P[/display]
      For my θP = 28' = 0.47° the equivalent mosaic beam area is ΩB = 0.123 square degrees
    • Compute the number of independent/effective beam areas in mosaic using the formula
      [display]N_{\rm eff}=\frac{A_{\rm mos}}{\Omega_B}[/display]
      For my 25 square degree mosaic with ΩB = 0.123 square degrees I have 203 effective beams.
  3. How much integration time do I need? What is my Survey Speed (SS)?
    • Compute the integration time per "beam" tcalc using the VLA Exposure calculator
      I wish to reach RMS 0.05 mJy. For 600MHz useable bandwidth at 1.5GHz in B-configuration robust weighting dual pol I need 3m31s on-sky.
    • Compute the total integration time ttotal for the mosaic by multiplying by the number of beams. (Note: to first order, this is independent of how you actually split up the mosaic.)
      For 3m31s per beam and 203 beams I need 11h54m total over the mosaic.
    • Compute the Survey Speed (SS) by taking the mosaic area and dividing by the total integration time (SS = Amos/ ttotal). This is equivalent to simply computing directly SS = ΩB / tcalc also!
      For ttotal=11h54m (11.9 hours) total over the 25 square degree mosaic the implied survey speed is 2.10 square degrees per hour (or equivalently SS = 2.10 square arc-minutes per second).
  4. What mosaicking pattern do you wish to employ? What will be the spacing between pointings?
    • For discrete/pointed mosaics, we recommend to use a hexagonal mosaicking pattern with a spacing of θhex long rows and θrow ≈ √3 θhex/2 between rows. (Typically a value of θhex = θP/√2 is sufficient, but consider using θhex = θP/√3 if uniformity is a strong concern.)
      For our θP = 28' we get θhex = 19.8' for the spacing along rows and θrow = 17'9" (1029") between rows. We note that this will be more under-sampled at the upper band edge of 2GHz, and over-sampled at 1GHz, but for our basic observations this should be OK.
  5. How many pointings will this mosaic take for this pattern?
    • To fill a rectangular area, long and short rows should alternate, with 1 extra pointing in the long rows.
      Our square mosaic has sides of 5 deg (300'). The spacing between rows is θrow = 17'9" (1029") so there should be 17.5 spacings, and we will therefore schedule 18 rows. Our 300'-length rows will have spacing between pointings of θhex = 19.8', so we will observe 16 pointings in the short rows. The beginning and end pointings in each of these short rows will be 15 x 19.8' = 284' apart. The short rows will alternate with longer rows of 17 pointings (16 x 19.8' = 306'8" between the pointings at either end of a long row). We will have 9 short rows interspersed with 9 long rows, or 9 x 16 + 9 x 17 = 297 pointings in our mosaic.
  6. How much integration time should be allocated per discrete pointing?
    • Divide the total mosaic integration time by the number of mosaic pointings.
      Our total integration time of 11h54m is spread among 297 pointings, so each pointing should get 2m24s of integration time.
      You may wish to consider using On-the-fly (OTF) mosaicking if your integration time per pointing is less than 24 seconds; definitely consider it if your integration time is less than 15 seconds - see below.
  7. Calculate approximate duration (excluding calibration) for the mosaic.
    • The VLA slew and settling time for short distance (sub-degree) moves is 6-7 seconds.
      For 2m24s integrations we add 7s so we can have observations of 2m31s. The total time for 297 pointings is 12h28m.
  8. Calculate schedule overheads.
    • Follow the Exposure and Overhead guidelines in the Guide to Proposing for the VLA.
      For ease of scheduling, we will break our ~12.5h mosaic into three parts, each with 4h10m of observing time. Our overheads will include: 10m allowance to get on-source at the beginning of each scheduling block, a 10m scan of a flux calibrator, and 3m about every 28m (10 visits) to observe our gain calibrator. The total time for each scheduling block comes to 5 hours. This amounts to a 20% overhead, which is about average for VLA's low frequencies.
  9. If project is approved, when it comes time to observe, make schedule in OPT.
    • We are working on providing some Python tools (e.g. for CASA) that will help set up mosaic observations. Stay tuned. In the meantime, you may wish to externally generate lists of sources and scans that can be uploaded into the OPT, in order to generate all pointings at once. See the Text Files section of the OPT Manual for instructions.


Considerations for On-The-Fly (OTF) Mosaics

For OTF, rather than producing a mosaic from a large number of individual pointings, the VLA continuously takes data while scanning across the sky. An OTF observation typically amounts to scanning in a "back and forth" fashion over a large rectangular area of sky, one row at a time. The great benefit of OTF mosaicking is the ability to eliminate the slew-and-settle time that is required for each pointing in a discrete mosaic. Recall that the slew-and-settle time typically amounts to 7s per pointing, so OTF is particularly useful for large, shallow mosaics that require <15-25s per mosaic beam.

The use of OTF mosaicking with the VLA is the subject of ongoing development and commissioning, and as such is only available under the SRO program.

The most important question is "Do I need to use OTF mosaicking or is standard mosaicking sufficient?". You should only use OTF mosaicking if it will be significantly more efficient than standard mosacking. This comes down to whether the required dwell time in a pointing is so short that the 7 seconds of slew-and-settle time (3-4 seconds at best for short, elevation-only moves) per field will incur a very large overhead (>30%-50%) on the observations. Thus, you should refer back to the "integration time per discrete pointing" you calculated above in Step 6. If this is shorter than 12-14 seconds, then the 6-7 seconds it will take to move and settle between pointings will incur >50% overhead. In this case, unless this extra overhead is not a problem (i.e. the overall mosaic is quite small in area) you will likely wish to use OTF. You might also be able to arrange your mosaic schedule so that the moves are in elevation, which in some cases brings the overhead down to 3-4s. If you need less than 7 seconds per pointing you almost certainly want to use OTF! From 14 seconds to 24 seconds it is a gray area - you will benefit from OTF mosaicking but the extra processing cost and added complexity probably means you should just use standard mosaicking unless you are familiar with processing this type of data in CASA.

If you decide to use OTF mosaicking, the next question is "Can I use OTF mosaicking for my observations?". In other words, will the implied scan speeds and dump rates (and thus data rates) be within the capabilities of the VLA? This comes down to whether or not you have to scan the array too fast and set the integration times tinteg out of the correlator back-end too short as to not smear the beam. We recommend that you scan such that you have at least 10 samples across the primary beam FWHM, e.g. that your required scan rate R < 0.1 θP / tinteg where the minimum allowed tinteg is set by the maximum allowed data rate (usually 25MB/s for standard observing - for bandwidths of 2GHz or less this means 0.5 sec, and correspondingly longer for 3-bit modes). Note: as of 2017A, OTF is still classified as shared-risk for which the limit is nominally 60MB/s. This means that you can use shorter integration times when choosing OTF as you are already a shared-risk observer! But don't use a shorter integration time than you really need.

Thus, you determine the implied scanning rate R = SS / θrow from the computed survey speed (SS = ΩB / tcalc from Step 3 above) and the spacing of OTF rows θrow from Step 4 required to uniformly sample the mosaic. To determine θrowrow = θP/√2), we recommend using θP computed from the upper frequency limit of the band, as the highest frequency corresponds to the smallest primary beam (thus the highest frequency will have the lowest uniformity in coverage). To determine the Survey Speed, we recommend using θP at the middle of the band, so that the sensitivity can be easily related to the band average of a source with a modest non-zero spectral index. For example, at S-band (using θP= 15' at 3GHz, ΩB=127.5 square arc-minutes) for a depth of 0.1 mJy (tcalc= 7.7 sec) we have a survey speed SS = 16.56 square arc-minutes per second. For a row spacing of 8' (θP/√2 with θP= 11.25' at 4GHz) we need an OTF scan rate of R = 2.07 arc-minutes per second. In terms of the primary beam FWHM at 4 GHz (11.25') we have a rate relative to the PB of R/θP = 0.18 per second. Thus, to keep RtintegP < 0.1 we need tinteg< 0.54 seconds and thus 0.5 second integrations are recommended. This gives a data rate of 24MB/s which is within the standard observing limit of 25MB/s.

Note that the limitations on the allowed correlator dump times tinteg are not just from the allowed data rates (25MB/s for standard observing and 60MB/s for shared risk). There are also physical limitations on how fast the data from the correlator can be handled by the back-end processing cluster. Currently, we do not allow phasecenter changes in OTF mode faster than 0.6 seconds. However, it is possible in the OPT to request multiple integrations per phasecenter (e.g., one might request an integration time of 0.5s with two pointings per phasecenter, such that the phasecenter will change once per second). We restrict the allowed visibility integration times to a minimum tinteg of 0.5sec for up to 4GHz of correlated bandwidth, and 1 second for 4-8GHz of bandwidth. Shorter integration times are possible, but require restricted bandwidth to stay within the allowed data rates. For the current restrictions on integration times, see the OSS section on Time Resolution and Data Rates.

To set up the parameters of the mosaic (e.g. for the purposes of a proposal), carry out the steps outlined above, except for computing the number of discrete pointings.

  • Instead, you will break the OTF mosaic into a number of "rows" each of which is one or more "stripes" (e.g. a row from RA 0h to 0h15m at a given Declination might be broken into three stripes 0m-5m, 5m-10m, and 10m-15m) with calibration in between. Rows should be separated as in the hexagonal mosaic case, we recommend a value around [display]\theta_{\rm row} = \theta_P / \sqrt{2}[/display] where θP is computed at the upper frequency limit of the band.
  • We currently advocate OTF mosaics where the stripes are at constant Declination (e.g. you only need to clock the HA rate of the telescope). You will want to switch directions for each row so as to scan back and forth (e.g., from west to east for one row, then from east to west for the next, etc.). Note that scans from east to west move with the sidereal motion while scans from west to east are counter-sidereal. Therefore, for the same on-the-sky angular scan rate, the east-to-west scans will require faster telescope motion. We do not recommend requesting scan rates faster than about 3 arcmin/sec, even under Shared Risk Observing. We have confirmed that OTF functions acceptably for scan rates R up to 3 arcmin/sec, and are testing faster rates. Note that, as always, you should avoid observing near the Zenith where the azimuthal rate becomes very high.
  • Integration time and total mosaic time are calculated as before. Decide stripe times based on this.
  • The correlator dump time tinteg should be calculated using the scan rate considerations given above. We recommend to have RtintegP < 0.1 (i.e., at least 10 integrations covering the distance across the primary beam).
  • Your schedules for basic OTF mosaicking can now be made in the OPT. Choose "On The Fly Mosaicking" as the SCAN MODE, and fill in the START SOURCE, END SOURCE positions (from a Source Catalog as usual), which will set up a single stripe between those positions. You also choose a "Number of Steps" for phase center switching, and a number of "Integrations per Step". For example, for an instrument configuration with 0.5sec integrations you might choose 135 steps with 8 integrations per step. This means the phase center will change every 4 seconds (8 integrations) and thus an OTF stripe will be 540 seconds long (9 minutes). Note that an additional preparatory step will be added to allow the array to get moving in the right direction, and so the "stripe duration" will be reported as 544 seconds. Finally, the user chooses a total Duration for the scan which must be larger than the "stripe duration" needed and including overhead to get to the start position. If you have a previous scan at or close to the START SOURCE then something like an additional 10-12 seconds should be enough. In our example a Duration of 9m15s should be enough. You then schedule the stripes (scans) needed to do your entire mosaic. Note: we recommend setting the "Integrations per Step" to a value corresponding to at least 1 second for 8-bit modes with 16 sub-bands per polarization, or at least 4 seconds for more than 16 sub-bands per polarization (e.g. 3-bit continuum modes).

Rather than entering each OTF scan into the OPT individually, you may wish to generate a scan list in an external text file that can be uploaded into the OPT, in order to generate all scans at once. See the Text Files section of the OPT Manual for instructions.


Survey Speed of the VLA for Large Continuum Mosaicked Surveys

Following the above guidelines (Steps 1-3 in the mosaic calculations) we can compute the survey speed SS [display]SS = \Omega_B / t_{calc} = 0.5665 \theta^2_{P} / t_{calc}[/display]of the VLA for our standard bands calculated at a given depth in RMS image sensitivity. We choose a "RMS Noise" of 0.1 mJy/beam in the Exposure Calculator (also 25 antennas, natural weighting, dual polarization, medium elevation, autumn weather, B-configuration) to compute tcalc. From this, we calculate SS from θP at band center.

The parameters are tabulated by band below:

Band (freq)Freq.Bandwidthtcalc (sec)θP (arcmin)SS (deg2/hr)
P (230-470MHz) 370 MHz 200 MHz 5940 135' 1.74
L (1-2GHz) 1.5 GHz 600 MHz 37 28' 12.00
S (2-4GHz) 3 GHz 1500 MHz 7.7 14' 14.42
C (4-8GHz) 6 GHz 3.03 GHz 4.4 7' 6.31
X (8-12GHz) 10 GHz 3.50 GHz 2.9 4.2' 3.45
KU (12-18GHz) 15 GHz 5.25 GHz 3.5 2.8' 1.27
K (18-26.5GHz) 22 GHz 7.20 GHz 7.0 1.91' 0.26
KA (26.5-40GHz) 33 GHz 7.20 GHz 11 1.27' 0.083
Q (40-50GHz) 45 GHz 7.20 GHz 50 0.93' 0.045

For C-band and higher frequencies 3-bit observing is assumed. Representative frequency, integration time, beam width, and survey speed are at approximately mid-band. You can adjust these values for different assumed sensitivity levels and bandwidths (e.g. for line sensitivity) by scaling according to the values that come out of the Exposure Calculator (e.g. SS will scale as the inverse of the integration time). These values are computed in the limit of OTF (continuous) sampling, but should be approximately valid for optimally sampled Hex mosaics also (see below). The beam widths here are approximate (see EVLA Memo 195 by R. Perley, 2016) and are narrow-band. For a wide-band mosaic, see the section below on Effective Primary Beam for a Wideband Mosaic.

The Details: Mosaic Sensitivity

Following are some in-depth calculations of the discrete mosaic sensitivity, provided for users who wants to know the gory details of how the values are calculated. These formulas are generally applicable to mosaics made with any interferometer (e.g. ALMA, ATCA), although some allowances would need to be made in the calculations to allow for non-homogeneous array elements (e.g. with antennas of different sizes as in ALMA+ACA, CARMA).

Gaussian Beam Pattern Sensitivity

We will be assuming a Gaussian pattern [inline]\theta_g[/inline] for the main beam response (the so-called primary beam pattern) assuming an array of homogeneous antennas. The sensitivity pattern or response to point sources at a distance θ from the pointing center on-sky is given by

[display]f(\theta) = e^{-{\frac{\theta^2}{2\theta^2_g}}}[/display]

The 2-D integral under this function gives the effective Gaussian beam area (solid angle)

[display]\Omega_g = 2\pi\theta^2_g[/display]

For purposes of mosaic coverage, the area under the primary beam squared is relevant ([inline]f(\theta)^2[/inline]):

[display]f(\theta)^2 = e^{-2{\frac{\theta^2}{2\theta^2_g}}} = e^{-\frac{\theta^2}{2(\theta_g/\sqrt{2})^2}}[/display]

So the effective Gaussian primary beam for a mosaic is equivalent to a Gaussian with half the area:

[display]\Omega_B = 2\pi(\frac{\theta_g}{\sqrt 2})^2 = \pi\theta^2_g = \frac{\Omega_g}{2}[/display]

It is common practice to specify the Gaussian width by the "full-width half-maximum" (FWHM) θP, where

[display]\theta_P = \sqrt{(8 \ln 2)}\; \theta_g = 2.3548 \theta_g[/display]


[display]\theta_g = 0.4247 \theta_P[/display]

We can reformulate the response function in terms of the FWHM via substitution:

[display]f(\theta) = e^{-\frac{\theta^2}{2\theta_g^2}} = e^{-4 \ln 2 (\frac{\theta}{\theta_P})^2} = 2^{-4 (\frac{\theta}{\theta_P})^2}[/display]

Our beam areas are

[display]\Omega_g = 2\pi\left(\frac{\theta_P}{\sqrt{8 \ln 2}}\right)^2 = 1.1331 \theta^2_P[/display]

and for the beam-squared

[display]\Omega_B = \frac{\pi}{8\ln 2} \theta^2_P = 0.5665 \theta^2_P[/display]

Effective Primary Beam for a Wideband Mosaic

The above formulas for the Primary Beam are approximations that apply exactly in the case of a narrow-band mosaic. For a wideband (multi-frequency synthesis) mosaic, the effective primary beam depends on the frequency variation of the narrow-band beam widths and the sensitivity as a function of frequency.

The mosaic imaging process weights the data explicitly by assigned weights (e.g., by the rms noise) and implicitly by the beam area at each frequency (because the effective integration time at each frequency is proportional to the beam area). This effect was pointed out by Condon (2015; reference 5) and can be simply calculated as the frequency-weighted mean beam area over the frequency channels [inline]k[/inline] according to the formula

[display]\bar{\Omega}_B = \frac{\Sigma_k\; w_k\; \Omega_{Bk}}{\Sigma_k\; w_k}[/display]

For uniform weights [inline]w_k[/inline] = const. and uniform frequency coverage over the band, we can approximate this sum by the integral

[display]\bar{\Omega}_B = \frac{1}{\nu_{\rm max} - \nu_{\rm min}}\; \int^{\nu_{\rm max}}_{\nu_{\rm min}}\; d\nu\; \Omega_B(\nu)[/display]

If we assume the primary beam FWHM scales inversely by frequency, then

[display]\bar{\Omega}_B = \frac{\nu_0^2}{\nu_{\rm min}\; \nu_{\rm max}}\; \Omega_B(\nu_0)[/display]

[display]\Omega_B(\nu) = \Omega_B(\nu_0)\; \left(\frac{\nu_0}{\nu}\right)^2[/display]

or equivalently [inline]\bar{\Omega}_B = \Omega_B(\bar{\nu})[/inline] where [inline]\bar{\nu} = \sqrt{\nu_{\rm min}\; \nu_{\rm max}}[/inline] is the geometric mean frequency.

Weighted Image Sensitivity

A mosaic image can be considered to be a weighted sum of individual field image data ([inline]d_k[/inline]) corrected for the beam response ([inline]f[/inline]) at each individual pointing:

[display]F = \frac{1}{Z}\sum_{k} w(\theta_k) f^{-1}(\theta_k)\; d_k[/display]

[display]Z = \sum_{k} w (\theta_k)[/display]

where the [inline]\theta_k[/inline] are the distances to the pointing centers for the image data points dk, [inline]w(\theta_k)[/inline] is the weight for data point dk, and [inline]Z[/inline] is the sum-of-weights function. If the image data have equal RMS sensitivity levels σk = σ0 then the optimal weighting gives



[display]F = \frac{1}{Z}\sum_{k}f(\theta_k)\; d_k[/display]

[display]Z = \sum_{k} f^2 (\theta_k)[/display]

This image will have the lowest possible RMS noise level, with the variance of [inline]F[/inline] given by

[display]\sigma_F^2 = \frac{1}{Z^2}\sum_k f^2(\theta_k)\sigma_0^2 = Z^{-1}\sigma_0^2[/display]

which just scales inversely with the sum-of-weights function Z. Since the equivalent integration time at a given point in the mosaic is inversely proportional to the variance (with all other things being equal) then this is given by Z:

[display]t_{eff} = Z t_0[/display]

where t is the integration time per field (assuming a uniformly observed mosaic).

Discrete Mosaic Spacing Considerations

For discrete (as opposed to OTF) mosaicking, the sampling pattern and spacing of pointing centers determines the sensitivity response of the mosaic. The concept of stepping or scanning an interferometer over an area of sky to synthesize a larger image has been around for a long time, see Ekers & Rots 1979 (reference 1) for the conceptual framework.

The simplest pattern is a rectangular mosaic, with pointing centers at vertices of squares. From the perspective that the FFT of the mosaic pattern is a "synthesized beam" in uv-space that sub-samples the antenna voltage patterns, the Nyquist sampling theorem suggests that a spacing of [inline]\theta_{\rm rect} = \theta_P/2[/inline] or better is needed (e.g. Cornwell 1998, reference 2). This is the spacing of samples on the sky needed to reconstruct the low spatial frequencies on the scale of the primary beam θP. However, if the goal is merely to cover large areas of sky to survey for relatively compact sources, then the spacing limit given by Nyquist sampling of the primary beam can be loosened and wider separations can be used, as long as the dimples in the sensitivity pattern are not too deep for purposes of having a nearly uniform survey over a large area.

The hexagonal-packed mosaic is the classic mosaic observing pattern. It has long been used at the VLA (e.g. for the NVSS, see reference 3) and at the ATCA (see reference 4). This pattern is like a regular rectangular raster but with alternate rows offset by 1/2 field separation, allowing rows to be placed further apart while still getting nearly uniform sensitivity. The mosaic is thus filled by equilateral triangles, with the triangle vertices defining the pointing centers of the pattern.

The ATCA recommended value for [inline]\theta_{\rm hex} = {\theta_P}/{\sqrt 3}[/inline] is based on Nyquist arguments (see reference 4). For the NVSS survey (reference 1), the authors argued that a spacing not much wider than [inline]\theta_{\rm hex} = {\theta_P}/{\sqrt 2}[/inline] would be acceptable from a sensitivity perspective, and in fact used a spacing of approximately [inline]{\theta_P}/{1.2}[/inline]. This is sufficient (see below) to have a reasonably uniform sensitivity pattern.

For the current VLA, where we have 2:1 bandwidths possible in a given band (e.g. 1-2 GHz, 2-4 GHz), you have to consider the spacing with respect to the primary beam FWHM over the range of frequencies you are going to map together. For example, for observations from 1-2 GHz, setting a spacing of 0.71 FWHM at 1.5 GHz would give a spacing of only 0.94 FWHM at 2 GHz which gives a minimum weight of Zhexmin = 0.586 (see below), but also with significant oversampling of 0.47 FWHM at 1 GHz. You may wish to err on the side of caution in these cases if having more variable sensitivity at the upper band edge is expected to be an issue for you. Note that we have not quantified any imaging consequences from this (e.g. for spectral index maps) so for now these are just some general guidelines.

Recommendation: For most cases where structure on large angular scales is not being imaged, a hex-pattern mosaic with relatively loose spacing of 0.70 - 0.85 FWHM is probably sufficient. If good imaging of large-scale low surface brightness emission is the goal, then a mosaic sampled at the Nyquist spacings or better should be used. In most cases, you can reasonably get away with setting the spacing by the FWHM at the center of your observing band, leaving the mosaic at the upper end of the band less well-sampled while the mosaic at the lower band edge will be better sampled. If for some reason you require excellent sampling over the whole band, then set the spacing using the FWHM at the highest frequency to be safe.

Example: Discrete Hexagonal Mosaic

Each mosaic pointing center has 6 nearest neighbors (hence the hexagonal pattern), with a distance to each given by θhex. For a pixel at a pointing center, counting that point and the 6 neighboring centers, the sum-of-weights is given by

[display]Z_{\rm hexmax} = 1 + 6f^2(\theta_{\rm hex})[/display]

The worst response is at the center of one of the equilateral triangle tiles. The nearest 3 vertices are at distances given by [inline]\theta_{\rm hex}/{\sqrt 3}[/inline] giving

[display]Z_{\rm hexmin} = 3 f^2 (\frac{\theta_{\rm hex}}{\sqrt 3})[/display]

If NVSS-style image-plane mosaicking is used, then next sets of vertices out will likely not be included in the image due to an imposed cutoff (see reference 3). Assuming a moderately liberal spacing of [inline]\theta_{\rm hex} = \theta_P/{\sqrt{2}}[/inline] we get:

[display]\theta_{\rm hex} = \frac{\theta_P}{\sqrt 2}[/display]

[display]f(\theta_{\rm hex}) = 0.25[/display]

[display]f(\theta_{\rm hex}/\sqrt 3) = 0.63[/display]


[display]Z_{\rm hexmax} = 1.375\; \; \; \; \; \; \; \;Z_{\rm hexmin} = 1.191[/display]

Thus the lowest points in the mosaic weighting pattern are at 0.87 of the maximum (for the NVSS choice, they are at 0.81 of the maximum). Note that the locations at the pointing centers get an equivalent integration time of 1.375 times the individual pointing integrations.

A large hexagonal mosaic of N x M rows and columns will cover a total area of approximately

[display]A_{\rm hex} = N \times \theta_{\rm hex} \times M \times \frac{\sqrt 3}{2}\theta_{\rm hex} = \frac{\sqrt{3}}{2} N_{\rm pt}\theta^2_{\rm hex}[/display]

For a sampling of [inline]\theta_{\rm hex}= \theta_P/\sqrt{2}[/inline] we get

[display]A_{\rm hex} = \frac{\sqrt3}{4}N_{\rm pt}\theta^2_P = 0.7644 N_{\rm pt}\Omega_B[/display]

for the area under the squared beam defined above. If we observe the mosaic for a total time T with each of the Npt pointings getting the same integration time tint

[display]t_{int} = \frac{T}{N_{\rm pt}}[/display]


[display]A_{\rm hex}t_{\rm int} = 0.7644 T \Omega_B[/display]

or using the effective integration time per point in the mosaic

[display]A_{\rm hex}t_{\rm eff} = 0.7644 Z\;T \Omega_B[/display]

For our hexagonal mosaic, the minimum weight is Zhexmin = 1.191 so

[display]A_{\rm hex} t_{\rm hexmin} = 0.91 T \Omega_B[/display]

For practical purposes, as we will see later on, mosaics in general follow the relation that

[display]A_{\rm mos} t_{\rm eff} \approx T \Omega_B[/display]

which can be used to compute the effective integration time on-sky to put into the exposure calculator for RMS sensitivity.

Recommendation: For most cases where you are using a hexagonal (or rectangular or OTF) mosaic with close to the optimal sampling and want the average sensitivity (not the max or min specifically), you can simply use the following to calculate the total integration time needed

[display]T \approx t_{\rm eff}\frac{A_{\rm mos}}{\Omega_B}[/display]

after getting teff from the VLA Exposure Calculator for your needed sensitivity and chosen bandwidth etc.

Example: Discrete Rectangular Mosaic

The use of rectangular mosaics has been deprecated in favor of hexagonal packed mosaics, but there are cases where they are expedient to set up, and they provide an illustrative case leading in to the discussion of on-the-fly mosaics.

For the rectangular mosaic each point is surrounded by eight immediate neighbors with the 4 nearest separated by θrect in the cardinal directions and next 4 by [inline]\sqrt{2}\theta_{\rm rect}[/inline] on the diagonals. Thus,

[display]Z_{\rm rectmax} = 1 + 4 f^2(\theta_{\rm rect}) + 4 f^2(\sqrt{2}\theta_{\rm rect}) = 2.25[/display]

for the optimal θrect = 0.5 θP.The weight minima have 4 nearest neighbors at θrect/√2

[display]Z_{\rm rectmin} = 4 f^2(\frac{\theta_{\rm rect}}{\sqrt 2}) = 2[/display]

Thus our rectangular mosaic has dimples at 0.89 of the maximum response. The maximum effective integration time is 2.25 times the per pointing integration time. Our mosaic of N rows by M columns covers an area of approximately

[display]A_{\rm rect} = N \times \theta_{\rm rec} \times M \times \theta_{\rm rect} = N_{\rm pt}\theta^2_{\rm rect}[/display]

so going through the same calculation as for the hexagonal mosaic

[display]A_{\rm rect} = \frac{1}{4}N_{\rm pt}\theta^2_{P} = 0.4413 N_{\rm pt}\Omega_B[/display]


[display]A_{\rm rect}t_{\rm eff} = 0.4413\; Z\; T\; \Omega_B[/display]

For our rectangular mosaic, the minimum weight is Zrectmin = 2 so

[display]A_{\rm rect}t_{\rm rectmin} = 0.88 T \Omega_B[/display]

The Continuum Limit and On-the-Fly Mosaic Sensitivity

The following are some in-depth calculations of the OTF mosaic sensitivity.

We first calculate the sensitivity in the continuum limit, where the array scans the sky over a given area A in a time T in as uniform a manner as possible. In this case, except near the edges, each point along the row has the same weight, and our sums in the previous derivations become integrals. The image at a given position on the sky ([inline]{\rm\bf x}_0[/inline]) amounts to a weighted integration of the field data ([inline]D(x)[/inline]) over all nearby sky positions ([inline]{\rm\bf x}[/inline]) corrected by the beam response ([inline]f[/inline]), and keeping in mind that the beam scans across the sky over time:

[display]F({\rm x_0}) = \frac{1}{Z}\int dt\; w({\rm\bf x-x_0})\; f^{-1}({\rm \bf x - x_0})\; D(x)[/display]

[display]{\rm\bf x} = {\rm\bf x}(t)[/display]

with normalization

[display]Z = \int dt\; w({\rm\bf x})[/display]

and as before

[display]w({\rm\bf x}) = f^2(x) = e^{-\frac{x^2}{\theta^2_g}}[/display]

We are sweeping at a constant rate so the areal (solid angle) rate is

[display]\dot{\Omega} = \frac{d\Omega}{dt} = \frac{dx\; dy}{dt} = \frac{A_{\rm mos}}{T}[/display]

where Amos is the total area of the mosaic and T the total integration time as before. Thus, we can recast the integrals

[display]F({\rm\bf x}_0) = \frac{1}{Z}\int\int\frac{dx\; dy}{\dot{\Omega}}\; w({\rm\bf x} - {\rm\bf x}_0)\; f^{-1}({\rm\bf x} - {\rm\bf x}_0)\; D({\rm\bf x})[/display]

[display] = \frac{1}{Z\dot{\Omega}}\int\int dx\;dy\; f({\rm\bf x} - {\rm\bf x}_0)\; D({\rm\bf x})[/display]

and more critically the normalization (which is constant over the uniform part of the mosaic) is related to area of the squared beam

[display]Z = \int\int dt \; w({\rm\bf x}) = \int\int\frac{dx\; dy}{\dot{\Omega}}f^2({\rm\bf x}) = \frac{T}{A_{\rm mos}}\Omega_B [/display]

As before, we can compute the RMS sensitivity

[display]\sigma^2_F = \frac{1}{Z^2}\int\int\frac{dx\; dy}{\dot{\Omega}}f^2({\rm\bf x})\; \sigma^2_D = \frac{\sigma_D^2}{Z}[/display]

where σ2D is the sensitivity of the data per unit time, so again we have the relation

[display]Z = \frac{\sigma^2_D}{\sigma^2_F} = t_{\rm eff}[/display]

Thus, in general for a uniformly scanned continuous mosaic, we have the survey area time product relation

[display]A_{\rm mos}t_{\rm eff} = T \Omega_B[/display]

which is what we found approximately for our hexagonal and rectangular discrete mosaics above. The effective integration time per point on sky is given by dividing the total time by the effective number of mosaic beams

[display]t_{\rm eff} = \frac{T}{N_B}\; \; \; \; \; \; \; \; N_B = \frac{A_{\rm mos}}{\Omega_B}[/display]

You can use the standard radiometer calculation (e.g. with the VLA Sensitivity Calculator) to compute the expected RMS on-sky for this effective integration time.


1. "Short Spacing Synthesis from a Primary Beam Scanned Interferometer", Ekers & Rots 1979, IAU Colloq. 49: Image Formation from Coherence Functions in Astronomy, 76, 61

2. "Radio-interferometric imaging of very large objects", Cornwell 1988, A&A, 202, 316

3. "The NRAO VLA Sky Survey", Condon et al. 1998, AJ 115, 1693.

4. "Mosaicing Observing Strategies", MIRIAD Users Guide, http://www.atnf.csiro.au/computing/software/miriad/userguide/node168.html

5. "An Analysis of the VLASS Proposal" Condon 2015, astro-ph > arXiv:1502.05616


5. Moving Objects


The VLA is able to observe moving objects (solar system bodies) in standard continuum modes as part of general observing. It is not currently possible to observe spectral lines in planets or comets, except in unusual circumstances (background source occultations, for instance), or as part of the Resident Shared Risk Observing (RSRO) program. There is an observational limit on the rate at which objects can be tracked, but it is fast enough that observation of all natural solar system bodies is allowed, including Near Earth Asteroids (NEAs). As an example, the NEA 2005 YU55 was observed during its closest approach in 2011, when its motion was many arcseconds per second.

Generally, observing solar system bodies is no different than any other source in terms of the calibrations that are necessary (frequency setups for continuum observing, etc.). Observers should follow the recommended practices described elsewhere in the setup of the scans in their Scheduling Blocks (SBs), and the setup of the hardware (tuning and correlator). The main difference is in the setup of the source itself, of course, and there is a minor difference in how calibrators need to be selected. These will be described next.

Setting Up a Solar System Source

When starting from the Observation Preparation Tool (OPT) page, click on the Sources link. Create a new source catalog and/or group, or select an existing one (see the OPT documentation for instructions on how to do this). Click on File (located in the dark blue area at the top), then click Create NewSource. You are presented with a screen that looks like Figure 7.5.1.

There are now two choices for setting up a solar system source:

  1. Sources known internally to the VLA software system, or;
  2. Sources for which you can provide an ephemeris file.

Note that in the near future you will be able to specify the motion terms of a polynomial, but that is not implemented in the OPT yet.

Internal Sources

For the planets, the software system of the VLA uses an internal representation of the JPL DE410 ephemeris. The list of bodies supported in this way are:

  • Sun
  • Moon
  • Mercury
  • Venus
  • Mars
  • Jupiter
  • Saturn
  • Uranus
  • Neptune

Please note that the positions for the objects specified in this way are barycentric, not bodycentric. The latter introduces small offsets to the actual on-the-sky positions for the VLA. If this is an important effect, you must use the other method of setting up your moving source. When in doubt whether this is affecting your observations, read on about the JPL Horizons page below or consult the NRAO Helpdesk.

To set up an internal ephemeris source, go to the SOURCE POSITIONS section of the New Source page (seen in Figure 7.5.1), and select Solar System Body with Internal Ephemeris in the POSITION TYPE pull-down menu. You will then see something similar to Figure 7.5.2 for the SOURCE POSITIONS section. You can now choose the object from the above list in the SOLAR SYSTEM BODY pull-down menu.


Ephemeris File Sources

If your body is not included in the list of sources known to the VLA, or if you care about bodycentric vs. barycentric positions, you may use an ephemeris file to specify the position of your source as a function of time. To set up an ephemeris file source, go to the SOURCE POSITIONS section of the New Source page (seen in Figure 7.5.1), and select Solar System Body with Uploaded Ephemeris in the POSITION TYPE pull-down menu. You will then see something similar to Figure 7.5.3 for the SOURCE POSITIONS section.

Click on the Browse… button to select the ephemeris file, and then click the Import button. The SOURCE POSITIONS section should now look similar to Figure 7.5.4, with the times and positions displayed.


Format of Ephemeris Files

Ephemeris files to be used in this way are created with the JPL Horizons system. Go to: http://ssd.jpl.nasa.gov/horizons.cgi, and specify:

To select your body, click on change next to Target Body, and use the lookup tool. JPL’s Horizons system knows about most solar system bodies, including comets, moons, and asteroids (NEAs included), and even spacecraft. To select your time range, click on change next to Time Span, and input the proper time range. Note that, for most bodies, using an ephemeris tabulated at 1 hour entries is sufficient. For some fast-moving near-Earth objects, a shorter interval between tabulated entries may be needed. To be sure that the Table Settings are correct, click on change, and then be sure that only options (1.) Astrometric RA & DEC and (20.) Observer range & range-rate are selected, then go to the Optional observer-table settings section (below Select observer quantities from table below), and be sure that the extra precision box is checked.

After everything is set up correctly, click on the Use Settings Above button and then Generate Ephemeris.After you are taken to that page, you will need to save the web page as a text file. Please note that currently Google Chrome does not allow for simple saving of web pages as text; Firefox, Safari, and IE do not suffer from this shortcoming. Once the file is saved to your computer, you can select it for use as described above.

Finding Calibrators

Finding calibrators for moving sources proceeds in much the same way as for other sources, but since the target object moves you must be a bit careful about it. For slow-moving sources in the outer solar system, using the same calibrators over periods of years is fine, since the motion is slow. For inner solar system bodies, however, this cannot be done—each new observation might require a new calibrator, and in extreme cases a single calibrator will not even suffice for a single Scheduling Block (for example, the case of 2005 YU55 mentioned above).

Fortunately, the SCT knows about moving sources, and their locations will be plotted properly in the bulls-eye source plots in that tool. See Figure 7.5.5 for an example. You can either use the normal search cone with radius method of finding a calibrator, or click on the bulls-eye icon for the moving source itself to identify good calibrators. The rules for choosing a calibrator for a moving source are no different than for other sources at the observing frequency.

6. VLBI at the VLA


These pages describe using the VLA as a VLBI station. Since we are still commissioning this capability, many of the areas such as single dish ('Y1') are incomplete.

The collecting area, receiver suite, and geographical location of the NRAO's Karl G. Jansky Very Large Array (VLA) make it a valuable addition to a VLBI array. The VLA supports standard VLBI observations at frequencies of 1.7, 3.0, 5.0, 8.4, 15, 22, 33, and 43 GHz. Note that P-band has not been commissioned. The VLA can only be used in phased array mode; observing with a single VLA antenna, or "Y1", is only available through the VLBA Resident Shared Risk Observing program. In phased array mode it offers the equivalent sensitivity, including sampling losses, of a single 115-m antenna. The VLA records up to 2 Gbps to a Mark5C recorder. The time and frequency standard is a hydrogen maser. The VLA participates in High Sensitivity Array (HSA) and Global programs. Its participation must be proposed through normal channels and is arranged by the VLA/VLBA scheduler who can be contacted through schedsoc@nrao.edu. Unless for specific reasons, the data should preferably be correlated at the DiFX correlator located at the Science Operations Center in Socorro, NM.

A well phased VLA, with all 27 antennas, when added to the 10 antennas of the VLBA, will improve the sensitivity in a naturally-weighted image by a factor of about 2.4. Baselines between the phased array and any VLBA antenna should be about 4.6 times more sensitive than baselines between any two VLBA antennas. The addition of the VLA also provides one shorter baseline (Y27-PT) than the VLBA which may be valuable for larger sources.

Questions and concerns should be directed to the NRAO Helpdesk.

Phasing the VLA

TelCal, a real-time program, runs at the VLA during the observations deriving the delay & phase corrections for each antenna/polarization/subband. The antenna signals are then corrected in the correlator, summed up, re-quantized to 2-bits, and finally recorded in VDIF format on the Mark5C recorder at the VLA site.

TelCal does not determine the correction until the end of a scan. In practice, there must be at least 3 good subscans, on a sufficiently strong source, to determine the corrections. The user should allow a scan of about 1 minute for phasing (software run by the NRAO analysts will automatically generate subscans), and the corrections will be determined and stored after the 3rd or 4th subscan. Subsequent scans can apply the stored corrections, e.g. on a target which is too weak to determine the correction.

Autophasing should be done on a calibrator which is a point source to the VLA's synthesized beam and, if transferring phases to a target, close to the target. The strength required depends on the frequency, weather and elevation. A good rule of thumb is >100 mJy for 1-12 GHz and >350 mJy for 12-45 GHz. Higher flux densities are required for low elevations particularly at high frequencies. A good place to look for an autophase calibrator is the VLA calibrator list.

Autophase corrections are valid for a duration that depends on the VLA array configuration, observing band, weather, elevation and, e.g., activity level of the sun. The weather and elevation are particularly important for higher frequencies, and solar activity at lower frequencies. Unfortunately the weather and solar activity cannot really be predicted for these fixed date observations. Our advice is to be conservative because an observation that does not contain frequent enough autophasing cannot be fixed in post-processing for the VLBI data, and sensitivity will be lost. When anticipated at the proposal stage, proper planning can mitigate the effects of weather. Consider observing at night when the atmosphere tends to be calmer and solar activity is not an issue, observing in the winter, and avoiding observing at sunrise and sunset. Very broad rules of thumb for frequency of determining and applying new autophase corrections are:

  • C & D config: 20-30 minutes at low frequencies; 10-20 minutes at high frequencies
  • A & B config: 5-10 minutes at low frequencies; 2-5 minutes at high frequencies. May want to avoid observing at 45 GHz in these configurations, also because of the very small synthesized beams.


Restrictions on Phasing

We are still commissioning the phased VLA so there are some restrictions on phasing:

  • Phasing uses all but the edge channels, i.e., a continuum source is assumed.
  • Subarrays are not allowed.
  • No transfer of phasing between subbands.
  • No transfer of phasing across different subband setups. That is, there must be no change in subband setup between determining the phase corrections and applying the phase corrections. Changes in setups include: change observing band, tuning, bandwidth, polarization etc. For example:
  1. You cannot have a set of scans like this:
  • scans 1-6: C-band determine autophase
  • scans 7-12: X-band determine autophase
  • scan 13: C-band apply autophase
  • scan 14: X-band apply autophase
  • scan 15: C-band apply autophase
  • scan 16: X-band apply autophase
  • etc...
  • Instead you should have a set of scans like this:
    • scans 1-6: C-band determine autophase
    • scan 7: C-band apply autophase
    • scan 8: C-band apply autophase
    • scans 9-14: X-band determine autophase
    • scan 15: X-band apply autophase
    • scan 16: X-band apply autophase
    • etc...
  • No transfer of phasing across a reference pointing scan, i.e., bracket your target on each side of the pointing scan with its own calibration scans.

    Basebands and Subbands for Phased VLA

    For the VLA, "baseband" refers to the frequency band that comes out of the samplers at the antenna electronics racks (its meaning is different from the traditional VLBA baseband). Only 8-bit samplers are used, i.e. there are two 1 GHz basebands, however the entire 1 GHz will not be available for phasing. See the VLA Observational Status Summary for a description of available frequencies and tuning restrictions, but note that they are less restrictive than VLBA tuning limitations.

    For the VLA, "subbands" are the continuous blocks of frequency which are correlated by WIDAR and written to the Mark5C unit for VLBI. Two subband pairs (RCP and LCP) may be phased up. Each pair is a different baseband/IF pair AC or BD. So each pair is independently tunable in frequency. Four or 8 subband pairs are also offered as shared risk observing as DDC-8 or PFB modes respectively. See the section on the RDBE in the VLBA OSS for more details on the DDC-8 and PFB modes and their restriction. The subband(s):

    1. The VLA is always dual polarization, even in shared risk modes. A & C (i.e. RCP and LCP) must be the same frequency and B & D (again, RCP and LCP) must be the same frequency.
    2. Must have the same bandwidth.
    3. Bandwidths of 16, 32, 64 and 128 MHz are allowed on a non-shared risk basis. Bandwidths of 1, 2, 4 and 8 MHz have not been tested and are only allowed as shared risk.
    4. Must align, in frequency and width, with the VLBA IF pairs.
    5. The restrictions are fewer for the VLA than for the VLBA or other HSA stations, so please follow the HSA guidelines.
    6. The VLA must be set up to match the VLBA, mixed modes are not allowed.

    Given the above restrictions, the maximum bandwidth is 256 MHz in 2 polarizations, which matches the maximum bandwidth on the VLBA. Given 2 bit sampling as on the VLBA, this gives a maximum data rate of 2 Gbps. Observing with the VLA that does not exactly mimic the VLBA in frequency setup is only available under the VLBA Resident Shared Risk Program. Examples of such RSRO projects would be single polarization observing and observing with the full VLA bandwidth but only recording the smaller bandwidth to be compatible with the VLBA.



    All phased array observations will be fixed date. Please see VLBI @ the VLA: Scheduling Hints.

    Phased array observations will be scheduled in the SCHED program, which is available via anonymous ftp, as described in the SCHED User Manual. Please see VLBI @ the VLA: Scheduling Hints. A keyin file is used to describe the observation and SCHED processes this keyin file and produces files to run the participating telescopes and correlator. One of the files created by SCHED is the VEX (VLBI Experiment) file which describes the entire observation. There is a program called vex2opt which converts the VEX file into files that can be read in by the VLA Observation Preparation Tool (OPT). Vex2opt will be run by NRAO staff once the schedule is submitted. The OPT will then write the observing script for the VLA.

    Standard practice is for the user to send the SCHED keyin file to vlbiobs@lbo.us, NRAO staff will then run SCHED, and distribute any control files to the telescopes participating in the observation. They will run vex2opt and submit the VLA script. However, the user may edit the VLA schedule after it is loaded into the OPT. If the observer adjusts the VLA schedule and the observation fails because of that, then the fault lies solely on the observer and there is no requirement of the NRAO to offer a remedy. Note that SCHED can schedule VLA specific items like pointing, flux calibration, etc., so there is little reason to modify the VLA schedule in the OPT.

    The observation will also produce standard VLA visibility data, so the user will probably want to do standard VLA flux calibration, and other calibration required to use the VLA data by itself.

    If you have problems scheduling or anything else please use the NRAO Helpdesk.


    Log Files

    After the observation is over the observer will receive by email logs from the VLA operator and the VLBA operator.



    Please see the VLA and VLBA Observational Status Summary (OSS) for specifics on frequency ranges and tuning limitations. Generally the VLBA is more restricted than the VLA, so it would be best to start with the VLBA. The VLA and VLBA have similar frequency bands, but the VLA receivers generally have a wider tuning range. The common frequency bands are: L (1.35 - 1.75 GHz), S (2.15 - 2.35), C (3.9 - 7.9), X (8.0 - 8.8), Ku (12.0 - 15.4), K (21.7 - 24.1) and Q (41.0 - 45.0). Currently P-band (0.23-0.47 GHz) cannot be phased.


    VLA Modes

    Only (27 antenna) phased array mode is allowed, single dish is only offered as part of the VLBA Resident Shared Risk Observing program. For situations where the observer may only want the inner antennas, this can be handled as a comment to the operator. All antennas in the subarray will be used for phasing, and all will be included in the phased sum. For instance, you cannot obtain WIDAR correlations for all antennas but use only a subset of those antennas in phasing or in forming the phased sum for VLBI recording.

    There are two basic modes when scheduling the phased array: determine autophasing and apply autophasing.


    Data from the VLA

    The VLA will produce two sets of data: 1) VDIF format data written to Mark5C recorder intended to be correlated with VLBA; and 2) standard WIDAR (VLA) correlator output.

    The standard WIDAR (VLA) correlator output will be available from the NRAO data archive and can be accessed through the observer's my.nrao.edu account. This data will be 64 channels per subband per polarization product and have a 1 second integration time (regardless of configuration).



    When preparing VLA schedule files, the following facts and guidelines should be noted:

    1. Please see VLBI @ the VLA: Scheduling Hints.
    2. The observer should follow the VLA general observing restrictions and advice, such as the one minute setup scan for each correlator configuration (i.e. band) at the beginning of the observation and the amount of overhead needed for reference pointing at the start of an observation.
    3. As a rule of thumb, the source on which you autophase should be a point source (to the VLA's synthesized beam) with >100 mJy for 1-12 GHz and >350 mJy for 12-45 GHz. Note that stronger sources may be required in bad weather and/or low elevation, particularly for higher frequencies.
    4. Assume about 1 minute to determine autophase.
    5. The frequency of determining/applying a new autophase depends on the VLA array configuration, elevation, day or night observations, the observing band and the weather. Please see the Phasing the VLA section for more details.
    6. Subarrays are not allowed.
    7. No pulse calibration system is available at the VLA. If you plan to use more than one subband, then you should observe a strong and compact source to serve as a manual pulse calibrator; see the VLBA Observational Status Summary.
    8. The minimum VLA elevation is 8°. The maximum VLA elevation is 125° if over-the-top antenna motion is allowed by the observer. However, such antenna motion is not normally recommended and not the default. At zenith angles less than about 2°, source tracking can be difficult.
    9. Positions accurate to a VLA synthesized beam (rather than the much larger primary beam) must be used for phased-array observations.
    10. Strong radio frequency interference (rfi) can make it impossible to autophase, so pick your subbands to avoid rfi.
    11. Those using the VLA at frequencies higher than 15 GHz should be aware that antenna pointing can be poor at these wavelengths. Therefore at these frequencies reference pointing for the VLA should be used, again see VLA documentation on high frequency observing.
    12. If you want to derive source flux densities and/or produce images from the standard VLA data, then your VLA observe file should include at least one scan of a primary flux density calibrator for the VLA.
    13. The VLA slews at a slower rate than the VLBA.
    14. If you want to do polarimetry with the standard VLA's data please consult the Polarimetry section of the Guide to Observing with the VLA.

    Questions and concerns should be directed to the NRAO Helpdesk.