Software Continuing Maintenance & Enhancement (CM&E)
• This Priority 3 Project encompasses:
– Operational support activities that must be scheduled into a development cycle
– Dedicated efforts to systemically understand & resolve issues that will improve
reliability and performance of software systems
– Improvements that will reduce the amount of telescope time needed to test software
• Current Activities and Work Packages:
– Linux Migration (charter complete; work started C9 2003)
– DCR Improvements (charter complete; work waiting to begin)
– Project Office Request List (all work treated as background tasks, completed as time
permits when other commitments are met)
• Intended Work Packages:
– Simulators (targeted for Q2 or Q3 2004; required before high frequency observing
season begins)
– IF Manager Improvements
– Spectral Processor Improvements
• Out of Scope:
– Active Surface Improvements & Antenna Improvements being managed as part of
PTCS project
Software Continuing Maintenance & Enhancement (CM&E)
• Cycle 9 2003/Cycle 1 2004 Accomplishments:
– Reduced dependencies of M&C on aips++ (11/03)
– Significant work to adapt software to RedHat 9 operating system (11-12/03)
– Provided software support for bringing up new gbtaio3 single board (12/03)
– All (non-3rd party) M&C build warnings eliminated (12/03)
– Fixed bug where incorrect scan numbers written to GO FITS file (1/04)
– Started work on Linux Migration work package to provide a long-term fix for the
systems overload issue in C9; porting SIB, MCS, GPIB, Converter Rack &
Analog Filter Rack in C1 (all software on gbteio1 and gbteio2)
• Cycle 2 2004 Requests include 2 FTEs for full cycle:
– [10 FTE-wk] Linux Migration: Port Receivers to Linux
– [1 FTE-wk] Spectrometer core dump issue (came up again on 1/19)
– [1 FTE-wk] Spectral Processor not responding to aborts
• Plans for Cycle 2 2004:
– During C1 2004, gbteio1 and gbteio2 were ported to Linux. C2 work will port
the software on gbtaio1 and gbtaio3.
• Risks:
– Completing the Linux Migration work package in the 2004 calendar year
requires that dedicated effort be put on this task during all cycles.
Ease of Use Initiative
• This Priority 1 Project encompasses:
– API Development. API’s are developed programming packages intended to
provide a means for experts to interact with the system. The typical beginning
or novice observer will not use them. (API’s are not to be confused with
hardware-software interfaces, which may just be defined on paper.)
– All software systems that a visiting observer interacts with to prepare for and execute an
observation, including:
• Configuration & Setup (new Configuration API)
• Observing (GO is replaced by new Observing API),
• Status information (new development)
• Automated balancing (new development, part of Observing API)
• Improved Security Mechanism for telescope control system
– One of the key goals is to get the GBT operable according to Scheduling Blocks (SB’s)
which can be dynamically scheduled
– This requires the release of all new APIs by the end of Q1
• Current Activities & Work Packages:
– Configuration API (beta release 11/18/03)
– Observing API (beta release 2/16/04)
– Security (design due 2/16/04; implementation 3/31/04)
– Addition of balancing to Observing API (production release 5/14/04)
• Out of Scope:
– Remote Observing (will be covered in “Ease of Use 2” project)
– Data Display (managed as part of Data Handling project)
Ease of Use Initiative
• Cycle 9 2003/Cycle 1 2004 Accomplishments:
– Configure: Configuration beta product developed in Python, 42/42 test cases
passed, released for community evaluation & testing on November 18
– Observe/Status: Design for the Observing API completed in C9 2003, and proof-of-
concept tests conducted on December 18 with antenna simulator and live telescope –
Observing API building blocks successfully moved the telescope! Work is being
completed in C1 to release an observing API which handles all observing procedures
that are not dependent upon precision time calculations.
• Q1-Q2 2004 Plans:
• Beta Release of Observing API – February 16
• Execute first Scheduling Block – February 27
• Production Release of Configuration API, Observing API, User Preferences and
Online Filler – March 31
• [Deprecate IARDS – March 31]
• Automate Balancing – May 15 (this will complete EU project)
• Deprecate GO – June 30 (timeframe is longer because we want to have a
“fallback” observing capability in case we run into problems with the APIs during
April, May and June)
• Risks:
– Pressure from visiting observers may encourage us to divert resources to the Data
Handling project. Any diversion of resources at this point, however, will delay our ability
to complete the project in its entirety by May 15.
Data Handling Improvements Project
• This Priority 1 Project encompasses:
– All software systems that a visiting observer interacts with once data has been taken,
including:
• Data Display (IARDS to be replaced by RTD)
• Data Export to IDL and CLASS
• Unified User Preferences & Online Filler
• Reengineering of DISH SD data reduction environment
• Analysis & Development in preparation for support of ALMA tests in Jan 05
(combined GBT/interferometric data) and Jan 06 (full SD data reduction)
– Key goals are to shorten the learning curve for reducing GBT data, deliver calibrated
data products to users, separate the development of non-astronomy software (e.g.
plotters) from the implementation of scientific algorithms, and make it easier for
astronomers to experiment with their own algorithms
• Current Work Packages:
– Data Display (beta release 12/18/03, production release planned 3/31/04)
– Data Export (beta release of SDFITS 11/24/03, production release 3/31/04, export to
CLASS 3/31/04)
– DISH Reengineering (analysis in progress C1 2004)
• Out of Scope:
– Archiving Project (Carl Bignell, Project Scientist)
– Proposal Submission Tool
Data Handling Improvements Project
• Cycle 9 2003/Cycle 1 2004 Accomplishments:
– Data Export: SDFITS beta released on November 24
– Data Display:
• Beta release of real-time display, supporting new dynamic pointing and focus
corrections from PTCS project, on December 18
• Integration of new real-time display with DEAP, an internally developed
environment for Data Extraction & Analysis – February 16 (completion of this
step will segment all code related to the display itself from astronomical
algorithms)
– DISH Reengineering:
• Design in progress; analysis due 2/20/04
– Calibration
• Scientific staff discussions taking place; specs due 2/20/04
• Q1-Q2 2004 Plans:
• Gap analysis for data display to handle spectroscopy – February 16
• Augment new data display to handle all procedures – March 31
• Speed up SDFITS for production release, segment Data Preprocessing API
and integrate with user preferences and the online filler concept – March 31
• Risks:
• Strong, proactive scientific leadership is required to deliver this project’s
interim deliverables! Cannot miss analysis deliverables or entire 2004
schedule is in jeopardy.
2004 Data Handling Goals: 2004 Ease of Use Goals:
• Complete architecture for reengineering DISH (Q1) • Complete new Data Display (end of Q1)
• Resolve calibration issues (Q1) • Deprecate IARDS (end of Q1)
• Complete specification of Analysis Procedures and share with • Release production versions of Configuration & Observing
ALMA team for iteration (Q2) APIs and ability to observe using Scheduling Blocks (end of Q1)
• Beta Release of reengineered single-dish analysis package to • Support automated balancing (Q2)
replace DISH; must support GBT capabilities at release time (Q4) • Deprecate GO (Q2)
• Complete all work to successfully support ALMA tests in Jan 05 • Formally end Ease of Use project (5/14/04)
Scientific Staff Tasks Software Development Tasks
C1 Calibration Dish Reengineering Architecture
Specs due 2/27/04 Specs due 2/27/04
C2 Balancing (for EU Project) Calibration
Specs due 3/26/04 Development due 3/31/04
C3 Analysis Procedures Balancing (for EU Project)
Specs due 5/14/04 Development due 5/14/04
C4 Remote Observing (for EU2) Analysis Procedures
C5 Remote Observing (for EU2) Analysis Procedures
Analysis due 8/16/04
C6 Flagging & Editing Analysis Procedures
Gap Analysis due 9/30/04 Beta Release of SD Analysis Package 9/30/04
C7 Publishable Plots Flagging & Editing
Gap Analysis due 11/19/04 Gap Analysis due 9/30/04
C8 Iterate on Documentation Iterate on Documentation
Production Release of SD Analysis Package Dec 04-Jan 05