Outline cell type annotations results section #60
Conversation
This file contains 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
|
Click the link below to download the manuscript build as a ZIP file. |
…l-type-outline Reorganize outline for cell type results section
|
Click the link below to download the manuscript build as a ZIP file. |
|
@jaclyn-taroni just noting that this still needs an approval whenever you get a chance. The draft is stacked on this branch. |
jaclyn-taroni
approved these changes
Mar 4, 2024
|
Click the link below to download the manuscript build as a ZIP file. |
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.
Closes #7
I went to write the results section for cell type annotation and realized that I hadn't actually outlined it yet. I think I was putting this one off because I think this is the most confusing section to write. I was torn on exactly how to organize it and what order to mention things in. Ultimately, I chose first to introduce the workflow and give a brief overview, then talk about the implementation of SingleR and CellAssign, then talk about the report, and finally, submitter cell types.
Where I was mostly torn was where the information on diagnostic plots goes. We could talk about all SingleR specific things together and all CellAssign specific things together, rather than have a separate section on the report. But I think I like discussing things in the report (diagnostic plots) separately from building references and implementation.