If you happen to see a question you know the answer to, please do chime in and help your fellow community members. We encourage our fourm members to be more involved, jump in and help out your fellow researchers with their questions. GATK forum is a community forum and helping each other with using GATK tools and research is the cornerstone of our success as a genomics research community.We appreciate your help!
Test-drive the GATK tools and Best Practices pipelines on Terra
Check out this blog post to learn how you can get started with GATK and try out the pipelines in preconfigured workspaces (with a user-friendly interface!) without having to install anything.
We will be out of the office on November 11th and 13th 2019, due to the U.S. holiday(Veteran's day) and due to a team event(Nov 13th). We will return to monitoring the GATK forum on November 12th and 14th respectively. Thank you for your patience.
I dont understand what is "filtering out during traversal" ?
When we run BaseRecalibrator i.e. the first phase of BQSR, we get some information in logs at the end of the process saying the following thing:
INFO 02:09:56,512 BaseRecalibrator - Processed: 1059663038 reads
INFO 02:09:56,514 ProgressMeter - done 1.06e+09 5.4 d 7.3 m 100.0% 5.4 d 0.0 s
INFO 02:09:56,514 ProgressMeter - Total runtime 464091.25 secs, 7734.85 min, 128.91 hours
INFO 02:09:56,514 MicroScheduler - 25351 reads were filtered out during traversal out of 45356 total (55.89%)
INFO 02:09:56,514 MicroScheduler - -> 155 reads (0.34% of total) failing DuplicateReadFilter
INFO 02:09:56,515 MicroScheduler - -> 25196 reads (55.55% of total) failing MappingQualityZeroFilter
INFO 02:10:00,308 GATKRunReport - Uploaded run statistics report to AWS S3
What does this phase means "filtered out during traversal"? Does it has some specific significance?