-
Notifications
You must be signed in to change notification settings - Fork 6
3D tracking #331
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
base: main
Are you sure you want to change the base?
3D tracking #331
Conversation
Edwardius
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice work! Some things to add now that we're moving into actual integration onto the car:
- make this an rclcpp_component (so that we can doo intraprocess communication) and rclcpp_lifecycle node (so that we can manage startup in a deterministic way)
- launch tracking with perception_bringup pkg (this is a metapackage that is used to launch all other packages under perception, you can see how its ran if you look at the perception_bringup service in the docker-compose.yaml)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what are these for? can we ignore them if their autogenerated?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
those contain the changes I made to bytetrack to turn it from 2d into 3d. the patch is pretty big though so probably not the greatest solution
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
might be better to make our own fork of bytetrack, then clone the modified fork into the vendor package
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sure, that works, since its MIT you can freely like copy the code and make changes to it. feel free to add it in (and i guess remove the vendor pkg)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
forking its history into the monorepo can get messy though, so best to just cherry pick what you need and adding it here , ie. writing your own tracker with notes of bytetrack :P (you can even open source it as your own, just crediting the original authors)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isnt this an rclcpp component? if not, can you make it so? it would remove the main.cpp here. also, if you can help perception get started with implementing this is a lifecycle node, that would be cool. you should use the wato_lifecycle_manager under infrastructure/ (copy in inside perception dockerfile), and launch it all through perception_bringup pkg
| @@ -0,0 +1,45 @@ | |||
| # Multi-Object Tracking β Developer Guide | |||
|
|
|||
| ## Dependencies | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just say refer to package.xml
π Description
Tracker is 3d now, needed for tracking boxes in 3d space
πΉ (Optional) Video Demo of Changes
β Checklist
π Related Issues / PRs
Fixes #123
Depends on #456
π Notes for reviewers