We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug The muon.atac.tl.count_fragments_features function uses the score in the fragment file to count fragments:
muon.atac.tl.count_fragments_features
muon/muon/_atac/tools.py
Line 860 in 31a45d7
This score also includes all duplicated read pairs: https://support.10xgenomics.com/single-cell-atac/software/pipelines/latest/output/fragments, but we only want to use the unique fragments for downstream analysis and not the duplicates.
Expected behaviour Only count the unique fragments by having: mx.data[i].append(int(1))
mx.data[i].append(int(1))
The text was updated successfully, but these errors were encountered:
a7320b7
Keep the legacy behavior in count_fragments_features
5f1d9cc
From v0.2, count fragments by default and not reads. See #110 for more details.
No branches or pull requests
Describe the bug
The
muon.atac.tl.count_fragments_features
function uses the score in the fragment file to count fragments:muon/muon/_atac/tools.py
Line 860 in 31a45d7
This score also includes all duplicated read pairs: https://support.10xgenomics.com/single-cell-atac/software/pipelines/latest/output/fragments, but we only want to use the unique fragments for downstream analysis and not the duplicates.
Expected behaviour
Only count the unique fragments by having:
mx.data[i].append(int(1))
The text was updated successfully, but these errors were encountered: