You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working with paired-end data from different projects (different origins). I wanted to reanalyze these data using my own pipeline with STAR (version 2.7.10a). I was able to obtain correct mapping, with an average of 80% uniquely mapped reads for most of my samples. However, when I started working on these data, I noticed that in the ReadsPerGene.out.tab file, a majority of my reads (~2/3) were classified as N_noFeature. Using rnaseqc, I observed that these reads were mapped to intronic regions.
Since the intergenic rate seems reasonable, I don't think there was DNA contamination in the samples. I have the impression that the issue might be related to an annotation problem. I used a genome index generated from Ensembl files, and I tried generating another index using Gencode files, but the result was the same.
Hello,
I'm working with paired-end data from different projects (different origins). I wanted to reanalyze these data using my own pipeline with STAR (version 2.7.10a). I was able to obtain correct mapping, with an average of 80% uniquely mapped reads for most of my samples. However, when I started working on these data, I noticed that in the ReadsPerGene.out.tab file, a majority of my reads (~2/3) were classified as N_noFeature. Using rnaseqc, I observed that these reads were mapped to intronic regions.
Here are some relevant statistics:
Since the intergenic rate seems reasonable, I don't think there was DNA contamination in the samples. I have the impression that the issue might be related to an annotation problem. I used a genome index generated from Ensembl files, and I tried generating another index using Gencode files, but the result was the same.
Here is the STAR command I used:
Do you have any idea why this might be happening?
Thanks for your help.
The text was updated successfully, but these errors were encountered: