# Section - 7 Predictive Modeling

We finally have everything we need to start making predictive models now that the data has been cleaned and we have come up with a gameplan to understand the efficacy of the models.

## 7.1 Example Simple Model

We can start by making a simple **linear regression** model:

```
##
## Call:
## lm(formula = target_price_24h ~ ., data = cryptodata)
##
## Coefficients:
## (Intercept) symbolADA symbolAPPC symbolARDR
## 16290.06190856 0.36750828 4.50458629 0.34301779
## symbolAVA symbolBAL symbolBAT symbolBNT
## 0.37386362 -0.38449865 0.43709219 0.41536901
## symbolBRD symbolBSV symbolBTC symbolBTG
## -1.69187022 3.25967983 1165.48212589 1.35681419
## symbolBTRST symbolCELR symbolCHZ symbolCKB
## -0.64815101 0.34235833 0.34231275 0.10982620
## symbolCOCOS symbolCROOLD symbolCRPT symbolDASH
## 0.65972056 0.35611217 -0.58453473 1.92727018
## symbolDCR symbolDENT symbolDGB symbolDODO
## 3.20137115 0.33693636 1.19807062 0.83379879
## symbolELF symbolENJ symbolEOS symbolETC
## 0.14573414 0.40911244 0.40087101 -2.25042356
## symbolETH symbolETP symbolHT symbolICP
## 93.77415431 -1.10802258 0.64505234 0.97946085
## symbolINJ symbolJST symbolKMD symbolKNC
## -0.58378161 0.33876176 0.89617563 0.77534475
## symbolKRRX symbolLAZIO symbolLEO symbolLTC
## 9.08640856 12.31229414 0.59620576 3.23224403
## symbolMAID symbolMANA symbolNAV symbolNCT
## 2.91290127 0.44306163 0.34517807 0.34350864
## symbolNEAR symbolNEXO symbolONG symbolORN
## 0.88207427 0.39411918 0.35937823 1.76490279
## symbolRCN symbolSTORJ symbolSXP symbolTRX
## 0.33712326 -0.93412759 -0.69484298 0.33832827
## symbolTXA symbolVIB symbolVSYS symbolWAXP
## 0.42546378 2.92926370 0.41347646 0.47527619
## symbolXCH symbolXEM symbolXMR symbolZEC
## 2.36721152 0.33964839 5.53950429 4.39061609
## symbolZKS symbolZRX date_time_utc date
## 0.00476464 0.42562572 -0.00002155 0.99865037
## price_usd lagged_price_1h lagged_price_2h lagged_price_3h
## 1.02348375 -0.07753332 -0.06711031 0.01882973
## lagged_price_6h lagged_price_12h lagged_price_24h lagged_price_3d
## -0.06553538 -0.02793499 0.05140611 0.11041530
## trainingtest trainingtrain split
## 67.16193854 59.57526836 12.69980584
```

We defined the **formula** for the model as ** target_price_24h ~ .**, which means that we are want to make predictions for the

**target_price_24h**field, and use (

**) every other column found in the data (**

`~`

**). In other words, we specified a model that uses the**

`.`

**target_price_24h**field as the dependent variable, and all other columns (

**) as the independent variables. Meaning, we are looking to predict the**

`.`

**target_price_24h**, which is the only column that refers to the future, and use all the information available at the time the rest of the data was collected in order to infer statistical relationships that can help us forecast the future values of the

**target_price_24h**field when it is still unknown on new data that we want to make new predictions for.

In the example above we used the **cryptodata** object which contained all the non-nested data, and was a big oversimplification of the process we will actually use.

### 7.1.1 Using Functional Programming

From this point forward, we will deal with the new dataset **cryptodata_nested**, review the previous section where it was created if you missed it. Here is a preview of the data again:

```
## # A tibble: 305 x 5
## # Groups: symbol, split [305]
## symbol split train_data test_data holdout_data
## <chr> <dbl> <list> <list> <list>
## 1 BTC 1 <tibble [215 x 11]> <tibble [72 x 11]> <tibble [72 x 11]>
## 2 ETH 1 <tibble [215 x 11]> <tibble [72 x 11]> <tibble [72 x 11]>
## 3 EOS 1 <tibble [215 x 11]> <tibble [72 x 11]> <tibble [72 x 11]>
## 4 LTC 1 <tibble [215 x 11]> <tibble [72 x 11]> <tibble [72 x 11]>
## 5 BSV 1 <tibble [215 x 11]> <tibble [72 x 11]> <tibble [72 x 11]>
## 6 ADA 1 <tibble [215 x 11]> <tibble [72 x 11]> <tibble [72 x 11]>
## 7 ZEC 1 <tibble [215 x 11]> <tibble [72 x 11]> <tibble [72 x 11]>
## 8 HT 1 <tibble [215 x 11]> <tibble [72 x 11]> <tibble [72 x 11]>
## 9 TRX 1 <tibble [215 x 11]> <tibble [72 x 11]> <tibble [72 x 11]>
## 10 XMR 1 <tibble [214 x 11]> <tibble [72 x 11]> <tibble [74 x 11]>
## # ... with 295 more rows
```

Because we are now dealing with a **nested dataframe**, performing operations on the individual nested datasets is not as straightforward. We could extract the individual elements out of the data using **indexing**, for example we can return the first element of the column **train_data** by running this code:

```
## # A tibble: 215 x 11
## date_time_utc date price_usd target_price_24h lagged_price_1h
## <dttm> <date> <dbl> <dbl> <dbl>
## 1 2021-11-12 00:00:01 2021-11-12 64779. 64129. 65166.
## 2 2021-11-12 01:00:01 2021-11-12 64819. 64336. 64779.
## 3 2021-11-12 02:00:01 2021-11-12 65101. 63856. 64819.
## 4 2021-11-12 03:00:01 2021-11-12 65014. 63725. 65101.
## 5 2021-11-12 04:00:01 2021-11-12 64823. 63790. 65014.
## 6 2021-11-12 05:00:02 2021-11-12 64967. 63683. 64823.
## 7 2021-11-12 06:00:01 2021-11-12 64661. 63616. 64967.
## 8 2021-11-12 07:00:01 2021-11-12 64492. 63859. 64661.
## 9 2021-11-12 08:00:02 2021-11-12 64484. 64023. 64492.
## 10 2021-11-12 09:00:01 2021-11-12 64890. 63823. 64484.
## # ... with 205 more rows, and 6 more variables: lagged_price_2h <dbl>,
## # lagged_price_3h <dbl>, lagged_price_6h <dbl>, lagged_price_12h <dbl>,
## # lagged_price_24h <dbl>, lagged_price_3d <dbl>
```

remove STORJ to resolve weird problem that arose March 3rd, 2021:

As we already saw dataframes are really flexible as a data structure. We can create a new column in the data to store the models themselves that are associated with each row of the data. There are several ways that we could go about doing this (this tutorial itself was written to execute the same commands using three fundamentally different methodologies), but in this tutorial we will take a **functional programming** approach. This means we will focus the operations we will perform on the actions we want to take themselves, which can be contrasted to a **for loop** which emphasizes the objects more using a similar structure that we used in the example above showing the first element of the **train_data** column.

When using a **functional programming** approach, we first need to create functions for the operations we want to perform. Let’s wrap the **lm()** function we used as an example earlier and create a new custom function called **linear_model**, which takes a dataframe as an input (the **train_data** we will provide for each row of the nested dataset), and generates a linear regression model:

We can now use the **map()** function from the **purrr** package in conjunction with the **mutate()** function from **dplyr** to create a new column in the data which contains an individual linear regression model for each row of **train_data**:

```
## # A tibble: 305 x 6
## # Groups: symbol, split [305]
## symbol split train_data test_data holdout_data lm_model
## <chr> <dbl> <list> <list> <list> <list>
## 1 BTC 1 <tibble [215 x 11]> <tibble [72 x 11~ <tibble [72 x 11~ <lm>
## 2 ETH 1 <tibble [215 x 11]> <tibble [72 x 11~ <tibble [72 x 11~ <lm>
## 3 EOS 1 <tibble [215 x 11]> <tibble [72 x 11~ <tibble [72 x 11~ <lm>
## 4 LTC 1 <tibble [215 x 11]> <tibble [72 x 11~ <tibble [72 x 11~ <lm>
## 5 BSV 1 <tibble [215 x 11]> <tibble [72 x 11~ <tibble [72 x 11~ <lm>
## 6 ADA 1 <tibble [215 x 11]> <tibble [72 x 11~ <tibble [72 x 11~ <lm>
## 7 ZEC 1 <tibble [215 x 11]> <tibble [72 x 11~ <tibble [72 x 11~ <lm>
## 8 HT 1 <tibble [215 x 11]> <tibble [72 x 11~ <tibble [72 x 11~ <lm>
## 9 TRX 1 <tibble [215 x 11]> <tibble [72 x 11~ <tibble [72 x 11~ <lm>
## 10 XMR 1 <tibble [214 x 11]> <tibble [72 x 11~ <tibble [74 x 11~ <lm>
## # ... with 295 more rows
```

Awesome! Now we can use the same tools we learned in the high-level version to make a wider variety of predictive models to test

## 7.2 Caret

Refer back to the high-level version of the tutorial for an explanation of the caret package, or consult this document: https://topepo.github.io/caret/index.html

### 7.2.1 Parallel Processing

R is a ** single thredded** application, meaning it only uses one CPU at a time when performing operations. The step below is optional and uses the

**parallel**and

**doParallel**packages to allow R to use more than a single CPU when creating the predictive models, which will speed up the process considerably:

### 7.2.2 More Functional Programming

Now we can repeat the process we used earlier to create a column with the linear regression models to create **the exact same models**, but this time using the **caret** package.

```
linear_model_caret <- function(df){
train(target_price_24h ~ . -date_time_utc -date, data = df,
method = 'lm',
trControl=trainControl(method="none"))
}
```

*We specified the method as *

`lm`

for linear regression. See the high-level version for a refresher on how to use different methods to make different models: https://cryptocurrencyresearch.org/high-level/#/method-options. the trControl argument tells the caret package to avoid additional resampling of the data. As a default behavior caret will do re-sampling on the data and do hyperparameter tuning to select values to use for the paramters to get the best results, but we will avoid this discussion for this tutorial. See the official caret documentation for more details.Here is the full list of models that we can make using the **caret** package and the steps described the high-level version of the tutorial:

We can now use the new function we created **linear_model_caret** in conjunction with **map()** and **mutate()** to create a new column in the **cryptodata_nested** dataset called **lm_model** with the trained linear regression model for each split of the data (by cryptocurrency **symbol** and **split**):

We can see the new column called **lm_model** with the nested dataframe grouping variables:

```
## # A tibble: 305 x 3
## # Groups: symbol, split [305]
## symbol split lm_model
## <chr> <dbl> <list>
## 1 BTC 1 <train>
## 2 ETH 1 <train>
## 3 EOS 1 <train>
## 4 LTC 1 <train>
## 5 BSV 1 <train>
## 6 ADA 1 <train>
## 7 ZEC 1 <train>
## 8 HT 1 <train>
## 9 TRX 1 <train>
## 10 XMR 1 <train>
## # ... with 295 more rows
```

And we can view the summarized contents of the first trained model:

```
## Linear Regression
##
## 215 samples
## 10 predictor
##
## No pre-processing
## Resampling: None
```

### 7.2.3 Generalize the Function

We can adapt the function we built earlier for the linear regression models using caret, and add a parameter that allows us to specify the **method** we want to use (as in what predictive model):

### 7.2.4 XGBoost Models

Now we can do the same thing we did earlier for the linear regression models, but use the new function called **model_caret** using the **map2()** function to also specify the model as **xgbLinear** to create an **XGBoost** model:

```
cryptodata_nested <- mutate(cryptodata_nested,
xgb_model = map2(train_data, "xgbLinear", model_caret))
```

We won’t dive into the specifics of each individual model as the correct one to use may depend on a lot of factors and that is a discussion outside the scope of this tutorial. We chose to use the **XGBoost** model as an example because it has recently gained a lot of popularity as a very effective framework for a variety of problems, and is an essential model for any data scientist to have at their disposal.

There are several possible configurations for XGBoost models, you can find the official documentation here: https://xgboost.readthedocs.io/en/latest/parameter.html

### 7.2.5 Neural Network Models

We can keep adding models. As we saw, caret allows for the usage of over 200 predictive models. Let’s make another set of models, this time setting the **method** to to create

`dnn`

**deep neural networks**:

*Again, we will not dive into the specifics of the individual models, but a quick Google search will return a myriad of information on the subject.*

### 7.2.6 Random Forest Models

Next let’s use create Random Forest models using the **method** `ctree`

### 7.2.7 Principal Component Regression

For one last set of models, let’s make Principal Component Regression models using the **method** `pcr`

### 7.2.8 Caret Options

Caret offers some additional options to help pre-process the data as well. We outlined an example of this in the high-level version of the tutorial when showing how to make a **Support Vector Machine** model, which requires the data to be **centered** and **scaled** to avoid running into problems (which we won’t discuss further here).

## 7.3 Make Predictions

Awesome! We have trained the predictive models, and we want to start getting a better understanding of how accurate the models are on data they have never seen before. In order to make these comparisons, we will want to make predictions on the test and holdout datasets, and compare those predictions to what actually ended up happening.

In order to make predictions, we can use the **prediict()** function, here is an example on the first elements of the nested dataframe:

```
predict(object = cryptodata_nested$lm_model[[1]],
newdata = cryptodata_nested$test_data[[1]],
na.action = na.pass)
```

```
## 1 2 3 4 5 6 7 8
## 58298.42 58591.60 58424.94 58267.68 58604.39 58335.72 58560.29 58626.41
## 9 10 11 12 13 14 15 16
## 59272.99 58803.34 59195.98 59106.40 59437.32 59156.69 58691.08 58402.81
## 17 18 19 20 21 22 23 24
## 57834.25 57842.40 57256.40 56941.06 56658.23 57336.81 57282.99 57293.98
## 25 26 27 28 29 30 31 32
## 57413.18 57288.41 57705.88 57347.91 57595.44 59278.91 58280.41 58779.90
## 33 34 35 36 37 38 39 40
## 58350.32 58081.40 57065.93 56308.02 56378.62 56747.41 57130.48 56630.75
## 41 42 43 44 45 46 47 48
## 57304.37 57375.83 57414.39 57304.71 56993.55 57023.32 56878.01 56468.09
## 49 50 51 52 53 54 55 56
## 56819.28 56983.37 56659.06 56666.20 56847.71 57755.33 58331.98 57243.72
## 57 58 59 60 61 62 63 64
## 58138.96 57695.61 57771.21 57840.31 57546.66 57694.71 57603.56 57561.30
## 65 66 67 68 69 70 71 72
## 57508.86 56971.47 56143.36 56565.21 56508.55 56502.11 56487.14 56399.13
```

Now we can create a new custom function called **make_predictions** that wraps this functionality in a way that we can use with **map()** to iterate through all options of the nested dataframe:

```
make_predictions <- function(model, test){
predict(object = model, newdata = test, na.action = na.pass)
}
```

Now we can create the new columns **lm_test_predictions** and **lm_holdout_predictions** with the predictions:

```
cryptodata_nested <- mutate(cryptodata_nested,
lm_test_predictions = map2(lm_model,
test_data,
make_predictions),
lm_holdout_predictions = map2(lm_model,
holdout_data,
make_predictions))
```

The predictions were made using the models that had only seen the **training data**, and we can start assessing how good the model is on data it has not seen before in the **test** and **holdout** sets. Let’s view the results from the previous step:

```
## # A tibble: 305 x 4
## # Groups: symbol, split [305]
## symbol split lm_test_predictions lm_holdout_predictions
## <chr> <dbl> <list> <list>
## 1 BTC 1 <dbl [72]> <dbl [72]>
## 2 ETH 1 <dbl [72]> <dbl [72]>
## 3 EOS 1 <dbl [72]> <dbl [72]>
## 4 LTC 1 <dbl [72]> <dbl [72]>
## 5 BSV 1 <dbl [72]> <dbl [72]>
## 6 ADA 1 <dbl [72]> <dbl [72]>
## 7 ZEC 1 <dbl [72]> <dbl [72]>
## 8 HT 1 <dbl [72]> <dbl [72]>
## 9 TRX 1 <dbl [72]> <dbl [72]>
## 10 XMR 1 <dbl [72]> <dbl [74]>
## # ... with 295 more rows
```

Now we can do the same for the rest of the models:

```
cryptodata_nested <- mutate(cryptodata_nested,
# XGBoost:
xgb_test_predictions = map2(xgb_model,
test_data,
make_predictions),
# holdout
xgb_holdout_predictions = map2(xgb_model,
holdout_data,
make_predictions),
# Neural Network:
nnet_test_predictions = map2(nnet_model,
test_data,
make_predictions),
# holdout
nnet_holdout_predictions = map2(nnet_model,
holdout_data,
make_predictions),
# Random Forest:
rf_test_predictions = map2(rf_model,
test_data,
make_predictions),
# holdout
rf_holdout_predictions = map2(rf_model,
holdout_data,
make_predictions),
# PCR:
pcr_test_predictions = map2(pcr_model,
test_data,
make_predictions),
# holdout
pcr_holdout_predictions = map2(pcr_model,
holdout_data,
make_predictions))
```

We are done using the **caret** package and can stop the parallel processing cluster:

## 7.4 Timeseries

Because this tutorial is already very dense, we will just focus on the models we created above. When creating predictive models on timeseries data there are some other excellent options which consider when the information was collected in similar but more intricate ways to the way we did when creating the lagged variables.

For more information on using excellent tools for ARIMA and ETS models, consult the high-level version of this tutorial where they were discussed.

Move on to the next section ➡️ to assess the accuracy of the models as described in the previous section.