From 71cc5899a57852d85efe0dd42d9ea2ddac2a99ed Mon Sep 17 00:00:00 2001 From: "Jennifer (Jenny) Bryan" Date: Thu, 7 Jul 2016 23:13:09 -0700 Subject: [PATCH] Fix broken links --- iteration.Rmd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/iteration.Rmd b/iteration.Rmd index bc18257..9cf7e8e 100644 --- a/iteration.Rmd +++ b/iteration.Rmd @@ -654,7 +654,7 @@ y <- x %>% map(safely(log)) str(y) ``` -This would be easier to work with if we had two lists: one of all the errors and one of all the output. That's easy to get with `purrr::transpose()` (you'll learn more about `transpose()` in [transpose]) +This would be easier to work with if we had two lists: one of all the errors and one of all the output. That's easy to get with `purrr::transpose()` (you'll learn more about `transpose()` in [Switching levels in the hierarchy]) ```{r} y <- y %>% transpose() @@ -780,7 +780,7 @@ params ``` As soon as your code gets complicated, I think a data frame is a good approach because it ensures that each column has a name and is the same length as all the other columns. -We'll come back to this idea in [hierarchy], and again when we explore the intersection of dplyr, purrr, and model fitting. +We'll come back to this idea in [Handling hierarchy], and again when we explore the intersection of dplyr, purrr, and model fitting. ### Invoking different functions