Closed rstatistics closed 4 years ago
It's difficult for me to guess what is happening without seeing the stdout/stderr and the input BAMs and GTF. Perhaps there was an error reading the BAM files, or the reads just didn't indicate any alternative splicing
It's difficult for me to guess what is happening without seeing the stdout/stderr and the input BAMs and GTF. Perhaps there was an error reading the BAM files, or the reads just didn't indicate any alternative splicing Thank you for your reply. I have upload all my bam files and scripts in GitHub: git@github.com:rstatistics/rmats-issue.git I hope you could help me out. Thank you very much!
It seems that you didn't provide --readLength parameter when running both rmats, and the default value is 0 for this parameter. Different from v4.0.2, v4.1.0 version will filter out all reads that not match the input read length (in this case 0). And this is the reason you only have the header in those output files. You can easily fix it by providing the --readLength parameter. You can also add --variable-read-length flag in v4.1.0 to allow variable read length from bam files.
@ywang1993 It works with "--readLength 100 --variable-read-length " parameter, thank you for helping me out!
The output of rmats=4.1.0 with only header, pls check, thank you. rmats.py --b1 b1.txt --b2 b2.txt --gtf ./gene.gtf --od ../rmats --tmp ./tmp wc -l ../rmats/*