Please provide the following info (check/uncheck the boxes after creating this topic):
DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.6 and DriveWorks 4.0
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
Target Operating System
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
SDK Manager Version
Host Machine Version
native Ubuntu 18.04
I’m looking for best practice advice. I’m concerned mainly with power consumption and effective processor utilization. I didn’t find details on this in the NvMedia documentation, the SIPL documentation, or sample source code.
I’m bringing camera data in from 11 cameras to a Drive AGX Xavier. This data is then published to an AI algorithm. I noticed in the documentation for NvMedia, the getImage function is a blocking function. I presume this means that the function does not return until a new frame has arrived since the last call. What is the best practice for pulling this data in without locking the processor from the interpretation of other sensor data?
Should each image sensor processing be launched on its own thread prior to a call to this function? What are other concerns to keep in mind?
Below is a snippet from the getImage function documentation:
Any help is appreciated