Add an operations guide for customizing the PlanktoScope OS software#534
Merged
ethanjli merged 2 commits intodocumentation/betafrom Feb 21, 2025
Merged
Add an operations guide for customizing the PlanktoScope OS software#534ethanjli merged 2 commits intodocumentation/betafrom
ethanjli merged 2 commits intodocumentation/betafrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds an operations documentation guide for customizing the PlanktoScope OS's software. This includes instructions for re-enabling consecutive mask subtraction, as temporary workaround (at least until a GUI configuration is added) for undoing the changes made by PlanktoScope/device-backend#32 ; those instructions were requested by @fabienlombard in the 2025-02-06 software meeting.
This PR also adds a guide with screenshots in the "troubleshooting" section for downloading the Python hardware controller logs, to assist with troubleshooting (so that I can give users a link to a guide to follow in the docs site, instead of generating a new variation of the instructions each time I respond to a request for help on Slack).