---
title: "A discussion on branches in the multiverse"
author: "Abhraneel Sarma"
date: "`r Sys.Date()`"
output: 
  rmarkdown::html_vignette:
    toc: true
params:
  EVAL: !r identical(Sys.getenv("NOT_CRAN"), "true")
vignette: >
  %\VignetteEngine{knitr::rmarkdown}
  %\VignetteIndexEntry{A discussion on branches in the multiverse}
  %\usepackage[UTF-8]{inputenc}
---

```{r setup, message=FALSE, warning=FALSE}
library(knitr)
library(dplyr)
library(tidyr)
library(purrr)
library(ggplot2)
library(multiverse)
```

```{r, include=FALSE}
M = multiverse()
```


```{r, chunk-setup, include=FALSE}
opts_chunk$set(
  echo = TRUE,
  fig.width = 6, 
  fig.height = 4,
  eval = if (isTRUE(exists("params"))) params$EVAL else FALSE
)
```

## Branches in a multiverse analysis
In a multiverse analysis, researchers identify sets of defensible analysis choices (e.g., different ways of excluding outliers, different data transformations), implement them all, and then report the outcomes of all analyses resulting from all possible choice combinations. Thus, a multiverse analysis consists of different paths or **branches** of analysis for the same problem. 

For an example of how a branch might arise during analysis, let's say that you have a variable, $x$, which can assume any value between 1 and 60. You want to discretise this variable into two ordinal categories --- *high* (if x >= 30) and *low* (if x < 30). However, another researcher might argue for discretising this variable into three ordinal categories --- *high* (if x >= 40), *medium* (if 20 <= x < 40), and *low* (if x < 20).

An important aspect of this package is to make declaring such **branches** in the analysis more natural and convenient. Each **branch** is identified by a parameter, which can take two or more options. Thus, the different options are different branches within the multiverse. Below, we show how a user can specify these two alternative analysis paths using the `multiverse` library.

To do this, we first create a **multiverse object**, M:

```{r}
M = multiverse()
```

Let us then define the variable `x`:

```{r}
x = rnorm(100, 30, 10)
```

Then we can use the `branch()` function to specify the two alternatives as follows:

```{multiverse h-0, inside = M, echo = FALSE}
y = branch(discretisation, 
      "two_levels" ~ ifelse(x < 30, "low", "high"),
      "three_levels" ~ ifelse(x < 20, "low", ifelse(x > 40, "high", "medium"))
    )
```

````
```{multiverse default-m-0, inside = M}`r ''`
y = branch(discretisation, 
      "two_levels" ~ ifelse(x < 30, "low", "high"),
      "three_levels" ~ ifelse(x < 20, "low", ifelse(x > 40, "high", "medium"))
    )
```
````

Now, we can inspect the multiverse object to see if all the options were created. 

```{r}
expand(M)
```

Above, we see that the multiverse object contains two alternative analysis paths, one for each different option of discretisation.

### The syntax for declaring a `branch()`
The `branch()` function accepts three or more arguments---the first argument defines a *parameter* (here `discretisation`) which is used as an unique identifier for each decision point. The subsequent arguments, which we refer to as *options*, define the different choices that a researcher can make at that decision point of their analysis; these follow the syntax `<option_name> ~ <option_definition>`. The `<option_name>` part is intended to support meaningful naming of the branches to help the user keep track of choices. (in the multiverse specification below, "two_levels", and "three_levels" are used as option names). However, names can be omitted; if omitted, the entire syntax for performing that operation will be treated as the name for that particular option.

**Note**
In this vignette, we make use of [*multiverse code chunks*](https://mucollective.github.io/multiverse/articles/multiverse-in-rmd.html), a custom engine designed to work with the multiverse package, to implement the multiverse analyses. Please refer to the vignette (`vignette("multiverse-in-rmd")`) for more details. Users could instead make use of the \code{inside} function which is more suited for a script-style implementation. Please refer to the [README](https://mucollective.github.io/multiverse/index.html) or refer to `vignette("complete-multiverse-analysis")` for more details.


## Diving deeper: the multiverse compiler
In this section, we will go into a little detail on how the `branch()` function is used by `multiverse` to create two or more distinct end-to-end analysis paths from the user-specified syntax. You can skip to the next section if the specific implementation details of the `multiverse` library do not interest you. `Multiverse` captures the user's declared code as an unevaluated expression, which is an internal representation of an [abstract syntax tree](https://adv-r.hadley.nz/expressions.html) used by R for meta-programming purposes. This is why we need a dedicated multiverse code chunk or the `inside()` function, as such boilerplate allows us to prevent the code from being executed by R directly. The multiverse compiler transforms these unevaluated expressions into multiple unique R expressions, one for every possible analysis path in the multiverse. This is done in two steps.

First, `multiverse` enumerates all possible valid *parameter assignments*. A *parameter assignment* consists of a single assignment of an *option* to each *parameter*. Valid parameter assignments are those that satisfy all procedural dependencies (e.g., `%when%` clauses). Each parameter assignment corresponds to a single possible analysis path through the multiverse, in other words a single `universe.`

Second, multiverse takes each *universe* and uses its *parameter assignment* to recursively rewrite the unevaluated multiverse code expression into code specifically for that universe. It does this by replacing each `branch()` subexpression with the subexpression corresponding to the parameter assignment for that branch. 

We use a tree structure to store the output of the multiverse compiler, with each level in the tree corresponding to a single *unit* of the multiverse. If the analyst is using multiverse code chunks, each *unit* is a single code chunk; if the user is using `inside()`, each *unit* is one call to `inside()`. When the user declares their first *unit* with one or more *parameters*, we enumerate all combinations of the *options* which form the children of a singular root node, and then prune paths which are incompatible with declared *procedural dependencies*. At each subsequent level, we again enumerate all newly declared combinations of the  *options*, which are then added to each existing node from the previous level as children, followed by pruning any inconsistent analysis paths. Thus, if we declare a multiverse with $m parameters$, 1 parameter per unit on average, and $n options$ per *parameter* on average, we have a multiverse with $mn$ distinct analyses and a tree with approximately $\frac{m^(n+1) - m}{m-1}$ nodes.

Each node in the tree contains: (1) a *parameter assignment*---a dictionary mapping each *parameter* onto its assigned *option* for analysis paths passing through that node; (2) the unevaluated R expression for the current *unit* that is created using the *parameter assignment* for that node; (3) a unique R environment, which is a child environment of the parent node’s environment.

In R, environments are mutable dictionaries that encapsulate variable state and power scoping in the language (see https://adv-r.hadley.nz/environments.html); all code in R is executed inside an environment that determines the variables defined for that code and the values assigned to those variables. Moreover, every environment has a parent environment, and variable bindings in the parent environment are accessible via its child environments. We execute each node in its own environment. Because we share parent environments for nodes at the same level of the tree, two nodes which are children of the same parent node will automatically have results of the parent node’s computation available in their execution environment, avoiding redundant computation. Consequently, we reduce the execution time from the naive approach of executing all analysis paths *separately* ($O(nm^n)$) to executing just the code at each node in the tree: $O(\frac{m^(n+1) - m}{m - 1})$

## Going back to branches

A **branch** may be defined for:

- **Data substitution parameters** which offer to switch between different raw datasets, either collected or simulated.

- **Data processing parameters** which offer to process the same raw data in different ways before it is analyzed.

- **Modeling parameters** offer different ways of analyzing the same processed data

- **Presentation parameters** offer different ways of presenting analysis outcomes

In the rest of this document we describe different ways of declaring a **branch**, using different syntactical styles that are popular with R users, including base R syntax and tidyverse syntax.

## Example 1: A branch within functions in a "pipe": `|>`

Let's say that we have some data which indicates the amount of time spent by a user in four different conditions which are indexed 1, 2, 3 and 4 (the `modality` column in the following dataset). We will first load the data and convert the column into factor from integer.

```{r}
data("userlogs")
data.userlogs.raw = userlogs |>
  mutate( modality = factor(modality) ) |>
  arrange( modality )
```

We then create the multiverse object for this analysis

```{r}
M = multiverse()
```

The data variable `duration` is approximately normally distributed, however, as is common with such data it has a long right-tail. Before using a regression model, we can choose to either log-transform the data, or assume that it is normally distribution and analyse it. We can perform both analysis in our multiverse by declaring two branches --- one where the variable is log-transformed and the other where it is not.

```{multiverse h-1, inside = M, echo = FALSE}
df <- data.userlogs.raw |>
    select(modality, duration) |>
    mutate( duration = branch( data_transform, 
        "none" ~ duration,
        "log" ~ log(duration)
    ))
```

````
```{multiverse default-m-1, inside = M}`r ''`
df <- data.userlogs.raw |>
    select(modality, duration) |>
    mutate( duration = branch( data_transform, 
        "none" ~ duration,
        "log" ~ log(duration)
    ))
```
````

The `expand` shows that there are two rows for the `data transform` branch which correspond to the two different reasonable alternatives for transforming time spent data.

```{r}
expand(M)
```

If we look at the code column, which is a list of expressions, we see that the variable `duration` is defined in two separate ways, one for each row of the multiverse table. In other words, for each alternate analysis path, one of these would get executed and that would be the how the `duration` variable is transformed for that analysis path.

```{r}
expand(M)$.code
```

## Example 2: Another branch within a function

```{r}
M = multiverse()
```

Recall the hurricane example from the [README](https://mucollective.github.io/multiverse/). In that example, the researchers are faced with the decision of which hurricanes to exclude as outliers. They decide to exclude the two hurricanes which have caused the most deaths. However, there may be other possible ways of removing outliers based on extreme number of deaths:

-   No exclusion
-   Remove one most extreme hurricane
-   Remove two most extreme hurricanes

this decision node in a multiverse analysis can thus be declared as:

```{multiverse h-2, inside = M, echo = FALSE}
# here we just create the variable `df` in the multiverse
data("hurricane")

hurricane_data = hurricane |>
  # rename some variables
  rename(
      year = Year,
      name = Name,
      dam = NDAM,
      death = alldeaths,
      female = Gender_MF,
      masfem = MasFem,
      category = Category,
      pressure = Minpressure_Updated_2014,
      wind = HighestWindSpeed
  )

# here, we perform a `filter` operation in the multiverse
df.filtered = hurricane_data |>
  filter(branch(death_outliers,
      "no_exclusion" ~ TRUE,
      "most_extreme" ~ name != "Katrina",
      "two_most_extreme" ~ !(name %in% c("Katrina", "Audrey"))
))
```

````
```{multiverse default-m-2, inside = M}`r ''`
# here we just create the variable `df` in the multiverse
df = data("hurricane")

hurricane_data = hurricane |>
    # rename some variables
    rename(
        year = Year,
        name = Name,
        dam = NDAM,
        death = alldeaths,
        female = Gender_MF,
        masfem = MasFem,
        category = Category,
        pressure = Minpressure_Updated_2014,
        wind = HighestWindSpeed
    )

# here, we perform a `filter` operation in the multiverse
df.filtered = hurricane |>
  filter(branch(death_outliers,
      "no_exclusion" ~ TRUE,
      "most_extreme" ~ name != "Katrina",
      "two_most_extreme" ~ !(name %in% c("Katrina", "Audrey"))
))
```
````

We can inspect the multiverse object to see our declared analysis paths:

```{r}
expand(M)
```

## Example 3: Beware of the flexibility
`multiverse` provides a lot of flexibility in how you can use `branch()` to replace sub-expressions in R with multiple alternative subexpressions. For instance, the previous example could have been re-written as:

```{multiverse h-3, inside = M, echo = FALSE}
# here, we perform a `filter` operation in the multiverse
df.filtered = hurricane_data |>
  branch(death_outliers,
      "no_exclusion" ~ filter(TRUE),
      "most_extreme" ~ filter(name != "Katrina"),
      "two_most_extreme" ~ filter(!(name %in% c("Katrina", "Audrey")))
  )
```

````
```{multiverse default-m-3, inside = M}`r ''`
# here, we perform a `filter` operation in the multiverse
df.filtered = hurricane_data |>
  branch(death_outliers,
      "no_exclusion" ~ filter(TRUE),
      "most_extreme" ~ filter(name != "Katrina"),
      "two_most_extreme" ~ filter(!(name %in% c("Katrina", "Audrey")))
  )
```
````


However, we cannot chain additional pipes after the `filter()`, within the `branch()` statement. In other words, attempting to do something like this would result in an error:

````
```{multiverse default-m-4, inside = M}`r ''`
# do not do this
df.filtered = hurricane_data |>
  branch(death_outliers,
      "no_exclusion" ~ filter(TRUE) |> mutate(deaths = log(deaths + 1)),
      "most_extreme" ~ filter(name != "Katrina") |> mutate(deaths = log(deaths + 1)),
      "two_most_extreme" ~ filter(!(name %in% c("Katrina", "Audrey"))) |> mutate(deaths = log(deaths + 1))
  )
```
````

This is because, due to the presence of the pipe (`|>`) within the `branch` statement, we are not able to process the option expressions. Workarounds to this problem include declaring additional pipes outside branch (if these are invariant), or declaring it by reusing the same parameter (if they vary based on the options).

## Example 4: Variable assignment inside a branch statement

```{r}
M = multiverse()
```

There may be scenarios where you want to assign a value to a variable in a branch statement. The simplest example for this would be:

````
```{multiverse default-m-5, inside = M}`r ''`
# do not do this
branch(variable_declaration,
  "first_option" ~ x = 1,
  "second_option" ~ x = 2
)
```
````

Again, this is something which will result in an error because we are not able to parse the expression for each
option. The solution is to enclose the declaration within curly braces: `{` and `}` as shown below:


```{multiverse default-h-6, inside = M}
# do not do this
branch(variable_declaration,
  "first_option" ~ { x = 1 },
  "second_option" ~ { x = 2 }
)
```


````
```{multiverse default-m-6, inside = M}`r ''`
# do not do this
branch(variable_declaration,
  "first_option" ~ { x = 1 },
  "second_option" ~ { x = 2 }
)
```
````



## Example 5: A branch as a function

```{r}
M = multiverse()
```

Say we are not familiar with R's tidyverse packages and it's style of writing code. An alternate way of declaring a branch for transforming the `duration` variable in the analysis would be to use two separate functions for the transformation depending on which universe one is.

```{multiverse h-7, inside = M, echo = FALSE}
duration = branch(data_trans,
        "log-transformed" ~ log,
        "un-transformed" ~ identity
    )(data.userlogs.raw$duration)
```


````
```{multiverse default-m-7, inside = M}`r ''`
duration <- branch(data_trans,
        "log-transformed" ~ log,
        "un-transformed" ~ identity
    )(data.userlogs.raw$duration)
```
````

Then we execute the multiverse and inspect the results:

```{r}
execute_multiverse(M)

expand(M) |>
  mutate(transformed_duration = map(.results, "duration"))
```

As you can see, this creates, in each universe within the multiverse, a vector named `duration` which is either un-transformed or log-transformed. However, this suffers from being slightly unintuitive as it is harder to read or write the code. What is actually happening here is that the entire `branch(...)` gets replaced with either `log()` or `identity()` within a given universe.

A more readable pattern might be:

```{r}
M = multiverse()
```

```{multiverse h-8, inside = M, echo = FALSE}
duration_transform = branch(data_trans,
    "log-transformed" ~ log,
    "un-transformed" ~ identity
  )

duration = duration_transform(data.userlogs.raw$duration)
```

````
```{multiverse default-m-8, inside = M}`r ''`
duration_transform = branch(data_trans,
    "log-transformed" ~ log,
    "un-transformed" ~ identity
  )

duration = duration_transform(data.userlogs.raw$duration)
```
````

Next, we execute and inspect the results. Again, this alternate calculation also leads to the same result.

```{r}
execute_multiverse(M)

expand(M) |>
  mutate( transformed_duration = map(.results, "duration" ) ) |> 
  unnest(c(transformed_duration)) |>
  head()
```

## Example 6: Defining parameters separately

In this example, we show an alternative for how parameters can be declared. Here, we explore whether different ways of data transformation calculating confidence intervals impact the results. We consider two ways of calculating confidence intervals: the t-test and Bootstrapped CIs.

```{r}
library(boot)
library(broom)
samplemean <- function(x, d) {return(mean(x[d]))}

M = multiverse()

t_test_ci <- function(x, y) {
    broom::tidy(t.test(x, conf.level = y))
}

bootstrapped_ci <- function(x, y) {
    boot(data = x, statistic = samplemean, R = 5000) |>
        broom::tidy( conf.int = TRUE, conf.method = "bca", conf.level =  y) |>
        rename(estimate = statistic)
}
```

Instead of defining parameters locally in the code, where we want the code to differ, we can also just define it upfront by assigning it to a variable and use the variable in your code. For example, in the next example, we declare *two different branches* for data transformation, data modeling and data presentation respectively. We also define any necessary functions along the way.

```{multiverse h-9, inside = M, echo = FALSE}
data_trans <- branch(data_trans,
    "log-transformed" ~ log,
    "un-transformed" ~ identity
  )

fit <- branch(bootstrap,
      "t-dist" ~ t_test_ci,
      "bca" ~ bootstrapped_ci
    )

ci <- 0.95

df <- data.userlogs.raw  |>
    mutate( duration = data_trans(duration) ) |> 
    mutate( modality.f = factor(modality) ) |>
    group_by(subject, modality.f, modalityname) |> 
    summarise( duration = mean(duration), .groups = "drop" ) |>
    group_by(modality.f) |>
    rename( value = duration ) |>
    summarise( data = list(value), .groups = "keep" )

df <- df |>
    mutate( fit = map(data, ~ fit(.x, ci) ) ) |>
    select(-data) |>
    unnest( cols = c(fit) )
```


````
```{multiverse default-m-9, inside = M}`r ''`
data_trans <- branch(data_trans,
    "log-transformed" ~ log,
    "un-transformed" ~ identity
  )

fit <- branch(bootstrap,
      "t-dist" ~ t_test_ci,
      "bca" ~ bootstrapped_ci
    )

ci <- 0.95

df <- data.userlogs.raw  |>
  mutate( duration = data_trans(duration) ) |> 
  mutate( modality.f = factor(modality) ) |>
  group_by(subject, modality.f, modalityname) |> 
  summarise( duration = mean(duration), .groups = "drop" ) |>
  group_by(modality.f) |>
  rename( value = duration ) |>
  summarise( data = list(value), .groups = "keep" )

df <- df |>
  mutate( fit = map(data, ~ fit(.x, ci) ) ) |>
  select(-data) |>
  unnest( cols = c(fit) )
```
````

We then write the analysis and use those variables to indicate branches in our analysis within the multiverse.

```{r}
execute_multiverse(M)
```

To see the results of using branches, we plot a part of this multiverse. We see the different transformations (no transformations in the right column and log-transform in the left column). Each row shows the different data presentation branches by presenting different confidence levels.

```{r, fig.width = 8, fig.height = 4}
expand(M) |>
  mutate(df = map(.results, "df" ) ) |>
  unnest( cols = c(df) )  |>
  mutate( modality.f = recode( modality.f, 
                 "1" = "physical-touch",
                 "2" = "no-touch",
                 "3" = "virtual-prop",
                 "4" = "virtual-mouse"
  ) ) |>
  mutate( 
    estimate = ifelse(data_trans == "log", exp(estimate), estimate),
    conf.low = ifelse(data_trans == "log", exp(conf.low), conf.low),
    conf.high = ifelse(data_trans == "log", exp(conf.high), conf.high)
  ) |>
  arrange(desc(data_trans), desc(bootstrap)) |>
  filter( bootstrap == "bca" ) |>
  ggplot() + 
  geom_point( aes(x = estimate, y = modality.f)) +
  geom_errorbarh( aes(xmin = conf.low, xmax = conf.high, y = modality.f), height = 0) +
  facet_grid(. ~ data_trans, scales = "free") +
  theme_minimal()
```


## Example 7: Parameters can be re-used (and alternate ways of declaring the same branch)

Consider the modeling step from `vignette(hurricane)`. Here, one of the decisions that we face is the choice of regression model to use (gaussian or poisson). As described in the document, this requires two different local changes in the code: 

- the definition of the dependent variable in the model formula
- the family argument in the modeling function

However, these are *not* two separate decisions, but rather a consequence of the same analysis parameter: the choice of model. Often, a single analysis parameter will require the analyst to change the code in more than one location. To represent these semantics, multiverse allows us to re-use the same analysis parameter in multiple `branch()` statements, so long as each `branch()` uses the exact same set of analysis options. In a branch on a previously defined parameter, option names must be the same, but the code for each option can be different. Thus, we represent the consequences of the choice of model with a single analysis parameter: model. We insert two `branch()` statements using this parameter, one to set the variable transformation and one to set the family.

This may be implemented as such:

```{r}
M.1 = multiverse()
```


````
```{multiverse label = variable_definitions, inside = M.1}`r ''`
fit <- glm(branch(model,
        "linear" ~ log(death+1),
        "poisson" ~ death
    ) ~ femininity * damage + femininity * zpressure,
    family = branch(model, 
        "linear" ~ gaussian, 
        "poisson" ~ poisson
    ), data = df.filtered)
```
````


```{r}
M.2 = multiverse()
```

However, we can also write this as such:

````
```{multiverse label = variable_definitions, inside = M.2}`r ''`
fit <- branch(model
        "linear" ~ glm(log(death+1) ~ femininity * damage + femininity * zpressure, family = gaussian(), data = df),
        "poisson" ~ glm(death ~ femininity * damage + femininity * zpressure, family = poisson(), data = df)
    )
```
````

This is a more verbose way of specifying the same decision and requires the user to repeat code which may *potentially* introduce errors, but it might be easier to read.

## Example 6: Declaring continuous variables in `branch`
So far we have only looked at examples where we declare parameters within a branch which takes discrete values. In most cases, it makes sense to declare them separately and if the number of values for a discrete variable is not too high, sufficiently easy and concise to declare them in this manner. However, this does not apply to continuous variables as declaring all possible values would be painstakingly difficult. Hence we provide a alternate way of declaring branches where the parameter takes a continuous sequence of values.

```{r}
M = multiverse()
```


```{multiverse h-10, inside = M, echo = FALSE}
set.seed(branch(seed, .options = 1:25))

x1 <- rnorm(25)
x2 <- rnorm(25)
y <- x1 + x2 + runif(25)

m <- lm(y ~ x1+ x2)

intervals <- broom::tidy(m, conf.int = TRUE)
```



````
```{multiverse default-m-10, inside = M}`r ''`
set.seed(branch(seed, .options = 1:25))

x1 <- rnorm(25)
x2 <- rnorm(25)
y <- x1 + x2 + runif(25)

m <- lm(y ~ x1+ x2)

intervals <- broom::tidy(m, conf.int = TRUE)
```
````


```{r}
execute_multiverse(M)
```


We then plot the estimates from the multiverse to see if we obtain the correct results:

```{r, fig.width = 8, fig.height = 5}
expand(M) |>
  mutate(df = map(.results, "intervals" ) ) |>
  unnest( cols = c(df) ) |>
  unnest(seed) |>  # won't be necessary once issue #34 is fixed
  ggplot(aes(x = .universe, y = estimate, ymin = conf.low, ymax = conf.high), alpha = 0.5) +
  geom_pointrange() +
  facet_grid( . ~ term )  +
  scale_x_continuous( breaks = seq(0, 25, by = 5) ) +
  labs(x = "Universe (i.e. the seed parameter)", y = "Model Parameter Values", title = "Estimates with 95% confidence intervals") +
  theme_minimal()
```

**Note**: in this vignette we used the script-oriented `inside()` function for implementing the multiverse. However, we can implement the exact same multiverse in RMarkdown using the `multiverse-code-block` for more interactive programming. To implement this using a `multiverse-code-block`, we can simply place the code passed into the inside function (the second argument) inside a code block of type `multiverse`, provide it with the appropriate labels and multiverse object, and execute it. See \link(multiverse-in-rmd) and \link(branch) for more details and examples.


