RUN:
start a new observation
This page is part of the ING document
INS-DAS-24:
client-server interface for control of cameras
Purpose: set up the context in which a new observation can take
place.
Actors: udas_run client; udas_camera server.
Outline: the client invokes the RUN action. The server creates
internal storage for this new observation and relables the storage for
other observations that it has in memory. Some older observations
are deleted from memory.
Normal course of events:
-
Client invokes the RUN action on server with no arguments.
-
Server creates internal storage for the context of this new run; it assign
a run-number to the run. The new run is identified as having "rank 0".
-
Server increases the ranks of all runs still stored in its memory by one.
-
Server checks the older runs. If the highest-ranked context is no in use
by any function, the run at that rank is deleted from the server's memory.
This process is repeated until the server finds a run that is in use, or
until only runs at ranks 0 and 1 are left.
-
Server returns good status to client.
Variations:
-
Client invokes the RUN action on server with the following argument:
-
Argument 1 is the string 'scratch'
-
Server performs as normal, but does not assign a run number to the new
run, and does not increment the run number.
-
Client invokes the RUN action on server with the following argument:
-
Argument 1 is the string 'glance'
-
Server performs as normal, but does not assign a run number to the new
run, and does not increment the run number.