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

UMI mode - Internal Demultiplexing? #111

Open
vals opened this issue Jun 3, 2016 · 3 comments
Open

UMI mode - Internal Demultiplexing? #111

vals opened this issue Jun 3, 2016 · 3 comments

Comments

@vals
Copy link
Collaborator

vals commented Jun 3, 2016

Hi,

I am very excited that there finally is a tool out that does proper UMI quantification! I will retire my heuristic method and recommend this in it's place.

There are a couple of use cases though which might be problematic from a practical stand point.

Firstly, this requires the cells to be demultiplexed from each other. In many protocols, e.g. CEL-seq or MARS-seq, the cellular barcode is not demultiplexed by the Illumina pre-processing pipeline. Do you have any recommendations for demultiplexing?

Additionally, in the more recent nanoliter droplet based protocols, there are hundreds of thousands of potential cellular barcodes. Usually an experiment only captures a few thousand cells, but demultiplexing in to files before seeing which ones actually contained cells does not work well with most file systems. In my heuristic script, I handled this by doing cellular barcode demultiplexing internally and returning a table. Is there any way Kallisto could do the demultiplexing internally, similar to how UMI's are handled?

@lakigigar
Copy link
Contributor

Hi Valentine,

Thanks! We are thinking about demultiplexing but have not tackled that step
for now. We do have a workflow for 10x that starts after the demultiplexing
that we've just posted and that you might find useful for some of the
technologies you mentioned as well (we plan mods for some of them in the
near future). See

https://pachterlab.github.io/kallisto/singlecell.html

You are right that many of the steps (including demultiplexing) might be
best handled internally in kallisto and we're looking at that.
Lior

On Fri, Jun 3, 2016 at 4:05 AM, Valentine Svensson <[email protected]

wrote:

Hi,

I am very excited that there finally is a tool out that does proper UMI
quantification! I will retire my heuristic method
https://github.com/vals/umis and recommend this in it's place.

There are a couple of use cases though which might be problematic from a
practical stand point.

Firstly, this requires the cells to be demultiplexed from each other. In
many protocols, e.g. CEL-seq or MARS-seq, the cellular barcode is not
demultiplexed by the Illumina pre-processing pipeline. Do you have any
recommendations for demultiplexing?

Additionally, in the more recent nanoliter droplet based protocols, there
are hundreds of thousands of potential cellular barcodes. Usually an
experiment only captures a few thousand cells, but demultiplexing in to
files before seeing which ones actually contained cells does not work well
with most file systems. In my heuristic script, I handled this by doing
cellular barcode demultiplexing internally and returning a table. Is there
any way Kallisto could do the demultiplexing internally, similar to how
UMI's are handled?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#111, or mute the thread
https://github.com/notifications/unsubscribe/AC042AECowEdtCdOesOZLEwADH6qf7Phks5qIAqKgaJpZM4ItbWh
.

@jbergenstrahle
Copy link

Hi,

Just wanted to drop in and ask if there has there been any further development regarding internal demultiplexing with Kallisto? I would be very interested in such an implementation!

@hmassalha
Copy link

Dear Prof. @lakigigar,
I am wondering if you have any internal solution for demultiplexing mainly for the kallisto bus tool?
Thanks a lot. HM

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

4 participants