-
Notifications
You must be signed in to change notification settings - Fork 506
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
STARsolo output formatting issues #556
Comments
Hi @vpresnyak have you re-generated the genome index with the 2.7.0a version? There is pull-in request for the matrix header change, I will make a patch tonight. Cheers |
The genome reference was generated fresh from the GRCh38 gencode files. I did try running it with an older genome, which threw an error as it's supposed to. |
Thanks! I think I found the problem, please try the patch I just uploaded to GitHub master. |
We think this can be closed ... isn't it? |
It should be working, but I did not hear back from the OP. |
Hi @alexdobin,
I'm testing STARsolo for our single-cell use and have run into some issues using the output for downstream analysis. The formatting of the files does not match that of the Cellranger outputs and trips up tools that expect those files as input (e.g. scanpy).
The formatting of genes.tsv seems unusual - it looks like the information alternates between columns. This isn't the case in Cellranger output files:
As a separate issue, the matrix.mtx file is missing its header. This seems to be required by the file type definition (https://math.nist.gov/MatrixMarket/formats.html) and is checked by tools that read the file (cellranger outputs provided for comparison).
I'm not sure if I'm doing something funny at the command line, here's how I'm running it:
STAR --soloType Droplet --runThreadN 64 --soloCBwhitelist /scratch/cellranger-2.1.1/cellranger-cs/2.1.1/lib/python/cellranger/barcodes/737K-august-2016.txt --outFileNamePrefix . --genomeDir /scratch/temp_genome --readFilesCommand gunzip -c --readFilesIn ...
The text was updated successfully, but these errors were encountered: