You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
417 automatically pull bindings from bindings folder (#419)
* Remove old new scale, add const for bindings
* Add platform info
* Move Pinpoint ID to server
* Migrated bindings
* Generate GUI dynamically
* Dynamic binding instancing
* Updated binding documentation
Copy file name to clipboardExpand all lines: docs/development/adding_a_manipulator.md
+20-10Lines changed: 20 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ read [how the system works first](../home/how_it_works.md) before proceeding.
13
13
## Create a Manipulator Binding
14
14
15
15
Manipulators are added to Ephys Link through bindings. A binding is a Python class that extends the abstract base class
16
-
[`BaseBinding`][ephys_link.utils.base_binding] and defines the functions Ephys Link expects from a platform.
16
+
[`BaseBinding`][ephys_link.utils.base_binding] and defines the methods Ephys Link expects from a platform.
17
17
18
18
Create a new Python module in `src/ephys_link/bindings` for your manipulator. Make a class that extends
19
19
[`BaseBinding`][ephys_link.utils.base_binding]. Most IDEs will automatically import the necessary classes and tell you
@@ -23,7 +23,7 @@ descriptions of the expected behavior.
23
23
As described in the [system overview](../home/how_it_works.md), Ephys Link converts all manipulator movement into a
24
24
common "unified space" which is
25
25
the [left-hand cartesian coordinate system](https://www.scratchapixel.com/lessons/mathematics-physics-for-computer-graphics/geometry/coordinate-systems.html).
0 commit comments