Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is the reason for calculating covariance with mean[3] = height in Kalman filter? #289

Closed
YoungjaeDev opened this issue Nov 2, 2022 · 3 comments

Comments

@YoungjaeDev
Copy link

std_pos = [
self._std_weight_position * mean[3],
self._std_weight_position * mean[3],
1e-2,
self._std_weight_position * mean[3]]
std_vel = [
self._std_weight_velocity * mean[3],
self._std_weight_velocity * mean[3],
1e-5,
self._std_weight_velocity * mean[3]]

Why is there a special reason why I took it as a height when modeling?

@ydm365
Copy link

ydm365 commented Nov 4, 2022

As indicated by authors' comment, the position array is coded by order x, y, a, h. The forth number(mean[3]) is scale of the bounding box, and I think they assume larger object makes greater movement, and greater dilation or contraction. Actually the other three numbers is independent with scale of objects.

@YoungjaeDev
Copy link
Author

@ydm365
In other words, a cov is given to pos that changes in real time in proportion to the object size

@ydm365
Copy link

ydm365 commented Nov 11, 2022

@ydm365 In other words, a cov is given to pos that changes in real time in proportion to the object size

As far as I can tell, this is exactly what the authors are assuming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants