Skip to content
A package to automate my R workflow.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

Travis build statusBuild status


The goal of aliviateR is to help automate the process of building packages. It also contains functions that I constantly need for work. Maybe some of it is useful for you.


aliviateR is currently only available as a development version from GitHub. You can download this version with:

# install.packages("devtools")

For any issues, please feel free to email me or submit and issue.


Currently, there are 6 functions available through aliviateR. Below I will define the functions.

The first function is very simple and just prints a generic roxygen header for a function and/or data.

aliviateR::printroxygenheader(func = TRUE,
                              data = FALSE)

By default it returns only a function header but you can choose to return both or just a data header by changing the logicals.

The next function is aliviateR::alval_flow(). This function will create the project directory for a package similar to File > New Project > R package. In addition to creating the package directory filled in the proper package form, it allows you to edit the description with your personal information, add a vignette, add testing options, and adds the readme files.

alval_flow(path = NULL, 
           pkg_name = NULL, 
           vignette_name = NULL,
           testing = TRUE, 
           data = TRUE
           title = "What the Package Does (One Line, Title Case)",
           description = "What the package does (one paragraph).",
           firstname = "Alessandra", 
           lastname = "Valcarcel",
           email = "", 
           role = c("aut", "cre"))

Feel free to change the firstname, lastname, and email fields and use on your own. Type ?aliviateR::alval_flow for documentation.

The next function aliviateR::alval_git initializes a GitHub repo for your package, adds, commits, and pushes the package contents to GitHub. This requires that GitHub is properly configured on your machine and with RStudio. For more information on configuration see RStudio Support, R packages by Hadley Wickham, and Blog.

At the minium you need your GitHub username and email set up as well as a token set up in your .Renviron. R also has to know where your ssh keys are. You can check if this is done already by running:


If these are properly set up then aliviateR::alval_git() should run.

alval_git(pkg_path = NULL, 
          credentials = NULL)

You’ll need to specify the path to your package. By default the credentials are NULL. This arguement is passed to devtools::usethis::use_git() so check our their documentation for more info though NULL should still run. I set it to something special credentials = alval for a specialized path to my credentials. The other option is to input your own if NULL doesn’t seem to work. After you run this, check that the package folder is set up as a repo on your GitHub.

The aliviateR::alval_badges() function adds continuous integration and coverage checks. Additionally, it returns the badges you can add to your readme.

alval_badges(pkg_path = NULL, 
             gh_username = NULL, 
             interactive = TRUE,
             travis = TRUE,
             coverage = TRUE, 
             appveyor = TRUE,
             cran = TRUE)

You’ll specify the path to your package and GitHub username. Running this will prompt many of the continous integration sites to open (if interactive = TRUE) and you can configure the setting options interactively. If you have already done this and just need the badges then set interactive = FALSE. You only need to to copy and paste the badges you specified into your readme.

The aliviateR::sort_filepaths() function is a little different than the previous functions. It doesn’t help with building packages but is useful in everday research. This function should be used when you would like to sort a data.frame or tibble of filepaths by an ID contained inside the filepath. The ID by default must larger than 3 numbers. If you want to provide a specific ID pattern use id_pattern. This is passed to stringr::str_extract so the pattern format should be accepted by that function. A tibble will be returned with an additional id column.

sort_filepaths(filepaths, id_pattern = "[0-9][0-9][0-9]+")

The aliviateR::multiple_filepaths() function similarly does not help with building packages. This function wraps list.files() for a set of paths and patterns provided and creates a tibble of each of the files.

                   pattern = NULL, 
                   full.names = TRUE, 
                   sort = TRUE,
                   id_pattern = "[0-9][0-9][0-9]+")

As I work in imaging data, I’ve included some functions to help calculate Sørensen–Dice index or coefficient. This is (\dfrac{2 \times | X \cap Y| }{|X| + |Y|}). aliviateR::dsc() will calculate the Sørensen–Dice index between two vectors or images. The input class must be the same so two vectors or two NIFTI objects. It doesn’t really matter what vector or image is gold_standard or comp_method as you can see from the formula we can denote the objects as (X) and (Y) but in practice normally one image is a gold standard and the other is to compare.


The object returned is a single value representing Sørensen’s–Dice index between the two objects.

I have also included a function, aliviateR::dsc_mult_thresholds(), that calculates Sørensen–Dice index or coefficient for a variety of thresholds input when provided a probability map. Again, gold_standard and prob_map can be vectors or NIFTI objects so long as they match. thresholds is a grid of thresholds you would like to threshold the probability map to obtain binary values. Notice, mask = NULL by default. A mask is required if you provide NIFTI objects but can remain NULL if the inputs are already vectorized.

                    mask = NULL)

This function returns a tibble with a column of the threshold of the thresholds input and a column dsc of the Sørensen–Dice value for that threshold.

Often, I am importing many .RData or .rda objects that are saved in a single folder. This is especially useful for when the .RData file is the same and you planning to bind them.


Simply provide the path to the folder that houses all of the saved objects and the pattern of the files you wish to import. If there is no pattern and you’d simply like to import everything set to NULL.

For a full example of my flow see the vignette for an example.

You can’t perform that action at this time.