Add better handling for bedMethyl files #4662
Merged
Conversation
This file contains 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
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.
Our default bedMethyl parser would get confused by these, and think it was UCSC transcript. It is hard to really tell what data in a BED file is indicating without any header. We try to use heuristics to determine when something should be a UCSC transcript in BED format but it is tricky. In any case, this PR adds more heuristics to detect bedMethyl, parse it in a specialized way
This PR also makes it so that they can be displayed in a MultiQuantitativeTrack. This lets you split out the modifications types into different subtracts. This requires passing the currently displayed regions to the "getSources" wiggle RPC call. there were older comments that said it would do this but now it just does it :)