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
Currently, lines in the multipatch log file give the name of the manipulator to which they belong, but there is no way to determine anything else about the manipulator, such as:
What is being manipulated (a headstage with pipette? a stim electrode?)
Orientation
Association with ephys data
It might be the case that some of this information should be logged elsewhere. It would be nice if we could at least graphically reconstruct the pipette orientations when reading the log file.
An easy fix for orientation might be to just include the complete transform for each pipette as part of its initial state. We could also have each pipette provide a describe method that could provide more custom information (like MIES channel associations).
The text was updated successfully, but these errors were encountered:
Currently, lines in the multipatch log file give the name of the manipulator to which they belong, but there is no way to determine anything else about the manipulator, such as:
It might be the case that some of this information should be logged elsewhere. It would be nice if we could at least graphically reconstruct the pipette orientations when reading the log file.
An easy fix for orientation might be to just include the complete transform for each pipette as part of its initial state. We could also have each pipette provide a
describe
method that could provide more custom information (like MIES channel associations).The text was updated successfully, but these errors were encountered: