PROCESS: process
image data
This page is part of the ING document
INS-DAS-24:
client-server interface for control of cameras
Purpose: to prepare from the raw readouts of a run the image-data
required for display and archiving.
Actors: udas_run client; udas_camera server; image
display.
Outline: the client invokes the process action. The server combines
the raw data to get the data that must be saved in the eventual FITS file;
it stores these data and send a copy to the display.
Normal course of events:
-
Client is sequencing a run. It has already invoked as many readouts as
are required for this run and these are stored by server in the run context
of rank zero (q.v. the RUN action). The output-image display is turned
on (q.v. the DISPLAY action).
-
Client invokes the PROCESS action on server with these arguments:
-
Argument1 is rank of the run to be processed, set to zero.
-
Server takes the readouts of the run and combines them to make a set of
output images. The details of the processing are chosen according to server's
configuration and are not set by client.
-
Server returns good status to client.
-
Server sends the output images to the display.
Variations:
-
Client is sequencing a series of runs. It already has the next run in progress,
so the run needing processign is at rank 1, not rank 0. Client sets argument1
to 1 instead of 0 in step2; other steps proceed normally.
-
Client asks to process a run at some other rank where server has no run
to work on. Server stops at step 2, sends an error message to client and
returns to client the status UDAS__NOSUCHRUN.
-
Display of output images is turned off (q.v. the DISPLAY action). Server
skips step 5.