Actors: CCD specialist.
Outline: the specialist installs the profile and controller program for the camera, connects it to the DAS computer and turns it on. S/he orders the DAS to bring the camera on-line and tests it.
Related use cases:
Typical course of events:| User action | System response | ||
|---|---|---|---|
| 1. | Brings to the telescope the engineering profile for the camera and the object code for the detector controller(s), both of which were previously prepared away from the telescope. | ||
| 2. | Puts the profile into a configuration directory of the observing system. Puts the new object code into the observing system as a patch. | The observing system now knows how to run the camera. | |
| 3. | Runs use case change camera to use and test the installation. | As per subordinate use-case. | |
| 4. | Runs use case tune camera. | As per subordinate use-case | |
| 5. | Informs the telescope software-manager of the new detector and the patch. The software manager arranges to have the patch absorbed into the main system at the next system release. |
Steps 3 and 4 need not be done immediately after steps 1 & 2. However, it is important that the first use and test of the camera be overseen by a CCD specialist. If the profile is properly prepared, step 4 is not needed.