Diagnostic Instrumentation

Table of Contents | Internal operation: Motion data transfer | Internal operation: Code structure

Internal operation and motion data transfer

Internal motion data frame buffer

The motion data file is written in the encoded frame order. The diagnostic program therefore requires an input buffer to avoid lengthy parsing of the file or searching for frames in display order. The buffer is made up of a fixed-size one-dimensional array, the size of which can be set by command-line option and defaults to 50 frames. The motion file is read once only in the forward direction and frame data is written to the buffer at the position [frame_number % array_size]

It is therefore required that the buffer is large enough in order for frame data not to be overwritten before it is used. Such overwriting results in the program exiting.

The frame buffer may be reduced in size to minimise the program memory footprint. Another method of achieving this and to avoid buffer failure on sequences which require a very large buffer size, a sub-section of the sequence may be viewed in isolation using the -start and -stop command-line parameters.

SourceForge.net Logo