OBSDATA:
choose a data disc
This page is part of the ING document
INS-DAS-24:
client-server interface for control of cameras
Purpose: to select a disc on which to store raw observations.
Actors: udas_obsdata client; udas_camera server.
Outline: the client invokes the OBSDATA action, changing the
disc on which subsequent observations are saved.
Normal course of events:
-
Client invokes the OBSDATA action on the server with these arguments:
-
Argument1 is the name of the main data directory on the chosen disc.
-
Server validates the arguments: it checks that the directory exists; that
the directory is on one of the discs in the server's list of allowed discs;
that the disc is not full; that the directory is writable.
-
Server creates within the directory a sub-directory named for the date
of observation.
-
Server returns good status to client.
-
In all subsequent runs, server saves the observations in the sub-directory
it created at step 4.
Variations:
-
At step 1, no directory is named. Server selects the "best" (usually the
emptiest) disc from its list of allowed discs, and does steps 3+ for the
top directory on that disc.
-
At step 2, the nominated directory is unusable. Server skips steps 3+,
returns an error message to cleint, and returns status UDAS__BADOBSDATA to
client.
-
At step 1, no directory is named, and all the discs in the server's list
of allowed discs are full or unavailable. Server skips steps 3+, writes
an alarm message directly to the log, and returns status UDAS__OBSDISCSFULL
to client.