-
Notifications
You must be signed in to change notification settings - Fork 223
Fix typos and buggy code in modules docs #4105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks pretty good to me see like two comments.
Co-authored-by: Zach McKenzie <[email protected]>
Co-authored-by: Zach McKenzie <[email protected]>
doc/modules/curation.rst
Outdated
@@ -34,7 +34,7 @@ a subset of units from a spike sorting output and to perform some merges: | |||
remove_unit_ids = [1, 2] | |||
sorting_analyzer2 = sorting_analyzer.remove_units(remove_unit_ids=remove_unit_ids) | |||
|
|||
# merge some units | |||
# merge units 4 and 5, and units 7, 8 and 12 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we say merge units 4 and 5 and separately units 7, 8 and 12 to emphasize the concept of merge groups more or do you think adding in the numbers is enough?
doc/modules/motion_correction.rst
Outdated
) | ||
) | ||
|
||
Importantly, all the result and intermediate computations can returned to a motion object, for further loading, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Importantly, all the result and intermediate computations can returned to a motion object, for further loading, | |
Importantly, all the results and intermediate computations can returned to a motion object, for further loading, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few more typos found.
Genial. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I promise last typo I will find :)
Co-authored-by: Zach McKenzie <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good by me!
I went through all the modules docs, and tried to run all code in them (fun!!). This PR fixes anything obviously wrong that I found, mostly due to typos or deprecations that we never implemented in the docs. And fixed and text typos I found.
Aim was to fix code/typos and add some links, rather than dramatically improve/adjust docs.
When I felt the user might actually run the whole code-block, I added the necessary imports to make this smoother. Felt they weren't always needed.
Final PR from the Harvard docathon!!