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

Question on Deal with matched detections in main.py? #13

Open
tringn opened this issue Jan 18, 2019 · 1 comment
Open

Question on Deal with matched detections in main.py? #13

tringn opened this issue Jan 18, 2019 · 1 comment

Comments

@tringn
Copy link

tringn commented Jan 18, 2019

Hi @kcg2015,
Thanks for your great work.
I have a question on function Deal with matched detections in main.py.
Assume in the 1st frame, there is no matched detections, then we will jump to if len(unmatched_dets) > 0:. It does the tmp_trk.predict_only() by using current detection (x = np.array([[z[0], 0, z[1], 0, z[2], 0, z[3], 0]]).T; tmp_trk.x_state = x).
In the 2nd frame, I assume that all objects in 1st frame are matched to detections in 2nd frame, then we jump to if matched.size > 0, and do predict. However, in tmp_trk.kalman_filter(z), I saw that the code does predict then update with current detection info. I am confused because we already did predict when processing detection in the 1st frame?
Can you clarify my confusion?
I suppose that we should do update and then predict.
Thank you so much.

@mzhian
Copy link

mzhian commented Apr 6, 2019

Hi @tringn,
I agree with what you supposed. In the matched detection and tracker, I also think it should be update first followed by predict.
Hi @kcg2015,
Thanks for sharing you work and could you please clarify this if we are wrong?

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