error_list

Description of errors and warnings

This section lists some of the errors that the system reports to the user, as well as their descriptions and solutions.

No camera intrinsic are provided, or camera frame_id is not set.

Reason: The topic with camera parameters is not specified. Or, in this topic, the frame_id field is empty. Sometimes this message may appear due to the fact that the topic with parameters lags behind the main topic of the camera, for example, when playing a bag file.

Consequences: If this message appears multiple times, recognition will not be performed.

Solution: Single occurrences of this message can be ignored. In case of multiple, it is required to provide a topic with camera parameters.

Missed desired detection rate of __, actually loop takes __.

Reason: The period of work requested from the system cannot be reached.

Consequences: Messages with objects will be published less frequently than requested.

Solution:

1. Decrease the videoProcessUpdateRate parameter to extended_object_detection_node.
2. Reduce the number of objects for recognition.
3. Disable drawing of objects and publication of markers.

There are no attribute with name __! 

And

Can't find attribute __ in base needed for Logic__ attribute!

Reason: A simple object or other attribute cannot find an attribute with the specified name in the configuration file. In this case, either a typo in the name, or an attribute\object refers to a attribute that is ignored in this version (for example, DNN in OpenCV 3.2 or QR_Zbar without the corresponding library installed).

Consequences: This attribute will not be added to objects, which will change the expected recognition result.

__ Solution:__ Correct typos in the configuration file, remove unsupported attributes from the file.

Warning: some simple_objects in base have same ID.

Reason: Several simple objects have the same identifier.

Consequences: Objects with matching identifiers will not be detected after the first one.

Solution: Correct the matching identifiers in the configuration file.

Depth image is not provided for DepthAttribute!

Reason: An object with the Depth attribute is present in the database, but node was launched without subscribing to a depth camera.

Consequences: 3D localization will not be performed for an object with this feature.

Solution: Remove Depth tags from the configuration file if the work is done without a depth camera. Connect a depth camera if you plan to use it.