interval_method option for statistical summaries #7
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
…ehavior with sparse variableStep bigWig data
…er regions that do not vary much.
ghost
assigned 
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.
These are the modifications that were discussed with Lincoln several weeks ago regarding adding an interval_method option when working with statistical_summaries from BigWig datasets when drawing wiggle_xyplots. This allows the user to report the mean, sum, minimum, or maximum score for each interval. The default is mean, the same as pre-existing behavior.
Changes have been made to wiggle_xyplot (wiggle_data), hybrid_plot, and vista_plot glyphs to support this. Documentation have been added to wiggle_xyplot.
Also included are fixes for bad behavior with sparse variableStep data from bigWig, most visible when using the line graph_type. The default return value for each interval in the data array was 0 when the statistical_summary reported a validCount of 0, resulting in the line bouncing from real values to 0, unlike the behavior with wib files, which draws a line from real value to next available real value.
The fix is to change the default return value to undef, and then toss those undefined values when preparing the parts for rendering.