Skip to content
New issue

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

Read to Isoforms Mapping #10

Open
shizhuom opened this issue Oct 21, 2024 · 1 comment
Open

Read to Isoforms Mapping #10

shizhuom opened this issue Oct 21, 2024 · 1 comment

Comments

@shizhuom
Copy link

Hi,

I wonder where can I find the read-to-isoform mapping information from the tool?

Thank you!

@timbitz
Copy link
Collaborator

timbitz commented Dec 16, 2024

Hi @shizhuom, Isosceles does not perform a one-to-one mapping of reads-to-isoforms. Instead, it uses the expectation-maximization (EM) algorithm to assign reads to isoforms, based on the maximum likelihood estimates of the transcripts' relative expression levels. This means that ambiguous long reads can contribute to the quantification of multiple full-length transcripts, much like how RSEM or Kallisto handle ambiguous short-read data.  For example, we find that ambiguous truncated reads are pervasive in nanopore single-cell data, eg. from droplet-based protocols that anchor from the 5' or 3' ends.  

We believe this approach is why Isosceles—and Bambu, which also uses EM—outperform other methods in the quantification benchmarks in our recent paper. Before applying the EM algorithm, Isosceles groups reads into Transcript Compatibility Counts (TCCs), which are sets of reads that are compatible with the same isoforms. Isosceles does provide the counts and compatibility matrix mappings for these TCCs, which are available as a summarized experiment in R using the bam_to_tcc function.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants