-
Notifications
You must be signed in to change notification settings - Fork 3
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 TS4231 data source that automatically calculates 3D positions #166
Conversation
- Qualify all TS4231* nodes with V1 because they data handle is produced by V1 basesations. - We have V2 basestation variants of the FPGA core, but these classes will not work with that data.
- Addresses #152 - Addresses feedback in #154 - Testedl - Provides two possitvle data sources for TS4231 lighthouse sensor arrays. - TS4231V1Data provides low-level sensor index, pulse type, and pulse widths in microseconds that can be potentially combined with IMU data in a predictive filter to improve 3D tracking - TS4231GeometricPositionData provides naive geometric calculation of 3D positions.
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.
Looks good, just a few typos. No need to address the other comments now.
OpenEphys.Onix/OpenEphys.Onix/TS4231V1GeometricPositionConverter.cs
Outdated
Show resolved
Hide resolved
OpenEphys.Onix/OpenEphys.Onix/TS4231V1GeometricPositionConverter.cs
Outdated
Show resolved
Hide resolved
|
||
var t11 = time[2] + width[2] / 2 - time[0]; | ||
var t21 = time[5] + width[5] / 2 - time[3]; | ||
var theta0 = 2 * Math.PI * SweepFrequencyHz * t11 - Math.PI / 2; |
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 a thought here: It could be useful to output these angles in the data frame, as they could be potentially used in other tracking algorithms for fusion and would spare the complication of calculating them.
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 there is a lot of low level access one would potentially want and this is just one of those items.
I like the solution now because the other data class provides as low level as you would ever want and this one provides the opposite. I dont think we should mix the two personally.
- Fix typos - Add infinity check following matrix inversion
Addresses #152