-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Error in map_reads_STAR #135
Comments
Update: |
Hi there, thanks for opening the issue and for the update. We'll investigate this. |
Hi Qijie, the error is triggered by STAR, complaining about a read with 0 bytes of sequence. (The crash of STAR then also crashes the splice_bam_header.py script, which produces more error messages).
Can you confirm that indeed there is such a read in the FASTQ input data? What does the fastq record for SRR27331456.1 look like? |
Is it this read?
It is indeed very short and should not survive the adapter and polyA trimming. Should never end up being fed into STAR. I have a suspicion that the behavior of the DropSeqtools may have changed. We use 2.5.1, not 3.0.0. Could you perhaps give it a try with DropSeqTools 2.5.1 ? When you say it runs with spacemake 2.7.8, have you tested 2.7.9 as well? Do you use the same version of DropSeqTools? Best, |
Hi @marvin-jens , Thank you for the guidance!
It might be because of the Dropseqtools version. Now I am testing Dropseqtools 2.5.1 with spacemake 0.8.0 and Java 21.0.2 Qijie |
Hi @marvin-jens , I tried
While 0.7.9 and 0.7.8 sometimes worked, sometimes cannot pass the same rule with following message:
Do you have any suggestion on this? Or can you please share your environment with me (I also feel the Qijie |
Hi spacemake developer,
I got an error message when running openst & spacemake (v0.8.0) several times and I cannot overcome it.
The error is related to reading
unaligned_bc_tagged.polyA_adapter_trimmed.bam
usingpysam
. The full error message is showing below:I am using Dropseq-3.0.0 with Java-21.0.2.
And config command for spacemeke is (sample downloaded from openST GEO repository):
Please advise on how to overcome this issue..
Best,
Qijie
The text was updated successfully, but these errors were encountered: