Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filtering the bam of mapped fragments by MAPQ #67

Open
Sean-McGinty opened this issue Jul 25, 2024 · 1 comment
Open

Filtering the bam of mapped fragments by MAPQ #67

Sean-McGinty opened this issue Jul 25, 2024 · 1 comment
Labels
question Further information is requested

Comments

@Sean-McGinty
Copy link

Ask away!

As I understand it, the pipeline doesn't perform any kind of MAPQ filtering before generating the hic, pairs, or cooler files. What would be the easiest change I could make to this pipeline to filter out fragments with a low MAPQ before generation of the output files? If I am using singularity I wonder if making this change is even feasible. Any advice would be appreciated.

@Sean-McGinty Sean-McGinty added the question Further information is requested label Jul 25, 2024
@sarahjeeeze
Copy link
Contributor

Hi, if you are happy to ammend the script you can use something like samtools view -bq ${minimum_mapping_quality} input.bam

You could add that to the merge_name_sorted_bams/merge_coord_sorted_bams processes in modules/local/common.nf but we've not tested this and its not a supported feature currently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Development

No branches or pull requests

2 participants