We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi, always loved using VISDAT.
But now: vis_dat(diamonds) shows an empty visdat plot! (only a tenuous grid w/ light gray lines is visible...no colors).
vis_dat(iris) vis_dat(airquality) are both OK!.
Issue looks identical to Issue #32: "Blank plot with grid lines shown #32"
UPDATE: Downsampled the number of rows in diamonds and visdat works ok:
diamonds %>% slice(1:1000) %>% vis_dat()
Suggestion: would be VERY nice if visdat would "downsample" / "slice" the number of rows of a large DF automatically.
This would avoid presenting the (startled) user an empty plot, w/o any warning...
Just a suggestion of a long-time fan of VISDAT! :-)
The text was updated successfully, but these errors were encountered:
Hi there! This is a duplicate of #32 - unfortunately it is a bit tricky to solve!
Sorry, something went wrong.
No branches or pull requests
Hi,
always loved using VISDAT.
But now:
vis_dat(diamonds)
shows an empty visdat plot!
(only a tenuous grid w/ light gray lines is visible...no colors).
vis_dat(iris)
vis_dat(airquality)
are both OK!.
Issue looks identical to Issue #32:
"Blank plot with grid lines shown #32"
UPDATE:
Downsampled
the number of rows in diamonds
and visdat works ok:
diamonds %>%
slice(1:1000) %>%
vis_dat()
Suggestion:
would be VERY nice
if visdat would "downsample" / "slice"
the number of rows of a large DF
automatically.
This would avoid presenting the (startled) user
an empty plot,
w/o any warning...
Just a suggestion
of a long-time fan of VISDAT! :-)
SFd99
latest versions of:
visdat pkg 0.6.0.9000 (installed via devtools)
Ubuntu Linux 20.04 64bits
R 4.0.3
Rstudio 1.3.1073
The text was updated successfully, but these errors were encountered: