FeatureCount for miRNA count
Can Anyone help me ? I want to count number of miRNA from my miRNAseq data by using featureCount. I have mapped my draft genome against HG38 by using Bowtie2. Now i want to count, so i have tried featureCounts with various parameters but i couldn't. So can anyone suggest a idea. Thanks in advance.
• 5,262 views
•
link
0 answers
No answers yet.
Log in to answer this question.
And it would be VERY helpful if you can share which parameters you tried, and what the error message was. We can't magically know what's going wrong.
Command : featureCounts -t miRNA -g name -a hsa.gff -o counts.txt mapping_results.bam
Result : corrupted file ....Like ... Dot dot dot dot dot..........
Please use
ADD COMMENTorADD REPLYto answer to previous reactions, as such this thread remains logically structured and easy to follow. I have now moved your post but as you can see it's not optimal. Adding an answer should only be used for providing a solution to the question asked.It looks like your bamfile or gff is corrupted. Some things to look at:
miRNAis present in your gff?samtools index mapping_results.bam?Thanks for the reply WouterDeCoster
You misunderstood my questions:
samtools flagstat mapping_results.bamandsamtools idxstats mapping_results.bam?Thanks for the response WouterDeCoster,
Output :
Again, please use
ADD COMMENTorADD REPLYto answer to previous reactions, as such this thread remains logically structured and easy to follow. I have now moved your post but as you can see it's not optimal. Adding an answer should only be used for providing a solution to the question asked.That's quite a low fraction of mapped reads... What's in the log file of featureCounts?
Log File contains
I added markup to your post for increased readability. You can do this by selecting the text and clicking the 101010 button. When you compose or edit a post that button is in your toolbar, see image below:
I don't see anything wrong with the log. Just like the flagstat output: an enormous fraction of your reads are not mapped. To me, it seems that's an issue you should address first.