120 likes | 268 Views
JCMT OCS Workshop. Description of the TODD B.D.Kelly. Provide high-level, non time-critical control of a single observation Compatible with existing instruments (ADAM) Compatible with planned future instruments (DRAMA).
E N D
JCMT OCS Workshop Description of the TODD B.D.Kelly
Provide high-level, non time-critical control of a single observation Compatible with existing instruments (ADAM) Compatible with planned future instruments (DRAMA) Enable simplified programming of observing modes by the creation of recipes Provide feedback on the progress of the execution of a recipe Provide error reporting and handling Functionality
JCMT Software System investigator observer recipe designer RTS Observation preparation tool Observation scheduler Observation driver ORACDR Instr Astronomical databases Observation requests Observing recipes Tel
The Todd in Operation observe <odf name> RTS Todd dramaTodd ODF: name-value pairs Observing recipes ORACDR The “observe” command causes the odf to be read. This creates Todd variables with the given names and the given values. The value of “obsmode” is used as the name of the recipe file, which is then read. The recipe executes using the values of any relevant Todd variables. Instr Tel
External Todd Control Command process (queue) Communication is character strings through sockets Todd Command process (queue) The Todd receives each command and returns the status on completion Up to 5 commands can be handled by the Todd concurrently Unrecognised commands are handled as comments and echoed and written to the log file
Todd Example Telescope Observation Designer & Driver Recipe
Todd Components Command Has a command string. FoldBox Has a loop counter. CaseBox Has a selection variable.
Todd Command Completion The command-string associated with a Command can be of the form Dobeyw taskname actionname arguments Such a Command only completes when the final acknowledgement is received from the task, signifying the action has completed. Any informational or error messages returned by the task are displayed in a scrolling screen area, and recorded in the log-file.
Todd Error Handling If a DobeywCommand receives a bad status from a task in the action completion message, then the Command displays a dialogue box to the operator and waits until it is acknowledged. The choice controls what value is set into the Todd’s error variable. The DobeywCommand then completes, and its GUI component is coloured red to assist the operator in diagnosing problems. Subsequent stages in the recipe may be skipped, depending on the above choice of error level combined with the error levels set into the recipe components.
Todd Error Reporting Reports are made to three separate scrolling screens. One shows all the lines written to the logfile, one shows messages coming back from tasks, and the third shows only error conditions.
Todd Error Recipes The Todd error variable can be used as the selection variable on a CaseBox. Unfinished actions are terminated by using DRAMA KICK messages.
Todd Timeout Recipes The toddTimer task can be used to detect timeouts.