slopBed chromsizes filter on raw MACS2 output#51
Open
Conversation
Collaborator
|
Did you try it on data that has the bad peaks and see if this fixes it? |
Collaborator
Author
|
I've asked the person for the file - see #50 - I'll give it a try and let you know, though it seems pretty clear that MACS2 is outputting a peak that goes beyond the chromosome length. will keep you guys updated |
Collaborator
|
LGTM actually and I am seeing this issue. I will try it and check that this fixes it |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sometimes MACS2 produces outputs (peaks and bedgraphs) that extend beyond the annotated chromosome lengths. Downstream tools (UCSC tools in particular) will complain about this. To fix, I put a slopBed in the sorting/cleaning steps of the MACS2 peak calling pipeline (going from raw MACS2 output into cleaned up files). Have run a test w/ ATAC data to make sure these don't break the pipeline, might be good to get second confirmation from one more run by someone else.