-
Notifications
You must be signed in to change notification settings - Fork 13
Issue 112 #113
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?
Issue 112 #113
Conversation
Potentially here we should link to the different capabilities of the hardware depending what software it is used with. |
These are the differences I think are true off the dome:
@bparks13 can you help fill out this table or correct anything I might've gotten wrong here? |
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 made a separate PR (#117) to merge into this branch. Please take a look and incorporate my edits as you wish. Then I will approve review.
@cjsha There are a couple other things to mention, but you've highlighted most of the differences. The only other things I can see when glancing through the Onix1 library is:
|
Do the devices on the headstages have the same data streams and sample rates?
|
I think they're the same, maybe with the exception that the bno055 calibration data might be parsed differently by the GUI and by the Onix1 Bonsai package. I don't think we have to explain that here though |
The I agree with Cris that the mention of how the calibration data is parsed isn't worth mentioning. |
Even if not for this doc page, it would be good to have this information available outside the source code. It's not apparent to those of us that don't know the code what the differences in implementation are. Perhaps this belongs in a more of a spec sheet of the system capabilities per software. What would be the maximum sample rate of the Bno055 and PolledBno055 in Bonsai then? |
In the bonsai package, calibration data is sent as one byte. Each sensor calibration status (the magnetometer accelerometer and gyroscope) and the system calibration status occupies two bits in this byte (look at https://open-ephys.github.io/bonsai-onix1-docs/api/OpenEphys.Onix1.Bno055DataFrame.html for reference). In the GUI, I believe each sensor and the system calibration status get their own byte. Is this right @bparks13? As far as the sample rates, I don't know those details myself. |
Regarding the varying BNO055 sample rate in Bonsai, we can link to the article that spawns from this issue: |
sounds like there are no differences between the acq board and onix in the GUI and onix in Bonsai, in terms of datastreams available to the user and data processing. My worry was there was a difference here as there is between the implementation of the miniscope in the miniscope library vs the onix library. it doesn't seem to be. and we can spare them furtehr details, as y'all suggested. |
in my meeting with chuckles, we discussed maintaining a chart or list like the one from this comment on the onix-source plugin page instead of in the onix-docs. this is probably a more appropriate repo, and the page that's being edited in the PR can just link out to that plugin page where that info is. |
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 take what ideas you want from PR #117 and feel free to merge. Also feel free to re-request me if you want me to do another review
we should tack #121 to this PR |
Fixes #112