Version 10.2

Version 10.2 was released near July 11, 2012. It mainly provides support for the new wide C band receiver and switch control systems on the VLBA, improved support for the new wide bandwidth backends and recorders, and initial support for VLBI at the VLA/WIDAR.

• Add support for R1002 digital back-end used at KVAZAR stations (Svetloe, Badary, Zelenchuk) July 11, 2012. DMS

• Update source catalogs to RFC2012b and GSFC2011b. RCW July 4, 2012.

• Make a beta version June 25, 1012 RCW.

• Remove PTLINK parameter and example. Jun 19, 2012. RCW

• Remove the EVLA parameter. The EVLA is now being handled more like a normal station. Jun 19, 2012. RCW.

• When EXIT requested, shut down normally rather than aborting for no scans given. Jun 16, 2012 RCW.

• Add all the C band options for the new receiver to freq.dat so that we don't have to use freq_RDBE.dat when scheduling with the old system. $SCHED/RELATED_CODE/MAKEFREQ/makefq_c.f can make the list. The choice of new or old systems is hardcoded, but easy to change in this program that will likely only get used once. May 6, 2012 RCW.

• Add CORDFMT to request Mark4 output files from the correlator. The default is to request FITS output. June 4, 2012, RCW.

• Change the .v2d file to the .tv2d file. These files are not the final one used for correlation and we had too many cases where a rerun of SCHED would clobber the hand modified version. So now, the file should be renamed before hand editing. May 31, 2012. RCW.

• Add a warning if the LO for one channel is going to be in the IF for another. The scheme used does not recognize possible odd cases if we ever get receivers with multiple first LOs in the receivers, but will work for the main current case of the wide C band receivers or for the wide RCP option at X band. May 22, 2012 RCW.

• Make it possible to schedule the VLA for VLBI. Much old VLA code was removed or bypassed. It is now expected that the VLA will be scheduled by way of the VEX file. May 16, 2012. RCW

• Add INTENTs to sched input and to VEX output. SCHED treats these as character strings and does not attempt to parse them, at least not yet. They can be used to tell observing, correlation, and post processing systems of the intended use of the scans. May 07, 2012. RCW

• Fix Vex Freq naming convention to allow for 3 digit bandwidth for the RDBE/DDC 128 MHz option. May 7, 2012.

• Make a beta release May 4, 2012 RCW.

• Change maximum DDC bandwidth to 128 MHz. Before May 3, 2012. RCW.

• Make lists of stations in the Vex file work when there are large numbers of stations. The MODE lines will just get long, which is ok because each station is a parsable token. The comment lines with various other definitions are a single such token and are limited to 128 characters, so they overflow into multiple lines if needed. Apr 27, 2012.

• Fix bug when warning about two pointing centers using the same list of phase centers. A line break in a write to a character string caused overwrite of the next string. April 27, 2012.

• Add elevation of skipped scan when scheduling one station at a time. Meant for pointing observations when there is a question about why too many scans are being skipped. April 23, 2012 RCW.

• Improve the checks on bandwidths and frequency settings for the DDC personality. April 19, 2012. RCW

• When the IF sideband is lower, set the synthesizer frequency in the crd file to negative. This is the ruse we are using to convey the IF sideband information to the VME on-line system at the VLBA sites. Previously, it could always be figured out from the band name and synthesizer setting. But the new 6cm (4-8 GHz) receivers have made it possible for the sideband to be ambiguous. April 16, 2012 RCW.

• When making a RDBE schedule, the pulse cal tone detection for the artificial channels created for the VLBA old backend was being set up for the wrong frequencies in some cases (lower sideband IF). Fixed. March 11, 2012. RCW.

• There were some issues with the wrap calculation when different antennas were scheduled separately. Fixed, I hope. April 5, 2012.

• The DDC will use frequencies that require more digits than the usual 10kHz steps. In the output files, make the number of digits sensitive to the number required. March 2012 RCW

• Fixed a rarely encountered bug when making optimized schedules when they stopped on the first scan of a particular planet or satellite. Found in a pointing run. March 2012 RCW