Machine Learning Engineer Nanodegree

Supervised Learning

Project: Finding Donors for CharityML

Welcome to the second project of the Machine Learning Engineer Nanodegree! In this notebook, some template code has already been provided for you, and it will be your job to implement the additional functionality necessary to successfully complete this project. Sections that begin with 'Implementation' in the header indicate that the following block of code will require additional functionality which you must provide. Instructions will be provided for each section and the specifics of the implementation are marked in the code block with a 'TODO' statement. Please be sure to read the instructions carefully!

In addition to implementing code, there will be questions that you must answer which relate to the project and your implementation. Each section where you will answer a question is preceded by a 'Question X' header. Carefully read each question and provide thorough answers in the following text boxes that begin with 'Answer:'. Your project submission will be evaluated based on your answers to each of the questions and the implementation you provide.

Note: Please specify WHICH VERSION OF PYTHON you are using when submitting this notebook. Code and Markdown cells can be executed using the Shift + Enter keyboard shortcut. In addition, Markdown cells can be edited by typically double-clicking the cell to enter edit mode.

Getting Started

In this project, you will employ several supervised algorithms of your choice to accurately model individuals' income using data collected from the 1994 U.S. Census. You will then choose the best candidate algorithm from preliminary results and further optimize this algorithm to best model the data. Your goal with this implementation is to construct a model that accurately predicts whether an individual makes more than $50,000. This sort of task can arise in a non-profit setting, where organizations survive on donations. Understanding an individual's income can help a non-profit better understand how large of a donation to request, or whether or not they should reach out to begin with. While it can be difficult to determine an individual's general income bracket directly from public sources, we can (as we will see) infer this value from other publically available features.

The dataset for this project originates from the UCI Machine Learning Repository. The datset was donated by Ron Kohavi and Barry Becker, after being published in the article "Scaling Up the Accuracy of Naive-Bayes Classifiers: A Decision-Tree Hybrid". You can find the article by Ron Kohavi online. The data we investigate here consists of small changes to the original dataset, such as removing the 'fnlwgt' feature and records with missing or ill-formatted entries.


Exploring the Data

Run the code cell below to load necessary Python libraries and load the census data. Note that the last column from this dataset, 'income', will be our target label (whether an individual makes more than, or at most, $50,000 annually). All other columns are features about each individual in the census database.


In [1]:
# Import libraries necessary for this project
import numpy as np
import pandas as pd
from time import time
from IPython.display import display # Allows the use of display() for DataFrames

# Import supplementary visualization code visuals.py
import visuals as vs

# Pretty display for notebooks
%matplotlib inline

# Load the Census dataset
data = pd.read_csv("census.csv")

# Success - Display the first record
display(data.head(n=1))


age workclass education_level education-num marital-status occupation relationship race sex capital-gain capital-loss hours-per-week native-country income
0 39 State-gov Bachelors 13.0 Never-married Adm-clerical Not-in-family White Male 2174.0 0.0 40.0 United-States <=50K

Implementation: Data Exploration

A cursory investigation of the dataset will determine how many individuals fit into either group, and will tell us about the percentage of these individuals making more than \$50,000. In the code cell below, you will need to compute the following:

  • The total number of records, 'n_records'
  • The number of individuals making more than \$50,000 annually, 'n_greater_50k'.
  • The number of individuals making at most \$50,000 annually, 'n_at_most_50k'.
  • The percentage of individuals making more than \$50,000 annually, 'greater_percent'.

Hint: You may need to look at the table above to understand how the 'income' entries are formatted.


In [2]:
# TODO: Total number of records
n_records = data.count()[0]

# TODO: Number of records where individual's income is more than $50,000
n_greater_50k = data[data['income'].str.match('>50K')].count()[0]

# TODO: Number of records where individual's income is at most $50,000
n_at_most_50k = data[data['income'].str.match('<=50K')].count()[0]

# TODO: Percentage of individuals whose income is more than $50,000
greater_percent = float(n_greater_50k)/n_records * 100

# Print the results
print "Total number of records: {}".format(n_records)
print "Individuals making more than $50,000: {}".format(n_greater_50k)
print "Individuals making at most $50,000: {}".format(n_at_most_50k)
print "Percentage of individuals making more than $50,000: {:.2f}%".format(greater_percent)


Total number of records: 45222
Individuals making more than $50,000: 11208
Individuals making at most $50,000: 34014
Percentage of individuals making more than $50,000: 24.78%

Preparing the Data

Before data can be used as input for machine learning algorithms, it often must be cleaned, formatted, and restructured — this is typically known as preprocessing. Fortunately, for this dataset, there are no invalid or missing entries we must deal with, however, there are some qualities about certain features that must be adjusted. This preprocessing can help tremendously with the outcome and predictive power of nearly all learning algorithms.

Transforming Skewed Continuous Features

A dataset may sometimes contain at least one feature whose values tend to lie near a single number, but will also have a non-trivial number of vastly larger or smaller values than that single number. Algorithms can be sensitive to such distributions of values and can underperform if the range is not properly normalized. With the census dataset two features fit this description: 'capital-gain' and 'capital-loss'.

Run the code cell below to plot a histogram of these two features. Note the range of the values present and how they are distributed.


In [3]:
# Split the data into features and target label
income_raw = data['income']
features_raw = data.drop('income', axis = 1)

# Visualize skewed continuous features of original data
vs.distribution(data)


For highly-skewed feature distributions such as 'capital-gain' and 'capital-loss', it is common practice to apply a logarithmic transformation on the data so that the very large and very small values do not negatively affect the performance of a learning algorithm. Using a logarithmic transformation significantly reduces the range of values caused by outliers. Care must be taken when applying this transformation however: The logarithm of 0 is undefined, so we must translate the values by a small amount above 0 to apply the the logarithm successfully.

Run the code cell below to perform a transformation on the data and visualize the results. Again, note the range of values and how they are distributed.


In [4]:
# Log-transform the skewed features
skewed = ['capital-gain', 'capital-loss']
features_raw[skewed] = data[skewed].apply(lambda x: np.log(x + 1))

# Visualize the new log distributions
vs.distribution(features_raw, transformed = True)


Normalizing Numerical Features

In addition to performing transformations on features that are highly skewed, it is often good practice to perform some type of scaling on numerical features. Applying a scaling to the data does not change the shape of each feature's distribution (such as 'capital-gain' or 'capital-loss' above); however, normalization ensures that each feature is treated equally when applying supervised learners. Note that once scaling is applied, observing the data in its raw form will no longer have the same original meaning, as exampled below.

Run the code cell below to normalize each numerical feature. We will use sklearn.preprocessing.MinMaxScaler for this.


In [5]:
# Import sklearn.preprocessing.StandardScaler
from sklearn.preprocessing import MinMaxScaler

# Initialize a scaler, then apply it to the features
scaler = MinMaxScaler()
numerical = ['age', 'education-num', 'capital-gain', 'capital-loss', 'hours-per-week']
features_raw[numerical] = scaler.fit_transform(data[numerical])

# Show an example of a record with scaling applied
display(features_raw.head(n = 1))


age workclass education_level education-num marital-status occupation relationship race sex capital-gain capital-loss hours-per-week native-country
0 0.30137 State-gov Bachelors 0.8 Never-married Adm-clerical Not-in-family White Male 0.02174 0.0 0.397959 United-States

Implementation: Data Preprocessing

From the table in Exploring the Data above, we can see there are several features for each record that are non-numeric. Typically, learning algorithms expect input to be numeric, which requires that non-numeric features (called categorical variables) be converted. One popular way to convert categorical variables is by using the one-hot encoding scheme. One-hot encoding creates a "dummy" variable for each possible category of each non-numeric feature. For example, assume someFeature has three possible entries: A, B, or C. We then encode this feature into someFeature_A, someFeature_B and someFeature_C.

someFeature someFeature_A someFeature_B someFeature_C
0 B 0 1 0
1 C ----> one-hot encode ----> 0 0 1
2 A 1 0 0

Additionally, as with the non-numeric features, we need to convert the non-numeric target label, 'income' to numerical values for the learning algorithm to work. Since there are only two possible categories for this label ("<=50K" and ">50K"), we can avoid using one-hot encoding and simply encode these two categories as 0 and 1, respectively. In code cell below, you will need to implement the following:

  • Use pandas.get_dummies() to perform one-hot encoding on the 'features_raw' data.
  • Convert the target label 'income_raw' to numerical entries.
    • Set records with "<=50K" to 0 and records with ">50K" to 1.

In [6]:
# TODO: One-hot encode the 'features_raw' data using pandas.get_dummies()
features = pd.get_dummies(features_raw)

# TODO: Encode the 'income_raw' data to numerical values
income = pd.Series([1 if x == ">50K" else 0 for x in income_raw])

# Print the number of features after one-hot encoding
encoded = list(features.columns)
print "{} total features after one-hot encoding.".format(len(encoded))

# Uncomment the following line to see the encoded feature names
# print encoded


103 total features after one-hot encoding.

Shuffle and Split Data

Now all categorical variables have been converted into numerical features, and all numerical features have been normalized. As always, we will now split the data (both features and their labels) into training and test sets. 80% of the data will be used for training and 20% for testing.

Run the code cell below to perform this split.


In [7]:
# Import train_test_split
from sklearn.cross_validation import train_test_split

# Split the 'features' and 'income' data into training and testing sets
X_train, X_test, y_train, y_test = train_test_split(features, income, test_size = 0.2, random_state = 0)

# Show the results of the split
print "Training set has {} samples.".format(X_train.shape[0])
print "Testing set has {} samples.".format(X_test.shape[0])


Training set has 36177 samples.
Testing set has 9045 samples.
/Library/Python/2.7/site-packages/sklearn/cross_validation.py:44: DeprecationWarning: This module was deprecated in version 0.18 in favor of the model_selection module into which all the refactored classes and functions are moved. Also note that the interface of the new CV iterators are different from that of this module. This module will be removed in 0.20.
  "This module will be removed in 0.20.", DeprecationWarning)

Evaluating Model Performance

In this section, we will investigate four different algorithms, and determine which is best at modeling the data. Three of these algorithms will be supervised learners of your choice, and the fourth algorithm is known as a naive predictor.

Metrics and the Naive Predictor

CharityML, equipped with their research, knows individuals that make more than \$50,000 are most likely to donate to their charity. Because of this, *CharityML* is particularly interested in predicting who makes more than \$50,000 accurately. It would seem that using accuracy as a metric for evaluating a particular model's performace would be appropriate. Additionally, identifying someone that does not make more than \$50,000 as someone who does would be detrimental to *CharityML*, since they are looking to find individuals willing to donate. Therefore, a model's ability to precisely predict those that make more than \$50,000 is more important than the model's ability to recall those individuals. We can use F-beta score as a metric that considers both precision and recall:

$$ F_{\beta} = (1 + \beta^2) \cdot \frac{precision \cdot recall}{\left( \beta^2 \cdot precision \right) + recall} $$

In particular, when $\beta = 0.5$, more emphasis is placed on precision. This is called the F$_{0.5}$ score (or F-score for simplicity).

Looking at the distribution of classes (those who make at most \$50,000, and those who make more), it's clear most individuals do not make more than \$50,000. This can greatly affect accuracy, since we could simply say "this person does not make more than \$50,000" and generally be right, without ever looking at the data! Making such a statement would be called naive, since we have not considered any information to substantiate the claim. It is always important to consider the naive prediction for your data, to help establish a benchmark for whether a model is performing well. That been said, using that prediction would be pointless: If we predicted all people made less than \$50,000, CharityML would identify no one as donors.

Question 1 - Naive Predictor Performace

If we chose a model that always predicted an individual made more than \$50,000, what would that model's accuracy and F-score be on this dataset?
Note: You must use the code cell below and assign your results to 'accuracy' and 'fscore' to be used later.


In [8]:
# TODO: Calculate accuracy
accuracy = float(income[income == 1].count())/income.count()

# TODO: Calculate F-score using the formula above for beta = 0.5
beta = 0.5
TP = float(income[income == 1].count()) # If we predict all are true, then our TP are all the true records
FP = float(income[income == 0].count()) # If we predict all are true, then our FP are all the false records
FN = 0 # If we predict all are true, we will have no false negatives
precision = TP/(TP+FP)
recall = TP/(TP+FN)
fscore = (1+beta**2) * (precision * recall) / ((beta**2 * precision) + recall)

# Print the results 
print "Naive Predictor: [Accuracy score: {:.4f}, F-score: {:.4f}]".format(accuracy, fscore)


Naive Predictor: [Accuracy score: 0.2478, F-score: 0.2917]

Supervised Learning Models

The following supervised learning models are currently available in scikit-learn that you may choose from:

  • Gaussian Naive Bayes (GaussianNB)
  • Decision Trees
  • Ensemble Methods (Bagging, AdaBoost, Random Forest, Gradient Boosting)
  • K-Nearest Neighbors (KNeighbors)
  • Stochastic Gradient Descent Classifier (SGDC)
  • Support Vector Machines (SVM)
  • Logistic Regression

Question 2 - Model Application

List three of the supervised learning models above that are appropriate for this problem that you will test on the census data. For each model chosen

  • Describe one real-world application in industry where the model can be applied. (You may need to do research for this — give references!)
  • What are the strengths of the model; when does it perform well?
  • What are the weaknesses of the model; when does it perform poorly?
  • What makes this model a good candidate for the problem, given what you know about the data?

Answer:

  1. SVM

    • Describe one real-world application in industry where the model can be applied. (You may need to do research for this — give references!)
      • Have been used in text analytics and document classification[1](#doc_class) such as spam filters.
    • What are the strengths of the model; when does it perform well?
      • Good at handling high dimensional data
      • Can utilize domain knowledge (kernels)
      • Places greater consideration to points near a decision boundary
    • What are the weaknesses of the model; when does it perform poorly?
      • Performs poorly when there is no clear decision boundary or decision boundary is highly irregular
      • Performs poorly when the number of features greatly outnumbers the number of data points
      • Can be computationally expensive when relationships between features are complex
    • What makes this model a good candidate for the problem, given what you know about the data?
      • The relationships between features in this dataset can be a bit complex, so a non-linear kernel will be able to generate a good decision boundary (relative to linear methods)
  2. KNN

    • Describe one real-world application in industry where the model can be applied. (You may need to do research for this — give references!)
      • KNN can also be used for text analytics and document classification (as above)
      • A different application is in recommender systems, sepcifically through collaborative filtering[3](#collab)
    • What are the strengths of the model; when does it perform well?
      • Doesn't need to do any training (lazy-learner).
      • Simple
      • It performs well when it is safe to assume that data points are similar and change smoothly
      • It performs well when there are sufficient data points to make comparisons against new data points
    • What are the weaknesses of the model; when does it perform poorly?
      • Slow at runtime because it doesn't do any training. Consequently, it requires the data to be stored in its entirety and read into memory at run time. This means it performs poorly on very large datasets. In addition, KNN performs poorly when the number of features is very large (Curse of Dimensionality).
      • In some situations, it may be difficult to determine a good similarity metric (requires some domain knowledge when not all features should be weighted equally)
      • Features need to be normalized, otherwise a particular feature may completely dominate another one, causing changes in the smaller feature (which may be significant when only looking at that feature) to have little to no impact on the similarity metric.
    • What makes this model a good candidate for the problem, given what you know about the data?
      • It is reasonable to expect that individuals with similar statuses (same job, same education level, etc.) will have similar incomes.
      • Since our data has been normalized, no individual term will dominate the other terms
  3. Random Forest

    • Describe one real-world application in industry where the model can be applied. (You may need to do research for this — give references!)
      • Random forests are widely used in bioinformatics. Yanjun Qi[6](#bioinformatics) describes why random forests are desirable and a few applications such as protein-protein interaction prediction.
    • What are the strengths of the model; when does it perform well?
      • Performs well on classification problems (reduces variance via voting/averaging)
      • Can handle a large number of input variables
      • Is very quick to train (can train each decision tree in parallel)
    • What are the weaknesses of the model; when does it perform poorly?
      • Bad at handling continuous and time series data.
      • Slow at runtime.
      • Slight increase in bias (relative to a single decision tree) due to splitting occurring on a random subset of the features instead of splitting with respect to all of the features
    • What makes this model a good candidate for the problem, given what you know about the data?
      • Good at modelling classification problems
      • Good at handling a large number of input variables, especially categorical/boolean variables (only 5 of the 103 columns are numerical).

Sources:

  1. Document Classification
  2. Sklearn SVM
  3. Collaborative Filtering
  4. Udacity
  5. Sklearn Neighbors
  6. Random Forests in Bioinformatics
  7. Sklearn Ensemble

Implementation - Creating a Training and Predicting Pipeline

To properly evaluate the performance of each model you've chosen, it's important that you create a training and predicting pipeline that allows you to quickly and effectively train models using various sizes of training data and perform predictions on the testing data. Your implementation here will be used in the following section. In the code block below, you will need to implement the following:

  • Import fbeta_score and accuracy_score from sklearn.metrics.
  • Fit the learner to the sampled training data and record the training time.
  • Perform predictions on the test data X_test, and also on the first 300 training points X_train[:300].
    • Record the total prediction time.
  • Calculate the accuracy score for both the training subset and testing set.
  • Calculate the F-score for both the training subset and testing set.
    • Make sure that you set the beta parameter!

In [9]:
# TODO: Import two metrics from sklearn - fbeta_score and accuracy_score
from sklearn.metrics import fbeta_score, accuracy_score
def train_predict(learner, sample_size, X_train, y_train, X_test, y_test): 
    '''
    inputs:
       - learner: the learning algorithm to be trained and predicted on
       - sample_size: the size of samples (number) to be drawn from training set
       - X_train: features training set
       - y_train: income training set
       - X_test: features testing set
       - y_test: income testing set
    '''
    
    results = {}
    
    # TODO: Fit the learner to the training data using slicing with 'sample_size'
    start = time() # Get start time
    train_indices = X_train.sample(sample_size, random_state=123).index
    learner = learner.fit(X_train.loc[train_indices], y_train.loc[train_indices])
    end = time() # Get end time
    
    # TODO: Calculate the training time
    results['train_time'] = end - start
        
    # TODO: Get the predictions on the test set,
    #       then get predictions on the first 300 training samples
    start = time() # Get start time
    predictions_test = learner.predict(X_test)
    predictions_train = learner.predict(X_train[:300])
    end = time() # Get end time
    
    # TODO: Calculate the total prediction time
    results['pred_time'] = end - start
            
    # TODO: Compute accuracy on the first 300 training samples
    results['acc_train'] = accuracy_score(y_train[:300], predictions_train)
        
    # TODO: Compute accuracy on test set
    results['acc_test'] = accuracy_score(y_test, predictions_test)
    
    # TODO: Compute F-score on the the first 300 training samples
    results['f_train'] = fbeta_score(y_train[:300], predictions_train, beta=0.5)
    
    # TODO: Compute F-score on the test set
    results['f_test'] = fbeta_score(y_test, predictions_test, beta=0.5)
       
    # Success
    print "{} trained on {} samples.".format(learner.__class__.__name__, sample_size)
        
    # Return the results
    return results

Implementation: Initial Model Evaluation

In the code cell, you will need to implement the following:

  • Import the three supervised learning models you've discussed in the previous section.
  • Initialize the three models and store them in 'clf_A', 'clf_B', and 'clf_C'.
    • Use a 'random_state' for each model you use, if provided.
    • Note: Use the default settings for each model — you will tune one specific model in a later section.
  • Calculate the number of records equal to 1%, 10%, and 100% of the training data.
    • Store those values in 'samples_1', 'samples_10', and 'samples_100' respectively.

Note: Depending on which algorithms you chose, the following implementation may take some time to run!


In [10]:
# TODO: Import the three supervised learning models from sklearn
from sklearn.svm import SVC
from sklearn.neighbors import KNeighborsClassifier
from sklearn.ensemble import RandomForestClassifier
# TODO: Initialize the three models
clf_A = SVC(random_state=777)
clf_B = KNeighborsClassifier()
clf_C = RandomForestClassifier(random_state=777)

# TODO: Calculate the number of samples for 1%, 10%, and 100% of the training data
samples_1 = X_train.count()[0]/100
samples_10 = X_train.count()[0]/10
samples_100 = X_train.count()[0]

# Collect results on the learners
results = {}
for clf in [clf_A, clf_B, clf_C]:
    clf_name = clf.__class__.__name__
    results[clf_name] = {}
    for i, samples in enumerate([samples_1, samples_10, samples_100]):
        results[clf_name][i] = \
        train_predict(clf, samples, X_train, y_train, X_test, y_test)

# Run metrics visualization for the three supervised learning models chosen
vs.evaluate(results, accuracy, fscore)


/Library/Python/2.7/site-packages/sklearn/metrics/classification.py:1113: UndefinedMetricWarning: F-score is ill-defined and being set to 0.0 due to no predicted samples.
  'precision', 'predicted', average, warn_for)
SVC trained on 361 samples.
SVC trained on 3617 samples.
SVC trained on 36177 samples.
KNeighborsClassifier trained on 361 samples.
KNeighborsClassifier trained on 3617 samples.
KNeighborsClassifier trained on 36177 samples.
RandomForestClassifier trained on 361 samples.
RandomForestClassifier trained on 3617 samples.
RandomForestClassifier trained on 36177 samples.

Improving Results

In this final section, you will choose from the three supervised learning models the best model to use on the student data. You will then perform a grid search optimization for the model over the entire training set (X_train and y_train) by tuning at least one parameter to improve upon the untuned model's F-score.

Question 3 - Choosing the Best Model

Based on the evaluation you performed earlier, in one to two paragraphs, explain to CharityML which of the three models you believe to be most appropriate for the task of identifying individuals that make more than \$50,000.
Hint: Your answer should include discussion of the metrics, prediction/training time, and the algorithm's suitability for the data.

Answer: Of these 3 models, the one that performed best overall is Random Forest. They performed consistently better wrt both accuracy and F-score than the other 2, with exception to SVMs on the test set when training with 10% of the training set.

SVMs only performed marginally better on the test set with 10% of the training set, but as the training set size increased, it began to perform more poorly on the test set (overfitting). Additionally, the training time for SVMs was significantly higher than the other 2 models. Also, when the training set was small, the default SVM implementation couldn't even separate the labels, opting to output every input as 0 instead (We can verify this since the accuracy_score is ~75%, which is the number of samples that have the label 0). Therefore SVMs are a worst candidate than Random Forests.

On the other hand, KNNs performed the worst on the test set in all cases except when trained on 1% of the training set (recall, SVMs weren't able to fit a good model in this scenario). Furthermore, the runtime for a KNN is significantly higher than the other two models. Therefore, KNNs are a worst candidate than Random Forests.

The training and runtime for Random Forests is quite a bit smaller than I had expected it to be. However, It should be noted that the accuracy and fscore between predictions on the training and testing set had the largest difference. This suggests that there is some overfitting occuring as the accuracy drops about 15% when making predictions on the test set. The other models on the other hand, only changed slightly (<~5%).

Question 4 - Describing the Model in Layman's Terms

In one to two paragraphs, explain to CharityML, in layman's terms, how the final model chosen is supposed to work. Be sure that you are describing the major qualities of the model, such as how the model is trained and how the model makes a prediction. Avoid using advanced mathematical or technical jargon, such as describing equations or discussing the algorithm implementation.

Answer:

A random forest is essentially a group of decision tress which combine their answers at the end. To create one, we begin by creating a bunch of decision trees and train them separately. The decision trees are chosen by randomly selecting different subsets of the features. This ensures that it is very unlikely that 2 decision trees are exactly the same, and thus makes the forest meaningful.

Each individual decision tree is trained by creating splits on the training data which ultimately results in a tree that divides the dataset into our two target labels.

At runtime, the input is passed to each of the decision trees, and each decision tree returns a label with its prediction of what the output should be. The final output is then the label with the most votes (tie breakers can be decided in some other manner, or we can ensure the number of trees is odd)

Implementation: Model Tuning

Fine tune the chosen model. Use grid search (GridSearchCV) with at least one important parameter tuned with at least 3 different values. You will need to use the entire training set for this. In the code cell below, you will need to implement the following:

  • Import sklearn.grid_search.GridSearchCV and sklearn.metrics.make_scorer.
  • Initialize the classifier you've chosen and store it in clf.
    • Set a random_state if one is available to the same state you set before.
  • Create a dictionary of parameters you wish to tune for the chosen model.
    • Example: parameters = {'parameter' : [list of values]}.
    • Note: Avoid tuning the max_features parameter of your learner if that parameter is available!
  • Use make_scorer to create an fbeta_score scoring object (with $\beta = 0.5$).
  • Perform grid search on the classifier clf using the 'scorer', and store it in grid_obj.
  • Fit the grid search object to the training data (X_train, y_train), and store it in grid_fit.

Note: Depending on the algorithm chosen and the parameter list, the following implementation may take some time to run!


In [12]:
# TODO: Import 'GridSearchCV', 'make_scorer', and any other necessary libraries
from sklearn.grid_search import GridSearchCV
from sklearn.metrics import make_scorer
# TODO: Initialize the classifier
clf = RandomForestClassifier(random_state=777)

# TODO: Create the parameters list you wish to tune
parameters = {
    'n_estimators': [x for x in range(1,21,2)],
    'criterion': ['gini', 'entropy'],
    'max_features': ['sqrt', 'log2'],
    'max_depth': [x for x in range(1,11)],
    'bootstrap': [True, False]
}

# TODO: Make an fbeta_score scoring object
scorer = make_scorer(fbeta_score, beta=0.5)

# TODO: Perform grid search on the classifier using 'scorer' as the scoring method
grid_obj = GridSearchCV(clf, parameters, scoring=scorer)

# TODO: Fit the grid search object to the training data and find the optimal parameters
grid_fit = grid_obj.fit(X_train, y_train)

# Get the estimator
best_clf = grid_fit.best_estimator_

# Make predictions using the unoptimized and model
predictions = (clf.fit(X_train, y_train)).predict(X_test)
best_predictions = best_clf.predict(X_test)

# Report the before-and-afterscores
print "Unoptimized model\n------"
print "Accuracy score on testing data: {:.4f}".format(accuracy_score(y_test, predictions))
print "F-score on testing data: {:.4f}".format(fbeta_score(y_test, predictions, beta = 0.5))
print "\nOptimized Model\n------"
print "Final accuracy score on the testing data: {:.4f}".format(accuracy_score(y_test, best_predictions))
print "Final F-score on the testing data: {:.4f}".format(fbeta_score(y_test, best_predictions, beta = 0.5))


Unoptimized model
------
Accuracy score on testing data: 0.8387
F-score on testing data: 0.6746

Optimized Model
------
Final accuracy score on the testing data: 0.8559
Final F-score on the testing data: 0.7271

Question 5 - Final Model Evaluation

What is your optimized model's accuracy and F-score on the testing data? Are these scores better or worse than the unoptimized model? How do the results from your optimized model compare to the naive predictor benchmarks you found earlier in Question 1?
Note: Fill in the table below with your results, and then provide discussion in the Answer box.

Results:

Metric Benchmark Predictor Unoptimized Model Optimized Model
Accuracy Score 0.2478 0.8387 0.8559
F-score 0.2917 0.6746 0.7271

Answer:

The optimized model performs a bit better (~2% more accurate, ~5% higher f-score) which performed much better than the naive predictor.

I had originally wanted to tune n_estimators from 1-50 and also tune min_samples_split, however it was clear that it was going to take a very long time to run.


Feature Importance

An important task when performing supervised learning on a dataset like the census data we study here is determining which features provide the most predictive power. By focusing on the relationship between only a few crucial features and the target label we simplify our understanding of the phenomenon, which is most always a useful thing to do. In the case of this project, that means we wish to identify a small number of features that most strongly predict whether an individual makes at most or more than \$50,000.

Choose a scikit-learn classifier (e.g., adaboost, random forests) that has a feature_importance_ attribute, which is a function that ranks the importance of features according to the chosen classifier. In the next python cell fit this classifier to training set and use this attribute to determine the top 5 most important features for the census dataset.

Question 6 - Feature Relevance Observation

When Exploring the Data, it was shown there are thirteen available features for each individual on record in the census data.
Of these thirteen records, which five features do you believe to be most important for prediction, and in what order would you rank them and why?

Answer:

  1. Hours-Per-Week
  2. Education_Level
  3. WorkClass
  4. Age
  5. Occupation

I believe these 5 have the greatest effects on prediction because:

  • Hours-Per-Week: This could be used to identify part time/full time employees. Those working part time (\< 30 hours/week) probably don't make more than 50K unless they work as consultants, has some specialized skill, own a business, or have some other unique circumstances (outliers).
  • Education_Level: It is probably not that hard for an individual with a PhD or Masters degree to make more than 50K. Similarly, individuals who have yet to graduate high school or are in college probably don't make more than 50K.
  • WorkClass: We can immediately filter out 'Without-pay' and 'Never-worked' individuals. I am not too familiar with the exact ranking for the other classes, however, there is probably some ranking (eg. private makes more than local-gov on avg) that could be used to find a decision boundary.
  • Age: Individuals under 18 likely won't be making more than 50K a year. Anyone over 18, will need to combine other factors. This is similar to education_level but when used in conjunction with education_level, can tell us a bit more (for eg. a 30 year old high school drop out has a lower chance of making 50K/year than a 30 year old with a Bachelor's degree)
  • Occupation: I think that occupation is likely important and it was tough to choose this over the remaining features because an argument could be made for many of the other features. I selected occupation because I think that its generally more important than the others and I'm hoping the data will support my gut feeling. However, it is dependent on many factors, such as location and seniority which aren't specified. Additionally the available categories are a little limited (in clarity and diversity). For eg. 'Farming-Fishing', does that mean you're a laborer on a farm? Or do you sell farm equipment? Or perhaps you own the farm. Similarly, for 'Sales', a door-to-door salesman might make significantly less than a real estate agent or a car salesman with a high number of sales each month.

Implementation - Extracting Feature Importance

Choose a scikit-learn supervised learning algorithm that has a feature_importance_ attribute availble for it. This attribute is a function that ranks the importance of each feature when making predictions based on the chosen algorithm.

In the code cell below, you will need to implement the following:

  • Import a supervised learning model from sklearn if it is different from the three used earlier.
  • Train the supervised model on the entire training set.
  • Extract the feature importances using '.feature_importances_'.

In [15]:
# TODO: Import a supervised learning model that has 'feature_importances_'
from sklearn.ensemble import RandomForestClassifier
clf = RandomForestClassifier(random_state=777)
# TODO: Train the supervised model on the training set 
model = clf.fit(X_train, y_train)

# TODO: Extract the feature importances
importances = model.feature_importances_

# Plot
vs.feature_plot(importances, X_train, y_train)


[  2.25451059e-01   5.83457696e-02   1.22170564e-01   4.26419028e-02
   1.14668332e-01   5.39881930e-03   5.56130044e-03   9.99463317e-03
   5.16069533e-03   7.93971013e-03   5.31420031e-03   8.84932374e-05
   2.09830899e-03   2.62333236e-03   8.35251002e-04   3.00817106e-04
   9.60562999e-04   1.77130654e-03   1.20424636e-03   2.22007849e-03
   2.72813837e-03   1.10128313e-02   2.75729008e-03   8.17613449e-03
   6.84801659e-03   1.56099191e-05   5.93215070e-03   5.39055760e-03
   3.86615690e-03   1.77688149e-04   6.96899214e-02   1.04400927e-03
   2.47060069e-02   1.57979096e-03   1.85389816e-03   5.54381694e-03
   3.82055874e-05   6.25916276e-03   2.06469142e-02   4.69217159e-03
   3.40548032e-03   3.69411843e-03   9.09103058e-03   3.30998293e-04
   1.48928916e-02   3.21209308e-03   6.83344200e-03   3.99459153e-03
   4.18875092e-03   5.86256932e-02   1.12854997e-02   1.45132895e-03
   6.74439223e-03   7.28870078e-03   1.03343837e-02   1.49649470e-03
   3.11410686e-03   5.14998006e-03   9.61264507e-04   6.18193047e-03
   9.12450234e-03   8.02055879e-03   2.65925654e-04   1.28715550e-03
   9.00129022e-04   2.65824067e-04   1.03681372e-03   1.98905966e-04
   9.08969524e-05   2.90759346e-04   1.09801309e-03   2.89716592e-04
   9.62778096e-04   3.26963714e-04   8.88340733e-05   1.84573451e-04
   0.00000000e+00   2.08323595e-05   1.30358088e-04   2.10869729e-04
   7.80501057e-04   4.46129552e-04   2.87968533e-04   6.44028113e-04
   3.00699307e-04   5.35425176e-04   1.13640011e-04   1.65342060e-03
   1.44618660e-04   2.80330464e-05   2.65333527e-04   1.12570561e-03
   6.59550640e-04   2.81631924e-04   5.44964873e-04   7.66896017e-05
   5.44260037e-04   2.65496394e-04   7.78414381e-05   1.41707672e-04
   5.82696378e-03   3.48369867e-04   1.27583452e-04]

Question 7 - Extracting Feature Importance

Observe the visualization created above which displays the five most relevant features for predicting if an individual makes at most or above \$50,000.
How do these five features compare to the five features you discussed in Question 6? If you were close to the same answer, how does this visualization confirm your thoughts? If you were not close, why do you think these features are more relevant?

Answer:

I had correctly predicted Age and Hours-Per-Week as relevant features. I had incorrectly predicted Workclass, Education_Level, Occupation. The more relevant features were capital-gain, marital_status (married-civ-spouse), and relationship (husband).

I think that Age and Hours-Per-Week were matched because they were the easiest features to make sense of without any prior domain knowledge. For example, it isn't clear to a ML algorithm that someone with a PhD should make more than a 6th grader. If it were encoded numerically, there should be a rather smooth increase in income as age increases, and such is the case with hours-per-week (if you work more, you make more). Workclass and Occupation similarly require some domain knowledge. Additionally, these 3 features require far more description and data before they are useful.

Capital-gain makes a lot of sense in that it directly contributes to your income (if its more than 50K, you automatically make more than 50K). As for the other 2 features, it seems to suggest that being a married man is a good predictor. Perhaps the data supports the conclusion that married men have enough income to take care of a family, and that tends to be over 50K/year

Feature Selection

How does a model perform if we only use a subset of all the available features in the data? With less features required to train, the expectation is that training and prediction time is much lower — at the cost of performance metrics. From the visualization above, we see that the top five most important features contribute more than half of the importance of all features present in the data. This hints that we can attempt to reduce the feature space and simplify the information required for the model to learn. The code cell below will use the same optimized model you found earlier, and train it on the same training set with only the top five important features.


In [16]:
# Import functionality for cloning a model
from sklearn.base import clone

# Reduce the feature space
X_train_reduced = X_train[X_train.columns.values[(np.argsort(importances)[::-1])[:5]]]
X_test_reduced = X_test[X_test.columns.values[(np.argsort(importances)[::-1])[:5]]]

# Train on the "best" model found from grid search earlier
clf = (clone(best_clf)).fit(X_train_reduced, y_train)

# Make new predictions
reduced_predictions = clf.predict(X_test_reduced)

# Report scores from the final model using both versions of data
print "Final Model trained on full data\n------"
print "Accuracy on testing data: {:.4f}".format(accuracy_score(y_test, best_predictions))
print "F-score on testing data: {:.4f}".format(fbeta_score(y_test, best_predictions, beta = 0.5))
print "\nFinal Model trained on reduced data\n------"
print "Accuracy on testing data: {:.4f}".format(accuracy_score(y_test, reduced_predictions))
print "F-score on testing data: {:.4f}".format(fbeta_score(y_test, reduced_predictions, beta = 0.5))


Final Model trained on full data
------
Accuracy on testing data: 0.8559
F-score on testing data: 0.7271

Final Model trained on reduced data
------
Accuracy on testing data: 0.8198
F-score on testing data: 0.6324

Question 8 - Effects of Feature Selection

How does the final model's F-score and accuracy score on the reduced data using only five features compare to those same scores when all features are used?
If training time was a factor, would you consider using the reduced data as your training set?

Answer:

The reduced data set produced results worse than the full data set which is to be expected. However, the reduced dataset had worst scores than the untuned model trained on the full data set.

In this particular scenario, I would not use a reduced data set. In general, there are many things I would consider before reducing my data set:

  • How much training time is actually reduced? If it only saves a few seconds, why bother? If it saves hours to months, then possibly.
  • How many features are being left out? What are those features? In this problem, features such as 'Name' or 'Height' are probably safe to remove without impacting the score very much.
  • Is a drop in performance acceptable? In cases such as a recommender system, it probably doesn't matter too much if the accuracy drops a few percent. However in higher-risk situations such as fraud detection or self-driving cars, every percent matters.
  • Can the training be done in parallel? If yes, I could just throw more hardware at the problem.

Note: Once you have completed all of the code implementations and successfully answered each question above, you may finalize your work by exporting the iPython Notebook as an HTML document. You can do this by using the menu above and navigating to
File -> Download as -> HTML (.html). Include the finished document along with this notebook as your submission.