Add page that describes hardware configuration & data acquisition #186
Conversation
This file contains 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
- To avoid rate-limiting, update to v2 in actions and set max-retries | max-concurrency | cache in both the local installation and the Action. Tested with version 0.18.0 locally, which removed the rate-limiting 429 response from learn.microsoft.com
Merged
cjsha
changed the title
Other edits to onix-bonsai.md: - Change uid/title to reflect content better - Fix header hierarchy and their capitalization - Minor syntactical improvements Other edits to other files: - Add workflows where necessary - Fix ref in template after changing uid - Change some headings from progressive to imperative tense in visualize page
ChucklesOnGitHub
approved these changes
Jan 20, 2025
|
|
||
| The DeviceName property of the AnalogInput operator is set to "BreakoutBoard/AnalogIO". This links | ||
| the operator to the AnalogIO device on the Breakout Board meaning that the AnalogInput operator will | ||
| streams data from that device. |
There was a problem hiding this comment.
typo: streams -> stream
| > - Each hardware guide has a Python script to load and view data. You can use this is to load and | ||
| > view data from the example workflow or as a starting point for loading data from your own workflow. | ||
|
|
||
| <!-- For high data rates, use <xref:Bonsai.Dsp.MatrixWriter>. For lower data rates or files that store |
There was a problem hiding this comment.
I think the comment about when to use each data writer is helpful, even if reductive. In fact, it could warrant a separate section on Writing Data, same as you did for Visualize Data. This could also include how to know what type of data a node produces (by either checking the reference or by using the text visualizer or whatever the actual method is).
There was a problem hiding this comment.
I agree, we should have a section like "visualize data" for "write data". that would be a good spot to plug a solution for issue #165
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Resolve #93
Resolve #56