 News |
FAQ
|
| Search
|
Home
|
| Getting Started | Documentation | Glish | Learn More | Programming | Contact Us |
|
| Version 1.9 Build 1367 |
|
The Project area of the analysis deals with capabilities the system should provide in the area of work organization for the user. A Project is any user-defined self-contained work unit.
A user defines and accesses his/her various Projects through the user interface. Depending upon implementation, the user interface may serve many astronomers, each with a defined list of Projects. The astronomer must be able to create new Projects, list existing Projects and select a Project to be worked upon. The astronomer should also be able to save a Project and all its associated data on a permanent storage medium, and to restore it later.
A Project should consist of a list of all data sets associated with the Project and should define any special environment (e.g., Single Dish) within which the astronomer operates. The Project provides methods for associating new data sets, removing (and optionally deleting) data sets, and listing names of the various data sets in use. In this context, data sets can include observational data, derived images, catalogues, etc. A Project should also keep track of other types of associated data such as a log of all operations on the data sets, collections of useful scripts, text documents such as draft manuscripts, etc. The astronomer may also wish to include observing schedules with the Project. It should also keep track of data sets that have been stored to permanent media through an archive log.