improve heatmap limits #177
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.
By default, heatmap limits now encompass only values for mutations not excluded by initial slider values.
Designed to address this issue: dms-vep/dms-vep-pipeline-3#40
Specifically:
version 6.7
heatmap_lims_from_slider_initoption tolineplot_and_heatmapso that by default heatmap range is set by data shown with initial slider stats. Set this option toFalseif you want old behavior for plot limitsinit_floor_at_zeroformut_icXX_plotto beTruelike for other plots.