NRAO Home  >  Green Bank  |  Wiki Topic:    GB > Data > SoftwareReportCentral_ReleaseNotes > ReleaseNotes_5_3 > AstronomersIntegratedDesktopReleaseNotes5_3

Changes | Index | Contents | Search | Statistics | Jump to Topic

Release Notes for Astrid Version 5.3 - Released on Wednesday, May 25, 2005

Modification: The default beam name is now "1", instead of "C" for all Scan types in the Observing API (i.e. Slew, Track, etc.)

In the past for single feed receivers, users had to use "C" (a virtual beam) when using the Observing API Scan types when what was really desired was physical beam (e.g. "1"). Because the Antenna Manager now treats beams "C" and "1" equivalently, the Observing API now uniformly uses physical beams within Scan types. Those Scheduling Blocks that already use the default will be unaffected. Those users who specify "C" in any of their Scheduling Blocks are encouraged to change them to "1", although "C" will continue to work.

New Feature: Addition of Online/Online Monitor Only/Offline modes

There are now three "real time" modes associated with Astrid:
• offline
  • In this mode, the user does not connect to the telescope, only to the observing database which stores Scheduling Blocks. Users may (a) import and validate their observing scripts and save them to the database as Scheduling Blocks for later retrieval, (b) open existing Scheduling Blocks and edit the observing scripts, and (c) open existing Scheduling Blocks and export the observing scripts to a file. In this mode, the text in Astrid title bar will read Astrid (OFFLINE).
• online (monitor only)
  • In this mode, the user connects to the telescope and to the observing database, but cannot control the telescope. However, the user may submit Scheduling Blocks to the Job queue (note that this is the list on the left side of the Run tab); this is to support multiuser observing collaboration. In this mode, the text in Astrid title bar will read Astrid (ONLINE MONITOR ONLY).
• online
  • In this mode, the user controls the telescope. Only one user may be online at a time. In this mode, the text in Astrid title bar will read Astrid (ONLINE).

When Astrid is started, the following dialog appears:



Users may select their online mode via this mechanism at startup. Also, users may change their online mode at any time by clicking on the File drop-down menu (located at the top left of Astrid) and selecting Real time mode....

The GBT Operator's account, gbtops, has overriding control of the telescope. That is, if an observer already has online real time mode privileges in his/her Astrid session, the operator may take those away by choosing online as the real time mode in the operator's Astrid session. The previously online observer will then be bumped to online monitor only and notified. In order for the observer to regain control, the operator must change to online monitor only and the observer must reselect online in his/her Astrid session.

New Feature: The Observing API now uses the local dev_health.conf file, if present, during configuration.

When doing a Configure in a Scheduling Block, the user's local dev_health.conf file is now used (if present). Please note that this dev_health.conf file must be located in the same directory from which Astrid was launched and this file overrides the system dev_health.conf file. This behavior is now identical to the behavior of the config_tool when used stand-alone.

New Feature: The Observing API now recognizes when a configuration fails.

When doing a Configure in a Scheduling Block, the Observing API now reports back via the Monitor tab when a configuration has failed.

New Feature: Validator enhanced to detect illegal configurations.

The user will now be notified via a dialog if any Configure statement contains an illegal configuration. Please note that the Validator will not catch configurations which are legal, but are not routable due to the current state of the system (e.g. bad modules).

New Feature: New scan type AutoPeakFocus.

AutoPeakFocus combines AutoPeak and AutoFocus, respectively, into one convenient Scan. See documentation.

Modification: Balancing during Auto Scan types (i.e. AutoPeak, AutoFocus, AutoPeakFocus) is optional.

Normally, the Auto procedures (AutoPeak, AutoFocus, and AutoPeakFocus) balance the IF power levels as one of their functions. They now provide an optional argument balance which allows the user to skip the balance step of the scan. See documentation.

Attachment:	Action:	Size:	Date:	Who:	Comment:
realtimemode.jpg	action	13460	20 May 2005 - 15:32	AmyShelton	Real Time Mode Dialog