# SystemML Algorithms Reference

# 5 Matrix Factorization

## 5.1 Principal Component Analysis

### Description

Principal Component Analysis (PCA) is a simple, non-parametric method to
transform the given data set with possibly correlated columns into a set
of linearly uncorrelated or orthogonal columns, called *principal
components*. The principal components are ordered in such a way
that the first component accounts for the largest possible variance,
followed by remaining principal components in the decreasing order of
the amount of variance captured from the data. PCA is often used as a
dimensionality reduction technique, where the original data is projected
or rotated onto a low-dimensional space with basis vectors defined by
top-$K$ (for a given value of $K$) principal components.

### Usage

```
hadoop jar SystemML.jar -f PCA.dml
-nvargs INPUT=<file>
K=<int>
CENTER=[int]
SCALE=[int]
PROJDATA=<int>
OFMT=[format]
MODEL=<file>
OUTPUT=<file>
```

```
$SPARK_HOME/bin/spark-submit --master yarn-cluster
--conf spark.driver.maxResultSize=0
--conf spark.akka.frameSize=128
SystemML.jar
-f PCA.dml
-config=SystemML-config.xml
-exec hybrid_spark
-nvargs INPUT=<file>
K=<int>
CENTER=[int]
SCALE=[int]
PROJDATA=<int>
OFMT=[format]
MODEL=<file>
OUTPUT=<file>
```

#### Arguments

**INPUT**: Location (on HDFS) to read the input matrix.

**K**: Indicates dimension of the new vector space constructed from $K$
principal components. It must be a value between `1`

and the number
of columns in the input data.

**CENTER**: (default: `0`

) `0`

or `1`

. Indicates whether or not to
*center* input data prior to the computation of
principal components.

**SCALE**: (default: `0`

) `0`

or `1`

. Indicates whether or not to
*scale* input data prior to the computation of
principal components.

**PROJDATA**: `0`

or `1`

. Indicates whether or not the input data must be projected
on to new vector space defined over principal components.

**OFMT**: (default: `"csv"`

) Matrix file output format, such as `text`

,
`mm`

, or `csv`

; see read/write functions in
SystemML Language Reference for details.

**MODEL**: Either the location (on HDFS) where the computed model is
stored; or the location of an existing model.

**OUTPUT**: Location (on HDFS) to store the data rotated on to the new
vector space.

#### Examples

```
hadoop jar SystemML.jar -f PCA.dml
-nvargs INPUT=/user/ml/input.mtx
K=10
CENTER=1
SCALE=1O
FMT=csv
PROJDATA=1
OUTPUT=/user/ml/pca_output/
```

```
$SPARK_HOME/bin/spark-submit --master yarn-cluster
--conf spark.driver.maxResultSize=0
--conf spark.akka.frameSize=128
SystemML.jar
-f PCA.dml
-config=SystemML-config.xml
-exec hybrid_spark
-nvargs INPUT=/user/ml/input.mtx
K=10
CENTER=1
SCALE=1O
FMT=csv
PROJDATA=1
OUTPUT=/user/ml/pca_output/
```

```
hadoop jar SystemML.jar -f PCA.dml
-nvargs INPUT=/user/ml/test_input.mtx
K=10
CENTER=1
SCALE=1O
FMT=csv
PROJDATA=1
MODEL=/user/ml/pca_output/
OUTPUT=/user/ml/test_output.mtx
```

```
$SPARK_HOME/bin/spark-submit --master yarn-cluster
--conf spark.driver.maxResultSize=0
--conf spark.akka.frameSize=128
SystemML.jar
-f PCA.dml
-config=SystemML-config.xml
-exec hybrid_spark
-nvargs INPUT=/user/ml/test_input.mtx
K=10
CENTER=1
SCALE=1O
FMT=csv
PROJDATA=1
MODEL=/user/ml/pca_output/
OUTPUT=/user/ml/test_output.mtx
```

#### Details

Principal Component Analysis (PCA) is a non-parametric procedure for orthogonal linear transformation of the input data to a new coordinate system, such that the greatest variance by some projection of the data comes to lie on the first coordinate (called the first principal component), the second greatest variance on the second coordinate, and so on. In other words, PCA first selects a normalized direction in $m$-dimensional space ($m$ is the number of columns in the input data) along which the variance in input data is maximized – this is referred to as the first principal component. It then repeatedly finds other directions (principal components) in which the variance is maximized. At every step, PCA restricts the search for only those directions that are perpendicular to all previously selected directions. By doing so, PCA aims to reduce the redundancy among input variables. To understand the notion of redundancy, consider an extreme scenario with a data set comprising of two variables, where the first one denotes some quantity expressed in meters, and the other variable represents the same quantity but in inches. Both these variables evidently capture redundant information, and hence one of them can be removed. In a general scenario, keeping solely the linear combination of input variables would both express the data more concisely and reduce the number of variables. This is why PCA is often used as a dimensionality reduction technique.

The specific method to compute such a new coordinate system is as
follows – compute a covariance matrix $C$ that measures the strength of
correlation among all pairs of variables in the input data; factorize
$C$ according to eigen decomposition to calculate its eigenvalues and
eigenvectors; and finally, order eigenvectors in the decreasing order of
their corresponding eigenvalue. The computed eigenvectors (also known as
*loadings*) define the new coordinate system and the square
root of eigen values provide the amount of variance in the input data
explained by each coordinate or eigenvector.

#### Returns

When MODEL is not provided, PCA procedure is applied on INPUT data to generate MODEL as well as the rotated data OUTPUT (if PROJDATA is set to $1$) in the new coordinate system. The produced model consists of basis vectors MODEL$/dominant.eigen.vectors$ for the new coordinate system; eigen values MODEL$/dominant.eigen.values$; and the standard deviation MODEL$/dominant.eigen.standard.deviations$ of principal components. When MODEL is provided, INPUT data is rotated according to the coordinate system defined by MODEL$/dominant.eigen.vectors$. The resulting data is stored at location OUTPUT.

## 5.2 Matrix Completion via Alternating Minimizations

### Description

Low-rank matrix completion is an effective technique for statistical data analysis widely used in the data mining and machine learning applications. Matrix completion is a variant of low-rank matrix factorization with the goal of recovering a partially observed and potentially noisy matrix from a subset of its revealed entries. Perhaps the most popular applications in which matrix completion has been successfully applied is in the context of collaborative filtering in recommender systems. In this setting, the rows in the data matrix correspond to users, the columns to items such as movies, and entries to feedback provided by users for items. The goal is to predict missing entries of the rating matrix. This implementation uses the alternating least-squares (ALS) technique for solving large-scale matrix completion problems.

### Usage

**ALS**:

```
hadoop jar SystemML.jar -f ALS.dml
-nvargs V=<file>
L=<file>
R=<file>
rank=[int]
reg=[L2|wL2]
lambda=[double]
maxi=[int]
check=[boolean]
thr=[double]
fmt=[format]
```

```
$SPARK_HOME/bin/spark-submit --master yarn-cluster
--conf spark.driver.maxResultSize=0
--conf spark.akka.frameSize=128
SystemML.jar
-f ALS.dml
-config=SystemML-config.xml
-exec hybrid_spark
-nvargs V=<file>
L=<file>
R=<file>
rank=[int]
reg=[L2|wL2]
lambda=[double]
maxi=[int]
check=[boolean]
thr=[double]
fmt=[format]
```

**ALS Prediction**:

```
hadoop jar SystemML.jar -f ALS_predict.dml
-nvargs X=<file>
Y=<file>
L=<file>
R=<file>
Vrows=<int>
Vcols=<int>
fmt=[format]
```

```
$SPARK_HOME/bin/spark-submit --master yarn-cluster
--conf spark.driver.maxResultSize=0
--conf spark.akka.frameSize=128
SystemML.jar
-f ALS_predict.dml
-config=SystemML-config.xml
-exec hybrid_spark
-nvargs X=<file>
Y=<file>
L=<file>
R=<file>
Vrows=<int>
Vcols=<int>
fmt=[format]
```

**ALS Top-K Prediction**:

```
hadoop jar SystemML.jar -f ALS_topk_predict.dml
-nvargs X=<file>
Y=<file>
L=<file>
R=<file>
V=<file>
K=[int]
fmt=[format]
```

```
$SPARK_HOME/bin/spark-submit --master yarn-cluster
--conf spark.driver.maxResultSize=0
--conf spark.akka.frameSize=128
SystemML.jar
-f ALS_topk_predict.dml
-config=SystemML-config.xml
-exec hybrid_spark
-nvargs X=<file>
Y=<file>
L=<file>
R=<file>
V=<file>
K=[int]
fmt=[format]
```

### Arguments - ALS

**V**: Location (on HDFS) to read the input (user-item) matrix $V$ to be
factorized

**L**: Location (on HDFS) to write the left (user) factor matrix $L$

**R**: Location (on HDFS) to write the right (item) factor matrix $R$

**rank**: (default: `10`

) Rank of the factorization

**reg**: (default: `L2`

) Regularization:

`L2`

=`L2`

regularization`wL2`

= weighted`L2`

regularization

**lambda**: (default: `0.000001`

) Regularization parameter

**maxi**: (default: `50`

) Maximum number of iterations

**check**: (default: `FALSE`

) Check for convergence after every iteration, i.e., updating
$L$ and $R$ once

**thr**: (default: `0.0001`

) Assuming `check=TRUE`

, the algorithm stops and
convergence is declared if the decrease in loss in any two consecutive
iterations falls below threshold `thr`

; if
`check=FALSE`

, parameter `thr`

is ignored.

**fmt**: (default: `"text"`

) Matrix file output format, such as `text`

,
`mm`

, or `csv`

; see read/write functions in
SystemML Language Reference for details.

### Arguments - ALS Prediction/Top-K Prediction

**X**: Location (on HDFS) to read the input matrix $X$ with following format:

- for
`ALS_predict.dml`

: a 2-column matrix that contains the user-ids (first column) and the item-ids (second column) - for
`ALS_topk_predict.dml`

: a 1-column matrix that contains the user-ids

**Y**: Location (on HDFS) to write the output of prediction with the following
format:

- for
`ALS_predict.dml`

: a 3-column matrix that contains the user-ids (first column), the item-ids (second column) and the predicted ratings (third column) - for
`ALS_topk_predict.dml`

: a (`K+1`

)-column matrix that contains the user-ids in the first column and the top-K item-ids in the remaining`K`

columns will be stored at`Y`

. Additionally, a matrix with the same dimensions that contains the corresponding actual top-K ratings will be stored at`Y.ratings`

; see below for details

**L**: Location (on HDFS) to read the left (user) factor matrix $L$

**R**: Location (on HDFS) to write the right (item) factor matrix $R$

**V**: Location (on HDFS) to read the user-item matrix $V$

**Vrows**: Number of rows of $V$ (i.e., number of users)

**Vcols**: Number of columns of $V$ (i.e., number of items)

**K**: (default: `5`

) Number of top-K items for top-K prediction

**fmt**: (default: `"text"`

) Matrix file output format, such as `text`

,
`mm`

, or `csv`

; see read/write functions in
SystemML Language Reference for details.

### Examples

**ALS**:

```
hadoop jar SystemML.jar -f ALS.dml
-nvargs V=/user/ml/V
L=/user/ml/L
R=/user/ml/R
rank=10
reg="wL"
lambda=0.0001
maxi=50
check=TRUE
thr=0.001
fmt=csv
```

```
$SPARK_HOME/bin/spark-submit --master yarn-cluster
--conf spark.driver.maxResultSize=0
--conf spark.akka.frameSize=128
SystemML.jar
-f ALS.dml
-config=SystemML-config.xml
-exec hybrid_spark
-nvargs V=/user/ml/V
L=/user/ml/L
R=/user/ml/R
rank=10
reg="wL"
lambda=0.0001
maxi=50
check=TRUE
thr=0.001
fmt=csv
```

**ALS Prediction**:

To compute predicted ratings for a given list of users and items:

```
hadoop jar SystemML.jar -f ALS_predict.dml
-nvargs X=/user/ml/X
Y=/user/ml/Y
L=/user/ml/L
R=/user/ml/R
Vrows=100000
Vcols=10000
fmt=csv
```

```
$SPARK_HOME/bin/spark-submit --master yarn-cluster
--conf spark.driver.maxResultSize=0
--conf spark.akka.frameSize=128
SystemML.jar
-f ALS_predict.dml
-config=SystemML-config.xml
-exec hybrid_spark
-nvargs X=/user/ml/X
Y=/user/ml/Y
L=/user/ml/L
R=/user/ml/R
Vrows=100000
Vcols=10000
fmt=csv
```

**ALS Top-K Prediction**:

To compute top-K items with highest predicted ratings together with the predicted ratings for a given list of users:

```
hadoop jar SystemML.jar -f ALS_topk_predict.dml
-nvargs X=/user/ml/X
Y=/user/ml/Y
L=/user/ml/L
R=/user/ml/R
V=/user/ml/V
K=10
fmt=csv
```

```
$SPARK_HOME/bin/spark-submit --master yarn-cluster
--conf spark.driver.maxResultSize=0
--conf spark.akka.frameSize=128
SystemML.jar
-f ALS_topk_predict.dml
-config=SystemML-config.xml
-exec hybrid_spark
-nvargs X=/user/ml/X
Y=/user/ml/Y
L=/user/ml/L
R=/user/ml/R
V=/user/ml/V
K=10
fmt=csv
```

### Details

Given an $m \times n$ input matrix $V$ and a rank parameter $r \ll \min{(m,n)}$, low-rank matrix factorization seeks to find an $m \times r$ matrix $L$ and an $r \times n$ matrix $R$ such that $V \approx LR$, i.e., we aim to approximate $V$ by the low-rank matrix $LR$. The quality of the approximation is determined by an application-dependent loss function $\mathcal{L}$. We aim at finding the loss-minimizing factor matrices, i.e.,

In the context of collaborative filtering in the recommender systems it is often the case that the input matrix $V$ contains several missing entries. Such entries are coded with the 0 value and the loss function is computed only based on the nonzero entries in $V$, i.e.,

where and , respectively, denote the $i$th row of $L$ and the $j$th column of $R$, denotes the training set containing the observed (nonzero) entries in $V$, and $l$ is some local loss function.

ALS is an optimization technique that can
be used to solve quadratic problems. For matrix completion, the
algorithm repeatedly keeps one of the unknown matrices ($L$ or $R$)
fixed and optimizes the other one. In particular, ALS alternates between
recomputing the rows of $L$ in one step and the columns of $R$ in the
subsequent step. Our implementation of the ALS algorithm supports the
loss functions summarized in **Table 16**
commonly used for matrix completion [ZhouWSP08].

**Table 16**: Popular loss functions supported by our ALS implementation;
and , respectively, denote the number of nonzero entries in
row $i$ and column $j$ of $V$.

Loss | Definition |
---|---|

Note that the matrix completion problem as defined in (1)
is a non-convex problem for all loss functions from
**Table 16**. However, when fixing one of the matrices
$L$ or $R$, we get a least-squares problem with a globally optimal
solution. For example, for the case of we
have the following closed form solutions

where (resp. ) denotes the $i$th row of (resp. $j$th column of ), $\lambda$ denotes the regularization parameter, $I$ is the identity matrix of appropriate dimensionality, (resp. ) denotes the revealed entries in row $i$ (column $j$), (resp. ) refers to the corresponding columns of $R_n$ (rows of ), and $N_1$ (resp. $N_2$) denotes a diagonal matrix that contains the number of nonzero entries in row $i$ (column $j$) of $V$.

**Prediction.** Based on the factor matrices computed by ALS we provide
two prediction scripts:

`ALS_predict.dml`

computes the predicted ratings for a given list of users and items.`ALS_topk_predict.dml`

computes top-K item (where $K$ is given as input) with highest predicted ratings together with their corresponding ratings for a given list of users.

### Returns

We output the factor matrices $L$ and $R$ after the algorithm has
converged. The algorithm is declared as converged if one of the two
criteria is meet: (1) the decrease in the value of loss function falls
below `thr`

given as an input parameter (if parameter
`check=TRUE`

), or (2) the maximum number of iterations
(defined as parameter `maxi`

) is reached. Note that for a
given user $i$ prediction is possible only if user $i$ has rated at
least one item, i.e., row $i$ in matrix $V$ has at least one nonzero
entry. In case, some users have not rated any items the corresponding
factor in $L$ will be all 0s. Similarly if some items have not been
rated at all the corresponding factors in $R$ will contain only 0s. Our
prediction scripts output the predicted ratings for a given list of
users and items as well as the top-K items with highest predicted
ratings together with the predicted ratings for a given list of users.
Note that the predictions will only be provided for the users who have
rated at least one item, i.e., the corresponding rows contain at least
one nonzero entry.