allow UnitWaveformsWidget to use probeinterface plot_probe #3819
Conversation
This file contains hidden or 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
Member
|
We demand there's a probe attached already in so we can safely assume there's a probe around 👍 |
alejoe91
approved these changes
May 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Allows the UnitWaveformsWidget to use probeinterface
plot_probefor channel locations, and implements axes_equal arg which was not previously implemented. This would depend on ProbeInterface PR 334 to allow the plot_probe function not to plot directly to an set of axes.Would this be safe enough (do we expect the sorting_analyzer_or_templates object to always have a probe attached, or should I include a fallback to the original implementation too?