updating to the new Optitrack SDK #6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
trivial
added trajectory number notice per magnitude
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We bought a new set of Optitrack cameras that are only supported by newer version of SDK. The new SDK has several interface details that are different from the old one. The majority of the changes are regarded to that. Also, the new cameras have higher resolution so we can on longer afford to rasterize every frame otherwise we have data transfer issue. I changed the code so that we rely entirely on the object information from the cameras and only pull full frame when calibrating cameras. Finally, added the function to do 3-way matching.