Backend: refactor optional binning in lineplot and the bin* family of fxns
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Refactorización
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Stack tecnológico
- r
- Área
- data-visualization
Línea de trabajo
Start by locating the lineplot, bin* and group* functions in the R package and compare their current arguments and behavior for numeric and date axes. Trace how unbinned results are represented, then identify the relevant tests or examples. Done means the optional binning design and the proposed bin* to group* refactor are implemented consistently without relying on placeholder bin widths.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
so currently if you dont want the line plot binned youd have to pass it a binwidth of 0 for numeric x axes and 1 day for dates. the response you get is consistent w if the data were to have been binned, except bin start and bin end are the same value and the bin label is essentially useless.. that seems less than ideal.
additionally, the bin* family of fxns now have some members that take only an x-axis arg, and some that take both an x and y axis. that also seems less than ideal, and while on the surface unrelated to the prev problem im starting to suspect the solution to both problems might be the same..
i think to solve both these problems we should consider adding the concept of 'bin' optionally to any/all group* fxns where its even remotely relevant. if we can we should also refactor the two bin* fxns that only take an x-axis argument to take both x and y args and become group* fxns themselves. this is likely to become a bit involved and requires some careful thinking, so i didnt want to try to attach it to the lineplot deadline.
- Lenguaje dominante
- R
- Estrellas
- 1
- Forks
- 0
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de VEuPathDB/plot.data
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 25/100
-
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
-
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
-
empty two by two Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
Todos los issues de VEuPathDB/plot.data
Issues similares
-
bug triage_needed
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
pharmaverse/rtables#1123 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Incorrect coaches in games.csv Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
-
Trying to reassign a reactiveVal to the name of an existing reactiveVal doesn't overwrite the latter Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100