-
Notifications
You must be signed in to change notification settings - Fork 6
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
Run fails after 1 hour #2
Comments
Hi @JBreunig, can you share the command used, the first lines of your TE BED file (using |
Here you go...thanks again: $$head Mm10TEannotation.bed $ls -Rlht |
Can you share the first lines of the output of |
Here you go: samtools view Aligned.sortedByCoord.out.bam | head |
Ok, I see the issue: your BAM file doesn't match the names of the BED file. For example, BED file has "chr1" whereas the BAM has "1". First, delete all files from the SoloTE output directory you were using, and then use |
That makes sense but the same error happened despite deleting directories and referring to new BED. Could it be the second 'chr' in the bed file? Shall I try: edit: that didn't fix it either. |
Looking at the BAM lines you shared, an additional issue is the reads not associated with genes have the This is similar to issue #3, and we are working on a fix. Can you share your alignment protocol? This would help us better expand the usability and compatibility of our tool. In #3, there was a mention of using the Cumulus's STAR solo pipeline. . |
Yes, I'm also using STARsolo (but not Cumulus). I use a custom reference based on mm10 but which includes a handful transgenes that we add. Happy to share the BAM or other items if it helps. |
Thanks for the quick reply. And yes, I would appreciate it a lot If you could share the BAM file of chromosome 1 only, which hopefully should be enough for validation (we are now working on the fix to this issue). |
Just tried to run and got a new error:
Edit, looking at the code, it sems like there is a new command line argument for outprefix so I added one and it is running now. |
@JBreunig you are correct. We detected a bug when running it, so we modified the command line arguments. Please let us know if you are able to successfully run the pipeline, in order to make an official release of this updated version. |
Everything looks good through to processing in Seurat...thanks! |
You're more than welcome! |
I tried running the commands and it failed after about an hour. Might you have any suggestions on troubleshooting from the output below?
(Samtools 1.16.1; Bedtools v2.30.0; R 4.2.1)
The text was updated successfully, but these errors were encountered: