Changes

Jump to: navigation, search
Real-timeness, frame dropping, and latency
==Real-timeness, frame dropping, and latency==
One of the major concerns that were faced during the conception of the PoC was related to its real-timeness. In principle, regarding the acquisition of the frames from the image sensor, such a PoC should be based on a real-time system because it should guarantee that all of them frames are captured (no frame loss), no matter what processing is performed simultaneously (encoding the live stream, serving a web page, etc.). This is true However, this requirement holds when the system is waiting for an alarm to happen. Once an alarm buffer is filled, a fame loss can be tolerated instead. Once When an alarm is detected, say A1, the system, in fact, ignores new possible alarms until the buffer associated with A1 is stored on the SSD.
A new frame is sent by the image sensor to the processing platform every 3ms approximately. Taking into account that the sensor has no buffering capabilities, this implies that if the processing platform takes longer has to complete the acquisition of a frame in less than 3ms to get although the arrival of a new frame a frame Of course, arrival times are is an asynchronous with respcet to the Frames event.
In order Despite these considerations, a system not specifically designed with real-time capabilities was used to limit the implementation effort and the costs. Rather, we choseit was used a platform providing enough headroom in terms of processing power. Nevertheless, the application software implements a mechanism to detect frame loss allowing to verify if the system is operating properly.
==Future work==
4,650
edits

Navigation menu