Improve autoplot for when dealing with many unique keys + heatmap#693
Open
JavierMtzRdz wants to merge 92 commits intodevfrom
Open
Improve autoplot for when dealing with many unique keys + heatmap#693JavierMtzRdz wants to merge 92 commits intodevfrom
autoplot for when dealing with many unique keys + heatmap#693JavierMtzRdz wants to merge 92 commits intodevfrom
Conversation
… step for epi_df.
…ed x-axis, and improved mode bar controls, and refine data grouping and subsampling warnings.
…ve `autoplot` and archive views to use it
autoplot for when dealing with many unique keysautoplot for when dealing with many unique keys + heatmap
…format the epi_df when in long format.
…eformat the epi_df when in long format.
It verifies that autoplot chooses the value when no variable is specified.
…le is not numeric.
Contributor
Author
It seems useful/common enough that we should not have a hiccup requiring user to go back and install plotly.
And add lines in examples so that paragraph-chunk-eval will actually let user look at each one.
…arning and error messages
…c for facets, dropdowns, and color legends.
… removing jsonlite dependency.
…iple signal variables
…ot all numeric columns by default, and standardize values in `plot_heatmap` for multiple variables.
… create specific pivot functions for epi_df and epi_archive
…d create specific pivot functions for epi_df and epi_archive
5 tasks
The results were still probably valid and converting is slower, but we don't want any surprises.
Automated pivoting for long-format data with `as_epi_*` and enhanced response selection in `autoplot`
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
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.
Checklist
Please:
PR).
brookslogan, nmdefries.
DESCRIPTION. Always incrementthe patch version number (the third number), unless you are making a
release PR from dev to main, in which case increment the minor version
number (the second number).
(backwards-incompatible changes to the documented interface) are noted.
Collect the changes under the next release number (e.g. if you are on
1.7.2, then write your changes under the 1.8 heading).
/styleto check the style and fix any issues./documentto check the package documentation and fix any issues./preview-docsto preview the docs.process.
Improve
autoplotfor when dealing with many unique keysThis PR improves the usability and performance of
autoplot()when handling many distinct key combinations. It introduces automatic subsampling for static plots and an interactive dropdown interface for easier exploration.Static plots for
epi_dfwith many keys now automatically subsample to 10 unique keys by default. This prevents the plot from becoming unreadable. When subsampling occurs, a warning is issued with suggestions for.max_keys = Inf,interactive = TRUE, or.facet_filter.Added the
interactiveparameter to support plotly plots. In this scenario, facetedepi_dfandepi_archiveplots use dropdown menus.I also included the heatmap function we previously discussed.
Some examples below.
reprex_pr_explanation.html
Magic GitHub syntax to mark associated Issue(s) as resolved when this is merged into the default branch