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

[Feature Request] report number of duplicated fragments in bulk #145

Closed
dawe opened this issue Dec 13, 2023 · 4 comments
Closed

[Feature Request] report number of duplicated fragments in bulk #145

dawe opened this issue Dec 13, 2023 · 4 comments

Comments

@dawe
Copy link

dawe commented Dec 13, 2023

Hello and thanks once more for chromap.
I know for scATAC-seq data, the output BED file contains the duplicate_count in 5th column. I wonder if it would be possible to report this information also for bulk analysis, possibly using the 4th column (currently unassigned and set to N). I'm asking this as I would like to use such information for some QC. Having the duplicate count for each fragment could be used to derive some ENCODE-like measures, but also to streamline decoratio analysis. Currently I do both by running chromap without any duplicate removal and count them later.

@mourisl
Copy link
Collaborator

mourisl commented Dec 13, 2023

Thank you for the suggestion. Indeed, the duplication number should be included in the output for the bulk data as well. We will implement this in the next few days.

@mourisl
Copy link
Collaborator

mourisl commented Dec 26, 2023

We have added the duplicate number to the last column of the BED file for bulk analysis in the li_dev5 branch. Could you please check out that branch and give it a try to see whether it works on your data? Thank you.

@dawe
Copy link
Author

dawe commented Dec 27, 2023

It works, thank you! Can I start using this version or should I wait for the next official release?

@mourisl
Copy link
Collaborator

mourisl commented Dec 27, 2023

This branch will be the next official release if no other significant bug is found. I'm currently waiting for the #143 . Once it is resolved, we will draft a new release based on li_dev5.

I think you can use this version for now if it is time-sensitive.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants