Summary and timeline
In April 2020, R officially released version 4.0. One of the major changes was the removal of the default
stringsAsFactors = TRUE when reading in data frames. This was tentatively announced in late July 2019 and officially announced in February 2020. While this change has been seen as a good thing by the majority of the R community as a step towards reducing common pitfalls, it produces an interesting pedagogical challenge for some of our lessons that use errors and warnings generated from this default behavior as mechanisms to introduce learners to the concept of factors.
Our initial recommendation has been for instructors to continue teaching using R 3.6 (which can be installed via the Windows installer, or macOS installer), but this is only a short-term solution. This blog post serves as an outline for the long-term solution to this particular transition and a potential roadmap for R 5.0 (which may emerge in another 7 to 11 years). In the end, we recommend migrating all official Carpentries lessons to use R 4.0 by 30 November 2020. We believe that this gives sufficient time for Maintainers to implement and test solutions.
What will be affected?
All R-based lessons will be affected to some degree, but this is minimized if the example data is purely numeric (which is the case for the inflammation data set in Programming with R). When the example data contains textual elements, then it is important to check the prose and the output to make sure that everything works as expected. Most of the time, the code will run without errors, but will give results that are out of sync with the prose.
To help maintainers identify changes, we ran R-based lessons with both R 3.6.3 and R 4.0.0 using the rocker project geospatial docker container. The results are located here and are organized by lesson and episode for easier browsing.
we recommend migrating all official Carpentries lessons to use R 4.0 by 30 November 2020
Instructors: Managing Expectations
Instructors should prime the learners to expect some dissonance between what is presented in the materials and what the learner will see on their screen, and let them know if factors are a topic that will be discussed in the workshop. Be aware that there may be some heterogeneity in the installed versions of R for the course and plan accordingly. To maintain consistency through a lesson, the instructor should teach from a single version of R (whichever version will be consistent with the majority of learners in the workshop).
Maintainers: Lesson Content
Several lessons use the former (i.e. < 4.0) default setting of
stringsAsFactors = TRUE to introduce the learner to the concept of factors. Factors themselves are a bit of a weird concept in R, their importance dates back to when R users had to worry about the storage space of their computer. Given that today’s netbook has no problem working with character data, our lessons should provide more meaningful introductions to the usefulness of factors.
In previous versions of R, factors were often one of the first data structures people see when reading data into R. Thus, it made sense to teach these concepts to novice R users, which follows the concept of teaching immediately useful content first.
Now that characters are no longer converted to factors by default, for lessons that previously used the default parameters as an introduction, we can reinvigorate our lessons to provide more meaningful introductions to factors. Maintainers of the lessons will need to evaluate the underlying structure of the lessons to determine how to meaningfully introduce factors. Maintainers of lessons that are affected by this change in the default behavior might find motivations for the usefulness of factors in data wrangling and data visualization tasks. For example, when summarizing variables, the author may wish for a table of character data to have a specific ordering. Alternatively, when visualizing how a relationship changes over time, it may be inappropriate for time to be considered as continuous. Additionally, maintainers can reference the section on factors from the R for Social Science lesson, which was unaffected by the changes.
These recommendations came out of a collaborative effort between members of The Carpentries Maintainer community. Moving forward, the Maintainer community will review the landscape of the software used in our curriculum and strive to make the necessary adjustments to reduce the friction learners and Instructors experience in workshops soon after major software changes. Above all, we strive to adhere to our principles of people first and evidence-based learning.
Dialogue & Discussion
Comments must follow our Code of Conduct.