This is the first writing here. (So far I have only observed many threads here.) Please let me have the solution for this issue.
From RNA-seq, I have tried to call SNVs using samtools. (mpileup)
Previously, when I used Mapsplice as an alighment tool, the SNV calling using Samtools worked well. However, now I am trying to use RNASEQR alignment tool (NAR 2012; this is shown to be good for SNV calling purpose; this tool mainly use bowtie-alignment inside), and the Samtools results (using same parameter as for mapsplice) from the RNASEQR-generated sam/bam files were strange. The vcf file size is big, and when I look at inside the files, almost all locations are called as SNVs.
as a short example,
1 14544 . T C 6.02 ...
1 14545 . T C 6.02 ...
1 14546 . C A 6.02 ...
1 14547 . C G 6.02 ...
1 14548 . G C 6.02 ...
1 14551 . C T 6.02 ...
Do you know what is the reason of this? Please let me solve it.
Thanks,
From RNA-seq, I have tried to call SNVs using samtools. (mpileup)
Previously, when I used Mapsplice as an alighment tool, the SNV calling using Samtools worked well. However, now I am trying to use RNASEQR alignment tool (NAR 2012; this is shown to be good for SNV calling purpose; this tool mainly use bowtie-alignment inside), and the Samtools results (using same parameter as for mapsplice) from the RNASEQR-generated sam/bam files were strange. The vcf file size is big, and when I look at inside the files, almost all locations are called as SNVs.
as a short example,
1 14544 . T C 6.02 ...
1 14545 . T C 6.02 ...
1 14546 . C A 6.02 ...
1 14547 . C G 6.02 ...
1 14548 . G C 6.02 ...
1 14551 . C T 6.02 ...
Do you know what is the reason of this? Please let me solve it.
Thanks,
Comment