agregar comentario sobre aviso al resumir agrupamiento con dos variables

[avallecam]

• Please check if the PR fulfills these requirements

• I have read the CONTRIBUTING guidelines
• Checks have been run locally and pass

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Agregamos parrafo y pestaña desplegable para comentar sobre el mensaje de salida al agrupar dos variables y luego usar summarise(), funcion que remueve la ultima variable de resumen.

`summarise()` has grouped output by 'edad'. You can override using the `.groups` argument.

Secciones del tutorial con este mensaje:

• https://epiverse-trace.github.io/epitkit/Visualizacion.html#ejemplo-1-gr%C3%A1fico-de-dispersi%C3%B3n-scatter-plot
• https://epiverse-trace.github.io/epitkit/Visualizacion.html#ejemplo-5--gr%C3%A1fico-con-facet-wrap

• Other information:

Esto permitira apoyar a instructores en la aclaracion las dudas que surjan en este paso. Propuesto luego de consulta por @lgbermeo

reprex de soporte

# importar librerias
library(tidyverse)

# leer datos
covid19 <- readr::read_rds("http://epiverse-trace.github.io/epitkit/data/muestra_covid.RDS")

# agrupar por "edad" y "sexo"
# con dplyr::group_vars() confirmamos agrupamiento
covid19 %>%
  dplyr::group_by(edad, sexo) %>%
  dplyr::group_vars()
#> [1] "edad" "sexo"

# resuminos por "edad" y "sexo"
# con dplyr::group_vars() confirmamos que
# luego de usar dplyr::summarise()
# removemos una variable de agrupamiento
# (debido a que ese grupo es ahora una sola fila)
covid19 %>%
  dplyr::group_by(edad, sexo) %>% 
  dplyr::summarise(casos = n()) %>% 
  dplyr::group_vars()
#> `summarise()` has grouped output by 'edad'. You can override using the
#> `.groups` argument.
#> [1] "edad"

^{Created on 2025-09-05 with reprex v2.1.1}

[github-actions]

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/epiverse-trace/epitkit/compare/md-outputs..md-outputs-PR-42

The following changes were observed in the rendered markdown documents:

 Visualizacion.md                                   | 131 +++++++++++++++++++--
 ...alizacion-rendered-unnamed-chunk-12-1.png (new) | Bin 0 -> 26827 bytes
 ...alizacion-rendered-unnamed-chunk-13-1.png (new) | Bin 0 -> 4405 bytes
 fig/Visualizacion-rendered-unnamed-chunk-16-1.png  | Bin 4552 -> 4680 bytes
 fig/Visualizacion-rendered-unnamed-chunk-18-1.png  | Bin 5019 -> 4552 bytes
 fig/Visualizacion-rendered-unnamed-chunk-20-1.png  | Bin 5512 -> 5019 bytes
 fig/Visualizacion-rendered-unnamed-chunk-22-1.png  | Bin 11222 -> 5512 bytes
 fig/Visualizacion-rendered-unnamed-chunk-25-1.png  | Bin 23669 -> 11222 bytes
 fig/Visualizacion-rendered-unnamed-chunk-26-1.png  | Bin 9729 -> 24402 bytes
 fig/Visualizacion-rendered-unnamed-chunk-28-1.png  | Bin 28518 -> 23669 bytes
 ...alizacion-rendered-unnamed-chunk-29-1.png (new) | Bin 0 -> 9729 bytes
 ...alizacion-rendered-unnamed-chunk-30-1.png (new) | Bin 0 -> 10619 bytes
 ...alizacion-rendered-unnamed-chunk-31-1.png (new) | Bin 0 -> 28518 bytes
 ...ualizacion-rendered-unnamed-chunk-9-1.png (new) | Bin 0 -> 53897 bytes
 md5sum.txt                                         |   2 +-
 15 files changed, 119 insertions(+), 14 deletions(-)

What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2025-09-05 05:58:35 +0000