Questions about SQANTI3 vs. SQANTI-single-cell default parameters (min_cov and ratio_TSS) for single-cell long-read data #608
Replies: 1 comment
-
|
Hi @lihua061777-ops , thank you for your question. The important thing to understand is that these are not parameters that change how SQANTI3 performs its structural classification. min_cov and ratio_TSS are columns that SQANTI3 populates in the classification file using short-read data, when you provide the relevant input (--coverage for junction support, --SR_bam or --short_reads for TSS coverage). You can then use those columns as criteria in a filter JSON as you were commenting if you wish, but that is a decision given to the filter module for post-QC filtering. In SQANTI-single-cell, these parameters are not yet implemented as filtering decisions, as the filter module is still under development. However, they are implemented as CLI options to give to the QC module as a way to establish a threshold for short-read QC validation. SQANTI-single-cell creates a cell-level classification file called the cell summary, containing values for different metrics for each cell barcode. Typically these metrics are normalized, showing them as the proportion of reads/transcripts in the cell barcode that satisfy a given requirement (e.g. being a FSM, having a length above 2000bp, etc.). These two metrics follow the same logic: we needed to establish a threshold so that the feature could represent something like "proportion of reads/transcripts in the cell whose junctions are validated by orthogonal short reads" and "proportion of reads/transcripts in the cell whose TSS is validated by orthogonal short reads." The specific reasons for those default thresholds:
I'm curious about how were you planning to tackle the filtering of your isoforms using short-read data at single-cell level. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am using SQANTI3 to process long-read single‑cell RNA‑seq data and have noticed default parameter differences between SQANTI3 and SQANTI‑single‑cell. I’d appreciate your clarification.
--min_cov: In SQANTI3, the default is 3; in SQANTI‑single‑cell, it’s 1. Is this change intended to accommodate the sparser nature of single‑cell data? For my single‑cell dataset, can I simply set min_cov=1 in a custom JSON filter when using SQANTI3?
--ratio_TSS: In SQANTI‑single‑cell, there is a --ratio_TSS parameter with a default value of 2.0. Is this 2.0 threshold also applicable as a reference when running the standard SQANTI3 pipeline on single‑cell data? If so, should I enforce it by adding a rule for the ratio_TSS column in a filtering JSON file?
Beta Was this translation helpful? Give feedback.
All reactions