Draft notebook for spatial day 1 #883
Open
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.
Towards #882
This PR contains a draft notebook for day 1 of the spatial workshop we are developing. As noted in #882, depending on discussion this PR may or may not end up being merged, but we'll at a minimum use the PR for communicating feedback and discussion.
This notebook goes through processing for a Visium dataset, using a sample from SCPCP000006, with sections as follows. My goal was to get enough drafted material here to inspire discussion, with some potentially for both paring down and expanding in various areas.
Rendered draft: 01-processing_visium.nb.html
To run the code
renvenvironment (uses bioc3.22)data/(it's ok if the summary report and metadata json are also present, e.g. if you download from the portal as I did) as:data └── SCPCS000190 └── SCPCL000429_spatial ├── filtered_feature_bc_matrix ├── raw_feature_bc_matrix └── spatialGoals for reviewing
Based on review, we can determine whether to proceed with this draft version, or whether a bigger pivot is needed. In the event of proceeding, I'd anticipate a several more stacked PRs to flesh out each section. But, I think it will make more sense to outline an accompanying exercise and/or different day's notebook before taking the effort to formalize a draft.
*Miscellaneous note for future us: these Visium plots are big. We need to make sure to use custom
fig.widthsettings to ensure the rendered HTML doesn't get too big (some plots are currently squished, but this is a draft!).