Controlling Animation for Points When There Are Missing Values (ggplotly)
Nessuno ha ancora preso questa issue.
- Lingua principale
- R
- Stelle
- 2.7k
- Fork
- 641
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
I am building a Hans Rosling type visualisation, however, I am having issues with the point movements. I have attached some code that creates an example of my problem, which can be found below.
The best way I can describe it is that whenever there is a missing value, a point has to disappear, therefore a different becomes assigned to a point even if it's in a different group. This logically doesn't make any sense to me.
In the example below, I've removed the Month Year of Feb 2021 from Clinic A, (i.e. I've removed the whole row), which means that the point disappears as shown in the play animation movement. However, if you notice instead of the Clinic A point simply disappearing, it chooses to keep the Clinic A point, turn into a different Clinic, in this case Clinic B and also convert the surrounding points to different clinics as well. I think it's working off the logic of turn into whatever point is the nearest somehow.
To really understand what is happening observe the hover of the points from Jan 2021 to Feb 2021
My question(s) is/are:
- Why is this happening?
- How do I specify some sort of group or ID to the points so that they aren't randomly turning into other Clinics?
In my real world scenario I have over 90+ different unique IDs/Clinics so ideally someone would be able to press play and then follow a single point moving across the viz, specifically noticing for any abnormalities in movement. It's extremely difficult to do this, or rather almost impossible, if a given point is converting itself into another point on the fly.
Note: I have confirmed this problem is replicated when using both plot_ly() and ggplotly() and only seems to happen when there is missing data
Code to Replicate Problem:
set.seed(24)
test <- data.frame(Month_Year = rep(paste(month.abb, rep(2021:2022, each = 12), sep = "_"), 4),
x = abs(rnorm(24*4)),
y = abs(rgamma(24&4,2,1)),
Clinic = rep(c("Clinic A", "Clinic B", "Clinic C", "Clinic D"), each = 24))
test$Month_Year <- factor(test$Month_Year, levels = paste(month.abb, rep(2021:2022, each = 12), sep = "_"))
test <- test[-c(2,8,12),]
pt <- test %>%
ggplot(aes(x = x, y = y, frame = paste0(sprintf("%02d", as.numeric(Month_Year)), Month_Year), text =
paste(
"RAR:", round(y, 3),
"\nMR:", round(x, 3),
"\nClinic:", Clinic
))) +
geom_point(shape = 1, color = "firebrick", aes(group = Clinic)) +
# geom_text(aes(y = NAG + 5)) +
theme_minimal() +
labs(x = "Rolled Mortality Rate - 3 Month Average", y = "Rolled Admission Rate - 3 Month Average") +
scale_x_continuous(limits = c(0, 6))
ggplotly(pt, tooltip = "text") %>%
animation_opts(
3000,
redraw = T
) %>%
animation_slider(
currentvalue = list(prefix = "Month Year: ")
)
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Inizia eseguendo la riproduzione R fornita sia con plot_ly() sia con ggplotly(), includendo animation_opts() e animation_slider(). Confronta l’identità dei punti e le etichette al passaggio del mouse tra Jan 2021 e Feb 2021 quando mancano delle righe. Il lavoro è considerato completato quando il comportamento è spiegato e viene identificato un modo documentato per preservare le identità di Clinic, oppure un fix circoscritto.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- r
- Ambito
- data-visualization
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100