-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Hyphenate URLs & update the "install bonsai" page for Onix1 (#13)
Hyphenate URLs & Update installation steps Onix1 - Underscores in file names replaced with hyphens - Update screenshots and rewrite some steps for installing Bonsai & OpenEphys.Onix1 package - New directory for putting editable screenshots to improve ease of maintaining edited screenshots used for docs - Rename workflows to avoid broken references
- Loading branch information
Showing
39 changed files
with
190 additions
and
134 deletions.
There are no files selected for viewing
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
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
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
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
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
File renamed without changes.
4 changes: 2 additions & 2 deletions
4
articles/devices/bno055_neuropixelsv1e.md → articles/devices/bno055-neuropixelsv1e.md
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,12 @@ | ||
--- | ||
uid: device-bno055_neuropixelsv1e | ||
uid: device-bno055-neuropixelsv1e | ||
title: NeuropixelsV1eBno055 | ||
isGuide: true | ||
isDevice: true | ||
device: BNO055 | ||
headstage: NeuropixelsV1e | ||
workflow: true | ||
workflow_file: ~/workflows/devices/Bno055_NeuropixelsV1e.bonsai | ||
workflow_file: ~/workflows/devices/Bno055-Neuropixelsv1e.bonsai | ||
visualize: true | ||
visualize_timeseries: true | ||
--- |
4 changes: 2 additions & 2 deletions
4
articles/devices/bno055_neuropixelsv2e.md → articles/devices/bno055-neuropixelsv2e.md
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,12 @@ | ||
--- | ||
uid: device-bno055_neuropixelsv2e | ||
uid: device-bno055-neuropixelsv2e | ||
title: NeuropixelsV2eBno055 | ||
isGuide: true | ||
isDevice: true | ||
device: BNO055 | ||
headstage: NeuropixelsV2e | ||
workflow: true | ||
workflow_file: ~/workflows/devices/Bno055_NeuropixelsV2e.bonsai | ||
workflow_file: ~/workflows/devices/Bno055-Neuropixelsv2e.bonsai | ||
visualize: true | ||
visualize_timeseries: true | ||
--- |
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,84 @@ | ||
--- | ||
uid: BonsaiInstallationAndConfiguration | ||
title: Bonsai Installation and Configuration | ||
--- | ||
|
||
## Install Bonsai | ||
|
||
To download Bonsai, select between the portable download and the installer download [here](https://bonsai-rx.org/docs/articles/installation.html). | ||
|
||
* The **Portable** download installs a sandboxed version of Bonsai. Portable environments enable users to switch between different environments to prevent package conflicts or confusion between similar packages. | ||
|
||
* To install from the **Portable** download, extract the downloaded file. You can start the portable Bonsai by running the `Bonsai.exe` that is inside the extracted folder. | ||
|
||
* The **Installer** download installs Bonsai and all its dependencies globally. | ||
|
||
* To install from the **Installer** download, run the downloaded `Bonsai-X.X.X.exe` file and agree to the involved licenses. You can start the globally installed Bonsai by launching it from the `Bonsai Setup` window after installing or searching for it in your OS's search function, for example. You can create a shortcut such that the portable Bonsai environment is easy and name it such that it is easy to differentiate between different environments. | ||
|
||
To use Bonsai for interfacing with Open Ephys hardware in a meaningful way, additional packages are required. | ||
|
||
## Open Bonsai Package Manager | ||
|
||
The Bonsai package manager can be accessed from Bonsai's landing window or its workflow editor: | ||
|
||
![Package manager from splash page](../../images/bonsai-splash-page-package-manager-highlight.png){width=350px} or ![Package manager from editor](../../images/bonsai-editor-package-manager-highlight.png){width=425px} | ||
|
||
## Install Packages in Bonsai | ||
|
||
The two required packages to run the workflows in this documentation are: | ||
|
||
* `Bonsai.StarterPack` | ||
|
||
* `OpenEphys.Onix1` | ||
|
||
Additional packages may be required if you wish to use Bonsai in ways that extend beyond the scope of this documentation. | ||
|
||
### Bonsai.StarterPack | ||
|
||
Install the `Bonsai.StarterPack` package. [Open the package manager](#open-bonsai-package-manager) and: | ||
|
||
1. Click the `Browse` tab. | ||
|
||
1. Set `Package source` to `Bonsai Packages`. | ||
|
||
1. Search for `Bonsai.StarterPack`. | ||
|
||
1. Click `Install`. | ||
|
||
![Bonsai Bonsai.StarterPack Install Screenshot](../../images/bonsai-install-Bonsai.StarterPack.webp){width=650px} | ||
|
||
### OpenEphys.Onix1 | ||
|
||
Install the `OpenEphys.Onix1` package. [Open the package manager](#open-bonsai-package-manager) and: | ||
|
||
1. Click the `Browse` tab. | ||
|
||
1. Set `Package source` to `All` or `NuGet`. | ||
|
||
1. Search `OpenEphys.Onix1`. | ||
|
||
1. Click `Install`. | ||
|
||
1. Click `I Accept` when the license agreement window appears. | ||
|
||
![Bonsai OpenEphys.Onix1 Install Screenshot](../../images/bonsai-install-OpenEphys.Onix1.webp){width=650px} | ||
|
||
## Update Packages in Bonsai | ||
|
||
It is good practice to periodically check for package updates. [Open the package manager](#open-bonsai-package-manager) and: | ||
|
||
1. Click the `Update` tab. | ||
|
||
1. Set `Package source` to `All`. | ||
|
||
1. Leave the search bar blank if you want to check for updates for all packages.\ | ||
Alternatively, if you want to check for an update for a particular package, you may type that package's name in the search bar to expedite the update retrieval process. | ||
|
||
1. Click `Update All` if you want to perform all available updates.\ | ||
Alternatively, click on a package and click `Update` if you want to perform a subset of the available updates. | ||
|
||
![Bonsai Update All or Just One Screenshot](../../images/bonsai-update.webp){width=650px} | ||
|
||
## Next Steps | ||
|
||
Now that Bonsai has been installed and configured, it is time to start placing operators and configuring those. If you are new to Bonsai, the following sections give a high-level understanding of how Bonsai is organized, and some of the ONIX-specific concepts that will be useful for learning how to work with the operators. |
This file was deleted.
Oops, something went wrong.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
--- | ||
uid: NextSteps | ||
title: Next Steps | ||
--- | ||
|
||
Continue browsing <xref:GettingStarted> and check out specific operators on the left to see how to configure each operator, as well as some ways to visualize data. Each page will have a fully functional workflow that can be copied into Bonsai to provide an easy starting point for generating data. | ||
|
||
For more technical information on each operator, head to the <xref:OpenEphys.Onix1> to see a more developer-focused view of each operator. | ||
|
||
More complex and in-depth tutorials for placing multiple operators and moving towards generating data in an experimental setting can be found in the <xref:TutorialsLandingPage>. |
This file was deleted.
Oops, something went wrong.
10 changes: 5 additions & 5 deletions
10
articles/getting-started/node_types.md → articles/getting-started/node-types.md
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,14 +1,14 @@ | ||
--- | ||
uid: NodeTypes | ||
title: Node Types | ||
uid: OperatorTypes | ||
title: Operator Types | ||
--- | ||
|
||
In Bonsai, all objects are called "nodes", and have a specific function associated with them depending on what they do; this can be `Source`, `Sink`, `Combinator`, `Transform`, or `Condition`. For ONIX nodes, they are all classified as either `Source`, `Sink`, or `Combinator`. | ||
In Bonsai, all objects are called "operators", and have a specific function associated with them depending on what they do; this can be `Source`, `Sink`, `Combinator`, `Transform`, or `Condition`. For ONIX operators, they are all classified as either `Source`, `Sink`, or `Combinator`. | ||
|
||
| Node Type | Description | Example ONIX nodes | | ||
| Operator Type | Description | Example ONIX operators | | ||
| --------- | ----------- | ------------------ | | ||
| Source | Generate event streams from devices or files | [`CreateContext`](xref:OpenEphys.Onix1.CreateContext), [`Bno055Data`](xref:OpenEphys.Onix1.Bno055Data), [`NeuropixelsV1eData`](xref:OpenEphys.Onix1.NeuropixelsV1eData) | | ||
| Sink | Save data or trigger external outputs | [`ConfigureHeadstage64`](xref:OpenEphys.Onix1.ConfigureHeadstage64), [`ConfigureNeuropixelsV1eHeadstage`](xref:OpenEphys.Onix1.ConfigureNeuropixelsV1eHeadstage) | | ||
| Combinator | Manage control flow or synchronize parallel inputs | [`StartAcquisition`](xref:OpenEphys.Onix1.StartAcquisition) | | ||
|
||
Nodes are placed in the Bonsai editor and can be saved into a "workflow", which is a grouping of nodes and saved settings. This workflow can then be run to perform some task, depending on what nodes are placed. | ||
Operators are placed in the Bonsai editor and can be saved into a "workflow", which is a grouping of operators and saved settings. This workflow can then be run to perform some task, depending on what operators are placed. |
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
This file was deleted.
Oops, something went wrong.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
--- | ||
uid: StartAWorkflow | ||
title: Start a Workflow | ||
--- | ||
|
||
Once all operators have been placed and linked correctly, and all **Configuration** properties have been set, it is now possible to run a workflow. Note that some aspects of Bonsai are only available in specific contexts; for instance, the GUIs mentioned above can only be opened when a workflow is not running. Once a workflow is running, these GUIs are not accessible, but visualizers for certain operators can be opened to view the streaming data. | ||
|
||
Running a workflow can be done in one of two ways: (1) Press the **Start** button at the top of the Bonsai editor, and (2) Press F5. Upon starting a workflow, a context will be created, and all devices will be configured based on the **Configuration** properties. Any `*Data` operators will then begin streaming data, and can be visualized. | ||
|
||
![Start button in Bonsai editor](../../images/bonsai-editor-start-button.png){width=700px} |
Oops, something went wrong.