Talks and Workshops | B101nfo

useR madrid: rtweet

Thu, 29 Feb 2024 19:00:00 +0200

This presentation was in Spanish. I shared the history of my involvement with rtweet and what is happening with the package and Twitter API.

Los paquetes van a CRAN

Fri, 25 Nov 2022 00:00:00 +0000

The “XII Jornadas de R y I congreso de R Hispano” conference is the meeting point of useRs in Spain with many people around the country and with different background from mathematicians, engineers, forest engineering. All the talks were in Spanish, although some of the contents were in English. I submitted this abstract in Spanish:

Por lo general, compartir nuestro trabajo con la comunidad R significa enviar un paquete a un archivo (CRAN, Bioconductor u otros). CRAN es el mayor repositorio de paquetes de R que viene aceptado por defecto por R. Pero, ¿Qué hay que hacer para escribir un paquete, que CRAN lo acepte y se mantenga en CRAN?
Que un paquete se mantenga en CRAN depende de la calidad del paquete. Esto se debe a que hay que pasar un proceso de revisión. Si el buen paquete sigue las reglas y tiene una calidad de acuerdo con sus criterios, se durará. Primero, hay un chequeo inicial automático; segundo, una revisión manual más profunda del código. Luego, si las sugerencias se aplican o se responden correctamente, el paquete se incluye en el archivo.
En cada paso se utilizan algunas reglas y criterios para decidir si el paquete avanza o no. Comprender lo que dicen estas reglas, los problemas comunes y los comentarios de los revisores ayudarán a evitar enviar un paquete para que sea rechazado. Reducir la fricción entre compartir nuestro trabajo, proporcionar paquetes útiles a la comunidad y minimizar el tiempo y los esfuerzos de los revisores.
A partir de los datos históricos veremos el proceso habitual, el tiempo de espera hasta su inclusión, el número de revisiones habituales antes de ser aceptados y el porcentaje de éxito. También haremos un recorrido histórico de los paquetes de CRAN: tiempo de duración de una versión en CRAN, relación entre versiones y dependencias y el número de paquetes nuevos habituales. Para ver qué características tienen que cumplir nuestro paquete para ser incluido y que otros usuarios pueden usar nuestro código con garantías de calidad.

It was accepted as a flash presentation of just 5 minutes in a parallel session focused in programming and teaching R. The room was full and people showed their interest before and after the talk, specifically how easy would it be to keep the package in CRAN or Bioconductor. If you have other questions let me know!

Releasing packages

Sun, 16 Jan 2022 00:00:00 +0000

On this presentation invited by the R User Group Ghana on the celebration of their 3rd anniversary. I presented a mix of data from previous work:

from the workshop I did for them for how to create packages.
from the useR!2021 talk about submitting packages to CRAN
About keeping packages on CRAN based on a previous blog post.

The slides are on the link on the top and here below as embedded:

Improving (analysis) process: developing packages

Thu, 11 Nov 2021 00:00:00 +0000

I was invited to give this talk shortly after my talk at useR!2021. I was very nervous because I would like to have such a community on Spain and work together with them.

I presented a about how R can be used on the public medical sector to enhance and improve analysis and their reproducibility.

Workshop: Creating packages

Wed, 20 Oct 2021 00:00:00 +0000

I was invited by Francis Mensha on R-devel slack to give this workshop on April 29th for the R User Group Ghana.

First time teaching R stats and remote I expected people to follow the workshop and run the code and then ask questions but I was asked to do it myself. Hope it was easy enough to follow.

Packages submission and reviews; how does it work?

Sat, 16 Oct 2021 00:00:00 +0000

The abstract I presented to be accepted was:

We benefit from others’ work on R and also by shared packages and for our programming tasks. Occasionally we might generate some piece of software that we want to share with the community. Usually sharing our work with the R community means submitting a package to an archive (CRAN, Bioconductor or others). While each individual archive has some rules they share some common principles.

If your package follows their rules about the submission process and has a good quality according to their rules it will be included. All submissions have some common sections: First, an initial screening; second, a more profound manual review of the code. Then, if the suggestions are applied or correctly replied then the package is included in the archive.

On each step some rules and criteria are used to decide if the package moves forward or not. Understanding what these rules say, common problems and comments from reviewers will help avoiding submitting a package to get it rejected. Reducing the friction between sharing our work, providing useful packages to the community and minimizing reviewers’ time and efforts.

Looking at the review process of three archives of R packages, CRAN, Bioconductor and rOpenSci, I’ll explain common rules, patterns, timelines and checks required to get the package included, as well as personal anecdotes with them. The talk is based on the post analyzing reviews available here: https://llrs.dev/tags/reviews/

I received excellent feedback from the reviewers and I got a full talk (I asked for a poster because I was nervous to present to a big audience).

This talk also received one of the Accessibility Awards.