Skip to content

Commit

Permalink
Merge pull request #1 from OxfordIHTM/dev
Browse files Browse the repository at this point in the history
update targets template
  • Loading branch information
ernestguevarra authored Mar 26, 2024
2 parents 50f7bdc + 84c2a9f commit 1c1d7db
Show file tree
Hide file tree
Showing 7 changed files with 176 additions and 11 deletions.
4 changes: 2 additions & 2 deletions .github/workflows/test-targets-workflow.yml
Original file line number Diff line number Diff line change
Expand Up @@ -12,11 +12,11 @@ on:
jobs:
test-targets-workflow:
runs-on: ubuntu-latest
container: rocker/tidyverse:4.3.1
container: rocker/tidyverse:4.3.3
env:
GIT_CRYPT_KEY64: ${{ secrets.GIT_CRYPT_KEY64 }}
steps:
- uses: actions/checkout@v3
- uses: actions/checkout@v4

- name: Install system dependencies
run: |
Expand Down
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -3,3 +3,4 @@
.RData
.Ruserdata
_targets
docs
34 changes: 34 additions & 0 deletions R/utils.R
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
#'
#' Collect all targets and lists of targets in the environment
#'
#'
all_targets <- function(env = parent.env(environment()),
type = "tar_target",
add_list_names = TRUE) {

## Function to determine if an object is a type (a target),
## or a list on only that type
rfn <- function(obj)
inherits(obj, type) || (is.list(obj) && all(vapply(obj, rfn, logical(1))))

## Get the names of everything in the environment
## (e.g. sourced in the _targets.R file)
objs <- ls(env)

out <- list()
for (o in objs) {
obj <- get(o, envir = env) ## Get each top-level object in turn
if (rfn(obj)) { ## For targets and lists of targets
out[[length(out) + 1]] <- obj ## Add them to the output

## If the object is a list of targets, add a vector of the target names
## to the environment So that one can call `tar_make(list_name)` to make
## all the targets in that list
if (add_list_names && is.list(obj)) {
target_names <- vapply(obj, \(x) x$settings$name, character(1))
assign(o, target_names, envir = env)
}
}
}
return(out)
}
54 changes: 54 additions & 0 deletions README.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -18,3 +18,57 @@ knitr::opts_chunk$set(

This repository is a template for a [`docker`](https://www.docker.com/get-started)-containerised, [`{targets}`](https://docs.ropensci.org/targets/)-based, [`{renv}`](https://rstudio.github.io/renv/articles/renv.html)-enabled [`R`](https://cran.r-project.org/) workflow for general data analysis.

## About the Project



## Repository Structure

The project repository is structured as follows:

```
sc-policy-review
|-- .github/
|-- workflows/
|-- data/
|-- data-raw/
|-- outputs/
|-- R/
|-- reports
|-- renv
|-- library/
|-- activate.R
|-- renv.lock
|-- .Rprofile
|-- packages.R
|-- _targets.R
```

* `.github` contains project testing and automated deployment of outputs workflows via continuous integration and continuous deployment (CI/CD) using Github Actions.

* `data/` contains intermediate and final data outputs produced by the workflow.

* `data-raw/` contains raw datasets, usually either downloaded from source or added manually, that are used in the project. This directory is empty given that the raw datasets used in this project are restricted and are only distributed to eligible members of the project. This directory is kept here to maintain reproducibility of project directory structure and ensure that the workflow runs as expected. Those who are collaborating on this project and who have permissions to use the raw datasets should include their copies of the raw dataset into this directory in their local versions of this repository.

* `outputs/` contains compiled reports and figures produced by the workflow.

* `R/` contains functions developed/created specifically for use in this workflow.

* `reports/` contains literate code for R Markdown reports rendered in the workflow.

* `renv/` contains `renv` package specific files and directories used by the package for maintaining R package dependencies within the project. The directory `renv/library`, is a library that contains all packages currently used by the project. This directory, and all files and sub-directories within it, are all generated and managed by the `renv` package. Users should not change/edit these manually.

* `renv.lock` file is the `renv` lockfile which records enough metadata about every package used in this project that it can be re-installed on a new machine. This file is generated by the `renv` package and should not be changed/edited manually.

* `.Rprofile` file is a project R profile generated when initiating `renv` for the first time. This file is run automatically every time R is run within this project, and `renv` uses it to configure the R session to use the `renv` project library.

* `packages.R` file lists out all R package dependencies required by the workflow.

* `_targets.R` file defines the steps in the workflow's data ingest, data processing, data analysis, and reporting pipeline.

## Reproducibility

### R package dependencies

This project was built using `R 4.3.3`. This project uses the `renv` framework to record R package dependencies and versions. Packages and versions used are recorded in `renv.lock` and code used to manage dependencies is in `renv/` and other files in the root project directory. On starting an R session in the working directory, run `renv::restore()` to install R package dependencies.

83 changes: 83 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,3 +11,86 @@ This repository is a template for a
[`{targets}`](https://docs.ropensci.org/targets/)-based,
[`{renv}`](https://rstudio.github.io/renv/articles/renv.html)-enabled
[`R`](https://cran.r-project.org/) workflow for general data analysis.

## About the Project

## Repository Structure

The project repository is structured as follows:

sc-policy-review
|-- .github/
|-- workflows/
|-- data/
|-- data-raw/
|-- outputs/
|-- R/
|-- reports
|-- renv
|-- library/
|-- activate.R
|-- renv.lock
|-- .Rprofile
|-- packages.R
|-- _targets.R

- `.github` contains project testing and automated deployment of outputs
workflows via continuous integration and continuous deployment (CI/CD)
using Github Actions.

- `data/` contains intermediate and final data outputs produced by the
workflow.

- `data-raw/` contains raw datasets, usually either downloaded from
source or added manually, that are used in the project. This directory
is empty given that the raw datasets used in this project are
restricted and are only distributed to eligible members of the
project. This directory is kept here to maintain reproducibility of
project directory structure and ensure that the workflow runs as
expected. Those who are collaborating on this project and who have
permissions to use the raw datasets should include their copies of the
raw dataset into this directory in their local versions of this
repository.

- `outputs/` contains compiled reports and figures produced by the
workflow.

- `R/` contains functions developed/created specifically for use in this
workflow.

- `reports/` contains literate code for R Markdown reports rendered in
the workflow.

- `renv/` contains `renv` package specific files and directories used by
the package for maintaining R package dependencies within the project.
The directory `renv/library`, is a library that contains all packages
currently used by the project. This directory, and all files and
sub-directories within it, are all generated and managed by the `renv`
package. Users should not change/edit these manually.

- `renv.lock` file is the `renv` lockfile which records enough metadata
about every package used in this project that it can be re-installed
on a new machine. This file is generated by the `renv` package and
should not be changed/edited manually.

- `.Rprofile` file is a project R profile generated when initiating
`renv` for the first time. This file is run automatically every time R
is run within this project, and `renv` uses it to configure the R
session to use the `renv` project library.

- `packages.R` file lists out all R package dependencies required by the
workflow.

- `_targets.R` file defines the steps in the workflow’s data ingest,
data processing, data analysis, and reporting pipeline.

## Reproducibility

### R package dependencies

This project was built using `R 4.3.3`. This project uses the `renv`
framework to record R package dependencies and versions. Packages and
versions used are recorded in `renv.lock` and code used to manage
dependencies is in `renv/` and other files in the root project
directory. On starting an R session in the working directory, run
`renv::restore()` to install R package dependencies.
11 changes: 2 additions & 9 deletions _targets.R
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
################################################################################
#
# Seychelles General Targets Workflow
# General Targets Workflow
#
################################################################################

Expand Down Expand Up @@ -47,11 +47,4 @@ deploy_targets <- tar_plan(


## List targets
list(
data_targets,
processing_targets,
analysis_targets,
output_targets,
report_targets,
deploy_targets
)
all_targets()
Empty file removed docs/.gitkeep
Empty file.

0 comments on commit 1c1d7db

Please sign in to comment.