The SSS Observation Preparation Tool (OPT) is a browser based application that allows users to prepare observations for scheduling. The highest level model object with which the OPT works is the project. Each project is for one telescope, such as the EVLA or GBT. The project may be split into one or more programs, where each program typically represents a different configuration of an array of antennas. Within a program the observer crafts one or more scheduling blocks. Finally, for each scheduling block the observer sets up one or more scans and/or loops of scans. When configuring a scan, the observer may select from catalogs of sources and catalogs of resources. Though it might not be obvious to the observer, these catalogs will be furnished by the Source Catalog Tool and the Resource Catalog Tool, respectively.
The manual is not yet available.
A test version of the SSS Observation Preparation Tool may be found at http://webtest.aoc.nrao.edu/opt/. You are invited to play with the tool by creating and configuring new projects. Understand, though, that during this phase in our development, your projects may be removed at any point and without prior notice.
Since version 0.6 we have used JIRA to create release notes each time we update the application.
You will notice that the application has surprisingly few classes. This is because it relies heavily on the richness of the classes in the building block packages to do much of the needed work. The application programmers' interface for all OPT classes may be seen by going to the API overview.
The source code for this application is held in a subversion repository (user name and password required). The files used for providing help messages to users is held in a separate subversion repository.
The SSS Observation Preparation Tool is dependent on the all the SSS Building Block Software, but not on any other SSS Application, even though it appears as if both the SCT and RCT are a part of it. It is also dependent on some third party software. The full set of dependencies may be found in the pom.xml file that we use in our Maven 2 build process. Various versions of these may be found in the OPT Repository.