Supplemental functions and data for OpenIntro resources, which includes open-source textbooks and resources for introductory statistics at openintro.org. The package contains data sets used in our open-source textbooks along with custom plotting functions for reproducing book figures. The package also contains the datasets used in OpenIntro labs. Note that many functions and examples include color transparency; some plotting elements may not show up properly (or at all) when run in some versions of Windows operating system.
You can install the released version of openintro from CRAN with:
You can install the development version of openintro from GitHub with:
This package was produced as part of the OpenIntro project. For the accompanying textbook, visit openintro.org. A PDF of the textbook is free and paperbacks can be purchased online (royalty-free).
Questions, bugs, feature requests
You can file an issue to get help, report a bug, or make a feature request.
When filing an issue to get help or report a bug, please make a minimal reproducible example using the reprex package. If you haven’t heard of or used reprex before, you’re in for a treat! Seriously, reprex will make all of your R-question-asking endeavors easier (which is a pretty insane ROI for the five to ten minutes it’ll take you to learn what it’s all about). For additional reprex pointers, check out the Get help! section of the tidyverse site.
Before opening a new issue, be sure to search issues and pull requests to make sure the bug hasn’t been reported and/or already fixed in the development version. By default, the search will be pre-populated with
is:issue is:open. You can edit the qualifiers (e.g.
is:closed) as needed. For example, you’d simply remove
is:open to search all issues in the repo, open or closed.
Process for adding new data to the package
The following steps use the devtools and usethis packages for various steps. We recommend using this process when suggesting new datasets to be added to the package. If the dataset is large (>500MB) or you’d like to add a function, please open an issue first for discussion before making the pull request.
- Fork and clone the repo with
- Note: If you have write access to the repo, you can skip this step.
- Start a new pull request with
BRANCH-NAMEis an informative branch name.
- If adding a file that is not an .rda file to begin with (Excel, csv, etc.), create a folder in the
data-rawfolder with the name of the dataset (how you’d like it to show up in the package). Please use
snake_casefor naming, e.g.
- Place your dataset in its raw form in the folder.
- Also in the
data-rawfolder, create a new R script called
name_of_dataset-dataprep.Rand write the code needed to read in the file, make any modifications to the data that are needed (if any), and end with
usethis::use_data()to save the data in the package as an .rda file with the ideal compression. See examples from other folders in
data-rawfor sample code. The contents of this folder do not end up in the package (the entire folder is ignored in the
.Rbuildignore) so you don’t need to worry about adding package dependencies etc.
- In the
Rfolder, create an R script called
data-name_of_datasetand add documentation using Roxygen style. See other documentation files for help with style. In the examples, use tidyverse syntax but do not use
library(tidyverse)and only use the relevant packages, e.g.
- Restart R and run
devtools::load_all()to make sure the data loads and run your examples to confirm they all work.
devtools::document(), restart R, and then
devtools::load_all(). Then, check out
?name_of_datasetto make sure the documentation looks as expected.
devtools::check(). The only NOTE you should see as a result of the check should be about the package size. If any other ERRORs, NOTEs, or WARNINGs are generated, resolve them or open an issue for help.
- In the
pkgdown.ymlfile, add the name of the dataset under
reference, in the correct alphabetical order.
- Add a note in the
NEWS.mdwith the new dataset you’ve added with a link to your GitHub username so we can acknowledge your contribution, e.g. “added by @mine-cetinkaya-rundel”.
Code of Conduct
Please note that the openintro project is released with a Contributor Code of Conduct. By contributing to this project, you agree to abide by its terms.