-
Notifications
You must be signed in to change notification settings - Fork 172
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
STAR always uses V2 chemistry #60
Comments
This should be fixed in the latest |
This is actually NOT fixed in the latest dev version, as I get
with a v3 library. (v3 has 28nt barcode+umi, compared to 26 in v2) |
We should get this fix into 2.0.0 too in my opinion :-( |
I think this parameter is missing. Should be somehow generated by the java code in the |
Should be fixed in #113 now |
Check Documentation
I have checked the following places for your error:
Description of the bug
STARsolo uses 10X-V2 chemistry, regardless of what is specified.
Steps to reproduce
Steps to reproduce the behaviour:
nextflow run nf-core/scrnaseq -r 1.1.0 -params-file nf-params.json
nf-params.json
Where:
genome.fa
is fromhttp://ftp.ebi.ac.uk/pub/databases/gencode/Gencode_mouse/release_M27/GRCm39.genome.fa.gz
;genes.gtf
is fromhttp://ftp.ebi.ac.uk/pub/databases/gencode/Gencode_mouse/release_M27/gencode.vM27.annotation.gtf.gz
; and the fastq files are fromhttps://www.ncbi.nlm.nih.gov/sra/?term=SRR14597268
Expected behaviour
According to the STAR readme,
This option is not specified by the pipeline. The STAR script should differ by the chemistry, as per https://www.biostars.org/p/462568/
Log files
nextflow.log
System
Nextflow Installation
Container engine
Additional context
Would be happy to write a PR
The text was updated successfully, but these errors were encountered: