multiple sample version of Annotating cell clusters by integrating single-cell RNA-seq data
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 323
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
hey kaizhang:
great tools for single cell chromatin analysis. especially the ['fragment_paired'] is integrated into adata.obsm make quantification on consensus extremely fast.
I recently using snapatac2 to analysis my dataset. which consists of scATAC and scRNA both with multiple sample (not paired multiome).
following the tutorial I transfer label from scRNA annotation to scATAC
here is my question, in this tutorial,
scvi.model.SCVI.setup_anndata(data, batch_key="batch")
adata was setup with batch_key 'batch' which is used to distinguish scRNA data and gene activity generated by scATAC. and now given my data is all consist of multiple sample. is it necessary to add this sample-batch to batch_key of scvi.model.SCVI.setup_anndata.
or only batch to distinguish scRNA and scATAC is all I need despite multiple samples?
and as I can search, the parameter batch_key of scvi.model.SCVI.setup_anndata can only accept one obs.
so may be a new batch = sample batch + scRNA/scATAC batch is feasible?
like
| Sample | scRNA/scATAC | Batch |
|---|---|---|
| 1 | scRNA | 1-scRNA |
| 2 | scRNA | 2-scRNA |
| 3 | scRNA | 3-scRNA |
| 1 | scATAC | 1-scATAC |
| 2 | scATAC | 2-scATAC |
| 4 | scATAC | 4-scATAC |
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the annotation tutorial and the linked scvi.model.SCVI.setup_anndata documentation, focusing on how batch_key is described for multiple scRNA and scATAC samples. Clarify the supported configuration and update the tutorial or its notes so the expected batch fields and completion criteria are explicit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, documentation, machine-learning
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100