NRAO Home  >  Green Bank  |  Wiki Topic:    GB > Software > SoftwareReportCentral_ReleaseNotes > ObservingAPIReleaseNotes_6_1

Changes | Index | Contents | Search | Statistics | Go

Release Notes for Observing API (turtle) Version 6.1 - Released on Wednesday, February 15, 2006

• New Features
  • Scan Types Update: Auto*, Peak, Focus
  • Missing or Late Pointing/Focus Corrections Generate Dialog
  • Imported Scheduling Blocks Retain Their Names

New Features

Scan Types Update: Auto*, Peak, Focus

The following scan types have been modified in order to standardize their behavior and to incorporate new features: AutoFocus, AutoPeak, AutoPeakFocus, Focus, Peak. A full description of the syntax and behaviors of these scan types can be found at ScanTypes.

• AutoFocus/AutoPeak/AutoPeakFocus Syntax:
  • AutoFocus(source, location, frequency, flux, radius, balance, configure, beamName)
  • AutoPeak(source, location, frequency, flux, radius, balance, configure, beamName)
  • AutoPeakFocus(source, location, frequency, flux, radius, balance, configure, beamName)
• Peak Syntax:
  • Peak(location, hOffset, vOffset, scanDuration, beamName)
• Focus Syntax:
  • Focus(location, start, offset, scanDuration, beamName)
  • *IMPORTANT!* - Because of the addition of the location argument calls to Focus will not be backwards compatible. Therefore, you will have to update all of your scheduling blocks that use Focus! Also Focus no longer requires a preceding call to Slew. An example of the new syntax and its differences from the old syntax is shown below:

Slewing to mySource using beam 1 beginning at -100mm and moving 200 mm over a 120 second duration.

Before:

Slew("mySource")
Focus(-100, 200, 120.0, "1")

After:

Focus("mySource", -100, 200, 120.0, "1")

Missing or Late Pointing/Focus Corrections Generate Dialog

The user is informed when Observation Management is experiencing a delay in receiving updated pointing/focus corrections from GFM by a dialog which provides the option to continue to wait for the standard timeout of 45 seconds.

Imported Scheduling Blocks Retain Their Names

When importing a scheduling block, its existing name is used as a default when saving to the database. This name is only a default and can be overridden if desired.