-
Notifications
You must be signed in to change notification settings - Fork 49
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
zero mapped rates uisng rmats #396
Comments
After examining the Log.final.out file, >90% of reads were unmapped due to too many mismatches as follows: However, when I used STAR for alignment, the unique mapped rates reached 90%. |
Hi, Dr EricKutschera, I have found the reasons but I still do not know how to address them. STAR was run with the default argument "--outFilterMismatchNmax 10 ", however, STAR in rmats was run with the argument "--outFilterMismatchNmax 3", resulting in a high proportion of reads flagged as a mismatch. Thus, only <1% of reads were mapped to the genome, and few AS events were detected. |
You can align the reads outside of rMATS and then use --b1/--b2: https://github.com/Xinglab/rmats-turbo/tree/v4.3.0?tab=readme-ov-file#starting-with-bam-files If you still want to use --s1/--s2 then you can edit the STAR parameters in https://github.com/Xinglab/rmats-turbo/blob/v4.3.0/rmats.py#L66 |
When I use STAR alone to align reads from two Fastq files, the alignment rate reaches 90%. However, when I use rMATS, the alignment rate is 0%, resulting in no output of any alternative splicing events.
The text was updated successfully, but these errors were encountered: