RUR: execute one Read-Up-the-Ramp cycle

This page is part of the ING document INS-DAS-24: client-server interface for control of cameras

Purpose: perform a read up the ramp observation sequence and store the resulting pixels.

Actors: udas_run client; udas_camera server; camera.

Outline: the client invokes the RUR action. The server orders the camera to read out at intervals determined by the integration time string. As the pixels arrive from the camera, the server captures and stores them, demultiplexing the pixel-stream during the readouts to save processing time.

Normal course of events:

Client invokes the RUR action on the server with these arguments:

Argument1 is the number of readouts to do between each integration, set to 1.
Argument2 is the integration time string, containg a list of increasing integration times in seconds, separated by spaces.
Argument3 is the preflash time, inseconds, set to 0.0.
Argument4 is the type of integration, set to "expose".

Server returns good status to client.

Variations:

Client varies the integration time string. Any time greater or equal to zero is acceptable; negative times are rejected. The integration times must be in order of increasing times.
Client varies the number of readouts. Negative or zero counts are rejected. Counts greater than 2 + UDAS_MAX_RUN_ROS/2 (where UDAS_MAX_RUN_ROS is a compile-time constant set in udas_limits.h) are rejected.
Client puts "dark" instead of "expose" for Argument4. Server uses this value when emulating the INTEGRATE action.

Notes:

As will be obvious from the text above, this action does nothing that cannot be done by a sequence of other actions. The composite RUR action is provided to speed up the events, to increase the timing accuracy of the integrations, and to reduce communications delays.