-
Notifications
You must be signed in to change notification settings - Fork 163
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
Alevin "incorrect call for umi extract" with --dropseq option #258
Comments
Hi @pophipi ,
If it's too much trouble to compile from source, we will release a version w/ the hot-fix by today/tomorrow and would update you soon. P.S: I was curious how did the |
hi @k3yavi, Thanks for your help! I'm glad it's a quick fix. As for the dataset, I am not sure why the read length is 25bp. The paper I pulled it from stated that they used the standard DropSeq protocol and did not seem to mention and changes in CB and UMI length. In the case that they did change those lengths, what options can I use to set the pipeline? |
We might have to go through the paper and the dropseq guidelines to check what really changed. |
hey @pophipi , we have released Also, I tried running the |
@k3yavi To follow up on this dataset: I tried the alignment using DropSeq Tools and STAR and got similar alignment rates, so I think the custom length alignment is working properly. I may try using some other reference databases instead of GRCh38.p12 to see if alignment improves. Otherwise it may just be an issue regarding the dataset itself. |
Glad to hear that, let us know if you need any other help or have suggestions / feedbacks to improve Alevin. |
Hi,
I'm having issues getting alevin to work on dropseq data after following the tutorial for setting it up.
I am using the following command to run it:
salmon alevin -l ISR -1 SRR6054189.sra_1.fastq -2 SRR6054189.sra_2.fastq --dropseq -i ~/Documents/CordBlood/data/index_15 -p 10 -o ~/Documents/CordBlood/data/alevin_out --tgMap ~/Documents/CordBlood/data/txp2gene.tsv --dumpCsvCounts
and eventually get
"Incorrect call for umi extract"
Here's the full output:
I traced it back to AlevinUtils.cpp in the source files but could not make sense of it from there.
The program will run completely on the same data and library if I change --dropseq to --Chromium, eventually outputting the following after processing the reads:
and then this after processing the cells:
Other info:
Salmon v0.11.0 - downloaded binary from Github
I used Gencode 28 for the transcriptome
read files: https://www.ncbi.nlm.nih.gov/sra/SRX2676721[accn]
OS: CentOS
version: 2.6.32-696.23.1.el6.centos.plus.x86_64
LSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
Distributor ID: CentOS
Description: CentOS release 6.9 (Final)
Release: 6.9
Codename: Final
The text was updated successfully, but these errors were encountered: