-
Notifications
You must be signed in to change notification settings - Fork 4
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
[FEATURE] Documentation for Build #22
Comments
Yes, the ordering is correct. The instructions for running the calibration and capture are in the README: Lines 64 to 69 in 2f8ce03
@loolirer can give you more details if something remains unclear. |
@nikunjsanghai is your issue solved? |
@debOliveira thank you for the support. Both @nikunjsanghai and I are attempting to recreate the results in your conference paper and so far things are going smoothly. We are waiting for our IR LED lights to arrive this week, and we will let you know if any issues arise. If you are curious, we are putting together the following experimental rig to evaluate a SLAM algorithm I have developed. |
Hey @adthoms, That is excellent work! Please keep me posted when the paper comes out; we may apply it. Contact us if issues arise or if you want to brainstorm some ideas. @loolirer developed a digital twin for our arena to facilitate prototyping. Maybe it is useful for some of your visualizations. |
Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
From the existing documentation, it is not entirely clear how to operationalize the entire motion capture system. From our understanding, there is central script
mocaprasp.py
, and from here would call the following functions in order:Is this ordering correct?
Describe alternatives you've considered
NA
Additional context
NA
The text was updated successfully, but these errors were encountered: