Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Clarify RSeQC bam_stat proper pairs column title#3526

Merged
ewels merged 4 commits into
MultiQC:mainfrom
pinin4fjords:fix/rseqc-bamstat-proper-pairs-label
Apr 9, 2026
Merged

Clarify RSeQC bam_stat proper pairs column title#3526
ewels merged 4 commits into
MultiQC:mainfrom
pinin4fjords:fix/rseqc-bamstat-proper-pairs-label

Conversation

@pinin4fjords

@pinin4fjords pinin4fjords commented Apr 9, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Rename the RSeQC bam_stat "Proper Pairs" General Statistics column to "% Proper Pairs (MAPQ>=30)"
  • Expand the description to explain that the value only reflects reads with MAPQ >= mapq_cut (default 30)

Context

RSeQC bam_stat.py applies a default MAPQ >= 30 filter before counting. Its proper pairs percentage uses a filtered numerator (only MAPQ >= 30 reads) against total records as denominator, but the column title doesn't indicate any filtering is happening. This has caused confusion for users who expect the value to reflect all reads.

Adding "(MAPQ>=30)" to the title makes the filtering immediately visible.

Changes

  • multiqc/modules/rseqc/bam_stat.py: Updated title and description for the proper_pairs_percent General Statistics column header

🤖 Generated with Claude Code

pinin4fjords and others added 2 commits April 9, 2026 10:51
RSeQC bam_stat.py only counts proper pairs among reads with
MAPQ >= mapq_cut (default 30), but the General Statistics column
was titled simply "Proper Pairs", matching the samtools stats
column which counts all proper pairs regardless of MAPQ. This
causes confusion when both columns appear side by side with very
different percentages for the same sample.

Add "(MAPQ>=30)" to the title and expand the description to
explain the filtering.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

@ewels ewels left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I think we can get away with it being a little simpler / shorter? What do you think?

Could add some clarification in the MultiQC module docs as a compromise if you wanted.

Comment thread multiqc/modules/rseqc/bam_stat.py Outdated
pinin4fjords and others added 2 commits April 9, 2026 11:00
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

@ewels ewels left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@ewels ewels merged commit 97eff3a into MultiQC:main Apr 9, 2026
11 checks passed
@ewels ewels added this to the v1.34 milestone Apr 9, 2026
@ewels ewels self-assigned this Apr 9, 2026
ewels pushed a commit that referenced this pull request May 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants