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

meaning of the State transition function #3

Open
wzhang1 opened this issue May 10, 2018 · 2 comments
Open

meaning of the State transition function #3

wzhang1 opened this issue May 10, 2018 · 2 comments

Comments

@wzhang1
Copy link

wzhang1 commented May 10, 2018

In line 339 of windows.py, what's the meaning of 0.5 for velocity? I change it to 0.0 and the result seems not changed?

@peter-moran
Copy link
Owner

peter-moran commented May 13, 2018

That is a bit of an under documented tweak I made.

self.kf.F is the Kalman update function. It describes what we think the next state (the horizontal position of the window) of the system will be based on the last state. In this particular configuration, it is saying:

  • The first line of the matrix is stating that I expect the next position to be at the previous position + previous velocity * time.

  • The second line is stating that I expect the velocity to be about half the previous state. This is essentially like friction and theoretically helps the tracker from overshooting.

@wzhang1
Copy link
Author

wzhang1 commented May 13, 2018

I agree with the explanation of the meaning for the second line, if you change it to 0.0, your model will be extremely simplified and I did not see the obvious different in the 3 udacity videos.(I tried ion other videos but hit the this line(TODO: Do something if not enough windows to fit. Most likely fall back on old measurements.)), so not sure if the velocity term have effects

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