Undefined tracking states

[jkaniuka]

Hi,

I was playing back rosbag with body tracking data recorded using ROS 2 wrapper. I've spotted that sometimes tracking_state equals 3 - this value is not mentioned in message definition file (see below).

# Tracking state
# 0 -> OFF (object not valid)
# 1 -> OK
# 2 -> SEARCHING (occlusion occurred, trajectory is estimated)
int8 tracking_state

I found this thread on Stereolabs Community - What does POSITIONAL_TRACKING_STATE = 5 indicate?. In API docs there are 6 values within POSITIONAL_TRACKING_STATE enum and only 3 of them were described in Object.msg file. Could you please clarify this? I think that adding constants in Object.msg is worth considering (see example below).

# Constants
int8 TRACKING_STATE_OFF = 0
int8 TRACKING_STATE_OK = 1
int8 TRACKING_STATE_SEARCHING = 2

# Tracking state
int8 tracking_state

Thanks in advance,
Jan 😎

[Myzhar]

It matches the TERMINATE status of the ZED SDK:
https://www.stereolabs.com/docs/api/group__Object__group.html#ga43eecfa6fb832a9e5d86bb5e5007b2fa

The package will be updated to support it

[jkaniuka]

Thanks @Myzhar.

Fixed in 1a89992.
Closing.

[jkaniuka]

@Myzhar, actually I think it should be also backported to humble and jazzy branches.

[Myzhar]

Yes, when we will update them to be used with apt

[Myzhar]

Yes, when we will update them to be used with apt