Add visualization documentation section#186
Merged
mat10d merged 8 commits intocheeseman-lab:mainfrom Feb 10, 2026
Merged
Conversation
- Add new 4.visualization.md with overview, getting started, env vars, application sections, and tips - Renumber development docs from 4 to 5 - Update index.md to include visualization in toctree
Collaborator
|
Sounds good, I can add to this soon! |
Contributor
Author
|
@mat10d Great context and guidance. Thank you! |
Collaborator
|
Yes, the updated numbering is correct--my bad, didn't realize that led to a conflict! |
Collaborator
|
Would you like me to rebase or do you want to give it another look? |
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.
Description
Not sure how deep to go on the actual content of the QC/Cluster data. Perhaps some further detail from a biologist's perspective would be helpful there. I think I've captured the general overview, and technical details related to running it. Perhaps in too much detail in one place (We could probably drop the static assets env var documentation, we unless you expect others to want to make permanent public deployments, and if you expect that I could write a whole section on how we did that).
What is the nature of your change?
Checklist
Please ensure that all boxes are checked before indicating that a pull request is ready for review.
pyproject.tomlto reflect the change as designated by semantic versioning.ruff checkandruff format.