JuergensSandbox: Difference between revisions
No edit summary |
|||
(154 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
<math>f</math> | |||
The | The new Karl G. Jansky Very Large Array (VLA) has extremely powerful and versatile spectral capabilities. The final specifications include up to 4 million channels that can be distributed in up to 64 subbands with a spectral resolution from 2MHz down to the the Hz regime. This guide is intended to clarify the spectral line capabilities of the VLA, with a focus on capabilities offered for the August 2012 VLA proposal deadline, and enable users to plan, prepare, and process spectral observations. | ||
<!-- | |||
[http://www.vla.nrao.edu/astro/guides/sline/current/ VLA spectral line guide] | |||
Contents | |||
INTRODUCTION | |||
SYSTEM SPECIFICATIONS | |||
Receivers and IF System | |||
The Local Oscillator Chain | |||
The Correlator | |||
Total Number of Channels | |||
Some Advanced Spectral Line Topics | |||
Creative Use Of The Spectral Line System | |||
High Accuracy Spectral Line Polarization Observations | |||
The Lag Spectrum, Gibbs Phenomenon and Hanning Smoothing | |||
Continuum Observations in Line Mode | |||
OBSERVATIONAL CONSIDERATIONS | |||
Amplitude and Phase Calibration | |||
Bandpass Calibration | |||
Continuum Subtraction | |||
Interference | |||
Bandwidth and Time Smearing | |||
Determining the Observing Frequency | |||
Doppler tracking and dopset | |||
Velocity Definition | |||
Summing Velocities | |||
Velocity Rest Frame | |||
Running dopset | |||
Setting the LO Chain: loser | |||
System Temperature Corrections | |||
Changes In T$_{sys}$ With Elevation (T$_{spill}$) | |||
Contributions to T$_{sys}$ From Strong Lines | |||
REFERENCES | |||
Bandwidth and Number of Channels | |||
Normal Mode | |||
On-line Hanning Smoothing Option | |||
--> | |||
= Introducing VLA Spectral Line Observing = | |||
The newly available wide bandwidths of the VLA allow users to observe up to 8GHz of bandwidth at a time. All observations with the upgraded VLA are inherently spectral observations, including those intended for continuum science. The VLA's improved sensitivity and wide bandwidths greatly enhance the VLA's functionality for spectral line purposes, enabling simultaneous imaging of multiple spectral lines. The WIDAR correlator is extremely flexible and can act as up to 64 independent correlators with different bandwidths, channel numbers, polarization products, and observing frequencies. The final VLA will be 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 64 independently tunable subbands within a baseband; these can be configured with different bandwidths, channel numbers, and polarization products | |||
* tune the baseband and subband frequencies according to the object's velocity with respect to the earth (Doppler Setting) | |||
* dynamically schedule observations to use the best weather conditions for high frequency, high scientific impact projects | |||
<!-- | |||
* Post-processing: The [http://casa.nrao.edu CASA] package is the main data reduction software for VLA and ALMA and contains cutting edge data reduction code with continuum and spectral line processing being the main focus. The software and reference guides can be obtained on the [http://casa.nrao.edu CASA homepage]. The [http://casaguides.nrao.edu CASAguides wiki] contains guides on VLA spectral line data reduction as well as some hints, tips and tricks on using CASA and the visualization tools that are designed to display spectral data cubes | |||
--> | |||
The following capabilities are offered for standard observing in the August 2012 proposal submission deadline. Greater flexibility is available through "shared risk" observing, as discussed below and detailed in the [https://science.nrao.edu/facilities/evla/docs/manuals/oss VLA Observational Status Summary]. | |||
* Maximum data rates of 20MB/s | |||
* Doppler setting | |||
* 8-bit samplers providing | |||
** two 1GHz basebands | |||
** up to 16 independently tunable subbands per baseband | |||
** independent number of polarization products in each subband | |||
** independent subband bandwidths ranging from 31.25kHz to 128MHz | |||
** independent number of channels in each subband; maximum number of channels distributed across all subbands and polarization products cannot exceed 16384 channels | |||
* 3-bit samplers providing | |||
** four 2GHz basebands with a total of 64 128MHz subbands. 2MHz resolution full polarization, 1MHz dual and 0.5MHz single polarization | |||
= Line Frequencies and Velocity Conventions = | |||
== Line Rest Frequencies == | |||
Spectral line calalogues available online are useful for selecting targeted line rest frequencies. The recommended catalog for VLA and ALMA observing is [http://splatalogue.net Splatalogue] which contains molecular line data from sources including the [http://physics.nist.gov/cgi-bin/micro/table5/start.pl Lovas catalog], the [http://spec.jpl.nasa.gov/ JPL/NASA molecular database]], the [http://www.astro.uni-koeln.de/cdms/ Cologne Database for Molecular Spectroscopy], as well as radio recombination lines. | |||
== Observing Frequency and Velocity Definitions == | == Observing Frequency and Velocity Definitions == | ||
The | The frequency at which we must tune the correlator in order to observe a spectral line (<math> \nu </math>) is derived from the radial velocity of the source (v) and the rest frequency of the spectral line (<math> \nu_0 </math>). The ''relativistic velocity'', or true radial velocity, is related to the observed and rest frequencies by <math> v = \frac{\nu_0^{2} - \nu^{2}}{\nu_0^{2}+\nu^{2}}</math>. This equation is a bit cumbersome to use; in astronomy two different approximations are typically used: | ||
* '''Optical Velocity''' <math> v^{optical} = \frac{\lambda-\lambda_0}{\lambda_0}\,\,c = cz </math> (<math>z</math> is the redshift of the source) | |||
* ''' | * '''Radio Velocity''' <math> v^{radio} = \frac{\nu_0-\nu}{\nu_0}\,\,c = \frac{\lambda-\lambda_0}{\lambda}\,\,c \neq v^{optical}</math> | ||
The radio and optical velocities are not identical. Particularly,<math> v^{optical}</math> and <math> v^{radio}</math> diverge for large velocities. Optical velocities are predominantly used for extragalactic and radio velocities for Galactic targets. | |||
The radio and optical velocities are not identical. | |||
At | At high redshifts, it is advisable to place the zero point of the velocity frame into the source via | ||
<math> \nu = \frac{\nu_0}{z+1} </math> | <math> \nu = \frac{\nu_0}{z+1} </math>, | ||
where the redshifted <math>\nu</math> can now be used as the input frequency for the observations. This method will appropriately apply the redshift correction to the channel and line widths and the resulting velocities are also intrinsic to the source. | |||
== Velocity Frames == | == Velocity 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. | The earth rotates, revolves around the sun, rotates around the galaxy, moves within the Local Group, and shows motion against the cosmic microwave background. Any source velocity must therefore always be specified relative to a reference frame. | ||
Various velocity rest frames are used in the literature. The following table lists their name, the motion that is corrected for, and the maximum amplitude of the velocity correction. Each rest frame correction is incremental to the preceding row: | |||
<TABLE CELLPADDING=4 BORDER="1"> | <TABLE CELLPADDING=4 BORDER="1"> | ||
Line 37: | Line 107: | ||
<tr><td>Geocentric</td><td>Earth Center</td><td>Earth rotation</td><td>0.5</td></tr> | <tr><td>Geocentric</td><td>Earth Center</td><td>Earth rotation</td><td>0.5</td></tr> | ||
<tr><td>Earth-Moon Barycentric</td><td>Earth+Moon center of mass</td><td>Motion around Earth+Moon center of mass</td><td>0.013</td></tr> | <tr><td>Earth-Moon Barycentric</td><td>Earth+Moon center of mass</td><td>Motion around Earth+Moon center of mass</td><td>0.013</td></tr> | ||
<tr><td>Heliocentric</td><td>Center of the Sun</td><td>Earth | <tr><td>Heliocentric</td><td>Center of the Sun</td><td>Earth orbital motion</td><td>30</td></tr> | ||
<tr><td>Barycentric</td><td>Earth+Sun center of mass</td><td>Earth+Sun center of mass</td><td>0.012</td></tr> | <tr><td>Barycentric</td><td>Earth+Sun center of mass</td><td>Earth+Sun center of mass</td><td>0.012</td></tr> | ||
<tr><td>Local Standard of Rest (LSR)</td><td>Center of Mass of local stars</td><td>Solar motion relative to nearby stars</td><td>20</td></tr> | <tr><td>Local Standard of Rest (LSR)</td><td>Center of Mass of local stars</td><td>Solar motion relative to nearby stars</td><td>20</td></tr> | ||
Line 48: | Line 118: | ||
<p> | <p> | ||
The velocity frame should be chosen | The velocity frame should be chosen based on the science. For most observations, however, one of the following three reference frames is commonly used: | ||
<br> | |||
* '''Topocentric''' | * '''Topocentric''' is the velocity frame of the observatory (defining the sky frequency of the observations). Visibilities in a measurement set are typically stored in this velocity 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. | * '''Local Standard of Rest''' is the native output of images in CASA. Note that there are two varieties of LSR: the kinematic LSR ('''LSRK''') and the dynamic (LSRD) definitions for the kinematic and dynamic centers, respectively. In almost all cases LSRK is being used and the less precise name 'LSR' is usually used synonymously with more modern LSRK definition. | ||
* '''Barycentric''' is a | * '''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 were frequently used interchangeably. | ||
<br> | |||
A full list of CASA supported reference frames is provided in the [http://casa.nrao.edu/docs/userman/UserMan.html CASA reference Manual and Cookbook] and also on the [http://casaguides.nrao.edu/index.php?title=Velocity_Reference_Frames casaguides.nrao.edu webpage] | |||
== 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. A spectral line's observed frequency will shift during any observing campaign. Within a day, the rotation of the earth dominates and the line may shift up to <math>\pm</math>0.5km/s, depending on the position of the source on the sky (see above). Observing campaigns that span a year may have spectral lines that shift by up to <math>\pm</math>30km/s due to the earth's motion around the sun. | |||
<i>Note: As a rule of thumb, 1 MHz in frequency corresponds roughly to <math>x</math> km/s for the line at a wavelength of <math>x</math> in mm. E.g., at a wavelength of 7mm, 1MHz corresponds to about 7km/s in velocity, at 21cm 1MHz corresponds roughly to 210km/s. </i> | |||
== Doppler | Using this rule of thumb, a line may shift by up to <math>\pm</math>5MHz in Q-band and by up to <math>\pm</math>0.15MHz in L-band over the course of a year. This needs to be taken into account when setting up the observations. This issue can be handled in different ways: | ||
* use the same sky frequency for all observations, accommodating the line shift (maximum of <math>\pm</math>30km/s) by using a wide enough bandwidth to cover the line at any time in the observing campaign. The data is later regridded in CASA to a common LSRK or BARY velocity frame. The sky frequency of an observation can be computed with the [http://www.vla.nrao.edu/astro/guides/dopset/ Dopset tool] for a given time. One may find the LST dates for an observation on the [http://www.vla.nrao.edu/cgi-bin/schedules.cgi VLA Schedule 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''' and offered by OPT '''for each baseband''' (currently only in OSRO mode). The line shift is then reduced to the rotation of the earth (maximum amplitude <math>\pm</math>0.5km/s). This small shift is corrected in data processing. | |||
* 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 pre-upgrade VLA. <i>The new VLA does NOT support Doppler tracking.</i> The WIDAR correlator offers enough bandwidth and spectral channels to cover any line shift and post-processing regridding needs. In addition, a non-variable sky frequency may also deliver a more robust calibration and overall system stability. | |||
The regridding of the spectrum can be completed during data processing in CASA, either directly during imaging in the task <tt>clean</tt>, or alternatively with the task <tt>cvel</tt>. The regridding works well when the spectral features are sampled with at least 4 channels. | |||
= The WIDAR Correlator = | |||
== Basebands == | |||
Let's start with the basics: A signal from the telescope enters WIDAR, is split into its left and right hand circular polarizations, and passes through analog filters that define the <b>basebands</b>. Basebands set the spectral range that can be accessed by subbands, and they come in baseband pairs to cover L and R polarizations. Each baseband pair can be set to one baseband sky frequency. Basebands are the most fundamental spectral ranges delivered from the samplers and digitizers to the correlator. With 8-bit sampling, the samplers deliver two independently tuneable baseband pairs (dubbed A0/C0 and B0/D0) with 1 GHz bandwidth each. 3-bit sampling provides four baseband pairs (A1/C1, A2/C2, B1/D1, B2/D2), each of them 2GHz wide. | |||
[[File:WIDARcorrelatorbands.png|300px|thumb|right|Baseband with WIDAR subbands]] | |||
=== Baseband Tuning Restrictions === | |||
The following restrictions apply to baseband tuning: | |||
* With 8-bit sampling in Ka band, only one baseband can be below 32GHz and that must be B0/D0 | |||
* 3-bit samplers can only be used in C-band or above, where the instantaneous frequency width of the receiver is larger than 2GHz. | |||
* The 3-bit A1C1 baseband frequency can have a separation of max. 4GHz from the A2D2 baseband. B1D1 and B2D2 have the same restriction of 4GHz maximum separation | |||
== Fixed 128MHz Subbands and 128MHz "Suckouts" == | |||
After filtering through the basebands, the signal enters the correlator and is split into fixed, 128MHz wide subbands. They are placed adjacently to cover the full width of the basebands. Narrow subbands can be arranged within these fixed 128MHz subbands. Because each fixed 128MHz subband has a filter shape with soft corners, the sensitivity of the VLA drops to about half its maximum value between any two fixed 128MHz subbands. These frequency ranges are called "128 MHz Suckouts". There are two primary options for dealing with the suckouts: | |||
1. Try to set the baseband frequency such that targeted lines do not fall in the suckouts. We offer the [https://e2e.nrao.edu/tune.shtml spectral line setup tool "TUNE"] that can be used to maximize the frequency separation between a number of spectral lines and the suckouts. | |||
2. If it is not possible to obtain coverage of all of your lines using the above method, observe with two basebands shifted by 10-64MHz apart. This will ensure that at one baseband covers the suckouts of the other baseband with full sensitivity. An example is given in the figures to the right. | |||
[[File:BlankFieldRMS.AC.png|300px|thumb|right| | |||
rms noise in a blank field as a function of frequency for one baseband consisting of 8 contiguous sub-bands. Note the increased rms noise at the subband edges.]] | |||
[[File:BlankFieldRMS.interlace.png|300px|thumb|right| | |||
rms noise in a blank field as a function of frequency for two basebands consisting of 8 contiguous sub-bands, where the basebands are separated by one-half of the subband width. Wherever signal in one baseband is compromised by edge effects, data from the other subband are substituted.]] | |||
== Correlator Resources and Subband Placement == | |||
Correlator baselineboards (BlBs, also named "BL.BPS" for "baselineboard pairs" in the OPT) are independent hardware units that are allocated to narrow subbands. <b>WIDAR has 64 baselineboard pairs.</b> As a result, WIDAR supports a maximum of 64 subband pairs (again, pairs to cover the two polarizations), but the number of subbands depends on the subband setups as described below. For the same number of channels, single (RR or LL), dual (RR & LL), and full (RR, LL, RL, and LR) polarization products require 1, 2, and 4 times the correlator baselineboards respectively. Similarly, doubling the number of channels in a subband doubles the number of correlator resources used. | |||
=== Narrow Subbands with the 8-bit sampler === | |||
Narrow subbands define the frequency ranges in which the spectrum is measured. Narrow subbands with bandwidths between 31.25kHz and 128MHz can be arranged to obtain desired frequency coverage and spectral resolution within the baseband. Each narrow subband needs to be entirely within a fixed 128MHz subband, as <b> narrow subbands cannot cross a 128MHz suckout frequency.</b> The baseband center frequency can be shifted and subband bandwidths and frequencies must be arranged to avoid the suckouts. This implies that the 128MHz fixed subbands cannot be moved as they would fall on a suckout at any frequency offset from a 128MHz "raster" within the baseband. All subbands less than 128MHz in width, however, and can be independently tuned as long as they do not cross a suckout. Furthermore, <i>all subbands can be set up with different bandwidths, frequency resolutions, channel numbers, and polarization products.</i> | |||
=== Standard Subbands === | |||
Standard subbands allocate a single baselineboard pair to a each subband. Standard subbands contain 64 channels when full polarization (RR,LL, RL & LR) products are required, 128 channels in dual polarization mode (RR & LL), and 256 channels for single polarization (RR or LL). Options for full and dual polarization subbands, with frequency and velocity resolutions, are shown in the following tables. For the August 2012 deadline, we offer up to 16 subbands per baseband for normal observations, and up to 64 for shared risk observations. | |||
* Full polarization | |||
<table class="grid listing" border="1"> | |||
<tr valign="top"> | |||
<th>Sub-band BW (MHz) </th><th>Number of channels/poln product </th><th>Channel width (kHz) </th><th>Channel width (km/s at 1 GHz) </th><th>Total velocity coverage per sub-band (km/s at 1 GHz) </th> | |||
</tr> | |||
<tr valign="top"> | |||
<td>128</td> | |||
<td>64</td> | |||
<td>2000</td> | |||
<td>600/ν(GHz)</td> | |||
<td>38,400/ν(GHz)</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>64</td> | |||
<td>64</td> | |||
<td>1000</td> | |||
<td>300</td> | |||
<td>19,200</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>32</td> | |||
<td>64</td> | |||
<td>500</td> | |||
<td>150</td> | |||
<td>9,600</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>16</td> | |||
<td>64</td> | |||
<td>250</td> | |||
<td>75</td> | |||
<td>4,800</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>8</td> | |||
<td>64</td> | |||
<td>125</td> | |||
<td>37.5</td> | |||
<td>2,400</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>4</td> | |||
<td>64</td> | |||
<td>62.5</td> | |||
<td>19</td> | |||
<td>1,200</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>2</td> | |||
<td>64</td> | |||
<td>31.25</td> | |||
<td>9.4</td> | |||
<td>600</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>1</td> | |||
<td>64</td> | |||
<td>15.625</td> | |||
<td>4.7</td> | |||
<td>300</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>0.5</td> | |||
<td>64</td> | |||
<td>7.813</td> | |||
<td>2.3</td> | |||
<td>150</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>0.25</td> | |||
<td>64</td> | |||
<td>3.906</td> | |||
<td>1.2</td> | |||
<td>75</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>0.125</td> | |||
<td>64</td> | |||
<td>1.953</td> | |||
<td>0.59</td> | |||
<td>37.5</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>0.0625</td> | |||
<td>64</td> | |||
<td>0.977</td> | |||
<td>0.29</td> | |||
<td>18.75</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>0.03125</td> | |||
<td>64</td> | |||
<td>0.488</td> | |||
<td>0.15</td> | |||
<td>9.375</td> | |||
</tr> | |||
</table> | |||
* Dual Polarization | |||
<table class="grid listing" border="1"> | |||
<tr valign="top"> | |||
<th>Sub-band BW (MHz) </th><th>Number of channels/poln product </th><th>Channel width (kHz) </th><th>Channel width (km/s at 1 GHz) </th><th>Total velocity coverage (km/s at 1 GHz) </th> | |||
</tr> | |||
<tr valign="top"> | |||
<td>128</td> | |||
<td>128</td> | |||
<td>1000</td> | |||
<td>300/ν(GHz)</td> | |||
<td>38,400/ν(GHz)</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>64</td> | |||
<td>128</td> | |||
<td>500</td> | |||
<td>150</td> | |||
<td>19,200</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>32</td> | |||
<td>128</td> | |||
<td>250</td> | |||
<td>75</td> | |||
<td>9,600</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>16</td> | |||
<td>128</td> | |||
<td>125</td> | |||
<td>37.5</td> | |||
<td>4,800</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>8</td> | |||
<td>128</td> | |||
<td>62.5</td> | |||
<td>19</td> | |||
<td>2,400</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>4</td> | |||
<td>128</td> | |||
<td>31.25</td> | |||
<td>9.4</td> | |||
<td>1,200</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>2</td> | |||
<td>128</td> | |||
<td>15.625</td> | |||
<td>4.7</td> | |||
<td>600</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>1</td> | |||
<td>128</td> | |||
<td>7.813</td> | |||
<td>2.3</td> | |||
<td>300</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>0.5</td> | |||
<td>128</td> | |||
<td>3.906</td> | |||
<td>1.2</td> | |||
<td>150</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>0.25</td> | |||
<td>128</td> | |||
<td>1.953</td> | |||
<td>0.59</td> | |||
<td>75</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>0.125</td> | |||
<td>128</td> | |||
<td>0.977</td> | |||
<td>0.29</td> | |||
<td>37.5</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>0.0625</td> | |||
<td>128</td> | |||
<td>0.488</td> | |||
<td>0.15</td> | |||
<td>18.75</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>0.03125</td> | |||
<td>128</td> | |||
<td>0.244</td> | |||
<td>0.073</td> | |||
<td>9.375</td> | |||
</tr> | |||
</table> | |||
=== Baselineboard Stacking === | |||
In order to obtain a larger number of channels per subband, a method called "baselineboard stacking" can be used. Baselineboard stacking allows a larger number of baseline boards to be allocated to a single subband, increasing the number of channels within the subband. To double the number of channels in a subband, simply double the number of baselineboards allocated to the subband. Thus each additional BlB for a subband adds another 64 channels in full and 128 channels in dual, and 256 channels in single polarization modes. | |||
As an example, the full 2GHz bandwidth of the 8-bit samplers can be covered by 16 128MHz standard narrow subbands, each with 128 channels in dual polarization, as shown in the table above. The 16 subbands, however, only require 16 BlBs and another 48 are available for baselineboard stacking. One can thus use 4 BlBs for each of the subbands, quadrupling the number of channels from 128 to 512, which reduces the channel widths from 1MHz to 0.25 MHz over the full 2 GHz frequency range. This method works for any subband bandwidth. | |||
Baselineboard stacking can be very useful for spectral line work, as it allows for wider bandwidths for each subband while maintaining frequency resolution. With baselineboard stacking, you can use fewer subbands to cover a set frequency range, thereby minimizing the number of filter edges and resulting sensitivity dropoff. Baselineboard stacking is offered for the August 2012 deadline. For shared risk observations, however, we recommend that observers do not use all 64 baselineboards to allow for observing in the event that one or two baselineboards are not working on any given day. | |||
<!-- JUERGEN - might be helpful to have a table that shows the # of channels in a single, dual, and full polarization subband and the # of baselineboard pairs allocated --> | |||
=== Recirculation === | |||
"Recirculation" is a second method for obtaining more spectral channels in a given subband. Recirculation uses the fact that the correlator has more computing capability when the data is averaged in time. The standard correlator dump time is 1s. If this is doubled to 2s, WIDAR can produce twice as many channels as listed in the tables above. 4s would allow 4 times the number of channels. Recirculation is only available for shared risk observations for the August 2012 proposal deadline. | |||
== Narrow Subbands with the 3-bit sampler == | |||
As the 3-bit samplers are still under commissioning, the August 2012 proposal deadline offers only a single observing setup with 3-bit sampling. This setup includes full coverage over all four baseband pairs (using 64 128MHz subband) 2MHz resolution for full polarization, 1MHz dual, and 0.5MHz for single polarization. | |||
== Data Rate Limits == | |||
Baselineboard stacking, recirculation, and time resolution can add up to an extremely high data rate in the correlator. The VLA currently supports data rates of up to 20MB/s for regular and more for shared risk observing, see the [https://science.nrao.edu/facilities/evla/docs/manuals/oss Observational Status Summary for details]. The OPT instrument configuration calculates data rates based on the spectral line setup and the data rate maxima should not be exceeded for any observational setup. | |||
= Tips for Planning, Setup, and Processing of VLA Spectral Line Observations = | |||
'''Reminder:''' The following capabilities are offered for regular observing for the August 1 2012 proposal deadline. Consult the [https://science.nrao.edu/facilities/evla/docs/manuals/oss VLA Observational Status Summary] for additional options available through shared risk observing: | |||
* Maximum data rates of 20MB/s | |||
* Doppler setting | |||
* 8-bit samplers providing | |||
** two 1GHz basebands | |||
** up to 16 independently tunable subbands per baseband | |||
** independent number of polarization products in each subband | |||
** independent subband bandwidths ranging from 31.25kHz to 128MHz | |||
** independent number of channels in each subband; maximum number of channels distributed across all subbands and polarization products cannot exceed 16384 channels | |||
* 3-bit samplers providing | |||
** four 2GHz basebands with a total of 64 128MHz subbands. 2MHz resolution full polarization, 1MHz dual and 0.5MHz single polarization | |||
== Considerations for Planning Subband Bandwidths and Resolution == | |||
=== Bandwidths required for UV continuum subtraction === | |||
When determining the bandwidths needed in your subbands, it is important to observe enough line-free channels on each side of the spectral line to allow for good continuum subtraction. It is possible to interpolate the continuum levels from one subband to another, but it is usually a better solution to derive the continuum level in each subband separately. The number of line free channels ideally equals or exceeds the number of channels that cover the line. When the line free channels are distributed equally on both sides of the spectral line, a low order polynomial (polynomials of order 1 appear to be good models for most cases) usually provides a good fit. Whenever higher order polynomials are needed, e.g. for a continuum source with a significant spectral curvature over the subband(s), the number of line-free channels should be increased. | |||
=== Channel Widths for High Dynamic Range Imaging: Dealing with the Gibbs Phenomenon === | |||
For very sharp spectral or lag features, the spectrum can prominently display a ringing effect known as the Gibbs phenomenon, a sinc function that zig-zags on alternating channels. If this is apparent in the data, smoothing adjacent channels will reduce or even eliminate the effect. Hanning smoothing is the most effective method, which uses a triangular smoothing kernel with the central channel weighed by 0.5 and the two adjacent channels by 0.25. After Hanning smoothing, however, the channels are not independent anymore and one can eliminate every other channel without losing signal to noise. | |||
In the pre-upgrade VLA days, the correlator design had a realtively short, truncated lag spectrum, which could result in prominent Gibbs ringing. To avoid this effect, Hanning smoothing was frequently applied online during the observations. With the new WIDAR capabilities of the upgraded VLA, however, ringing is very rare and only observed for extremely strong maser or RFI sources. Consequently, the VLA does not support online Hanning smoothing anymore; if required, Hanning smoothing can be applied during post-processing (e.g. with the CASA task [http://casa.nrao.edu/docs/TaskRef/hanningsmooth-task.html <i>hanningsmooth</i>].). The Gibbs effect can also be reduced by using higher spectral resolution that covers the spectral feature with several channels. In that case, the ringing effects from the individual channels beat against each other, effectively reducing the zig-zag pattern that appears on alternating, neighboring channels when the peak is within a single spectral channel. | |||
== Sensitivity/Exposure Time Calculation == | |||
[[File:ExposureCalculator.png|300px|thumb|right|The VLA Exposure Calculator]] | |||
After planning your general setup and sensitivity needs, the required on-source observing time is best calculated with the [https://science.nrao.edu/facilities/evla/calibration-and-tools/exposure VLA Exposure Calculator]. This JAVA tool (see screenshot) allows one to input the required rms noise and bandwidth limits and outputs the required time on source given a frequency, weather, weighting scheme, and number of polarization products. The input '''Bandwidth''' should correspond to the frequency resolution that is required to perform the science. This may or may not be the width of individual spectral channels. Overheads need to be added according to our [https://science.nrao.edu/facilities/evla/proposing/frequently-asked-questions VLA frequently asked questions webpage]. We refer to the [http://evlaguides.nrao.edu/index.php?title=Category:LowFrequency low frequency guide] and [http://evlaguides.nrao.edu/index.php?title=Category:HighFrequency high frequency guide] for further advice on how to set up the observations, depending on the receiver band to be used. | |||
== The Proposal Submission Tool (PST) == | |||
The Proposal Submission Tool (PST, accessible at [http://my.nrao.edu my.nrao.edu] ) is used to submit proposals, including the scientific justification, abstract, and authors, as well as planned target sources, observing session lengths, and correlator setups. In order to ensure that planned correlator setups comply with the capabilities offered for the August 2012 deadline, the Proposal Submission Tool (PST) includes a spectral setup tool. | |||
< | <!-- link to Michaels docs--> | ||
[[File:PST-narrow.png|200px|thumb|right|Snapshot of the 8-bit sampler, 2x1GHz PST setup tool]] | |||
In the example to the right, 9 subbands were chosen in Ka band with 8-bit sampling. Four of the subbands are in the first and five in the second baseband. The setup features different subband bandwidths, polarization products and uses baselineboard stacking (up to 16 baseline board pairs per subband pair are used for a couple of subbands). A total of 49 baseline boards are used for this configuration. | |||
[[File:PST-wide.png|200px|thumb|right|Snapshot of the 3-bit sampler, wideband mode PST setup tool]] | |||
Wide-band mode (3-bit sampler, up to 8GHz bandwidth) can be used for spectral line observing as well. The channel width is fixed to a resolution of 2MHz for full, 1MHz for dual and 0.5MHz for single polarization products. No narrow subbands can be chosen. | |||
== | == Setting up a Spectral Observation using the Observation Preparation Tool (OPT) == | ||
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 program used for a single observing run. This consists of at least a few startup scans, a pointing reference, a bandpass calibration, a flux calibration, gain calibration and target observations. In the OPT, you specify your sources, scan lengths and order, and correlator setups. A full project may consist of several SBs. To access the OPT, go to [http://my.nrao.edu my.nrao.edu] and click on the ''Obs Prep'' tab, followed by [https://e2e.nrao.edu/opt/ ''Login to the Observation Preparation Tool'']. Instructions for using the OPT and for selecting appropriate calibrators are provided in the [http://evlaguides.nrao.edu/index.php?title=Category:OPT-QuickStart OPT QuickStart Guide], and a comprehensive user's manual and up to date information on the OPT are available at [https://science.nrao.edu/facilities/evla/observing/opt OPT webpage]. As such, this guide provides only brief notes on the bandpass and gain calibrators and then focuses on the task of setting up correlator resources. | |||
=== 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. This implies that, for a bandpass calibrator with flux density S<sub>cal</sub> observed for a time t<sub>cal</sub> and a science target with flux density S<sub>obj</sub> observed for a time t<sub>obj</sub>, <math> S_{cal} \sqrt{t_{cal}}</math> should be greater than <math>S_{obj} \sqrt{t_{obj}}</math>. How many times greater will be determined by one's science goals and the practicalities of the observations, but <math> S_{cal} \sqrt{t_{cal}}</math> 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 chose 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 [http://casa.nrao.edu/docs/TaskRef/bandpass-task.html 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, Q), 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. <!-- JUERGEN - can you suggest any --> 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 that narrow one. This may be good to a level of a few per cent, but we advise to use that option only when absolutely necessary. | |||
The | The stability of bandpasses as a function of time is of concern for high-dynamic-range spectral work. 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.42GHz, the error is in the per cent range. A guide for CASA is described on [http://casaguides.nrao.edu/index.php?title=Combining_Bandpasses this CASAguides wiki page]. | |||
<!-- JUERGEN - some of this should be incorporated into the QuickStart Guide --> | |||
=== Phase/Complex Gain Calibration === | |||
The complex gain (phase/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 gain calibrator and the science target. For weak calibrators, however, it is possible to use wider bandwidths for the phase calibrator and then transfer the phases to the source. However, there will be a phase offset between them. The phase offset between the narrow and wide subbands can be determined by observing a strong source (e.g. the bandpass calibrator) and applied in post-processing from the complex gain calibrator to the target sources. A similar method can be used if the complex gain calibrator is observed at a slightly different frequency, e.g. to avoid a contaminating line feature such as Galactic HI. | |||
=== Correlator Resources Setup === | |||
- | '''For the data taken early 2013 (August 2012 deadline), we will provide a specific new OPT Instrument Configuration layout for the regular and shared risk observing modes. The description below is for the current OSRO and RSRO modes. ''' <!-- JUERGEN - Not sure if you need to explain the current OPT resources, since this guide is designed for the Aug 2012 deadline. Just a thought --> | ||
- | Correctly specifying the WIDAR setup is essential for spectral line observations. In the OPT, click on the ''Instrument Configuration'' tab. The most advanced setting is currently the RSRO setting (''File -> Create New -> RSRO Configuration''). This opens a page for the frequency setup as shown in the figures. Note that you may only have access to the OSRO configuration utility, depending on your history of VLA observations. The OSRO setup is a more restricted version of the RSRO setup. | ||
- | |||
* Enter a name and select the receiver in the top panel. This will adjust the available frequency range described below the drop down menu. The 1dB and 3dB ranges describe the roll-off behavior of the receiver sensitivity at the receiver band edges. If the frequency to be observed is close to the edge frequency of a receiver, one may check if the next higher or lower frequency receiver is more suitable. | |||
* ''Baseband Tuning'': Select the position of the basebands. For the ''8bit samplers'', the central frequencies for 2 basebands are to be provided, each with a width of 1GHz. The center frequencies will go into the A0C0 box for frequency 1 and into the B0D0 box for frequency 2. For ''3bit samplers'', 4 basebands are available, each 2 GHz wide. Here, the center frequencies need to placed into the A1C1, A2C2, B1D1, and B2D2 boxes. A1C1 and A2C2 cannot be more than 4GHz apart, and the same restrictions apply to B1D1 and B2D2. Note that additional frequency restrictions may apply and the OPT/ICT will issue a clear warning or error message for those cases. The graphical panel above the input boxes shows the position of the two or four basebands. They are displayed as pairs to accommodate the R and L polarization inputs that may later be converted into single, dual, or full polarization products. | |||
* | * ''Integration Time:'' this defines how data is dumped from the correlator backend into data files. A larger integration time will reduce the data volume. In addition, larger values can be chosen to take advantage of recirculation (only shared risk). On the other hand, time smearing effects, RFI excision, or time resolution may demand smaller integration times. It is important though, to not exceed the maximum data rate of 60MB/s (15MB/s for regular observing) and the integration time parameter is a good way to stay below this threshold for observations that demand large number of spectral channels. | ||
* | * The total data rates are displayed in the ''Configuration Summary''. The same panel also shows the number of baseline boards that are used in the setup. Remember that a maximum of 64 baseline boards are available and make sure that the data rate limits are not exceeded. | ||
[[File:OPT-config1.png|200px|thumb|right|OPT - Instrument Configuration: Baseband Settings]] | |||
[[File:OPT-config2.png|200px|thumb|right|OPT - Instrument Configuration: Subband Settings]] | |||
* '''Subband Setup''': Depending on the baseband setup, the '''Subband Configuration''' panel sports tabs for each baseband. Under each tab one can now select the individual subbands. Up to 64 subbands are available (16 for regular observing): click ''Add subband'' to create a subband setting and select the frequency range from the "Sky Range" drop-down menu. The ''Offset Freq from Center'' shows the placement of the subband with respect to the baseband center. For small bandwidths, the drop-down menu is not available as there are too many choices and the placement needs to be entered by hand in the ''Offset Freq from Center'' box. In the current OSRO/RSRO interface, the subbands are not independently tunable yet (but this feature will be available for the August 2012 deadline) and the subbands will snap on a frequency grid defined by the subband bandwidth. Now select the number of polarization products and the number of channels will be displayed in the ''Spectral Points'' box. The ''comments box'' can be used to describe the setup, e.g. by entering the transitions that should fall in that subband. Those entries are currently not used anywhere outside OPT. The ''delete'' button removes the subband if is no longer required, and ''Bulk Edit'' is used for bulk editing of many subbands (see the OPT guide on this feature). '''Note: if you chose subbands with different bandwidths during OSRO/RSRO, contact NRAO staff as these scripts currently need manual editing after OPT submission.''' | |||
* If not all subbands are used, one can use the remaining baseline boards to obtain a higher spectral resolution for those in the Subband Configuration panel. Select a higher number in the ''BL.BPS'' drop-down panel for baselineboard stacking. During commissioning, we recommend to use 2,4,8, etc. BlBs here but in principle any of the options in the drop down menu should work. | |||
* | * Recirculation: only shared risk | ||
<!-- JUERGEN - maybe consider giving only a few pointers, and saying that the instructions are in the quick start guide. I'm not sure that you need specific instructions in this guide. --> | |||
==== Using Doppler Setting ==== | |||
[[File:Doppler.png|200px|thumb|right|OPT - Doppler Setting]] | |||
Doppler setting will calculate the sky frequency of your observation based on the time of the observation, the source velocity, position and line rest frequency. In contrast to Doppler tracking, Doppler setting calculates this once '''for each baseband''' at the start of the observation (execution time of the SB) and the sky frequency will stay fixed for the entire run of the SB. Every subsequent run of the SB will perform a recalculation of the sky frequency. Doppler setting is currently only supported in OSRO mode (and will be available for the August 2012 deadline), RSRO observers need to calculate their own sky frequency (which is usually not too difficult given that the movement of the earth shifts the line by <math>\pm</math>30 km/s over a year, <math>\pm</math>0.5 km/s over a day - a velocity range that can under almost any circumstances be accommodated for by the wide bandwidths of WIDAR). <!-- JUERGEN - most of this is said above. Not sure if you want it to be said twice. --> | |||
To use Doppler Setting, first select ''Rest'' in the baseband frequency setup section of the OPT/Instrument Configuration Tool. All velocities will then be calculated against the center baseband frequency which may or may not be the rest frequency of your spectral line. Supply the reference position (a source from a catalog can be chosen, typically this will be your target source) and the velocity with their frames in the ''Doppler Setting'' section in the OPT/ICT. Doppler Setting can only be applied for each baseband and all subbands will shift by the same frequency amount, offset by the the subband tunings. | |||
== | == Post-Processing Guidelines == | ||
= | please see our [http://casaguides.nrao.edu/index.php?title=EVLA_Tutorials extensive VLA turoials] on the [http://casaguides.nrao.edu/ CASAguides wiki] for examples of how to process VLA spectra line data. |
Latest revision as of 14:05, 2 July 2012
The new Karl G. Jansky Very Large Array (VLA) has extremely powerful and versatile spectral capabilities. The final specifications include up to 4 million channels that can be distributed in up to 64 subbands with a spectral resolution from 2MHz down to the the Hz regime. This guide is intended to clarify the spectral line capabilities of the VLA, with a focus on capabilities offered for the August 2012 VLA proposal deadline, and enable users to plan, prepare, and process spectral observations.
Introducing VLA Spectral Line Observing
The newly available wide bandwidths of the VLA allow users to observe up to 8GHz of bandwidth at a time. All observations with the upgraded VLA are inherently spectral observations, including those intended for continuum science. The VLA's improved sensitivity and wide bandwidths greatly enhance the VLA's functionality for spectral line purposes, enabling simultaneous imaging of multiple spectral lines. The WIDAR correlator is extremely flexible and can act as up to 64 independent correlators with different bandwidths, channel numbers, polarization products, and observing frequencies. The final VLA will be 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 64 independently tunable subbands within a baseband; these can be configured with different bandwidths, channel numbers, and polarization products
- tune the baseband and subband frequencies according to the object's velocity with respect to the earth (Doppler Setting)
- dynamically schedule observations to use the best weather conditions for high frequency, high scientific impact projects
The following capabilities are offered for standard observing in the August 2012 proposal submission deadline. Greater flexibility is available through "shared risk" observing, as discussed below and detailed in the VLA Observational Status Summary.
- Maximum data rates of 20MB/s
- Doppler setting
- 8-bit samplers providing
- two 1GHz basebands
- up to 16 independently tunable subbands per baseband
- independent number of polarization products in each subband
- independent subband bandwidths ranging from 31.25kHz to 128MHz
- independent number of channels in each subband; maximum number of channels distributed across all subbands and polarization products cannot exceed 16384 channels
- 3-bit samplers providing
- four 2GHz basebands with a total of 64 128MHz subbands. 2MHz resolution full polarization, 1MHz dual and 0.5MHz single polarization
Line Frequencies and Velocity Conventions
Line Rest Frequencies
Spectral line calalogues 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 frequency at which we must tune the correlator in order to observe a spectral line () is derived from the radial velocity of the source (v) and the rest frequency of the spectral line (). The relativistic velocity, or true radial velocity, is related to the observed and rest frequencies by . This equation is a bit cumbersome to use; in astronomy two different approximations are typically used:
- Optical Velocity ( is the redshift of the source)
- Radio Velocity
The radio and optical velocities are not identical. Particularly, and diverge for large velocities. Optical velocities are predominantly used for extragalactic and radio velocities for Galactic targets.
At high redshifts, it is advisable to place the zero point of the velocity frame into the source via
,
where the redshifted can now be used as the input frequency for the observations. This method will appropriately apply the redshift correction to the channel and line widths and the resulting velocities are also intrinsic to the source.
Velocity 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. Any source velocity must therefore 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:
Rest Frame Name | Rest Frame | Correct for | Max amplitude [km/s] |
Topocentric | Telescope | Nothing | 0 |
Geocentric | Earth Center | Earth rotation | 0.5 |
Earth-Moon Barycentric | Earth+Moon center of mass | Motion around Earth+Moon center of mass | 0.013 |
Heliocentric | Center of the Sun | Earth orbital motion | 30 |
Barycentric | Earth+Sun center of mass | Earth+Sun center of mass | 0.012 |
Local Standard of Rest (LSR) | Center of Mass of local stars | Solar motion relative to nearby stars | 20 |
Galactocentric | Center of Milky Way | Milky Way Rotation | 230 |
Local Group Barycentric | Local Group center of mass | Milky Way Motion | 100 |
Virgocentric | Center of the Local Virgo supercluster | Local Group motion | 300 |
Cosmic Microwave Background | CMB | Local Supercluster Motion | 600 |
The velocity frame should be chosen based on the science. For most observations, however, one of the following three reference frames is commonly used:
- Topocentric is the velocity frame of the observatory (defining the sky frequency of the observations). Visibilities in a measurement set are typically stored in this velocity frame.
- Local Standard of Rest is the native output of images in CASA. Note that there are two varieties of LSR: the kinematic LSR (LSRK) and the dynamic (LSRD) definitions for the kinematic and dynamic centers, respectively. In almost all cases LSRK is being used and the less precise name 'LSR' is usually used synonymously with more modern LSRK definition.
- 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 were frequently used interchangeably.
A full list of CASA supported reference frames is provided in the CASA reference Manual and Cookbook and also on the casaguides.nrao.edu webpage
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. A spectral line's observed frequency will shift during any 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 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.
Note: As a rule of thumb, 1 MHz in frequency corresponds roughly to km/s for the line at a wavelength of in mm. E.g., at a wavelength of 7mm, 1MHz corresponds to about 7km/s in velocity, at 21cm 1MHz corresponds roughly to 210km/s.
Using this rule of thumb, a line may shift by up to 5MHz in Q-band and by up to 0.15MHz in L-band over the course of a year. This needs to be taken into account when setting up the observations. This issue can be handled in different ways:
- use the same sky frequency for all observations, accommodating the line shift (maximum of 30km/s) by using a wide enough bandwidth to cover the line at any time in the observing campaign. The data is later regridded in CASA to a common LSRK or BARY velocity frame. The sky frequency of an observation can be computed with the Dopset tool for a given time. One may find the LST dates for an observation on the VLA Schedule 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 and offered by OPT for each baseband (currently only in OSRO mode). The line shift is then reduced to the rotation of the earth (maximum amplitude 0.5km/s). This small shift is corrected in data processing.
- 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 pre-upgrade VLA. The new 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. In addition, a non-variable sky frequency may also deliver a more robust calibration and overall system stability.
The regridding of the spectrum can be completed during data processing in CASA, either directly during imaging in the task clean, or alternatively with the task cvel. The regridding works well when the spectral features are sampled with at least 4 channels.
The WIDAR Correlator
Basebands
Let's start with the basics: A signal from the telescope enters WIDAR, is split into its left and right hand circular polarizations, and passes through analog filters that define the basebands. Basebands set the spectral range that can be accessed by subbands, and they come in baseband pairs to cover L and R polarizations. Each baseband pair can be set to one baseband sky frequency. Basebands are the most fundamental spectral ranges delivered from the samplers and digitizers to the correlator. With 8-bit sampling, the samplers deliver two independently tuneable baseband pairs (dubbed A0/C0 and B0/D0) with 1 GHz bandwidth each. 3-bit sampling provides four baseband pairs (A1/C1, A2/C2, B1/D1, B2/D2), each of them 2GHz wide.
Baseband Tuning Restrictions
The following restrictions apply to baseband tuning:
- With 8-bit sampling in Ka band, only one baseband can be below 32GHz and that must be B0/D0
- 3-bit samplers can only be used in C-band or above, where the instantaneous frequency width of the receiver is larger than 2GHz.
- The 3-bit A1C1 baseband frequency can have a separation of max. 4GHz from the A2D2 baseband. B1D1 and B2D2 have the same restriction of 4GHz maximum separation
Fixed 128MHz Subbands and 128MHz "Suckouts"
After filtering through the basebands, the signal enters the correlator and is split into fixed, 128MHz wide subbands. They are placed adjacently to cover the full width of the basebands. Narrow subbands can be arranged within these fixed 128MHz subbands. Because each fixed 128MHz subband has a filter shape with soft corners, the sensitivity of the VLA drops to about half its maximum value between any two fixed 128MHz subbands. These frequency ranges are called "128 MHz Suckouts". There are two primary options for dealing with the suckouts:
1. Try to set the baseband frequency such that targeted lines do not fall in the suckouts. We offer the spectral line setup tool "TUNE" that can be used to maximize the frequency separation between a number of spectral lines and the suckouts.
2. If it is not possible to obtain coverage of all of your lines using the above method, observe with two basebands shifted by 10-64MHz apart. This will ensure that at one baseband covers the suckouts of the other baseband with full sensitivity. An example is given in the figures to the right.
Correlator Resources and Subband Placement
Correlator baselineboards (BlBs, also named "BL.BPS" for "baselineboard pairs" in the OPT) are independent hardware units that are allocated to narrow subbands. WIDAR has 64 baselineboard pairs. As a result, WIDAR supports a maximum of 64 subband pairs (again, pairs to cover the two polarizations), but the number of subbands depends on the subband setups as described below. For the same number of channels, single (RR or LL), dual (RR & LL), and full (RR, LL, RL, and LR) polarization products require 1, 2, and 4 times the correlator baselineboards respectively. Similarly, doubling the number of channels in a subband doubles the number of correlator resources used.
Narrow Subbands with the 8-bit sampler
Narrow subbands define the frequency ranges in which the spectrum is measured. Narrow subbands with bandwidths between 31.25kHz and 128MHz can be arranged to obtain desired frequency coverage and spectral resolution within the baseband. Each narrow subband needs to be entirely within a fixed 128MHz subband, as narrow subbands cannot cross a 128MHz suckout frequency. The baseband center frequency can be shifted and subband bandwidths and frequencies must be arranged to avoid the suckouts. This implies that the 128MHz fixed subbands cannot be moved as they would fall on a suckout at any frequency offset from a 128MHz "raster" within the baseband. All subbands less than 128MHz in width, however, and can be independently tuned as long as they do not cross a suckout. Furthermore, all subbands can be set up with different bandwidths, frequency resolutions, channel numbers, and polarization products.
Standard Subbands
Standard subbands allocate a single baselineboard pair to a each subband. Standard subbands contain 64 channels when full polarization (RR,LL, RL & LR) products are required, 128 channels in dual polarization mode (RR & LL), and 256 channels for single polarization (RR or LL). Options for full and dual polarization subbands, with frequency and velocity resolutions, are shown in the following tables. For the August 2012 deadline, we offer up to 16 subbands per baseband for normal observations, and up to 64 for shared risk observations.
- Full polarization
Sub-band BW (MHz) | Number of channels/poln product | Channel width (kHz) | Channel width (km/s at 1 GHz) | Total velocity coverage per sub-band (km/s at 1 GHz) |
---|---|---|---|---|
128 | 64 | 2000 | 600/ν(GHz) | 38,400/ν(GHz) |
64 | 64 | 1000 | 300 | 19,200 |
32 | 64 | 500 | 150 | 9,600 |
16 | 64 | 250 | 75 | 4,800 |
8 | 64 | 125 | 37.5 | 2,400 |
4 | 64 | 62.5 | 19 | 1,200 |
2 | 64 | 31.25 | 9.4 | 600 |
1 | 64 | 15.625 | 4.7 | 300 |
0.5 | 64 | 7.813 | 2.3 | 150 |
0.25 | 64 | 3.906 | 1.2 | 75 |
0.125 | 64 | 1.953 | 0.59 | 37.5 |
0.0625 | 64 | 0.977 | 0.29 | 18.75 |
0.03125 | 64 | 0.488 | 0.15 | 9.375 |
- Dual Polarization
Sub-band BW (MHz) | Number of channels/poln product | Channel width (kHz) | Channel width (km/s at 1 GHz) | Total velocity coverage (km/s at 1 GHz) |
---|---|---|---|---|
128 | 128 | 1000 | 300/ν(GHz) | 38,400/ν(GHz) |
64 | 128 | 500 | 150 | 19,200 |
32 | 128 | 250 | 75 | 9,600 |
16 | 128 | 125 | 37.5 | 4,800 |
8 | 128 | 62.5 | 19 | 2,400 |
4 | 128 | 31.25 | 9.4 | 1,200 |
2 | 128 | 15.625 | 4.7 | 600 |
1 | 128 | 7.813 | 2.3 | 300 |
0.5 | 128 | 3.906 | 1.2 | 150 |
0.25 | 128 | 1.953 | 0.59 | 75 |
0.125 | 128 | 0.977 | 0.29 | 37.5 |
0.0625 | 128 | 0.488 | 0.15 | 18.75 |
0.03125 | 128 | 0.244 | 0.073 | 9.375 |
Baselineboard Stacking
In order to obtain a larger number of channels per subband, a method called "baselineboard stacking" can be used. Baselineboard stacking allows a larger number of baseline boards to be allocated to a single subband, increasing the number of channels within the subband. To double the number of channels in a subband, simply double the number of baselineboards allocated to the subband. Thus each additional BlB for a subband adds another 64 channels in full and 128 channels in dual, and 256 channels in single polarization modes.
As an example, the full 2GHz bandwidth of the 8-bit samplers can be covered by 16 128MHz standard narrow subbands, each with 128 channels in dual polarization, as shown in the table above. The 16 subbands, however, only require 16 BlBs and another 48 are available for baselineboard stacking. One can thus use 4 BlBs for each of the subbands, quadrupling the number of channels from 128 to 512, which reduces the channel widths from 1MHz to 0.25 MHz over the full 2 GHz frequency range. This method works for any subband bandwidth.
Baselineboard stacking can be very useful for spectral line work, as it allows for wider bandwidths for each subband while maintaining frequency resolution. With baselineboard stacking, you can use fewer subbands to cover a set frequency range, thereby minimizing the number of filter edges and resulting sensitivity dropoff. Baselineboard stacking is offered for the August 2012 deadline. For shared risk observations, however, we recommend that observers do not use all 64 baselineboards to allow for observing in the event that one or two baselineboards are not working on any given day.
Recirculation
"Recirculation" is a second method for obtaining more spectral channels in a given subband. Recirculation uses the fact that the correlator has more computing capability when the data is averaged in time. The standard correlator dump time is 1s. If this is doubled to 2s, WIDAR can produce twice as many channels as listed in the tables above. 4s would allow 4 times the number of channels. Recirculation is only available for shared risk observations for the August 2012 proposal deadline.
Narrow Subbands with the 3-bit sampler
As the 3-bit samplers are still under commissioning, the August 2012 proposal deadline offers only a single observing setup with 3-bit sampling. This setup includes full coverage over all four baseband pairs (using 64 128MHz subband) 2MHz resolution for full polarization, 1MHz dual, and 0.5MHz for single polarization.
Data Rate Limits
Baselineboard stacking, recirculation, and time resolution can add up to an extremely high data rate in the correlator. The VLA currently supports data rates of up to 20MB/s for regular and more for shared risk observing, see the Observational Status Summary for details. The OPT instrument configuration calculates data rates based on the spectral line setup and the data rate maxima should not be exceeded for any observational setup.
Tips for Planning, Setup, and Processing of VLA Spectral Line Observations
Reminder: The following capabilities are offered for regular observing for the August 1 2012 proposal deadline. Consult the VLA Observational Status Summary for additional options available through shared risk observing:
- Maximum data rates of 20MB/s
- Doppler setting
- 8-bit samplers providing
- two 1GHz basebands
- up to 16 independently tunable subbands per baseband
- independent number of polarization products in each subband
- independent subband bandwidths ranging from 31.25kHz to 128MHz
- independent number of channels in each subband; maximum number of channels distributed across all subbands and polarization products cannot exceed 16384 channels
- 3-bit samplers providing
- four 2GHz basebands with a total of 64 128MHz subbands. 2MHz resolution full polarization, 1MHz dual and 0.5MHz single polarization
Considerations for Planning Subband Bandwidths and Resolution
Bandwidths required for UV continuum subtraction
When determining the bandwidths needed in your subbands, it is important to observe enough line-free channels on each side of the spectral line to allow for good continuum subtraction. It is possible to interpolate the continuum levels from one subband to another, but it is usually a better solution to derive the continuum level in each subband separately. The number of line free channels ideally equals or exceeds the number of channels that cover the line. When the line free channels are distributed equally on both sides of the spectral line, a low order polynomial (polynomials of order 1 appear to be good models for most cases) usually provides a good fit. Whenever higher order polynomials are needed, e.g. for a continuum source with a significant spectral curvature over the subband(s), the number of line-free channels should be increased.
Channel Widths for High Dynamic Range Imaging: Dealing with the Gibbs Phenomenon
For very sharp spectral or lag features, the spectrum can prominently display a ringing effect known as the Gibbs phenomenon, a sinc function that zig-zags on alternating channels. If this is apparent in the data, smoothing adjacent channels will reduce or even eliminate the effect. Hanning smoothing is the most effective method, which uses a triangular smoothing kernel with the central channel weighed by 0.5 and the two adjacent channels by 0.25. After Hanning smoothing, however, the channels are not independent anymore and one can eliminate every other channel without losing signal to noise.
In the pre-upgrade VLA days, the correlator design had a realtively short, truncated lag spectrum, which could result in prominent Gibbs ringing. To avoid this effect, Hanning smoothing was frequently applied online during the observations. With the new WIDAR capabilities of the upgraded VLA, however, ringing is very rare and only observed for extremely strong maser or RFI sources. Consequently, the VLA does not support online Hanning smoothing anymore; if required, Hanning smoothing can be applied during post-processing (e.g. with the CASA task hanningsmooth.). The Gibbs effect can also be reduced by using higher spectral resolution that covers the spectral feature with several channels. In that case, the ringing effects from the individual channels beat against each other, effectively reducing the zig-zag pattern that appears on alternating, neighboring channels when the peak is within a single spectral channel.
Sensitivity/Exposure Time Calculation
After planning your general setup and sensitivity needs, the required on-source observing time is best calculated with the VLA Exposure Calculator. This JAVA tool (see screenshot) allows one to input the required rms noise and bandwidth limits and outputs the required time on source given a frequency, weather, weighting scheme, and number of polarization products. The input Bandwidth should correspond to the frequency resolution that is required to perform the science. This may or may not be the width of individual spectral channels. Overheads need to be added according to our VLA frequently asked questions webpage. We refer to the low frequency guide and high frequency guide for further advice on how to set up the observations, depending on the receiver band to be used.
The Proposal Submission Tool (PST)
The Proposal Submission Tool (PST, accessible at my.nrao.edu ) is used to submit proposals, including the scientific justification, abstract, and authors, as well as planned target sources, observing session lengths, and correlator setups. In order to ensure that planned correlator setups comply with the capabilities offered for the August 2012 deadline, the Proposal Submission Tool (PST) includes a spectral setup tool.
In the example to the right, 9 subbands were chosen in Ka band with 8-bit sampling. Four of the subbands are in the first and five in the second baseband. The setup features different subband bandwidths, polarization products and uses baselineboard stacking (up to 16 baseline board pairs per subband pair are used for a couple of subbands). A total of 49 baseline boards are used for this configuration.
Wide-band mode (3-bit sampler, up to 8GHz bandwidth) can be used for spectral line observing as well. The channel width is fixed to a resolution of 2MHz for full, 1MHz for dual and 0.5MHz for single polarization products. No narrow subbands can be chosen.
Setting up a Spectral Observation using the Observation Preparation Tool (OPT)
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 program used for a single observing run. This consists of at least a few startup scans, a pointing reference, a bandpass calibration, a flux calibration, gain calibration and target observations. In the OPT, you specify your 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 QuickStart Guide, and a comprehensive user's manual and up to date information on the OPT are available at OPT webpage. As such, this guide provides only brief notes on the bandpass and gain calibrators and then focuses on the task of setting up correlator resources.
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. This implies that, for a bandpass calibrator with flux density Scal observed for a time tcal and a science target with flux density Sobj observed for a time tobj, 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 chose 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, Q), 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 that narrow one. This may be good to a level of a few per cent, 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. 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.42GHz, the error is in the per cent range. A guide for CASA is described on this CASAguides wiki page.
Phase/Complex Gain Calibration
The complex gain (phase/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 gain calibrator and the science target. For weak calibrators, however, it is possible to use wider bandwidths for the phase calibrator and then transfer the phases to the source. However, there will be a phase offset between them. The phase offset between the narrow and wide subbands can be determined by observing a strong source (e.g. the bandpass calibrator) and applied in post-processing from the complex gain calibrator to the target sources. A similar method can be used if the complex gain calibrator is observed at a slightly different frequency, e.g. to avoid a contaminating line feature such as Galactic HI.
Correlator Resources Setup
For the data taken early 2013 (August 2012 deadline), we will provide a specific new OPT Instrument Configuration layout for the regular and shared risk observing modes. The description below is for the current OSRO and RSRO modes.
Correctly specifying the WIDAR setup is essential for spectral line observations. In the OPT, click on the Instrument Configuration tab. The most advanced setting is currently the RSRO setting (File -> Create New -> RSRO Configuration). This opens a page for the frequency setup as shown in the figures. Note that you may only have access to the OSRO configuration utility, depending on your history of VLA observations. The OSRO setup is a more restricted version of the RSRO setup.
- Enter a name and select the receiver in the top panel. This will adjust the available frequency range described below the drop down menu. The 1dB and 3dB ranges describe the roll-off behavior of the receiver sensitivity at the receiver band edges. If the frequency to be observed is close to the edge frequency of a receiver, one may check if the next higher or lower frequency receiver is more suitable.
- Baseband Tuning: Select the position of the basebands. For the 8bit samplers, the central frequencies for 2 basebands are to be provided, each with a width of 1GHz. The center frequencies will go into the A0C0 box for frequency 1 and into the B0D0 box for frequency 2. For 3bit samplers, 4 basebands are available, each 2 GHz wide. Here, the center frequencies need to placed into the A1C1, A2C2, B1D1, and B2D2 boxes. A1C1 and A2C2 cannot be more than 4GHz apart, and the same restrictions apply to B1D1 and B2D2. Note that additional frequency restrictions may apply and the OPT/ICT will issue a clear warning or error message for those cases. The graphical panel above the input boxes shows the position of the two or four basebands. They are displayed as pairs to accommodate the R and L polarization inputs that may later be converted into single, dual, or full polarization products.
- Integration Time: this defines how data is dumped from the correlator backend into data files. A larger integration time will reduce the data volume. In addition, larger values can be chosen to take advantage of recirculation (only shared risk). On the other hand, time smearing effects, RFI excision, or time resolution may demand smaller integration times. It is important though, to not exceed the maximum data rate of 60MB/s (15MB/s for regular observing) and the integration time parameter is a good way to stay below this threshold for observations that demand large number of spectral channels.
- The total data rates are displayed in the Configuration Summary. The same panel also shows the number of baseline boards that are used in the setup. Remember that a maximum of 64 baseline boards are available and make sure that the data rate limits are not exceeded.
- Subband Setup: Depending on the baseband setup, the Subband Configuration panel sports tabs for each baseband. Under each tab one can now select the individual subbands. Up to 64 subbands are available (16 for regular observing): click Add subband to create a subband setting and select the frequency range from the "Sky Range" drop-down menu. The Offset Freq from Center shows the placement of the subband with respect to the baseband center. For small bandwidths, the drop-down menu is not available as there are too many choices and the placement needs to be entered by hand in the Offset Freq from Center box. In the current OSRO/RSRO interface, the subbands are not independently tunable yet (but this feature will be available for the August 2012 deadline) and the subbands will snap on a frequency grid defined by the subband bandwidth. Now select the number of polarization products and the number of channels will be displayed in the Spectral Points box. The comments box can be used to describe the setup, e.g. by entering the transitions that should fall in that subband. Those entries are currently not used anywhere outside OPT. The delete button removes the subband if is no longer required, and Bulk Edit is used for bulk editing of many subbands (see the OPT guide on this feature). Note: if you chose subbands with different bandwidths during OSRO/RSRO, contact NRAO staff as these scripts currently need manual editing after OPT submission.
- If not all subbands are used, one can use the remaining baseline boards to obtain a higher spectral resolution for those in the Subband Configuration panel. Select a higher number in the BL.BPS drop-down panel for baselineboard stacking. During commissioning, we recommend to use 2,4,8, etc. BlBs here but in principle any of the options in the drop down menu should work.
- Recirculation: only shared risk
Using Doppler Setting
Doppler setting will calculate the sky frequency of your observation based on the time of the observation, the source velocity, position and line rest frequency. In contrast to Doppler tracking, Doppler setting calculates this once for each baseband at the start of the observation (execution time of the SB) and the sky frequency will stay fixed for the entire run of the SB. Every subsequent run of the SB will perform a recalculation of the sky frequency. Doppler setting is currently only supported in OSRO mode (and will be available for the August 2012 deadline), RSRO observers need to calculate their own sky frequency (which is usually not too difficult given that the movement of the earth shifts the line by 30 km/s over a year, 0.5 km/s over a day - a velocity range that can under almost any circumstances be accommodated for by the wide bandwidths of WIDAR).
To use Doppler Setting, first select Rest in the baseband frequency setup section of the OPT/Instrument Configuration Tool. All velocities will then be calculated against the center baseband frequency which may or may not be the rest frequency of your spectral line. Supply the reference position (a source from a catalog can be chosen, typically this will be your target source) and the velocity with their frames in the Doppler Setting section in the OPT/ICT. Doppler Setting can only be applied for each baseband and all subbands will shift by the same frequency amount, offset by the the subband tunings.
Post-Processing Guidelines
please see our extensive VLA turoials on the CASAguides wiki for examples of how to process VLA spectra line data.