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

Making tracking a multi-threaded process #9

Open
michael5486 opened this issue Mar 3, 2017 · 8 comments
Open

Making tracking a multi-threaded process #9

michael5486 opened this issue Mar 3, 2017 · 8 comments
Assignees

Comments

@michael5486
Copy link
Contributor

Now when a new user enters the FOV, the program gives them one frame for classification. If it can't get a torso or shoulder measurement, than the comparison doesn't work. I need to create a thread for each person to let the program gather info about a new person and still keep the main loop going

@michael5486
Copy link
Contributor Author

I may create a global vector to store info on users tracked that all threads can access. I will have to do some memory management to ensure it doesn't get too large but that can be addressed later

@michael5486
Copy link
Contributor Author

Integrated threading and made threads to format program into a prettier output for the demo. Working on using threading to temporarily monitor users when the target user can't be located

@michael5486
Copy link
Contributor Author

Up next: Need to make threads register when target user leaves FOV

@michael5486
Copy link
Contributor Author

knows when user leaves FOV, was trying to set pointer to NULL but it was never happening. Was getting trapped in an if statement that never occurred. Works better, but now it thinks the user leaves FOV too much

@michael5486
Copy link
Contributor Author

threading works better, focusing on initialization rather than threading for now

@michael5486
Copy link
Contributor Author

May not need to use threading, focusing on a method that doesn't require all user's past locations, just compares their current locations to the target user's location buffer

@michael5486
Copy link
Contributor Author

Threading will need to be used to send commands to the motors. Not using it for display purposes anymore, but the threading experience and code will be repurposed.

@michael5486
Copy link
Contributor Author

May not need threading, but I will keep this open until I am sure I won't need it

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

No branches or pull requests

1 participant