Skip to content
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

All the values of IJC_SAMPLE_1 and SJC_SAMPLE_1 are zero #452

Open
yutaixian opened this issue Nov 19, 2024 · 3 comments
Open

All the values of IJC_SAMPLE_1 and SJC_SAMPLE_1 are zero #452

yutaixian opened this issue Nov 19, 2024 · 3 comments

Comments

@yutaixian
Copy link

hi,I run rmats with python rmats.py --b1 ./d_1D.txt --tmp ./output/d_11/tmp --statoff --gtf 1D_43_stringtie.gtf -t single --readLength 75 --nthread 4 --od test_output/d_11 but all the values of IJC_SAMPLE_1 and SJC_SAMPLE_1 are zero. Why? I have checked my BAM files and there are no problems.
image

@EricKutschera
Copy link
Contributor

Since you ran with only --b1 the statistical model is not run and there is no filtering so events will be included in the output files even if there are no supporting reads: #96 (comment)

If there are no supporting reads for any event then the read outcome section should show why reads were not USED: #328 (comment)

@yutaixian
Copy link
Author

Since you ran with only --b1 the statistical model is not run and there is no filtering so events will be included in the output files even if there are no supporting reads: #96 (comment)

If there are no supporting reads for any event then the read outcome section should show why reads were not USED: #328 (comment)

This is my nohup output file. I'd like to ask you if this looks normal. Are there any data flaws? I noticed that the value of EXON_NOT_MATCHED_TO_ANNOTATION is 110,612,760, which accounts for nearly 50%. Any suggestion?
image

@EricKutschera
Copy link
Contributor

The large number of reads filtered for EXON_NOT_MATCHED_TO_ANNOTATION looks like the main issue. Those reads were aligned without a splice junction and the region they aligned to is not annotated as an exon in your --gtf. One possible reason for EXON_NOT_MATCHED_TO_ANNOTATION is the bam files being aligned with a different gtf or version of the reference genome. If the aligner used different reference information then it makes sense for the alignments not to match the --gtf

Your previous post mentioned --gtf 1D_43_stringtie.gtf. It could be that the stringtie gtf just doesn't match up well with your reads

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants