## 
## Attaching package: 'dplyr'
## The following objects are masked from 'package:stats':
## 
##     filter, lag
## The following objects are masked from 'package:base':
## 
##     intersect, setdiff, setequal, union

Introduction

The CPOP package provides functions to perform Cross-Platform Omics Prediction method described in our paper. The aim is to construct a transferable risk prediction mode with a strong emphasis on addressing practical challenges in the implementation of biomarkers/assays.

Below is a schematic drawing of the CPOP procedure:

  1. Identify a collection of datasets with similar clinical outcomes that can be used for joint modelling.

  2. Following that, CPOP creates features that are the ratio of each gene’s expression to that of other genes.

  3. Features that are predictive of the clinical outcome are then selected using a regularised regression modelling framework. These features forms a candidate set of features for further selection.

  4. The candidate features in Step 3 are reduced to only those features with consistent effect sizes across multiple datasets.

  5. The final selected features serve as the markers used for final model construction. Visualisation methods are provided.

Running CPOP

Step 1 and 2 - data selection and pre-processing

The CPOP package provides an example data, cpop_data_binary, to demonstrate how the various functions can be run.

cpop_data_binary contains a list of 7 objects:

  • x1, x2, and x3 which are simulated gene expression data.
  • y1, y2, and y3 which are simulated binary response corresponding to the x’s.
  • beta which is the true coefficients of interest.

After attaching these objects, we can perform the feature constructions on the matrices x1, x2, and x3.One of the main idea behind CPOP is that, the gene expression data scale (x1, x2, and x3) can vary greatly between data platforms. But the relative expression between the genes (e.g. difference between gene A and gene B) are more stable. In CPOP, the pairwise_col_diff function computes all pairwise differences between the columns in a given matrix, with the new output being a matrix with the columns geneA--geneB. Assuming these matrices has already been logged, then the difference geneA--geneB is the same as log(A/B) in the unlogged scale.

Note: the phrase “log-ratio” is used in context where the expression values of biomarkers exhibit differences across several orders of magnitudes. This is the most common in the context of gene expression data with microarray (intensity measurements) and RNA-Sequencing (counts) data. pairwise_col_diff assumes that these values with large magnitude of difference has been dealt with, e.g. through the use of logarithm transformations, and thus, the act of taking difference between columns of a data matrix is similar to how one would construct a ratio (i.e. log(A/B) = log(A) - log(B)). Thus, even though we refer to these values as log-ratios, the actual data matrices that we are operating on are assuming that the columns are already on a transformed scale, such that the difference between feature values is meaningful.

data(cpop_data_binary, package = 'CPOP')

names(cpop_data_binary)
## [1] "x1"   "x2"   "x3"   "y1"   "y2"   "y3"   "beta"
x1 = cpop_data_binary$x1
x2 = cpop_data_binary$x2
x3 = cpop_data_binary$x3
y1 = cpop_data_binary$y1
y2 = cpop_data_binary$y2
y3 = cpop_data_binary$y3

boxplot(cbind(x1,x2))

Step 3 and 4: feature selection

The cpop_model function is the main function of the CPOP package. The first four inputs are x1, x2, y1 and y2, where (x1, y1) and (x2, y2) are the log-ratio matrix and the response variable of the first and second data, respectively. In this particular example, the response variable is binary, hence, we can also specify family = "binomial" (default) for this model. (Note: prior to version 0.1.0 of CPOP,z1 and z2 were the main data input of the cpop_model but have now been deprecated. This is an equivalent way of supporting the CPOP method, however, it would require the users to manually calculate these ratio matrice using pairwise_col_diff.)

The alpha parameter is one of the penalty terms of the classic Elastic Net model, where alpha = 1 corresponds to a Lasso model and alpha = 0 corresponds to a Ridge model. The cpop_model uses glmnet::cv.glmnet in the backend, and so the penalty term lambda is automatically chosen using the default of lambda.min.

The CPOP model iteratively selects features based on the fit of the model or, if it reaches a pre-determined number of features with the paramter n_features being the main control for this. Here, we arbitary set this to a small number of 10 for illustration.

cpop_result = cpop_model(
  x1 = x1, x2 = x2, 
  y1 = y1, y2 = y2, 
  family = "binomial",
  alpha = 1, 
  n_features = 10)
## Absolute colMeans difference will be used as the weights for CPOP
## Fitting CPOP model using alpha = 1
## Based on previous alpha, 0 features are kept
## CPOP1 - Step 01: Number of selected features: 0 out of 190
## CPOP1 - Step 02: Number of selected features: 8 out of 190
## CPOP1 - Step 03: Number of selected features: 15 out of 190
## 10 features was reached.
## A total of 15 features were selected.
## Removing sources of collinearity gives 12 features.
## 10 features was reached.
## A total of 12 features were selected.
## CPOP2 - Sign: Step 01: Number of leftover features: 12 out of 12
## The sign matrix between the two data:
##     
##      -1 0 1
##   -1  0 0 0
##   0   0 0 0
##   1   0 0 0

Step 5: visualisation

The output of the cpop_model function is a cpop object with its own defined methods.

The main method for a cpop object is the plot_cpop function, which produces several useful plot to understand what the CPOP methodology has done or performed.

class(cpop_result)
## [1] "cpop"

The first plot is using the type = "text" option. A labelled scatter plot shows the estimated coefficients of the selected features from data1 (i.e. (x1, y1), x-axis) vs the same coefficients from data2 (i.e. (x2, y2), y-axis).

plot_cpop(cpop_result = cpop_result, type = "text")
## $plot

## 
## $data
## # A tibble: 12 × 3
##    coef_name   coef1   coef2
##    <fct>       <dbl>   <dbl>
##  1 X01--X10  -0.310  -0.285 
##  2 X05--X06  -0.0417 -0.141 
##  3 X09--X17   0.780   0.434 
##  4 X12--X20   0.388   0.130 
##  5 X13--X14   0.0681  0.0638
##  6 X16--X19  -0.0532 -0.137 
##  7 X01--X07  -0.445  -0.385 
##  8 X01--X15  -0.136  -0.309 
##  9 X01--X17  -0.928  -0.546 
## 10 X04--X12   0.328   0.357 
## 11 X05--X09   0.183  -0.0478
## 12 X08--X19   0.0379  0.115

We can see that most of the selected features had similar coefficients across the two data. This is exactly what CPOP is aiming to achieve: selecting features that are consistent within each datasets.

However, each of the feature (e.g. X01--X10) actually corresponds to two of the original features in the raw data X01 and X10 in the data x1 and x2. We can further visualise these features in the original features.

plot_cpop(cpop_result = cpop_result, type = "ggraph")
## $plot

## 
## $data
## # A tibble: 12 × 7
##    from  to      coef1   coef2 coef_avg coef_abs sign_coef1
##    <chr> <chr>   <dbl>   <dbl>    <dbl>    <dbl> <chr>     
##  1 X01   X10   -0.310  -0.285   -0.298    0.298  Negative  
##  2 X05   X06   -0.0417 -0.141   -0.0912   0.0912 Negative  
##  3 X09   X17    0.780   0.434    0.607    0.607  Positive  
##  4 X12   X20    0.388   0.130    0.259    0.259  Positive  
##  5 X13   X14    0.0681  0.0638   0.0659   0.0659 Positive  
##  6 X16   X19   -0.0532 -0.137   -0.0953   0.0953 Negative  
##  7 X01   X07   -0.445  -0.385   -0.415    0.415  Negative  
##  8 X01   X15   -0.136  -0.309   -0.223    0.223  Negative  
##  9 X01   X17   -0.928  -0.546   -0.737    0.737  Negative  
## 10 X04   X12    0.328   0.357    0.342    0.342  Positive  
## 11 X05   X09    0.183  -0.0478   0.0676   0.0676 Positive  
## 12 X08   X19    0.0379  0.115    0.0767   0.0767 Positive

Here we see that despite the features that we have selected in terms of the ratio, in actual fact, only a handful of features are useful. In particular, X01, X09 and X17 are the main contributors.

Predictions

Another useful method on the cpop object is the predict_cpop function. This function takes the previous CPOP result and a new (log-)ratio matrix to produce predictions.

The first column of the output are the sample IDs. The second and third column are prediction results from data1 and data2 respectively. Since we have done the previous diagnostic test that the coefficient size between the two data are very similar, we do expect that these values to be very highly correlated. The last column is cpop_model_avg, which is a simple average between the two predicted values.

Note that the predicted values here are on the logit scale (recall that we are performing a logistic regression on binary responses using the elastic net model in the background). We can also transform these values back to predicted probability scale using the CPOP::expit function.

predict_cpop(cpop_result, newx = x3) %>% head()
## # A tibble: 6 × 6
##   samples cpop_model1 cpop_model2 cpop_model_avg cpop_model_avg_prob
##   <chr>         <dbl>       <dbl>          <dbl>               <dbl>
## 1 1             0.500      -0.169          0.165               0.540
## 2 2            -1.76       -0.896         -1.33                0.218
## 3 3             0.750       0.127          0.439               0.605
## 4 4            -1.09       -0.748         -0.918               0.287
## 5 5            -0.414       0.102         -0.156               0.462
## 6 6             0.997       1.41           1.20                0.767
## # … with 1 more variable: cpop_model_avg_class <chr>
predicted_plotdf = predict_cpop(cpop_result, newx = x3) %>%
  dplyr::mutate(
    cpop_model1 = expit(cpop_model1), 
    cpop_model2 = expit(cpop_model2), 
    cpop_model_avg = expit(cpop_model_avg))

predicted_plotdf %>% 
  ggplot(aes(x = cpop_model1, y = cpop_model2)) +
  geom_point() +
  geom_abline()