Most scheduling blocks (SBs) are observed dynamically, based on factors that NRAO controls and on factors that the observer controls. Such dynamic scheduling enhances science data quality and the array's ability to discharge time-sensitive science. On rare occasions, an SB that requires coordinated observations with other telescopes will be scheduled on a fixed sidereal date.

NRAO staff use the Observation Scheduling Tool (OST) to examine the current observing conditions and the queue of SBs submitted for the current array configuration. The observing conditions are quantified by the RMS phase measured with the Atmospheric Phase Interferometer (API), the wind speed, and the sunrise/sunset time. The OST then applies heuristics to create a schedule, which is just a time series of optimal SBs. The first optimal SB in the series is then sent off for execution by the monitor and control system. Just before that execution completes, the OST again applies heuristics to create a new schedule.

The heuristics used by the OST include the scheduling priority (A, B, or C) assigned by the Time Allocation Committee and the linear-rank score assigned by the Science Review Panel. The heuristics also include SB attributes under observer control, specifically its duration, weather constraints (API and wind limits), observing bands, range of LST start times and, optionally, an earliest start date and a request to avoid sunrise/sunset. The observer can also convey comments to the operator, for example to instruct the operator not to execute the SB for some reason if it has been selected from the queue.

Dynamic scheduling obviously means that the observer does not know when the observations will occur. This must be kept in mind when preparing an SB. In particular, the observer should check that none of the possible LST start times create problems with antenna wraps and the scans of the flux density scale calibrator. These topics are discussed in more detail below.

An antenna is shadowed when its line-of-sight to the source is partially or fully blocked by another antenna in front of it. The shadowed antenna will collect less radiation from the source than if it had not been shadowed, reducing the sensitivity on the baselines to that antenna. Shadowing is more likely to occur when sources are at low elevation and when the antennas are in more compact configurations. The OPT will report, per scan, the maximum amount of shadowing, if any, will occur according to the location in the sky of the target and the configuration of the observations. D-configuration is affected by shadowing more than the other configurations because the antennas are at their closest proximity to each other. If you select "Any" configuration, the OPT will calculate the worst-case scenario by assuming the D-configuration to calculate shadowing.

If any calibration scans will be shadowed for any of the valid LST start times, we recommend increasing the observing time of the calibration source to account for the loss of sensitivity. Table 2.1 shows the amount of shadowing in respect to the fraction of an antenna that is blocked with the corresponding loss of sensitivity. All shadowed baselines will be similarly affected. Note that the loss of sensitivity is not linear with the fractional shadowing.

Avoiding antenna shadowing during the D-configuration relies on the azimuth of the antennas, which is dependent on the location of the source and the LST start time. Therefore, to guarantee no more than a single shadowed antenna, restrict the elevations, if possible, to >40° for D-configuration and >25° for C-configuration. Shadowing is worst along the azimuths of the arms (in both directions), so has a six-fold symmetry. See Figure 2.1 below. Note that the maximum elevation (in degrees) for your target is its Declination plus 56°, so it may not be possible to avoid any shadowing for sources at Dec < -16° or Dec < -31° for D and C configuration, respectively.

Figure 2.1: Plot of shadowed azimuths in D-configuration (black line) and C-configuration (grey line), for three elevations: 25°, 15°, and 8°. (Important note, these plots and the post processing packages (AIPS and CASA) do not calculate shadowing flags for an antenna placed on the Master Pad or the antenna barn.)

Introduction

To help avoid confusion, we will define some terminology. For a visualization of these terms, refer to the wrap diagram below (Figure 2.4.1).

During the observation of a single source, or by switching from one source to the next, the antennas are continuously changing their pointing toward different directions in the sky. The cables for power, communication, and data transfer have a limited length and wrap around the rotation (azimuth) axis of the antenna while the antenna moves. Software directs the antenna movements to prevent them from tightening and snapping when the cables reach the azimuth cable wrap limit, i.e., when they have wrapped ±265° either direction (CW or CCW) from the south (at 180° real azimuth). At a wrap limit, instead of continuous tracking during a scan or directly moving to the next scan at a scan boundary, the antennas will move the opposite long way while unwrapping the cables. As the azimuth slew rate is 40°/min, a full 360° azimuth unwrap will take up 9 minutes (plus some settling time) of unusable observing time. It is important to avoid such a situation and pay attention to the antenna azimuth and wrap during the observation, which means paying attention to the wrap when the azimuth of the scan in the Schedule Summary reports if the scans approach 85° and 445°, or when the scan sequence crosses −85° and 275° azimuth (see Figure 2.4.1 below). Perhaps experiment with different azimuth (and elevation) starting positions to investigate the effect (and starting slew times) for a particular scheduling block (SB). Note: if adjustments are made to the starting azimuth and elevation positions of the SB, please return them to the default positions of 225° azimuth and 35° elevation.

Another inconvenient wrapping situation appears when observations near zenith (elevations larger than about 80°) switch between sources on different azimuth wraps. This happens when a target and calibrator are close to, but on opposite sides of 34.1° (34°04′43.497′′) declination (latitude of the VLA). The OPT will show slew times much longer than expected for the angular source separation, and indicate an azimuth wrap (CW or CCW) on only one of the sources in the reports of the scan list. So even if a calibrator may be a bit further away or less strong, it may be the better option when it is on the same side of zenith. Experiment with different LST start times to investigate the effect for a particular SB if no suitable calibrator can be found on the same side of zenith.

The most important antenna wrap issue arises at the start of the SB as the wrap chosen determines the wrap for the rest of the observation (if not specified in further scans). This wrap should also align the azimuth of antennas combined from previous different subarrays at the start of observing. At the end of the previous program the antennas (or subarrays of antennas) are left pointing in a direction that is dependent on the previous program, and may be any azimuth between −85° and +445°. When the antennas slew toward the first source in the SB, there are two options: clockwise (CW, also known as Right or Outer) or counterclockwise (CCW, also known as Left or Inner); see Figure 2.4.1. In dynamic scheduling, the software will choose the shortest slew to the first source unless otherwise specified in the antenna wrap option in the first scan(s) in the SB. This default software choice may or may not be the optimum case for the observations. To avoid problems, if any of the scans in the SB are observed outside the range between +85° and +275° in the south, then specify the antenna wrap at the start-up sequence to be assured that thereafter the wraps in the reports listing correspond to the actual wraps during the observations. Only when all scans in the SB remain between, or completely avoid the range of +85° and +275° azimuth during any of the start times specified in the LST start range, there is no explicit need to specify any wrap. That is, observations entirely on the south wrap or entirely on the north wrap should be fine, but if you include any of the common standard flux density scale calibrators (i.e., 3C48 or 3C286) most likely the observation will include LSTs where these sources are on the other wrap.

Quick Guide

When to request an antenna wrap: Unless the first source (i.e., setup scan(s) and the first standard observing or reference pointing scan) is always in the unambiguous (south) part of the wrap (85° ≥ AZ ≤ 275°; see Figure 2.4.1 below) during any LST start time within the set range, then you should request an antenna wrap for each scan of the start-up sequence (generally the first 10–15 minutes of the SB). If the SB starts with either 3C286 or 3C48, then an antenna wrap should be selected and continue to specify that wrap for the startup sequence of the SB. Be aware that when 3C286 or 3C48 rise and set they cross the ambiguous (275° ≥ AZ ≤ 85°; see Figure 2.4.1 below) part of the wrap, which can cause problems with unwrapping to the next source (i.e., the complex gain calibrator), so there may not be any time on the first complex gain calibrator scan or the first science target scan.

Which antenna wrap to choose: Look at the first scan under the Schedule Summary report to check if there is an unwrap issue (275° ≥ AZ ≤ 85°) for all times in the LST start range. Follow how the azimuth evolves during the observing block and whether it crosses the 275°/85° boundaries. Select a wrap which takes the antennas in a direction so there is plenty of room for the antennas to move without having to unwrap again; check the LST start range by stepping through at least every hour, making sure that all scans have plenty of on source time (no less than 20sec for standard observing and no less than 2min30sec for reference pointing). Sometimes the LST start range will need to be adjusted to avoid an unwrap.

Antenna Wrap Caveats: When the schedule summary reports a calculated wrap CW or calculated wrap CCW, do not assume that the calculated wrap will be the starting wrap. The calculated wrap is also a good indication that a wrap should be set, but not always in the calculated direction. Do not be alarmed if you request a wrap and it does not appear in the schedule summary report.

Addressing Both Wraps: When an SB can have two LST start ranges to cover the rising and setting of sources, we recommend submitting two SBs to cover the two LST start ranges and their corresponding antenna wraps. For more details on how to create linked SBs, refer to the FAQs page or the Linking SBs section of the OPT manual.

Antenna Wrap Bugs in the OPT:

• In some circumstances, and only for the first and second scan, there is a discrepancy in the reporting of the telescope azimuth. This is apparent when an SB starts on a source that is always in the north (dec > 34°) using the default of azimuth 225° (i.e., in the south). In this case, the OPT may report a confusing starting azimuth on the first scan and an azimuth jump and/or a wrap change for the second scan (even if it is the same source). This bug can be ignored and no wrap need be set.
• A slightly different wrap display bug in the Reports page, is where the first and second scan on the north wrap may differ by 360°.

Detailed Guide

Wrap Diagram

Figure 2.4.1 shows the antenna wrap diagram; this diagram is very helpful in resolving wrap issues. Use this diagram in conjunction with the azimuth column in the scan listing of the Schedule Summary Report table for different LST start times to investigate whether any wrap issues may occur. Often wrap issues will appear when the standard flux density scale calibrator sources 3C286 and 3C48 are scheduled to be observed at rise and/or set at either limit of the LST start range, or when they might be observed during culmination at zenith. That is, many observers should take note to avoid any problems by adhering to the antenna wrap guidelines.

It should be noted, for completeness, that the online software monitors the azimuth of the antennas constantly (i.e., on time scales of seconds; not per scan). As soon as the actual azimuth of a particular antenna hits the −85° or +445° azimuth limit, the antenna will be directed to unwrap and slew in the opposite direction to catch up with the observation instruction. As this happens at the actual azimuth (after the global pointing model and possible additional reference pointing corrections are applied), the time at which a specific (the first) antenna might unwrap may be different from another antenna (the last) by a minute or so. To avoid unwrapping antennas at different times, make sure the scans do not start or stop very close to these azimuth limits for any of the potential LST start times of the SB.

West (Setting sources)		East (Rising sources)
Figure 2.4.1: VLA wrap diagram with Azimuth conventions and readings and the cable wrap limits. Clockwise wrap goes over West (red; outermost curve from the bottom to the top of the spiral) and Counterclockwise over East (green; innermost curve). South (unambiguous) wrap is between azimuth +85° and +275° (black; bottom of the spiral) and North (ambiguous) wrap is in the area at the top, between −85° and +85° or +275° and +445°.

Antenna Wrap & Elevation Considerations

A source is rising when the LST (modulus 24h) is less than the RA of the source. A source is setting when the LST is greater than the RA of the source. Note that for this reasoning, the RA and LST (range) should be within 12h of each other to properly determine rise or set. If the difference is larger, add 24h to either the RA or LST range values, whichever has the lower value in the SB.

• If all of your sources, targets, and calibrators have declinations below about 8.5°, they are all observed in the south wrap and will never reach the ambiguous wrap region: no wrap setting is needed. Note that this almost never happens as you want to include one of your flux density scale calibrators and all have a declination larger than 8.5°. If any of the sources has a declination very close to 8–9°, this rule of thumb may not apply and more care should be taken in checking the observing schedule. This 8.5° limit assumes observations all the way down to the elevation limit of 8°. For observations using higher elevation limits, the 8.5° declination rule becomes a higher-than-nine declination rule, depending on the actual elevation limit:

• If all of your sources (targets and calibrators) have declinations above about 34°, they are all observed in the north wrap and will never use the south wrap region: no wrap setting is needed. Note that this is unlikely unless you use 3C147 as your flux density scale calibrator or 3C295 (in the case you observe only below 2 GHz in D configuration). If any of the sources has a declination very close to 34°, this rule of thumb may not apply and more care should be taken in checking the observing schedule.
• If your first source has a declination of less than about 34° and is rising at the start of the observation, set the starting sequence wraps (first 10–15 minutes worth of scans at the start of the block) to CCW (left). If the first source is setting, set the wrap to CW (right).
• If your first source has a declination of more than about 34° (i.e., it will be observed in the north), then there are two options that will only make a difference once the next source in the sequence has a declination below about 34° (otherwise you can use the second rule above). If that next southern declination source at the time of the observing LST (i.e., the starting LST time plus the duration of time into the observation) is rising then set the starting sequence (first 10–15 minute worth of scans at the start of the block) wraps to CCW (left). If this southern source is setting, set the beginning sequence wraps to CW (right).

Always make sure to check the wraps in the Reports tab of the SB in the OPT. If in doubt or confused, please leave the wrap designation to "No Preference" and consult the NRAO Helpdesk.

For more detailed information on setting antenna wraps, see the section How to Proceed below.

Wrap Issues & Standard Flux Density Scale Calibrators

The default standard flux density scale calibrators for the VLA, 3C286 (J1331+3030) and 3C48 (J0137+3309), are nicely separated by about 12 hours in Right Ascension (RA) but, unfortunately, have two major inconveniences. First, their declination is almost the latitude of the VLA (34.1°), which causes them to culminate almost at zenith on the southern wrap and, second, while they are mostly in the southern wrap, they rise and set in the northern wrap. Catching these flux density scale calibrators in short SBs may be difficult for target observations in certain regions distant from these calibrators on the sky. Therefore, it quite often happens that the flux density scale calibrator is observed in these dynamic SBs when a flux density scale calibrator just rises or just sets, where wrap issues may become a problem for targets on the southern wrap. For targets on the northern wrap, even though the flux density scale calibrators may be high in the sky, it decreases the usable LST start range to place the flux density scale calibration scans if wrap issues are to be avoided. See Table 2.4.2 and Figure 2.4.2 for details.

Table 2.4.2: Wraps and wrap limits for Standard Flux Density Scale Calibrators at the VLA

Southern wrap standard VLA flux density scale calibrators

	North Wrap		South Wrap				North Wrap
	RISE AT		AZ= 85/445°		AZ= −85/275°		SET AT
	AZ	LST	LST	EL	EL	LST	LST	AZ
3C48	55/415°	18:42	23:53	68°	68°	03:23	08:33	−56/304°
3C286	59/419°	06:45	10:53	57°	57°	16:09	20:18	−58/302°
3C138†	75/435°	23:16	00:29	23°	23°	10:13	11:27	−75/285°

† 3C138 has varied in flux density over the last few years, but appears to have settled back to its original flux density.

Northern wrap standard VLA flux density scale calibrators

	RISE AT		EASTERNMOST AZIMUTH	WESTERNMOST AZIMUTH	SET AT
AZ	LST	LST			AZ
3C147	33/393°	21:32	51/411°	−51/309°	13:53	−33/327°
3C295‡	30/390°	05:45	48/408°	−48/312°	22:38	−30/330°

‡ 3C295 is only useful at low frequencies and short baselines, i.e., typically at P- and L-band in D configuration.

Note: CASA does not have a flux density scale model for 3C295.

 

Figure 2.4.2: Antenna wrap as function of LST for the standard calibrators. (Click image for a larger view.)

When the source is observed at an LST shown in green in Figure 2.4.2 (above), the source is in the south and typically no wrap issues arise. When the LST is red, the source is in the northern wrap and either a CCW (left; at rise) or a CW (right; at set) wrap should be specified in the scan. For 3C147 and 3C295 the wrap should be specified as well; the wrap, however, will depend on the efficiency to reach the other sources specified in the schedule. The yellow LST regions are when the sources, 3C48 and 3C286, are at an elevation above 80° and should probably be avoided during high frequency observing. (Note, low frequency observing can observe up to 85° in elevation, too much higher in elevation can cause antenna wrap issues.)

How to Proceed

Initially, it is best not to worry about the antenna wrap until the SB has been created. Then extensively check the azimuth of the scans in the SB for all LST start times in the anticipated LST start time range. This action will reveal if any wrap issues occur for some or all of the possible LST start times.

Aside from any wrapping issues, remember that 3C286 and 3C48 culminate near zenith. To avoid pointing problems at high elevations (≥ 80°) during high frequency observations, it is probably best to avoid having scans for these flux density scale calibrators during the LST range 12:47–14:15 for 3C286 and the range 00:50–02:25 for 3C48. Restrict the LST start range so the scans with 3C286 and/or 3C48 will not happen for these LST times, or perhaps even split the LST start range in two (or more) non-overlapping LST start ranges in the INFORMATION tab of the SB. Ideally, one would want to observe the flux density scale calibrator at about the same elevation as the target sources to obtain a more accurate flux density, especially at the higher frequencies. However, this is hard to plan and not always manageable with dynamic scheduling: it would require a restricted LST start range which would decrease observing chances. Another suggestion, for similar reasons, is to try and observe the flux density or bandpass calibrator when the target source passes through zenith (if its declination is near 34°).

Assuming that the target sources are not scattered all over the sky (e.g., for a survey), there are essentially four cases when using 3C286, 3C48, and/or 3C138:

• 3C286/3C48 can only be observed between rise and culmination in the (South)East: The target source is leading the flux density scale calibrator in the south or north of zenith, typically by up to 6 hours in RA (otherwise the other flux density scale calibrator is more likely to be chosen).
• For dec < 34.1° the target source will be south of zenith and set after the flux density scale calibrator rises. There should be no wrap issues if the wrap directs the antennas to observe the flux density scale calibrator in the CCW (left) wrap or when the LST start range is limited such that the flux density scale calibrator scan can only happen after the LST time for AZ = 85°/445° for that flux calibrator in the table above. Typically, the flux density scale calibrator is observed at the end of the SB.
• For dec > 34.1° the target source will be north of zenith and stay on the north wrap. There should be no wrap issues if the flux density scale calibrator is observed before the LST time for AZ = 85°/445° for that flux density scale calibrator in the table above. Typically the flux density scale calibrator is observed whenever the scan can fit in the LST range for the eastern north wrap, i.e., between rise time LST and the LST time for AZ = 85°/445° for that flux density scale calibrator in the table above.
• 3C286/3C48 can only be observed between culmination in the (South)West and set: The target source is trailing the flux density scale calibrator in the south or north of zenith, typically by up to 6 hours in RA (otherwise the other flux density scale calibrator is more likely to be chosen).
• For dec < 34.1° the target source will be south of zenith and rise before the flux density scale calibrator sets. There should be no wrap issues if the wrap directs the antennas to observe the flux density scale calibrator in the clockwise CW (right) wrap or when the LST start range is limited such that the flux density scale calibrator scan can only happen before the LST time for AZ = −85°/275° for that flux density scale calibrator in the table above. Typically, the flux density scale calibrator is observed at the start of the SB.
• For dec > 34.1° the target source will be north of zenith and stay on the north wrap. There should be no wrap issues if the flux density scale calibrator is observed after the LST time for AZ = −85°/275° for that flux density scale calibrator in the table above. Typically the flux density scale calibrator is observed whenever the scan can fit in the LST range for the western north wrap, i.e., between the LST time for AZ = −85°/275° and set time LST for that flux density scale calibrator in the table above.
• 3C286/3C48 can be observed throughout the SB duration for all LST start times: For this case one would probably choose whether to put the flux density scale calibrator close to the start or close to the end of the SB. Placing it in the middle would not minimize the chances of culminating during the SB and introduce wrapping issues for northern wrap target sources. By placing the flux density scale calibrator observations at the start or the end of the SB, either of the above cases would apply as guideline on how to proceed. Continue checking the azimuth for different LST start times and perhaps even change the strategy on where to place the flux density scale calibrator observations.
• More complicated than any of the three above: If the SB cannot be converted to a simpler case by grouping source scans to the same wrap and/or choosing the flux density scale calibration scans at the start or end of the SB, this case may become more like a trial-and-error approach. Usually this is not a problem; however, if it remains, continue checking the azimuth for different LST start times, maybe limit the LST start range even further and/or perhaps even change the strategy on where to place the flux density scale calibrator observations.

After creating the SB, please check the wraps and look out for possible issues for all possible LST start times in the LST start range before submitting the SB. This may be time consuming but will prevent surprises during observing and in the data. When setting a wrap at the start of the SB, please continue to specify the same wrap during the start-up sequence, i.e., for all the scans that make up the first 10–15 minutes for the SB to force it to be effective.

Note that the slew to the first source, and the calculated wrap it chooses is calculated from the assumed starting position as specified in the INFORMATION tab of the SB. By default, this starting position is pointing toward the south; but the actual starting position is from wherever the previous program has left the antennas pointing (anywhere from azimuth −85° to +445°), and not necessarily the same direction for each antenna. Playing around with the starting azimuth may help to determine the maximum slew time for the worst case scenario and whether different wraps are possible for different LST start times. For testing maximum slew times at the start of the observation the worst cases arise, with the wraps specified as suggested above:

• When one or more antennas are at AZ = −85° and the SB is started at the latest possible LST start time of the LST start range, and;
• When one or more antennas are at AZ = +445° and the SB is started at the earliest possible LST start time of the LST start range.

For high frequency observations, there should be at least 2min30sec on source time in the reference pointing scan in addition to the worst case slew time. And to complicate it even further, the worst pointing case may not be at the worst starting LST.

Please ask the NRAO Helpdesk if you need assistance.

The Sun is a bright and variable radio source and can be a problem for VLA observations at all frequencies if it is near the target source. Phase fluctuations and elevated system temperatures will result when observing too close to the Sun. This section gives guidelines on how far sources should be from the Sun as a function of observing band at the VLA, as well as some links to tools to help in planning observations. Please note that these guidelines should not be confused with avoiding daytime observing for RFI reasons, or avoiding sunrise and sunset for phase stability reasons.

The OPT and the Observation Scheduling Tool (OST) currently do not look for or flag SBs containing sources which will be observed too close to the Sun. It is the responsibility of the observer, therefore, to monitor both if and when their sources will be too close to the Sun and the activity of the Sun. The VLA Sun & Moon Distance Check Tool can help determine if and when a source will be too close to the Sun. That tool also gives the distance to the Moon, although typically the Moon is not a problem unless it is very nearby (within a few primary beam FWHMs). A useful web page providing information on solar activity is: NOAA Space Weather site. If any of the target sources in an SB are too near the Sun (especially if it is particularly active), then the SB should not be submitted or, if already submitted, should be unsubmitted. Once the sources are all far enough away from the Sun, the SB can be (re)submitted. Another useful web page is the near real-time and archival solar activity (< 100) MHz all-sky observations by the Long Wavelength Array (LWA), located adjacent to the VLA.

Table 2.4 shows the minimum distance from the Sun for 10° phase errors (Φ), assuming the longest baselines can be tolerated. Depending on the solar activity of the Sun, the acceptable observing distance will increase.

The numbers in table 2.4 were calculated via:

[display]R_{deg}≈\left(\frac{7\lambda_{cm} * B^{0.29}_{km}}{\phi_{deg}}\right)^{0.71}[/display]

where B_km is the baseline in km, λ_cm is the frequency in cm, and Φ_deg is the phase error in degrees. Details on how this equation was derived are in VLA Test Memo 236, "How close to the Sun should we observe with the VLA?" Another useful memo is EVLA Memo 136, "EVLA Measurements Close to the Sun: Elevated System Temperatures."

More details about the effect of the Sun on VLA observations may be found in the Low Frequency and Very Low Frequency strategy guides.

The dynamic scheduler uses the current API and wind speed, as well as the predicted wind speed when deciding whether to run an observation, i.e. a SB. If the API, current or future wind speeds are above the constraints set in the SB using the OPT then the SB will not be selected. This can make it difficult to observe high frequency SBs.

The wind speed limit is based on the fact that wind will push the VLA dishes around causing the primary beam to move on the sky. At higher frequencies the primary beam is smaller and so it is easier to move a dish enough to move the target out of the center of the primary beam, therefore the wind speed limit is lower at higher frequencies. Wind speeds higher than the limits will cause the amplitudes to vary which cannot be calibrated after the observation.

However, the recommended API limits are based on estimates of the maximum API limit assuming that the science target could not or should not be self-calibrated. If the science target can be self-calibrated then the API limit can be much higher giving the SB a greater chance to be observed. Starting in December 2022 there are two possible Atmospheric Phase Limits (APLs) to choose from depending on whether or not the science target can be self-calibrated.

The following table lists the default weather constraints available in the Observation Preparation Tool (OPT) for each observing band. An observer may choose between the conservative APL or the less conservative self-calibration APL. The wind limit will remain the same between either APL choice.

How to choose the Atmospheric Phase Limit for your SB

Choose the lower (original) limit if:

• The science target is too faint to self-cal (see below), or
• The flux density of the science target is unknown and likely faint, or
• There is a scientific reason not to self-calibrate, e.g., when the scientific goal is to perform astrometry

Choose the higher limit if:

• It is desirable to self-calibrate the science target, and
• The signal to noise ratio (SNR) of the science target is > 3 in a solution interval using the subband width (for continuum) or the anticipated line/channel width (for spectral line) for a single baseline and polarization.
• a solution interval (solint) should be based on how fast the atmospheric phases are likely to be changing and therefore shorter for higher frequencies and longer baselines.
• for a 25 antenna VLA the SNR of the target peak flux density/rms_solint should be ≥20

Examples:

• Example 1: The science target is a compact source with a peak flux density of 15mJy/beam. Observing occurs  in A-configuration at Ka band continuum. Should we use the higher APL?
• Estimate the solint. The recommended calibration cycle time for A-configuration and Ka band is 3 minutes so we assume that the atmospheric phases will vary faster than that with the higher APL (which allows for observations at less favorable weather during the observation). So let's pick a solint of 30 seconds, which would allow ~6 solutions over 3 minutes to track the variations.
• Determine the rms for 30 seconds and a bandwidth of 128MHz, a single polarization and 25 antennas in Ka band using the VLA Exposure Calculator.
                       rms_solint=0.48mJy/beam
• Calculate the SNR: SNR=15/0.48=31 (peak/rms, all in mJy/beam)
                  As this ratio is over 20, this source is good to self-calibrate and therefore one can use the higher APL
• Example 2: The science target is a maser line in K band with a line width of ~3km/s (~220kHz). The expected peak flux of the maser is 147mJy over 3km/s or in a ~220 kHz channel and the observation occurs in C-configuration.
• Estimate the solint. The recommended calibration cycle time for C-configuration and K band is 6 minutes so we assume that the atmospheric phases will vary faster than that with the higher APL. So let's pick a solint of 1 minute, which would allow ~6 solutions over 6 minutes to track the variations.

• Determine the rms for 1 minute and a bandwidth of 3km/s or ~220 kHz, a single polarization and 25 antennas in K band using the VLA Exposure Calculator.
                       rms_solint=10.5mJy/beam
• Calculate the SNR: SNR=147/10.5=14 (peak/rms, all in mJy/beam)
                  This ratio is not near 20 so this maser source is probably not a good source to self-calibrate; use the lower, more restrictive APL.

Caveats:

• The theoretical rms_solint might be lower than the actual image rms for many reasons (e.g. RFI, overhead unaccounted for) and therefore self-calibration could be difficult. The SNR ≥ 20 is a slight overestimate of the SNR needed because of the likelihood that the rms will be slightly higher than that given by the VLA Exposure Calculator.
• If the target is dominated by extended emission, the flux detected by longer baselines may be much lower than the peak. It then might be difficult to get good self-calibration solutions on the longer baselines, although uv-restrictions in the self-calibration procedure may help.
• The recommendations and examples above are conservative. There are tricks that can be used to self-calibrate in non-ideal situations. If you are an experienced user and you know you can self-calibrate your science target then please use the higher APL; in that case doing these calculations can be skipped.

This document is intended for observers planning VLA observations at high frequencies, specifically Ku-band (12–18 GHz), K-band (18–26.5 GHz), Ka-band (26.5–40 GHz), and Q-band (40–50 GHz). All of these receiver bands share at least some of the same problems and solutions as compared to lower frequency bands (e.g., the need to account for antenna pointing, atmospheric phase coherence and opacity calibration). In particular, the calibration overheads for high frequency observing are typically considerably larger than for lower frequency observations, significantly impacting the overall time request. As described below (and in more detail within the Calibration section), the overheads grow with increasing frequency and maximum baseline length.

Ku-band, being the lowest of these high frequency bands, can, in some cases, be more suitably grouped with lower frequencies, e.g., when observing at or below 15 GHz only. We will point out some of those cases in this document.

For an instrumental overview, general performance, and some specifics of receiver band (e.g., sensitivity, etc.) of the VLA, consult the current Observational Status Summary (OSS). 

Calibration

Antenna Reference Pointing

For high-frequency observations above ~15 GHz, the a priori antenna pointing is generally not accurate enough, and thus pointing calibration is needed.

• Calibrate the pointing by observing a nearby calibrator in interferometric pointing mode. This calibrator should ideally be within 10° of the sky position of interest, as pointing corrections are needed for the azimuth and elevation near the target. The local pointing corrections can then be applied to subsequent scans.
• For this, choose a strong point-like calibrator (calibrator code P or S, but never a W, X, or ?) and bright (0.3 Jy or brighter) at X-band using the NRAO default resource in the OPT (X band pointing).
• Once a pointing calibration is determined, it typically remains valid for about 20° away from the AZ/EL for which the pointing was obtained, and for a time period determined by changes in temperature. This translates to the need of repeating the reference pointing every hour or so during nighttime, and every 30-40 minutes during daytime observing (including sunrise/sunset).
• Often the flux density and bandpass calibrators need pointing calibrations that differ from the target pointing calibrations as they typically are far away from the target source. These calibrators commonly use pointing scans on themselves.
• A pointing calibration scan needs an on-source time of 2m30s.

Note that near zenith (elevation > 80°) source tracking becomes difficult. Therefore, it is recommended to avoid such source elevations during the observation preparation setup.

For more details see the Antenna Reference Pointing Calibration guidelines located in the Calibration section.

Absolute Flux Density Scale 

In most observations, the accuracy of the absolute flux density scale is tied to the final uncertainty of whatever analysis you plan for your science target. Therefore, it is important to observe a known flux density standard with high signal-to-noise. Absolute flux density scale calibration is more difficult at higher frequencies because:

• all of the standard absolute flux density scale calibrators are significantly weaker at higher frequencies, and;
• they also range from being slightly to very resolved in the smallest to largest configurations, respectively.

For this reason, it is important to use a model image for the absolute flux density scale calibration in your data reduction. Models are already available in both CASA and AIPS for the standard flux density scale calibrators: 3C286 (J1331+3030), 3C48 (J0137+3309), 3C147 (J0542+498), and 3C138** (J0521+1638). Note that because 3C138** and 3C147 exhibit variability, 3C286 and 3C48 are better for absolute flux density scale calibration at the higher frequencies of the VLA.

It can be advantageous to observe your flux density scale calibrator as close as possible in elevation to your target(s), which will automatically reduce uncertainties that arise from opacity and gain curve corrections. These uncertainties may be large, in part because AIPS and CASA produce rough estimates of the opacity based on the VLA's weather station. Note that tipping scans to measure the opacity can be scheduled with the OPT but are not currently recommended due to the lack of analysis routines.

As described below, the phase fluctuates quickly at high frequencies, so in order not to de-correlate the amplitude of your flux density calibrator you will need to do a phase-only calibration that can achieve a S/N of at least 5 on a single baseline (assuming single polarization and the bandwidth of a single spectral window) in a solution interval shorter than the timescale of large phase variations (typically a few seconds at the highest frequencies/longest baselines). The required S/N for a single baseline over the full observing time of the absolute flux density calibrator should be > 20.

Following this advice, you should be able to get to an absolute accuracy of about 10%. If your science requires more detailed understanding of the absolute flux density calibration precision, it is wise to include a brief observation of a second known flux density standard if possible (this may be difficult to schedule in some cases). In this case the second source should also be observed at similar elevation to your target. Note that the VLA Calibration Pipeline will only use the first flux density calibrator seen in the schedule for use across all targets in the schedule.

For more details, refer to the Flux Density Scale Calibration in the Calibration section.

** The flux density scale calibrator 3C138 is currently undergoing a flare. From VLA calibration pipeline results, we have noticed that 3C138 is deviating from the model. The amount of this deviation is still being investigated by NRAO staff, but does seem to effect frequencies of 10 GHz and higher. At K and Ka-bands the magnitude of the flare is currently of order 40-50% compared to Perley-Butler 2017 flux scale. If you care about the flux density scale of your observations above 10 GHz, monitoring datasets are publicly available in the archive under project code TCAL0009, from which you may find an updated flux density ratio to use for your data.

Bandpass (and Delay)

For the VLA, it is essential to calibrate the spectral response of each correlator mode used, even for purely continuum projects. The requirements for bandpass calibration, however, are very dependent on your science goals/type of observation. If you are observing spectral lines, ensure you have a strong enough calibrator in order to perform bandpass calibration. For more details, refer to the Bandpass and Delay Calibration in the Calibration section, or the Spectral Line section.

Complex Gain

Phase

Phase fluctuations are caused by variations in the amount of precipitable water vapor (PWV) in the troposphere, as a function of time and position on the sky. This variation acts as an additional source of phase noise when observing at high frequencies.Phase calibration at high frequencies comes down to these questions:

• Can I use self-calibration? If your target source is strong (generally 0.1 Jy over a 1 GHz frequency band, although you might be able to use somewhat weaker sources) then you can apply self-calibration to the source, and it is sufficient to observe the calibrator every 30 minutes at high frequencies.
  • Note that self-calibration may introduce a shift in the source position in your final image. Normally this is not a serious issue. But if you need high astrometric accuracy, then self-calibration may not be a viable option.
  • If your source contains a strong maser, you can use the maser itself for self-calibration.

• If you cannot use self-calibration:
• How close the calibrator should be to the target? At these high frequencies, choose a calibrator as close as possible to your target source even if it is weaker compared to other calibrators farther away.
• What is the cycle time needed to track the phases (so one can remove the variations)? This depends on the frequency and the array configuration. See the Cycle Time subsection below.

Amplitude

Variations in amplitude tend to happen on much larger time scales than phase (minutes rather than seconds). This is because, unlike phase which varies due to turbulence in the troposphere, amplitude is mostly dependent on variations in the integrated precipitable water vapor (PWV) column (i.e., atmospheric opacity). PWV changes with elevation—you look through more water column at low elevation than at high elevation—and time, as clouds with varying water content move across the array. The phase calibrator observations are typically adequate to also calibrate the amplitude variations. Since amplitude is less variable than phase, if you have a weak phase calibrator you may want to average several phase calibrator scans to obtain adequate S/N for an accurate amplitude solution. This is rarely a problem unless the weather is changing very rapidly—in which case the overall calibration is likely to be poor regardless of what you do about amplitude.

In borderline cases, where you might be able to recover some data taken during poor(ish) weather conditions, take care in post processing and be aware that:

• Decorrelation can cause baseline-dependent amplitude variations;
• Antennas with unrefined positions (e.g., directly after an antenna move to a new antenna pad) will cause increased problems in patchy cloud conditions because, if they are looking through different water columns, the amplitude corrections will not be well-determined. In this case it may be best to not include these antennas in the data reduction.

For more details, refer to the Complex Gain Calibration in the Calibration section.

Cycle Time

For information on rapid phase calibration and the Atmospheric Phase Interferometer (API), refer to the VLA OSS. More details regarding cycle times may be found under the Calibration Cycles of the Calibration section.

Polarization

Information on polarization, including the most commonly used polarization calibrators, can be found in the Polarimetry guidelines.

An Observing Strategy Consideration

Are you doing multiple high frequencies or a mix of high and low frequencies? If so, start the SB with the highest frequency first and progress to the lower frequencies through the SB. Not only are the weather conditions at the start of the observation better than the specified constraints (weather conditions may deteriorate after the start), it also allows for slewing to the pointing source during the start-up time. This start-up time includes all of the initial setup scans as well as at least 2.5 minutes on source in the interferometric pointing mode.

Before submitting a scheduling block (SB), refer to the Presubmission Checklists:

Instrument Validation

SB Validation

Please submit any questions to the NRAO Helpdesk.

This document is intended for observers planning VLA observations at low frequencies, specifically L-band (1–2 GHz), S-band (2–4 GHz), C-band (4–8 GHz), and X-band (8–12 GHz). These four receiver bands share at least some of the same problems and solutions, as compared to higher frequency bands. Detailed guidelines for calibration are given in the Calibration section of the VLA observing guide. For an instrumental overview, general performance, and some specifics of receiver band (e.g., sensitivity, etc.) of the VLA, consult the current Observational Status Summary (OSS).

Observing Considerations

Receiver band changes; switching to and from P-band

The OPT accounts for a default 20 seconds to switch between bands (subreflector rotation and focus) which is typically sufficient. However, when switching to/from P-band and L-band or S-band an additional 15s is needed which currently is not accounted for in the OPT. Even when there is no actual telescope slew motion when the switch involves observing the same source, the Reports tab will only show 20s "slew" overhead. For these band switches please be aware of this extra overhead and allow a minimum of 35 seconds on source for the scan following the receiver band switch. When switching to/from P-band to other bands than L or S, the 20 seconds overhead is adequate.

Radio Frequency Interference (RFI)

RFI is a major issue at L, S, and C-bands and, to a certain extent, at X-band. More information about RFI can be found in the VLA RFI page. Here we note that S-band (2–4 GHz) is subject to very strong RFI from a number of satellites, in particular those providing satellite radio service. A satellite passing through the VLA beam during the initial slew may play havoc with the attenuators. To properly set up S-band observations, please refer to Special Case I in the 8/3-bit Attenuation and Setup Scans page. To set up C- and X-band 3-bit observations near the Clarke belt, please review the Low Frequency Observations in the Presence of Strong RFI section in the 8/3-bit Attenuation and Setup Scans page.

Note: C-band is also impacted by strong RFI caused by microwave links near 6 GHz in the A and B configurations. As a result, 3-bit data obtained with the standard setup are corrupted. We advise observers to use a setup with mixed 3-bit and 8-bit samplers. Refer to the C-band Observations in the Presence of Strong RFI Microwave Links section for more details.

Solar Activity

High solar activity results in emission that can severely affect the data to such a degree as to potentially render the observations useless. Also, such activity causes disturbing ionospheric effects. Therefore, it is imperative to avoid observing at L- and S-bands during daytime (including sunrise and sunset^†) at times of high solar activity, i.e., when solar flares occur (which happens more often during solar maximum). Solar flares with as much as a million Jy at L-band with narrow angular extents are a source of major interference. These flares are equivalent to bright unresolved sources with time-varying flux densities making it very difficult, if not impossible, to remove their effects. As a consequence, the resulting images will be of poor quality and low dynamic range.

Even the quiet Sun can pose problems for low-frequency observations, resulting in degraded image quality if the Sun is too close to the science target. The Avoiding the Sun section gives guidelines on how far sources should be from the (quiet) Sun as a function of VLA observing band and configuration.

Important Note: It is the responsibility of the observer to monitor if and when their sources will be too close to the Sun, in addition to monitoring the activity of the Sun. If you do not want your SB(s) executed on the array because of a solar flare, which would take a few days to reach Earth after the occurrence of an eruption on the Sun, you should cancel the submission of your SB(s) through the OPT and resubmit them later. Do not rely on the operator to know about conditions relating to solar flares.

Some useful links:

• Solar activity monitoring: Solar activity and general space weather can be reviewed at the NOAA Space Weather site. The site provides solar activity forecasts and geophysical (geomagnetic field) activity forecasts along with GOES X-ray flux values.
• Ionosphere monitoring: Global Ionospheric TEC maps.
• Near real-time and archival solar activity can be seen from < 100 MHz all-sky observations by the LWA.

^†Note: The statement to avoid observing at L- and S-bands during daytime (including sunrise and sunset) at times of high solar activity should not translate to checking the boxes of AVOID SUNRISE and/or AVOID SUNSET in the OPT, because these will not prohibit observing at daytime during a solar flare event. These options in the OPT are not meant to address or avoid solar activity but to avoid ionospheric phase fluctuations for low frequency observations and strong temperature gradients for high frequency observations during sunrise and sunset. 

Calibration

A number of calibrator observations are needed for the subsequent data reductions. These usually include: flux density scale calibrator, complex gain (phase and amplitude gain) calibrator, and polarization calibrators (if polarization is part of your science objective). You will also need to observe a bandpass calibrator to correct for the delays as well as the relative gains of the spectral channels, even if the observations are intended for continuum science. It is recommended that the flux density scale calibrator be observed at least once in a scheduling block (SB). The flux density scale calibrator itself, if desired, can be used to correct for the bandpass and antenna based delays, considering that the standard VLA flux density calibrators are strong sources at L, S, C, and X-bands. 

Absolute Flux Density Scale

Observe one of the standard VLA flux density calibrators to achieve absolute gain calibration: 3C286, 3C147, 3C48, 3C138**. The calibrator 3C295 may also be an option, however its use should be limited to L-band (or lower) frequencies and only in C and D array configurations.

** The flux density scale calibrator 3C138 is currently undergoing a flare. From VLA calibration pipeline results, we have noticed that 3C138 is deviating from the model. The amount of this deviation is still being investigated by NRAO staff, but does seem to effect frequencies of 10 GHz and higher. At K and Ka-bands the magnitude of the flare is currently of order 40-50% compared to Perley-Butler 2017 flux scale. If you care about the flux density scale of your observations above 10 GHz, monitoring datasets are publicly available in the archive under project code TCAL0009, from which you may find an updated flux density ratio to use for your data.

Bandpass (and Delay)

For the VLA, it is essential to calibrate the spectral response of each correlator mode used, even for purely continuum projects. The requirements for bandpass calibration, however, are very dependent on your science goals/type of observation. If you are observing spectral lines, ensure you have a strong enough calibrator in order to perform bandpass calibration. For the VLA low frequency bands, this calibrator could be the same source as the flux density scale calibrator. However, this will still depend on the specifics of your observations. For more details, refer to the Bandpass and Delay Calibration in the Calibration section, or the Spectral Line section. 

Complex Gain (phase and amplitude gain)

Complex gain calibrators need to be observed both before and after the target observation(s). In the choice of the complex gain calibrator, obviously a calibrator close to your target source will decrease slewing times. However, for the L, S, C and X-bands, we recommend choosing a strong P calibrator farther away, rather than a weak nearby S calibrator. See the VLA calibrator manual for a description of the calibrator codes P and S. It is highly recommended that the complex gain calibrator be within 15° of the target source(s).

For more details on the above calibrators, refer to the Calibration section.

Cycle Time

For information on rapid phase calibration and the Atmospheric Phase Interferometer (API), refer to the VLA OSS. More details regarding cycle times may be found under the Calibration Cycles of the Calibration section.

Polarization

Information on polarization, including the most commonly used polarization calibrators, can be found in the Polarimetry section. (Please note that avoiding daytime observations is even more critical for polarization observations, especially during peak solar activity, due to ionospheric Faraday rotation.)

Before submitting a scheduling block (SB), refer to the Presubmission Checklists:

Instrument Validation

SB Validation

Please submit any questions to the NRAO Helpdesk.

This document is intended for observers planning VLA observations at very low frequencies, and in particular at P-band (230–470 MHz). Polarization observations with P-band are currently offered through Shared-Risk Observing (SRO). The 4-band (54–86 MHz) system is currently available for continuum observations through SRO as well while it is undergoing commissioning. Joint 4-band observations with the Long Wavelength Array in New Mexico (ELWA) are only available through the Resident Shared Risk Observing (RSRO) program as described in the VLA Observational Status Summary (OSS). Observing time to use the ELWA may be requested through the RSRO program.

Important Notice:

The very low frequency bands (P and 4) of the VLA provide linear polarization, while all the other bands (L to Q; from 1 to 50 GHz) provide circular polarization. Whereas CASA version 4.6 and later in principle can load those data sets into a single measurement set for processing, it is strongly recommended to put the linearly polarized data in a measurement set of its own, different from the circularly polarized data, and process the 4 and P-band data separately from the other bands. In CASA convert the SDM-BDF to a measurement set, then use split to separate the linearly polarized data. When using BDF2AIPS in AIPS, the data will always be split per band for separate processing.

Observing Considerations

While preparing observations at very low frequencies, the following issues need to be kept in mind because they can have severe consequences:

Radio Frequency Interference (RFI)

RFI is a major issue at P-band (list of P-band RFI). Of the 256 MHz frequency span that P-band observations may cover, about 30-40% may be affected by RFI. Figure 6.3.1 shows time vs. frequency of a single short baseline. The frequency range is 224-352 MHz (top) and 352-480 MHz (bottom), and the channel separation is 125 kHz. Hanning smoothing was applied to minimize Gibbs ringing.

Figure 6.3.1: P-band time vs. frequency for short baseline pair.

At 4-band, narrow-band RFI is generally not a major issue since most high-power analog TV channels have disappeared with only low-power TV stations transmitting below 100 MHz. Note, the presence of a self-generated RFI comb peaking at 60 MHz with a spacing of 5 MHz at antennas with old antenna control units (ACUs). This issue will improve over time with more antennas having the new generation ACUs. The comb can easily be excised, affecting only a small number of channels. Another hard to detect source of RFI, of particular concern in more compact configurations, is produced by arcing on powerlines. This produces primarily bursts of broad-band noise and can significantly affect the sensitivity of antennas near overhead powerlines and create spurious high cross-correlations. While we try to address powerline issues as they arise, the RFI environment at the VLA is still being evaluated on an ongoing basis.

Solar Activity

While observing at P-band, the following guidelines may be followed while the Sun is quiet:

• In general, make sure that the Sun is more than 30° away from your sources. See the Avoiding the Sun section for more array configuration dependent details.
• In D-configuration, the solar disk will likely cause a problem on the short baselines (< 100m) if the Sun is less than 90° away from the observed source.
• The phases are always calibratable except during solar storms.

When the Sun is active, high solar activity results in emission that can severely affect the data to such a degree as to potentially render your observations useless. Also, such activity causes disturbing ionospheric effects. Therefore, it is imperative to avoid observing at very low frequencies at daytime (including sunrise and sunset^†) during times of high solar activity, i.e., when solar flares occur and which are more frequent during solar maximum. Solar flares with as much as a million Jy at P-band with narrow angular extents are a source of major interference. These flares are equivalent to bright, unresolved sources with time-varying flux densities that make it very difficult, if not impossible, to remove their effects. As a consequence, the resulting images will be of poor quality and low dynamic range.

Important Note: It is the responsibility of the observer to monitor if and when their sources will be too close to the Sun in addition to the activity of the Sun. If you do not want your SB(s) executed on the array due to a solar flare, which would take a few days to reach Earth after the occurrence of an eruption on the Sun, you should cancel the submission of your SB(s) through the OPT and resubmit them later. Do not rely on the operator to know about conditions relating to solar flares.

Some useful links:

• Solar activity monitoring: Solar activity and general space weather can be reviewed at the NOAA site. The site provides solar activity forecasts and geophysical (geomagnetic field) activity forecasts along with GOES X-ray flux values.
• Ionosphere monitoring: Global Ionospheric TEC maps or Local Ionospheric Weather from LWA.
• Near real-time and archival solar activity can be seen from < 100 MHz all-sky observations by the LWA.

^†Note:The statement to avoid observing at 4/P-band at daytime (including sunrise and sunset) during times of high solar activity should not translate to checking the boxes of AVOID SUNRISE and/or AVOID SUNSET in the OPT, because these will not prohibit observing at daytime during a solar flare event. Also, these options in the OPT are not meant to address or avoid solar activity, but to avoid ionospheric phase fluctuations for low frequency observations and strong temperature gradients for high frequency observations during sunrise and sunset.

Instrument Configuration

There are three different instrument setups available to observe with the VLA at 4 and P-band:

• P-band setup: Provides 16 subbands from the A0/C0 IF pair, each 16 MHz wide, to cover the frequency range 224-480 MHz, with a channel resolution of 125 KHz. The correlator integration time of this setup is 2 seconds with the 8-bit samplers.
• 4-band setup: Provides 8 subbands from the B0/D0 IF pair, each 4 MHz wide, to cover the frequency range 54-86 MHz, with a channel resolution of 15.6 kHz. The correlator integration time of this setup is 2 seconds with the 8-bit samplers.
• 4&P-band setup: This combined the two setups from above to observe 4 and P-band simultaneously.
  
  

Requantizer Setup Scans

We strongly recommend using requantizer gain level setup scans in very low frequency observations. Here we note two important sections on the use of these setup scans in 8-bit observations:

1. See the 8-bit General Information section under the '8/3-bit Attenuator Settings and Setup Scans' page of the VLA Observing Guide for information on how to trigger the requantizer gain setup scans while using the 8-bit samplers.
2. See the Special Case II in the '8/3-bit Attenuator Settings and Setup Scans' page of the VLA Observing Guide for the reasons to use the requintizer setup scans in P-band observations, and the current implementations in the Observation Preparation Tool (OPT) to utilize such scans.

Calibration

A number of calibrator observations are needed for the 4 & P-band observations. These usually include: flux density scale calibrator, complex gain (phase and amplitude gain) calibrator, and a bandpass calibrator to correct for the delays as well as the relative gains of the spectral channels even though the observations are intended for continuum science. It is recommended that the flux density calibrator be observed at least once in an observing run (a scheduling block).

Absolute Flux Density Scale

Accurate flux densities can be obtained by observing one of 3C48, 3C123, 3C138, 3C147, 3C196, 3C286, 3C295, or 3C380.  P-band models are available for these sources, or at minimum a subset of, in CASA or AIPS, therefore if a given calibrator is resolved (see the VLA calibrator list), make sure to set appropriate uv ranges while executing calibration tasks. For more details on flux density calibration, see the AIPS task SETJY or the CASA task setjy.

Bandpass (and Delay)

For the VLA it is essential to calibrate the spectral response of each correlator mode used, even for purely continuum projects. For P-band observations it is necessary to use a calibrator that is > 40 Jy to properly calibrate the bandpass response, this includes continuum and spectral line projects. Some of the flux density calibrators noted above can be used for bandpass calibration at P-band. The bandpass calibrator can also be used to calibrate the delays. For calibration of 4-band data it is strictly necessary to observe a bright kJy-scale calibrator to solve for delays and bandpass. The by far single best calibrator is Cygnus A, however if observing at the galactic anticenter, depending on the array configuration and resolved structure, Taurus A or Virgo A might be suitable as well. For more details, refer to the Bandpass and Delay Calibration in the Calibration section, or the Spectral Line section.

Complex Gain (phase and amplitude gain)

Considering the large field of view of very low frequency observations, it will always be possible to self-calibrate the target phases because there will be a strong source or several strong sources within the field. It is recommended, however, to observe a complex gain calibrator (flux density > 10 Jy) with a gain cal + target + gain cal time of 30 to 60 minutes regardless of the array configuration for initial calibration and system monitoring purposes.

For more details on the above calibrators, refer to the Calibration section.

For information on rapid phase calibration and the Atmospheric Phase Interferometer (API), refer to the VLA OSS. More details regarding cycle times may be found under the Calibration Cycles of the Calibration section.

Polarization

Polarimetric observations are available for P-band only under SRO. The details for polarimetric calibration are currently being commissioned. Guidance on observation setup and calibration using AIPS is documented in EVLA Memo #207.

At 4-band due to the nature of the dipole response, the sensitivity and beam-shapes are vastly different between the two polarizations. Thus, only continuum imaging is currently commissioned below 100 MHz. It is available to perform polarimetric observations at 4-band through RSRO proposals.

Before submitting a scheduling block (SB), refer to the Presubmission Checklists:

Instrument Validation

SB Validation

Please submit any questions to the NRAO Helpdesk.

The wide bandwidths of the VLA allow users to observe up to 8GHz of bandwidth at a time. All observations with the 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 at the time of the observation (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 (ν₀), 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; λ and λ₀ are the corresponding observed and rest wavelengths, respectively)
• 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 by redshifting the rest frequency of the line via [display]\nu=\frac{\nu_0}{z+1}[/display]

where the redshifted rest frequency ν can now be used as the nominal rest frequency for the observations. Zero velocity is then defined for that redshift and is therefore intrinsic to the object. This method will appropriately apply the redshift correction to the channel and line widths and the resulting velocities are also relative 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. Using 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:

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 the 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 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 will 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. Now, the 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 directly during imaging in the tasks clean and tclean. Tasks cvel or mstransform provide the same functionality for the visibilities in a MeasurementSet without imaging. 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. We therefore recommend to oversample an spectral feature with at least 4 channels during the observations.

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.

Figure 7.1.1: Blank field RMS, single 1GHz baseband. Subband edges at 128MHz show increased noise.

Figure 7.1.2: Blank field RMS, same as top, but now a combination of two 1GHz basebands shifted by 64MHz. Subband edges are replaced by channels from subbands of the second, frequency shifted baseband.

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 of a baseband (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 S_cal observed for a time t_cal and a science target with flux density S_obj observed for a time t_obj, should be greater than . How many times greater will be determined by one's science goals and the practicalities of the observations, but 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 at both setups (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.

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.

Guidelines

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. However, to achieve accuracy of polarization calibration to better than a few percent, sufficient signal-to-noise for the leakage calibrator is required to be able to correct for spectral variations in instrumental polarization with typical channel widths of the order of a few MHz. The best results are achieved using an unpolarized calibrator or a bright polarized calibrator with good parallactic angle coverage. More details on different calibration strategies can be found in EVLA Memo #201. At least one observation of 3C286 or 3C138 (or another polarized calibrator with known linear polarization angle) 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.

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. In addition, geometric effects appear to be limiting the absolute polarization angle calibration especially in cases where a source is observed at opposite sides of transit independent of observing band. A detailed investigation is documented in EVLA Memo #205.

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 correction for this effect. The AIPS program TECOR has been shown to be quite effective in removing large-scale ionospherically induced Faraday Rotation below 2 GHz. It uses currently-available data in IONEX format, which provide a global coarse correction. The effect of this ionospheric Faraday rotation on polarization angles is shown as an example in EVLA Memo #205, in particular see Fig. 3. Please consult the TECOR help file for detailed information. CASA provides 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 available experimentally in CASA 5.x releases pending further verification.

Monitoring

The results of a careful monitoring program of these and other polarization calibrators can be found at http://www.vla.nrao.edu/astro/evlapolcal/ for 2011/2012. More recent monitoring data is available from the NRAO archive under project TPOL0003 for secondary calibrators and under project TCAL0009 for primary linear polarization angle calibrators. There is also a list of calibrator monitoring for VLBA observations starting with the 21A semester. If you would like to request a specific set of sources to be monitored, please submit your request to the VLA Observing department in the NRAO Science Helpdesk.

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 auxiliary 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.2.6 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.2.1 and 7.2.2) 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.2.1 Notes:

• A1. Polarized fraction and angle values for these sources is given in Table 7.2.6 below.
• A2. 3C48 is weak at high frequency and somewhat resolved in larger configurations. Depolarized below 4GHz.
• A3. 3C48 has been undergoing a major event since 2016 affecting its polarization and flux density properties, especially above 5 GHz. For accurate polarization angle calibration, care should be taken that a current model of its polarization properties is available and applied during calibration.
  
• A4. 3C138 has been undergoing a major event since 2021 that could be affecting its polarization and flux density properties, especially above 5 GHz. For accurate polarization angle calibration, care should be taken that a current model of its polarization properties is available and applied during calibration. This can be obtained from monthly monitoring observations available from the NRAO archive with the project code TCAL0009.
  
• A5. 3C286 is our foremost primary calibrator and should be used if available.

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.2.3 Notes:

• C1. Very bright and low polarization (<1%), but variable flux density. Approaches 1% polarized at 43 GHz.
• C2. Steep spectrum and resolved, low polarization below 10GHz (best <4.5GHz). Stable polarization above. About 6% polarized at 43 GHz See Table 7.2.6 below.
• C3. Weak at high frequency, but stable flux and very low polarization.
• C4. Very 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.

Another potential set of unpolarized sources (verified only for S band) below 34 degree declination near 3C 48 and 3C 286 are listed in Table 7.2.5. However, like in the case of sources listed in Table 7.2.4, we strongly encourage to let us know before using these secondary unpolarized calibrators due to potential source variability.

Final Recommendations:

• 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.vla.nrao.edu/astro/evlapolcal (for VLA 2010-2012), as well as in the NRAO archive under project code TCAL0009, with regular observations since 2016.
• "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
  
  

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.2.6 shows the measured fractional polarization and intrinsic angle for the linearly polarized emission for these four sources in December 2010. Note that 3C138 and 3C48 are 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.

Since 3C48, 3C138, and 3C147 are variable above 10 GHz, we have performed new observations of these calibrators across the band January 31/February 1st, 2019. The updated values from this observation are listed below.

Link to Flux Density Scale, Polarization Leakage, and Polarization Angle text files.

Summary of Polarization Calibrator Monitoring

More details and up-to-date information on the regular and ad-hoc VLA polarization calibrator monitoring observations can be found on this confluence page.

The VLA can be split up in subarrays. That is, a subset 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 (i.e., Y1).

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.
• 8-bit and 3-bit default NRAO wideband continuum frequency setups may be used for standard interferometric observing (no phasing, binning, etc., and no spectral lines). Other modes may be offered as RSRO in the call for proposals.
• The division of observing directions, frequency bands, polarization products and integration times over subarrays is unrestricted. Observations where the correlator configuration changes within a given subarray are currently allowed as SRO.  OTF modes are not supported in subarray observations.
• 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 the Subarray Observing section.
• 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 review the Subarray Observing section in the OPT manual for further information or contact the NRAO Helpdesk.

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 made up of more than one observed field.

Mosaicking should be used when the desired field of view (patch of sky to be observed) is relatively large compared to the Primary Beam at the highest observing frequency (as defined in the Field of View section of the VLA OSS). Per definition of the Primary Beam (θ_PB), the image sensitivity will decrease with distance from the center of the field according to a Gaussian with FWHM=θ_PB. Thus, the sensitivity at a distance θ_PB from the pointing center will be worse by a factor of two as compared with the pointing center. To achieve approximately constant sensitivity over the field of view, the field of view must be << θ_PB. If the loss in sensitivity at the edge of the field of view is not acceptable, the observations should be made using a mosaic rather than a single pointing.

Note: The Largest Angular Scale (LAS) that can be imaged by the array is independent of both the Primary Beam and the use of mosaicking to increase the field of view. A table of the band- and configuration-dependent LAS is presented in the Resolution section of the OSS.

Mosaic observing with the VLA

There are two different ways of observing a patch of sky that is much larger than the telescope's instantaneous field-of-view. The standard approach, known as a discrete or pointed mosaic, is to combine together fields from individual pointings of the telescope. This method is typically used for smaller and/or non-rectangular patterns or when significant time needs to be spent per sky area to obtain sufficient sensitivity and image fidelity. The other approach, known as On-The-Fly mapping or OTF(M), combines 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. OTF 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. 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 General 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. Observers considering the use of OTF mode are encouraged to contact NRAO staff through the NRAO HelpDesk to ensure the feasibility of their OTF observations.

Preparing for mosaic observing: Discrete or On-The-Fly?

You should only use OTF mosaicking if it will be significantly more efficient than standard mosacking. The great benefit of OTF is the ability to eliminate the settling time (after every antenna move) that is required for each pointing in a discrete mosaic. For the VLA, the settle time typically amounts to 7s per pointing. Therefore OTF is particularly useful for large, shallow mosaics that require <15-25s per mosaic beam, where the settle time per field would amount to a very large overhead (>30%-50%) on the observations.

To determine if the standard approach will work for your purposes, first determine the "required integration time per discrete pointing" using the steps outlined below. If the integration time is >25 seconds, then you should use a standard discrete mosaic. For integration times ranging from 14 seconds to 24 seconds it is a gray area - OTF mosaicking would require less overhead, but the extra processing cost and added complexity probably mean you should use standard mosaicking unless you are familiar with processing this type of data in CASA. However, if your integration time is shorter than about 14 seconds, then the time it will take to move and settle between pointings will incur >50% overhead. Unless this extra overhead is not a problem (i.e. the overall mosaic is quite small in area) you should consider using OTF.

Use the following steps to determine the individual integration times (t_integ) that would be required for discrete pointings. You should go through the following steps to prepare your observations, even if you already know which type of mosaic (discrete or OTF) you plan to observe.

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.

     Example

     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)

     Example

     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 [display]\Omega_B = 0.5665~\theta^2_P[/display] (see the Gaussian Beam Pattern Sensitivity subsection below for more details)

     Example

     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 the mosaic using the formula

     [display]N_{\rm eff}=\frac{A_{\rm mos}}{\Omega_B}[/display]

     Example

     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" t_eff using the VLA Exposure calculator. (Note that t_eff is the effective integration time for any part of the mosaic, which is not the same as the actual integration time per discrete pointing.)
     

     Example

     I wish to reach RMS 0.05 mJy. For 600 MHz usable bandwidth at 1.5 GHz in B-configuration with robust weighting and dual polarization, I need 2m47s on-sky.

   • Compute the total integration time t_total 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.)

     Example

     For 2m47s per beam and 203 beams I need 9h25m total over the mosaic.

   • Compute the Survey Speed (SS) by taking the mosaic area and dividing by the total integration time (SS = A_mos/ t_total). This is equivalent to simply computing directly SS = Ω_B / t_eff also!
     

     Example

     For t_total=9h25m (9.4 hours) total over the 25 square-degree mosaic, the implied survey speed is about 2.65 square degrees per hour (or equivalently SS = 2.65 square arc-minutes per second).

4. What mosaicking pattern would 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 along 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. You might choose to use θ_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).
     

     Example

     For our θ_P = 28' at 1.5 GHz we get θ_hex = 19.8' for the spacing along rows and θ_row = 17'9" (1029") between rows. 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 discrete pointings will be required to cover this mosaic?
   
   • To fill a rectangular area, long and short rows should alternate, with 1 extra pointing in the long rows.

     Example

     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' = 297' apart. The short rows will alternate with longer rows of 17 pointings (16 x 19.8' = 316'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.

     Example

     Our total integration time of 9h25m is spread among 297 pointings, so each pointing should get 1m54s 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.

If at this point you think you should use OTF mosaicking, see the section below on Considerations for On-The-Fly (OTF) Mosaics. Or, continue with the following steps to determine the total amount of observing time required (including overhead) for a discrete mosaic.

7. Calculate approximate duration (excluding calibration) for the mosaic.
   • The VLA slew and settling time for short distance (sub-degree) moves is 7-8 seconds.

     Example

     For 1m54s integrations we add 8s so we can have observations of 2m02s. The total time for 297 pointings is 10h4m.

8. Calculate schedule overheads.
   • Follow the Exposure and Overhead guidelines in the Guide to Proposing for the VLA.
     

     Example

     For ease of scheduling, we will break our ~10h mosaic into three parts, each with 3h22m 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 after every 20m of mosaic observing (10 visits) to observe our gain calibrator. The total time for each scheduling block comes to 4h12m. This amounts to a 25% overhead, which is about average for VLA's low frequencies.

9. If project is approved, when it comes time to observe, make a schedule or schedules in the 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

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.

If you decide to use OTF mosaicking, after full consideration of the overheads for discrete pointings, the next question is "Can I use OTF mosaicking for my observations?". The decision depends on the implied scan speeds and dump rates (and thus data rates). Limitations on the allowed correlator dump times t_integ are not just from the allowed data rates (60 MB/s for standard and shared risk observing); there are also physical limitations on how fast the data from the correlator can be handled by the back-end processing cluster. For the current restrictions on integration times, see the OSS section on Time Resolution and Data Rates. Because some use of OTF is still classified as shared-risk (as of 2020B), the data rate limit is nominally 60 MB/s. This means that you can use shorter integration times when choosing OTF as a shared-risk observer, but for efficiency you should not use a shorter integration time than you truly need.

To set up the parameters of the mosaic (e.g. for the purposes of a proposal), start by following the first several steps outlined above. But instead of computing the number of discrete pointings, you will break the OTF mosaic into a number of "rows"; the antennas will slew back and forth one row at a time at a non-sidereal scan rate (R). Use the following steps to determine the row spacing (θ_row; similar to the discrete mosaic case), the required scan rate (R) to meet your sensitivity requirement, the integration/dump times (t_integ), and the associated data rates. Effective integration time (t_eff) and total mosaic time are calculated as before.

The following steps correspond to an example that is appropriate for OTF observing. Suppose you wish to observe 5x10 square degrees in S-band (2-4 GHz) in the B-configuration to a depth of 0.15 mJy. The effective integration time (t_eff) to reach this sensitivity (robust weighting, dual pol with 1.5 GHz of bandwidth) is 5.35 seconds.

1. What is the mosaic beam area? What is my Survey Speed (SS)?

• To determine the Survey Speed (SS = Ω_B / t_eff), 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. (See Steps 2 and 3 from above.)

  Example

  At 3 GHz, the primary beam size is θ_P =14'. The equivalent mosaic beam area is Ω_B = 0.031 square degrees. Therefore the survey speed is 20.75 square degrees per hour, equivalent to 20.75 square arc-minutes per second.

Survey Speed of the VLA for Large Continuum Mosaicked Surveys

Following the above guidelines, we can compute the survey speed SS [display]SS = \Omega_B / t_{eff} = 0.5665~\theta^2_{P} / t_{eff}[/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 the effective integration time, t_eff. From this, we calculate SS from θ_P at band center.

The parameters are tabulated by band below:

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]

or

[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 d_k, [inline]w(\theta_k)[/inline] is the weight for data point d_k, and [inline]Z[/inline] is the sum-of-weights function. If the image data have equal RMS sensitivity levels σ_k = σ₀ then the optimal weighting gives

[display]w(\theta_k)=f^2(\theta_k)[/display]

and

[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 3), 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 Z_hexmin = 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]

and

[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 N_pt pointings getting the same integration time t_int

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

then

[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 Z_hexmin = 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 t_eff 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]

and

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

For our rectangular mosaic, the minimum weight is Z_rectmin = 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 A_mos 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 σ²_D 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.

References

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

Introduction

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 New → Source. You are presented with a screen that looks like Figure 7.5.1.

Figure 7.5.1: The New Source screen in the Source Configuration Tool (SCT).

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.

Figure 7.5.2: The SOURCE POSITIONS section for internal ephemeris sources.

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.

Figure 7.5.3: The SOURCE POSITIONS section for ephemeris file sources.

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.

Figure 7.5.4. The SOURCE POSITIONS section after import of an ephemeris file.

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 near Moving Sources

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.

Figure 7.5.5. An SCT bulls-eye plot for a moving source (Mars).

Solar Observing

The VLA is able to observe the Sun but it poses a number of challenges: the Sun is a powerful source, it has a complex brightness distribution, it is variable in time – due to solar rotation and due to intrinsic variability (e.g., flares)– and, as a solar system object it displays significant apparent motion on the sky. For these reasons, solar observations require special hardware modifications, different observing procedures, and special calibration software.

The main difference between solar observing and observing sidereal sources from a user perspective is the need to provide one or more ephemerides to ensure that the solar target or targets of interest are tracked. In this respect, solar observing is similar to observing other solar system objects such as planets and comets. Most of the details related to the hardware changes required for solar observing such as switching in the 20 dB attenuators, applying delay corrections, setting stepped attenuator levels, and referring to solar signal to solar Pcal signals are done automatically behind the scenes and are therefore largely invisible to the user.

The OPT is used to produce scheduling blocks (SBs) for solar observations. The basic pattern used for VLA observations applies to solar observations: observation of a bandpass calibrator, and interleaving observations of one or more solar targets with those of one or more gain calibrators. It is assumed here that users are familiar with the OPT and only steps needed to observe a solar source are detailed.

Special Considerations

Array Configurations: The Sun is large, time variable, and can have a complex brightness distribution. It is not advisable to use the A and B-configurations to observe the Sun in general because the uv coverage is simply too dilute. In addition, scattering in the solar corona on density inhomogeneities limits the useful angular resolution with which one can image the Sun. Hence, for most programs, the C and D-configurations are recommended.

Frequency Bands: Solar observations with the VLA are currently available in the L, S, C, X, and Ku bands for which switched-power flux calibration is implemented. They are also possible in P band (230-470 MHz). While P band employed the same 20 dB attenuators to observe the Sun as L, S, and C bands (T302 module) P band does not currently have the special Tcals needed for switched-power flux calibration. Users should be aware that accurate flux calibration is therefore not possible in P band. 

Time Sharing vs Subarrays: Solar observers often wish to observe their target in more than one frequency band. It is not possible to do so over a number of days or weeks because solar targets evolve relatively quickly — on time scales of seconds (flares) to hours (active regions). Observers need to carefully consider whether their scientific objectives require observation in more than one band simultaneously, in which case subarrays should be used; or whether they can sample multiple bands in sequence, in which case time sharing is sufficient.

Mosaicking: The field of view of VLA antennas, taken to be roughly the FWHM width of the primary beam, is given as ϑ≈1.5λ arcmin, where λ is the wavelength in cm. For example, while the full disk of the Sun can be mapped with a single pointing for λ=20 cm, one must resort to mosaicking techniques to map the full disk at shorter wavelengths. The current time required per pointing is currently 40-50sec: 20sec to slew, 10sec for setup, and 10-20sec to integrate on source. Hence, users must again weigh desirability of imaging a larger angular domain against the time evolution of emission within the domain over time.

Short Correlator Integration Time (T_int): The Sun produces numerous transient phenomena: jets, flares, radio bursts. For such phenomena, the availability of short time integrations is desirable in order to resolve time scales of interest. The VLA can be used with very short integration times — down to tens of milliseconds. However, the use of short integrations comes at the cost of high data rates and large data volumes. They should be used with caution.

Ultra-high Brightness Sources: At frequencies less than 2-3 GHz, coherent radio bursts from the Sun become increasingly common. They can be highly polarized, show rapid variability (10s of ms), and complex spectral variability. The brightest bursts can exceed 10⁵ solar flux units, or 10⁹ Jy! The VLA 1-2 GHz band has a special signal path (the HNA or "reverse coupler" path) that allows such bursts to be observed without saturating the system. It has not yet been fully commissioned and is therefore not yet available to users. It is anticipated that it will be in the next two years.

Hardware Modifications

The Sun is an extremely intense source of radio emission. To ensure that that the system maintains adequate linearity the solar signal must be reduced to a level that no element along the IF/LO signal chain saturates. Solar observing is currently supported in five of the Cassegrain bands (L, S, C, X, and Ku) and one prime focus band (P band). In the case of the P, L, S, and C bands this is achieved by introducing a switchable 20 dB attenuators into the signal path of each antenna following the first LNA. The attenuator is switched into the signal path in the LSC frequency converter (T302 module). In the case of the X and Ku bands, the 20 dB attenuator is switched into the signal path after the first LNA and postamp. For all bands, the signal is further conditioned in the frequency downconverter which uses stepped input and output attenuators to set optimum signal levels (T304 module).

While the Sun can be observed when the 20 dB attenuators are switched into the signal path, calibrator sources cannot. Hence, the 20 dB attenuators must be switched out of the signal path when observing a calibrator source. The 20 dB attenuators introduce delay into the signal. This delay has been measured for each attenuator in each band and polarization (the attenuator is the same for the L, S, and C bands) and the delay correction is handled online. The stepped attenuators in the frequency downconverter are first optimized on the Sun. If they were allowed to re-optimize on a calibrator source, an uncalibrated phase error would be introduced. Therefore, the stepped attenuators settings are “set and remembered” on the Sun for use during calibrator scans.

Flux calibration is performed using the VLA switched power system (see Perley 2010). Under normal observing conditions a small, stable, and known calibration signal (Pcal) is periodically injected into the signal path following the polarizer at a rate of 20 Hz with a 50% duty cycle. At the point after the signal has been digitally subdivided into subbands, but before it is requantized and correlatated, the system power is synchronously detected when Pcal is switched on and when it is switched off, P_on and P_off. From these, P_dif = P_on - P_off and P_sum = P_on + P_off are formed from which the system gain and system temperature can be inferred. From the system gain and the so-called requantizer gain, the cross-power may be calibrated and from thence, the visibility amplitudes.

The VLA front ends have remarkable dynamic range and this arrangement is sufficient to observe the quiet Sun, active regions, and small flares. Unfortunately, the front end will saturate for large flares with the exception of the 1-2 GHz band (L band) for which special provisions have been made.

Source Information

Ephemerides

The user must provide the solar ephemeris or ephemerides needed to execute a solar observing program. A given ephemeris is used to track a particular feature of interest on the Sun, correcting for the Sun’s apparent motion on the sky and for the Sun’s differential rotation. Instances where more than one ephemeris is needed are:

• Time sharing between multiple solar targets.
• The use of subarrays to observe a solar target in more than one frequency band.
• The use of mosaicking to map an angular domain on the Sun that is larger than the primary beam.

Observers may wish to generate their own ephemeris using the JPL Horizons website at http://ssd.jpl.nasa.gov/horizons.cgi (please see the Observing Guide regarding Moving Objects for details). Alternatively, a convenient solar ephemeris generator can be found at http://celestialscenes.com/alma/coords/CoordTool.html. Please read the user manual carefully before using. As its name implies, the ALMA Solar Ephemeris Generator was developed as a tool in support of solar observations with ALMA. However, it can be used to generate ephemerides for solar observations from other observatories, including the VLA.

The ALMA Solar Ephemeris Generator offers two interface choices: GUI or Text. The former is attractive because it allows the user to point and click on solar targets using a user-selected Solar Dynamics Observatory Atmospheric Imaging Assembly reference image or a user-provided reference image. The latter requires the user to specify the helioprojective coordinates of the target.

• Note 1: Unlike ALMA solar observations, VLA solar observations use ephemerides that are referenced to the geocenter, not the location of the array. The reference is specified in the Location field. Click the Change default location (ALMA) box and use the pull-down menu to the right to select geocenter (not VLA!) as the location to which the ephemeris will be referenced.
• Note 2: If using the GUI, do not use the Mosaic observation option in the Pointing field. It is designed for ALMA mosaicking. Instead, generate one ephemeris per VLA mosaic pointing as described in the previous section.

The remaining fields are largely self-explanatory. Upon generating a given ephemeris, the user can inspect the result. If it is satisfactory, it may be downloaded for import into the OPT.

SB Setup

Observers can structure their SBs in the usual way with the following exceptions:

• For a solar SB the first scan must always slew to the Sun. This slew can be used to set attenuators for a dummy resource that uses the same receiver as the actual science resource.
• Once on the sun, observers must use setup scans for each frequency band that will subsequently be used. This ensures that the stepped attenuators in the frequency downconverter are appropriate, i.e., set and remembered.
• For each source thereafter, there should be a scan that slews to the source using the dummy resource, followed by a 10sec setup scan using the science resource to set the requantizer gain (use the setup intent), followed by an observation (calibrate complex gain, calibrate bandpass, calibrate delay, or observe target intents). That is, each source observed — calibrator or target — should be comprised of a triplet of scans that slews, sets up, and observes with the appropriate scan intent(s).
• Note: In cases where a preceding scan uses a different receiver, the requantizer scan length should be 30sec long to account for sub-reflector rotation. 

Example

05m00s SOL mode, slew to Sun with dummy resource [intent: setup intent]
01m00s SOL mode, attenuator setup scan on Sun with science resource [intent: setup intent]
02m00s STD mode, slew to phase cal with dummy resource [intent: setup intent]
00m10s STD mode, requantizer setup scan on phase cal with science resource [intent: setup intent]
03m00s STD mode, phase cal scan with science resource [intent: calibrate complex gain (A and P)]
02m00s SOL mode, slew to Sun with dummy resource [intent: setup intent]
00m10s SOL mode, requantizer setup scan on Sun with science resource [intent: setup intent]
Begin Loop (repeat scans n times)
 02m00s SOL mode, observe Sun with science resource [intent: observe target]
End Loop
02m00s STD mode, slew to phase cal with dummy resource [intent: setup intent]
00m10s STD mode, requantizer setup scan on phase cal with science resource [intent: scan intent]
01m20s STD mode, phase cal scan with science resource [intent: calibrate complex gain (A and P)]
04m00s STD mode, slew to flux cal with dummy resource [intent: setup intent]
00m10s STD mode, requantizer setup scan on flux cal with science resource [intent: setup intent]
03m00s STD mode, flux cal scan with science resource [intents: calibrate flux, calibrate bandpass]

Solar SBs, like those of other programs, can be complex and setting them up manually in the OPT can be tedious. It is often advantageous to import an SB or to import scans from an external text file. This is done through, e.g., FILE → IMPORT SCANS whereupon a window pops up prompting the user to Choose File and to Import. It is important to conform to the format expected for an SB or scan import as detailed in Section 5 of the OPT manual.

Calibration

As noted above, flux calibration of solar observations requires use of the switched power system described by Perley (2010). Flux calibration using the switched power system requires calibration in the Astronomical Image Processing System (AIPS). The decision to support flux calibration in AIPS was made as a matter of expediency – implementation in CASA will eventually take place but CASA development has a long lead time. Hence, the recommendation is for users to calibrate their data in AIPS, after which either AIPS or CASA may be used to image the calibrated data.

Calibration of solar data in AIPS proceeds in much the same way that it does for non-solar sources. The one exception is that instead of using the task TYAPL to apply switched power calibration to visibility data, solar observers must use the task SYSOL, which recognizes solar Tcal values for those antennas outfitted with solar Cal sources.

Introduction

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. The VLA can take part in VLBI observations as a phased array (Y27). Alternatively, assuming the full collecting area of the phased array in not needed, a single VLA antenna (Y1) can be added to the VLBI observations to provide a short baseline (~50 km) to the Pie Town VLBA antenna.

In phased array mode the VLA offers the equivalent sensitivity, including sampling losses, of a single 115-m antenna. The VLA records up to 4 Gbps to a Mark6 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 Mark6 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...

• 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...

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 Mark6 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 512 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 4 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.

Scheduling

All phased array observations will be fixed date. Please see the HSA, GMVA, and Global cm VLBI chapter of the Guide to Observing with the VLBA.

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 the Guide to Observing with the VLBA: Building a Scheduling File in SCHED. 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.

Frequencies

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

Both phased array (Y27) and single VLA dish (Y1) can be used.  For situations where the observer may only want the inner antennas of the whole VLA to be phased up, a comment to the operator would suffice . 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 also 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 Mark6 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).

Practicalities

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

1. Please see the HSA/GMVA/Global VLBI and Building a Scheduling File in SCHED chapters of the Guide to Observing with the VLBA.
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.

Introduction

The VLA is capable of performing imaging observations of pulsars by "phase-binning" visibilities (also sometimes known as gating).  In this observing mode, rather than continuously integrating visibility data for several seconds as in a standard observation, the data are accumulated into a number of "bins" corresponding to different rotational phase ranges of the pulsar.  The predicted phase versus time is computed from a user-supplied pulsar timing ephemeris; see below for more details.  This allows each pulse phase bin to be imaged separately, for example to identify which continuum source in a given field is the pulsar, or to image the surrounding area after subtracting off pulsed emission, or simply to increase S/N on the pulsar relative to a standard image, etc.

Note that this mode is not suitable for observations of pulsars whose period is unknown a priori, or for observations of single pulses from sources such as FRBs or RRATs.

Correlator Setup

There are several constraints on the bin width, total allowed bandwidth, and data rate that are specific to pulsar binning observations.  These are described in detail in the OSS pulsar section and in the VLA proposal guide.  Once you have decided on your basic setup (band, frequency resolution, etc), set up the subbands following the general instructions given in the RCT manual.  Pulsar binning can then be enabled by going to the "Pulsar" tab in the RCT, selecting "Phase Binned Imaging" mode, and entering the number of bins, as shown below:

The final option specifies whether the pulse period model should be computed from a timing ephemeris, also known as a "par file" or alternately if the binning should be done at a constant topocentric pulse period.  The RCT will verify that the chosen configuration is possible, and will report the total data rate, as shown.

Calibration

In general there is no special calibration that needs to be done for binning observations.  Calibration procedures for complex gain, flux density scale, and if necessary polarization should follow the general guidelines laid out in the Calibration section of the manual.  The only notable differences for pulsar observing are:

1. Calibrators should be observed using a standard (non-binned) correlator setup.  It is recommended that this setup use the same frequency configuration (tuning frequencies, subbands, numbers of channels) as is used for your pulsar target.  The easiest thing to do is first set up the pulsar configuration, then make a copy of it in the RCT and disable binning.
2. As for all VLA observing, binning projects should include an initial setup scan for each band used, to set attenuator levels.  However, there is no need to include additional setup scans to trigger requantizer setting.

Pulsar Ephemerides

When observing pulsars the apparent pulse period is slowly changing with time due to a number of effects including motion of the Earth, motion of the pulsar (binary orbits), intrinsic spin evolution, etc.  The period versus time can be predicted using an ephemeris or timing model.  For binning observations, you should supply an ephemeris using the standard TEMPO "par file" format.  A polynomial approximation to the pulse phase versus time will be generated on the fly using TEMPO at the time of your observation and used for binning the visibilities.  Note that TEMPO2-format par files are not currently accepted.  If you have a par file in TEMPO2 format (for example if it includes "UNITS TCB"), you will need to convert it to TEMPO (TDB) format.

Pulsar ephemerides should be uploaded into your source catalog in the SCT via the "Pulsar Ephemeris" tab:

Since VLA binning observations always generate bins covering the full pulse period there is no need to have absolute phase information about the source you are observing.  This also means it is not strictly necessary that the ephemeris be accurate over the full length of your observation, although the pulse "drifting" into different bins versus time may make data analysis harder.  The fundamental requirement to avoid smearing out pulses is that ΔP x δt < 1/N_bin, where ΔP is the error in the predicted pulse period and δt is the correlator integration time.

Many pulsar ephemerides can be found in the ATNF Pulsar Catalog, but they are not necessarily up to date for all sources.  It is always worthwhile to verify a timing model with recent data if there is any uncertainty about it.

3C48

# 3C48
# Date 31Jan/01Feb 2019 polarization properties
# Reference flux densities were used
# Frequency  I       P.F.       P.A.
# (GHz)      (Jy)               (rad)
1.022        20.68   0.00293     0.07445
1.465        15.62   0.00457    -0.60282
1.865        12.88   0.00897     0.39760
2.565        9.82    0.01548    -1.97046
3.565        7.31    0.02911    -1.46542
4.885        5.48    0.04286    -1.24875
6.680        4.12    0.05356    -1.15533
8.435        3.34    0.05430    -1.10638
11.320       2.56    0.05727    -1.08602
14.065       2.14    0.06097    -1.09597
16.564       1.86    0.06296    -1.11891
19.064       1.67    0.06492    -1.18266
25.564       1.33    0.07153    -1.25369
32.064       1.11    0.06442    -1.32430
37.064       1.00    0.06686    -1.33697
42.064       0.92    0.05552    -1.46381
48.064       0.82    0.06773    -1.46412

Link to download 3C48_2019.txt file.

3C138

# 3C138
# Date 31Jan/01Feb 2019 polarization properties
# Reference flux densities were used
# Frequency  I       P.F.       P.A.
# (GHz)      (Jy)               (rad)
1.022        10.07   0.05462    -0.23182
1.465        8.26    0.07795    -0.16694
1.865        7.21    0.08955    -0.16235
2.565        6.00    0.09848    -0.17721
3.565        4.89    0.10337    -0.16619
4.885        4.00    0.10524    -0.18386
6.680        3.23    0.10219    -0.20056
8.435        2.76    0.10939    -0.16412
11.320       2.24    0.09063    -0.13864
14.065       1.90    0.08231    -0.18290
16.654       1.69    0.08186    -0.23086
19.064       1.54    0.08437    -0.28012
25.564       1.25    0.08422    -0.31691
32.064       1.06    0.08541    -0.33910
37.064       0.96    0.08694    -0.34084
42.064       0.88    0.08772    -0.40503
48.064       0.82    0.09147    -0.42097

Link to download 3C138_2019.txt file.

3C147

# 3C147
# Date 31Jan/01Feb 2019 polarization properties
# Reference flux densities were used
# Frequency  I       P.F.      P.A.
# (GHz)      (Jy)              (rad)
1.022        27.73   0.00028    N/A
1.465        21.36   0.00018    N/A
1.865        17.86   0.00021    N/A
2.565        13.79   0.00015    N/A
3.565        10.40   0.00052   -0.59515
4.885        7.88    0.00157   -0.23002
6.680        5.91    0.00514   -1.00103
8.435        4.81    0.00476   -0.33225
11.320       3.67    0.00849    0.46557
14.065       3.02    0.01791    0.91642
16.564       2.61    0.02400    1.04399
19.064       2.32    0.02904    1.14768
25.564       1.82    0.03432    1.37341
32.064       1.53    0.04033    1.43967
37.064       1.38    0.04470    1.52606
42.064       1.26    0.04943    1.51182
48.064       1.14    0.05956    1.48944

Link to download 3C147_2019.txt file.

3C196

# 3C196
# Date 31Jan/01Feb 2019 polarization properties
# Reference flux densities were used
# Frequency  I       P.F.        P.A.
# (GHz)      (Jy)                (rad)
1.022        18.94   0.00048     0.78540
1.465        13.75   0.00052     0.29400
1.865        11.05   0.00174     0.70710
2.565        8.14    0.00992     0.89138
3.565        5.86    0.02256    -1.36438
4.885        4.22    0.02499    -0.97477
6.680        3.00    0.01969    -0.71829
8.435        2.33    0.01602    -0.59490
11.320       1.67    0.01293    -0.51003
14.065       1.30    0.01254    -0.51098
16.654       1.08    0.01244    -0.48004
19.064       0.92    0.01278    -0.57629
25.564       0.66    0.01307    -0.42159
32.064       0.51    0.01165    -0.45858
37.064       0.43    0.00595    -0.26686
42.064       0.37    0.02809    -0.38925
48.064       0.31    N/A        N/A

Link to download 3C196_2019.txt file.

3C286

# 3C286 - values from R. Perley based on 3C286 
# Date 31Jan/01Feb 2019 polarization properties
# Reference flux densities were used
# Frequency  I        P.F.        P.A.
# (GHz)      (Jy)                 (rad)
1.022        17.46    0.08618     0.57632
1.465        14.64    0.09794     0.57261
1.865        13.03    0.10122     0.57613
2.565        10.85    0.10575     0.57580
3.565        8.94     0.11153     0.57624
4.885        7.33     0.11525     0.57503
6.680        5.97     0.11858     0.57758
8.435        5.12     0.12045     0.57827
11.320       4.12     0.12261     0.58412
14.065       3.54     0.12303     0.59534
16.564       3.15     0.12544     0.60172
19.064       2.85     0.12633     0.60286
25.564       2.30     0.12700     0.62198
32.064       1.92     0.13062     0.63170
37.064       1.73     0.13485     0.62791
42.064       1.57     0.13420     0.64589
48.064       1.44     0.14629     0.62153

Link to download 3C286_2019.txt file.

3C295

# 3C295
# Date 31Jan/01Feb 2019 polarization properties
# Reference flux densities were used
# Frequency   I       P.F.       P.A.
# (GHz)       (Jy)               (rad)
1.022         29.13   0.00048    0.78540
1.465         21.60   0.00017    N/A
1.865         17.54   0.00045    0.34737
2.565         12.84   0.00047    0.78540
3.565         9.12    0.00102   -1.23511
4.885         6.42    0.00198    1.43111
6.680         4.45    0.00849   -0.10259
8.435         3.37    0.01134    0.54597
11.320        2.33    0.01537   -0.63780
14.065        1.75    0.01372   -1.16634
16.564        1.43    0.02449   -1.53089
19.064        1.19    0.03485    1.38367
25.564        0.82    0.05047    1.06163
32.064        0.60    0.06503    0.88536
37.064        0.50    0.06517    0.74524
42.064        0.44    0.06131    0.79286
48.064        0.41    N/A        N/A

Link to download 3C295_2019.txt file.

Integration Time & Time Averaging

The correlator integration time (T_int) should be appropriate for the array configuration, your scientific goals, and observing mode (i.e., on-the-fly-mosaicking, subarrays). Make sure you have short enough integration time in order to reduce time averaging losses and to offset atmospheric/ionospheric phase winding. The minimum possible integration time depends on the total number of channels produced in the correlator and the maximum data rate and data volume. The smaller the integration time, the larger your data set will be. Thus, making the integration time unnecessarily small should be avoided. Current integration time defaults and guidelines can be found in the Time Resolution and Data Rates section of the current VLA OSS.

Consider that time averaging causes some smearing of sources away from the phase center of the image; the further away from the phase center, the more smearing there is. This effect cannot be remedied by self-calibration and it persists after deconvolution. Therefore, it is important to devise observing strategies that hold the distortions down to acceptable levels. For more details, refer to the Time-Averaging Loss section in the current VLA OSS.

Continuum

Most observers will be able to utilize the NRAO's default continuum resources located within the Instrument Configuration tool (also known as the Resource Catalog Tool (RCT)). When choosing one of the defaults, be sure to select the resource according to the array configuration in which the SB will be observed. The defaults are organized by array configuration and corresponding correlator integration time. For example, A/Any config will contain 2s integration time resources and DCB/Any config will contain 3s and 5s integration time resources.

Did you choose the correct default resource?

While checking the Reports tab of the SB in question, the first table of that page summarizes the resource(s) utilized within in the SB. The NRAO defaults adhere to the following naming scheme: the first letter denotes the receiver band, the number following signifies the total number of subbands, the letter following denotes the polarization (f=full and d=dual), and the last number indicates the correlator integration time in seconds. Some defaults contain extra letters at the end, these signify the preferred array configuration for its integration time.

Default Examples:

K64f2 = K band, 64 subbands (3-bit), full polarization, 2s integration time

X16f5DCB = X band, 16 subbands (8-bit), full polarization, 5s integration time, D, C, or B configuration

The distinction between 3-bit and 8-bit resources can be made through the number of the subbands: 8-bit resources, regardless of the receiver band, have 16 subbands. The 3-bit resources have 64 subbands at K, Ka, and Q-bands, 48 subbands at Ku-band, and 32 subbands at X and C-bands. In order to see a detailed overview of a resource within an SB, click on Show All Subbands located in the first table of the Reports tab.

If a given default resource is not exactly what is required for the science (i.e., the default center frequency is not ideal), then the observer can either create a new continuum resource from scratch or copy/paste a default resource into their own catalog and then make adjustments to the resource as needed.

For very detailed guidelines on how to create continuum and spectral line resources, please read through the section on how to Create a Personal Resource Catalog within the OPT Manual.

Spectral Line

As noted above, please read the section Create a Personal Resource Catalog within the OPT Manual in addition to reading through the Spectral Line section within the Guide to Observing with the VLA.

If you are setting a spectral line resource that requires narrow subbands, you may want to use Doppler Setting. Details on this are available in the Spectral Line observing guide and the Spectral Line Resources of the OPT manual. With velocity resolution, make sure the spectral resolution is enough to resolve your line (take subsequent Hanning smoothing into account) and possibly over-sample by a factor of 4 to be able to correct for Doppler Setting effects. Also, make sure you have enough line-free bandwidth to measure the continuum flux.

During the process of building your spectral line resource be aware if, at the time of line placement, you see the following warning message in the pop up window: Warning: The subband overlaps a forbidden region of the baseband. When this happens, the 128 MHz boundary condition overrules the sky frequency of the subband and the subband gets placed off from the desired value because it cannot be on the boundary itself (note, this process is not reversible). The only way to address this is to shift the baseband frequency (within the Baseband tab).

When you change the baseband frequency, make sure to re-generate the subbands containing the spectral lines which had the above noted warning. The original spectral lines have been forced to a different frequency due to hitting the 128 MHz boundary.(Note, be sure to remove any incorrectly placed spectral lines within the subbands.) Then update the scheduling block (SB) with the new resource, and finally verify that the subbands are as expected in the Reports tab of the OPT (explained below).

After generating the lines, be sure to double check and/or adjust the following parameters to achieve the desired resolution:

• bandwidth (BW)
• polarization: full or dual
• Baseline Board Pairs (BlBPs) stacking
• Recirculation

Spectral Line Validity Check

Once the resource has been created and imported into the SB, we recommend performing a check on the spectral line sky frequencies and Doppler Settings (if applicable) to verify that everything is ok.

1. Within the OPT, go to the SB containing the resource in question and then go to the Reports tab. At the top of that page, insert an LST date and start time in the assumed LST start fields, then click Update. (LST dates for a given month can be found on the figure in the Scheduling Constraints page.)
2. In the Instrument Configuration Summary table (found within the Reports tab of an SB), locate the resource of interest and find the Doppler line, velocity, position, etc. columns. If they contain dashes instead of values, then the resource has not been set up to apply Doppler corrections at the time of observing and all frequency information for this resource relates to sky frequencies. Assuming Doppler corrections are essential, switch them on in the resource (bottom of the Baseband tab within the Instrument Configuration tool), change the resource name and re-import the new resource to all the scans with the old resource (using the Bulk Edit tab) and check these columns in the resource again.
3. Click Show All Subbands for the resource of interest. Here you will see the calculated sky frequencies of all subbands (frequency range, subband center, etc...) for the assumed date of the above step. With Doppler Setting active, these frequencies will change with date and time of observation as they are not fixed sky frequencies.
4. Select one of your lines to compare the subband center frequency with the value generated through the Dopset tool. In the Dopset tool, populate the appropriate fields, including the LST day and time you used in the OPT. The frequency reported by Dopset and the OPT may not be identical but it should be very close (within a kHz). However, if Doppler Setting was not used in the resource, then there would be a noticeable difference in the frequencies between Dopset and the OPT. For such cases, make sure that your spectral line of interest is well within the subband even if it is not at its center.
5. Repeat step 3 for other spectral lines in both the A/C and B/D basebands.
6. Repeat steps 3 and 4 for the other LST start dates/times to make sure the frequency values in the table will change as expected due to Doppler and are consistent with Dopset.

If you have questions or need assistance, please submit a ticket to the NRAO Science Helpdesk and include the URL of the resource in question along with the project code.

In this section we provide practical considerations to ensure that your VLA scheduling block (SB) adheres to the discrete requirements for successful observations. Please follow this list during the preparation of your SB and before submitting it through the Observation Preparation Tool (OPT). If you wish to check the validity of the correlator setup of your observations, please visit the Instrument Configuration Verification page.

It is essential that one checks their SBs carefully prior to submitting. Although the OPT has several features to deal with logistical observing issues, it will not catch everything. The same goes for the SB verification that NRAO staff performs after submission; SBs are checked only for common errors. Items like source positions, Doppler-setting frequencies, choice of calibrators, etc., and anything particular that refers to the science goal of the observations cannot be verified by the staff. Remember that the final responsibility for a correct observing schedule remains with the observer.

SB Information Tab

1. Appropriate wind and API constraints: Important because most of VLA observing is dynamic.
2. Be aware of selecting "avoid sunrise/sunset": In most cases this is not necessary and can decrease the chances of observing. For more details, refer to the Low Frequency and Very Low Frequency strategy guides.
3. Duration of the SB: This is highly dependent on the observing priority of the SB. Please see the optimal duration question in the Frequently Asked Questions section. (Note, any length of SB is permitted, i.e., 33min, 1hr12min, etc..)
4. Count: Should the SB be observed more than once?

SB Reports Tab

1. Setup scans: These are needed for observations with both the 8-bit and 3-bit samplers. Please see the 8/3-Bit Attenuation and Setup Scans section for more details (note there are special instructions for S- and P-band observations).
2. Start-up time: This is typically 10-12 minutes at the start of the SB. It is primarily for the initial slew to the first source in the SB and for setup scan(s). These are followed by the first calibrator-intent scan for low frequency observations or the first reference pointing scan for high frequency observations.
3. Scans in Duration (LST) only: In this mode, scans include both slew and on-source time.
4. Antenna Wrap Requests: While checking the elevation, make sure to set the LST start range to avoid antenna wrap issues and request an antenna wrap when appropriate. Note, not all SBs will require an antenna wrap request.
5. Elevation Limits: Ensure that all scans (for all LST start times) have appropriate elevation limits.

• High frequency (> 15 GHz) observing: avoid elevations < 30° (if possible) and > 80° (required).
• Low frequency (< 15 GHz) observing: avoid elevations < 10° (recommended) and > 85°.
• S-band (2-4 GHz) observing: avoid elevations < 20° (recommended to avoid ground spill-over).
• The VLA's hard lower elevation limit is 8°.
• Step through the LST start range to validate elevation limits for all scans.

• Bracket the science target scans with the complex gain calibrator and use the appropriate cycle time: This is especially important for high frequency observing. An exception may be when the target can be self-calibrated. The final decision, however, is up to the observer.
• If observing more than one frequency (LO/IF) setting - this being within a single receiver band or through multiple receiver bands - and switching between them in the SB, there is no guarantee to return to the same phase state upon returning back to a given frequency setting. Therefore, in such cases it is extremely important to bracket the target with complex gain calibrator scans that use the same frequency setting as the target to avoid experiencing any phase jumps.
• All scans have appropriate scan intents: If you wish to use the VLA Calibration Pipeline, a flux density scale and bandpass calibrator must be defined in the SB. (Note, do not use Determine Autophase or apply last Phase & Delay cal; these are reserved only for VLBI observations.)

• Repeat reference pointing scans when the difference from the last pointing position is at least 20° on the sky in AZ or EL.

• For regular (standard observing) scans, no less than 20 seconds on source after slewing. Note that the OPT will assume a minimum slew time of 20 seconds, including "slew" between receiver bands (to rotate and focus the subreflector). This 20s however is too short when P-band and L-band or S-band are involved. For switching between these bands (P↔L or P↔S) add another 15s for the"slew" and thus anticipate a minimum of 35 seconds on source as reported on the Reports tab.
• For flux density scale calibrator (standard observing) scans, no less than 40 seconds on source after slewing.
• For reference pointing scans, no less than 2.5 minutes on source after slewing.

• Regular (standard observing) scan types may be up to 30 minutes in total duration. However, we highly recommend using a sequence of shorter scans to avoid significant loss of data if a scan is dropped during the observation.
• OTF mosaicking scans are not subject to a maximum scan duration limit.
• Interferometric pointing (reference pointing) scans, under practical terms, can be as long as needed to ensure the required minimum 2.5 minutes of on-calibrator time.

Do not observe too close to the Sun, especially at low frequencies. This is not related to selecting the "avoid sunrise/sunset" options within an SB. For more information, refer to the Avoiding the Sun section.

If you would like more help with validating your SB(s) (i.e., instrument configuration or appropriate calibrators), please submit your questions to the NRAO Helpdesk.