-
Notifications
You must be signed in to change notification settings - Fork 65
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
Add positioning doc #511
Add positioning doc #511
Conversation
fixes #231 |
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.
I think this is good. What's missing (perhaps another PR from me?):
- We should add a launch argument for tracking/positioning. Only if motion_capture is selected, we should run the motion_capture node
- The "motion_capture" key in crazyflies.yaml needs to be replaced to be "motion_capture_rigid_body_tracking" (and accordingly in the launch file), and the documentation regarding this expanded (custom tracking vs. mocap vendor software tracking)
I have just added the launch file mocap argument since I've been hit by this problem many times myself :), however perhaps you can add the motion_capture_rigid_body_tracking as you know the most. Let me know if you agree with my launch file addition and I'll merge |
Looking great - thanks:-) |
Here is some explanation about mocap and other positioning systems. I've placed it in the usage.rst file for now
It is not as extensive as the crazyswarm1 doc: https://crazyswarm.readthedocs.io/en/latest/configuration.html but I think that the motion capture package also provides quite doc and explanation about it as well. Same goes with the positioning for onboard positioning (like the loco deck, flow deck etc) which can be referred to the bitcraze website.