In this project, we will employ several supervised algorithms of our choice to accurately model individuals' income using data collected from the 1994 U.S. Census. We 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.
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.
# 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))
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.
# TODO: Total number of records
n_records = data.shape[0]
# TODO: Number of records where individual's income is more than $50,000
n_greater_50k = np.sum(data['income'] == '>50K')
# TODO: Number of records where individual's income is at most $50,000
n_at_most_50k = np.sum(data['income'] == '<=50K')
# TODO: Percentage of individuals whose income is more than $50,000
greater_percent = 100 * (n_greater_50k/(n_greater_50k+n_at_most_50k))
# 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: {}%".format(greater_percent))
Featureset Exploration
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.
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'
.
# 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.
# Log-transform the skewed features
skewed = ['capital-gain', 'capital-loss']
features_log_transformed = pd.DataFrame(data = features_raw)
features_log_transformed[skewed] = features_raw[skewed].apply(lambda x: np.log(x + 1))
# Visualize the new log distributions
vs.distribution(features_log_transformed, transformed = True)
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.
# Import sklearn.preprocessing.StandardScaler
from sklearn.preprocessing import MinMaxScaler
# Initialize a scaler, then apply it to the features
scaler = MinMaxScaler() # default=(0, 1)
numerical = ['age', 'education-num', 'capital-gain', 'capital-loss', 'hours-per-week']
features_log_minmax_transform = pd.DataFrame(data = features_log_transformed)
features_log_minmax_transform[numerical] = scaler.fit_transform(features_log_transformed[numerical])
# Show an example of a record with scaling applied
display(features_log_minmax_transform.head(n = 5))
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.
# TODO: One-hot encode the 'features_log_minmax_transform' data using pandas.get_dummies()
#non_numerical = ['workclass','education_level','marital-status','occupation','relationship','race','sex','native-country']
features_final = pd.get_dummies(features_log_minmax_transform)
# TODO: Encode the 'income_raw' data to numerical values
income = (income_raw == '>50K')
income = income.astype(dtype = int)
# Print the number of features after one-hot encoding
encoded = list(features_final.columns)
print("{} total features after one-hot encoding.".format(len(encoded)))
# Uncomment the following line to see the encoded feature names
# print(encoded)
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.
# Import train_test_split
from sklearn.model_selection 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_final,
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]))
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.
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.
Accuracy measures how often the classifier makes the correct prediction. It’s the ratio of the number of correct predictions to the total number of predictions (the number of test data points).
Precision tells us what proportion of messages we classified as spam, actually were spam. It is a ratio of true positives(words classified as spam, and which are actually spam) to all positives(all words classified as spam, irrespective of whether that was the correct classificatio), in other words it is the ratio of
[True Positives/(True Positives + False Positives)]
Recall(sensitivity) tells us what proportion of messages that actually were spam were classified by us as spam. It is a ratio of true positives(words classified as spam, and which are actually spam) to all the words that were actually spam, in other words it is the ratio of
[True Positives/(True Positives + False Negatives)]
For classification problems that are skewed in their classification distributions like in our case, for example if we had a 100 text messages and only 2 were spam and the rest 98 weren't, accuracy by itself is not a very good metric. We could classify 90 messages as not spam(including the 2 that were spam but we classify them as not spam, hence they would be false negatives) and 10 as spam(all 10 false positives) and still get a reasonably good accuracy score. For such cases, precision and recall come in very handy. These two metrics can be combined to get the F1 score, which is weighted average(harmonic mean) of the precision and recall scores. This score can range from 0 to 1, with 1 being the best possible F1 score(we take the harmonic mean as we are dealing with ratios).
'accuracy'
and 'fscore'
to be used later.Please note that the the purpose of generating a naive predictor is simply to show what a base model without any intelligence would look like. In the real world, ideally your base model would be either the results of a previous model or could be based on a research paper upon which you are looking to improve. When there is no benchmark model set, getting a result better than random choice is a place you could start from.
'''
TP = np.sum(income) # Counting the ones as this is the naive case. Note that 'income' is the 'income_raw' data
encoded to numerical values done in the data preprocessing step.
FP = income.count() - TP # Specific to the naive case
TN = 0 # No predicted negatives in the naive case
FN = 0 # No predicted negatives in the naive case
'''
from sklearn.metrics import accuracy_score
from sklearn.metrics import precision_score
from sklearn.metrics import recall_score
# TODO: Calculate accuracy, precision and recall
income_pred = np.ones(shape=income.shape)
accuracy = accuracy_score(income,income_pred)
precision = precision_score(income,income_pred)
recall = recall_score(income,income_pred)
# TODO: Calculate F-score using the formula above for beta = 0.5 and correct values for precision and recall.
beta=0.5
fscore = ((1+beta*beta)*(precision*recall))/((beta*beta*precision)+recall)
# Print the results
print("Naive Predictor: [Accuracy score: {:.4f}, F-score: {:.4f}]".format(accuracy, fscore))
To properly evaluate the performance of each model you've chosen, it's important that we create a training and predicting pipeline that allows us to quickly and effectively train models using various sizes of training data and perform predictions on the testing data. Our implementation here will be used in the following section.
# 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' using .fit(training_features[:], training_labels[:])
start = time() # Get start time
learner = learner.fit(X_train[0:sample_size],y_train[0:sample_size])
end = time() # Get end time
# TODO: Calculate the training time
results['train_time'] = end-start
# TODO: Get the predictions on the test set(X_test),
# then get predictions on the first 300 training samples(X_train) using .predict()
start = time() # Get start time
predictions_test = learner.predict(X_test)
predictions_train = learner.predict(X_train[0:sample_size])
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 which is y_train[:300]
results['acc_train'] = accuracy_score(y_train[0:sample_size],predictions_train)
# TODO: Compute accuracy on test set using accuracy_score()
results['acc_test'] = accuracy_score(y_test,predictions_test)
# TODO: Compute F-score on the the first 300 training samples using fbeta_score()
results['f_train'] = fbeta_score(y_train[0:sample_size],predictions_train,0.5)
# TODO: Compute F-score on the test set which is y_test
results['f_test'] = fbeta_score(y_test,predictions_test,0.5)
# Success
print("{} trained on {} samples.".format(learner.__class__.__name__, sample_size))
# Return the results
return results
In the code cell, you will need to implement the following:
Note: Depending on which algorithms we chose, the following implementation may take some time to run!
# TODO: Import the three supervised learning models from sklearn
from sklearn.ensemble import AdaBoostClassifier
from sklearn.linear_model import SGDClassifier
from sklearn.svm import SVC
# TODO: Initialize the three models
clf_A = AdaBoostClassifier(random_state=42)
clf_B = SGDClassifier(loss ='perceptron',random_state = 42)
clf_C = SVC(random_state = 42)
# TODO: Calculate the number of samples for 1%, 10%, and 100% of the training data
# HINT: samples_100 is the entire training set i.e. len(y_train)
# HINT: samples_10 is 10% of samples_100 (ensure to set the count of the values to be `int` and not `float`)
# HINT: samples_1 is 1% of samples_100 (ensure to set the count of the values to be `int` and not `float`)
samples_100 = int(len(y_train))
samples_10 = int(0.1 * len(y_train))
samples_1 = int(0.01 * len(y_train))
# 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)
In this final section, we will choose from the three supervised learning models the best model to use on the student data. We 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.
Answer:
The above graph gives us a great intuition about the working of the three models that we chose namely, the perceptron classifier, the SVM classifier and the Adaboost classifier using the decision stump. As mentioned earlier the SVM classifier takes the maximum time when 100% of the training data is used.The green bar in the training and predicting time figure is manifolds greater than both the AdaBoost and the SGDC classifiers. Also if we look at the f-1 score for training and testing data when 100% of the dataset is used the AdaBoost and the SVM classifiers produce almost the same result. However if we take into consideration the training and prediction time we would definitely rule out the SVM classifier mainly due to the time is take for the algorithm to run and also owing to the fact that AdaBoost produces similar results. Also if we consider all the training and testing data sizes( 1%, 10% and 100%) the AdaBoost algorithm produces higher or almost the same f-1 scores as the SVM classifier and as a result of this I think that the AdaBoost classifier would be the best suited classifier for identifying individuals that make more than $50,000.
The above mentioned reasons also throw light to the fact that AdaBoost algorithm which gave us the highest f-1 scores on all sizes of dataset would be better at extracting the hidden attribute importances and therby would generalize well on the unseen data. Thus in conclusion AdaBoost is the best classifier that we can use in our urrent situation.
Answer:
The AdaBoost algorithm works by fitting a sequence of weak learners on data that is being modified at every iteration of those fittings of weak learners. At the end of the algorithm the predictions are made by combining all those weak models through a weighted sum. The process takes place as follows:
TRAINING: At the start of the training a weak decision tree classifier with depths as low as 1 is used to fit the data in such a way that minimum error is produced. After that all the correctly and incorrectly classified points are counted and the weights of the incorrectly classified points are modified in such a way that the total weight of correctly and incorrectly classified points become equal(This increase in weight is done to make sure that the next weak classifier classifies those incorrectly classified points perfectly when the fitting is done again.) The above mentioned process continues till there are no misclassified points or till maximum iteration is reached. Thus at the end of the training session we have a certain number of weak classifiers which we combine in the prediction step.
COMBINING THE MODELS: As mentioned in the training step above we created a certain number of weak classifiers. There is a weight associated with every such model. This weight can be any real number. For every such model the area classified as positive is given a positive value of the corresponding weight and the areas classified as negative are given negative value of the corresponding weight. After doing this all the models are combined and a weighted sum of all the regions is taken. In the end certain areas of the final model will have values of weights greater than zero and certain areas wile have values of weights less than zero.
PREDICTION: Finally any point that belongs to a positive area of the final model is classified as positive and any model belonging to the negative areas is classified as negative.
Thus by using many weak models and combining them we made a complex model that can classify data points well enough than not only a Naive classifier but also better and more efficiently than non-linear classifiers like SVM.
# TODO: Import 'GridSearchCV', 'make_scorer', and any other necessary libraries
from sklearn.metrics import make_scorer
from sklearn.model_selection import GridSearchCV
from sklearn.model_selection import ShuffleSplit
# TODO: Initialize the classifier
clf = AdaBoostClassifier(random_state=42)
# TODO: Create the parameters list you wish to tune, using a dictionary if needed.
# HINT: parameters = {'parameter_1': [value1, value2], 'parameter_2': [value1, value2]}
n_estimators = [int(x) for x in np.linspace(start = 100, stop = 500, num = 10)]
learning_rate = list(np.arange(0.5,2,0.2))
parameters = {'n_estimators': n_estimators,'learning_rate': learning_rate}
# TODO: Make an fbeta_score scoring object using make_scorer()
scorer = make_scorer(fbeta_score,beta = 0.5)
# TODO: Perform grid search on the classifier using 'scorer' as the scoring method using GridSearchCV()
grid_obj = GridSearchCV(clf,parameters,scoring=scorer)
# TODO: Fit the grid search object to the training data and find the optimal parameters using fit()
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)))
Metric | Naive Model | Unoptimized Model | Optimized Model |
---|---|---|---|
Accuracy Score | 0.2478 | 0.8576 | 0.8677 |
F-score | 0.2917 | 0.7246 | 0.7457 |
Answer:
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.
We will 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 we will fit this classifier to training set and use this attribute to determine the top 5 most important features for the census dataset.
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, the 5 features that we believe to be the most important for prediction are in the given order:
Answer:
The following are the top five features that I consider most important:
OCCUPATION(1) : Occupation comes at the topmost of the list because the income of a person is directly related to what a person does and certain occupations like doctor, lawyers etc. tend to make more money than their counterparts. Also since we are targeting people with salaries greater than 50K the occupation of a person gives us good insights. For example(A person at managerial role will have salaries higher than a person who is in a clerical position)
WORK_CLASS(2) : Work class is another important feature which can give us good insights about a person's salary. For example. A person working for a private sector company is definitely going to earn more than a person who works for a local government. I have onsidered the second most important feature because whatever the occupation of a person is, his salary greatly depends on the work_class he works in.(For eg. A doctor in private hospital is going to earn more than a doctor in public hospital)
EDUCATION (3) : Generally people who tend to have a good education also tend to make more money. A person with a Phd is definitely going to make more money than a high-school graduate. Thus education is an important feature in determining a person's salary. This feature is third in the list as I think its not always necessary that a person with good education is successful. We have good good examples of dropouts who have made it better than their graduate counter parts.
HOURS_PER_WEEK(4): The more a person works the more is his or hers' income and hece the number of hours a person works in a week gives us a meaningful insight of his or her's salary. However this feature is fourth in the list because sometimes a person may be working 40 hours a week on minimum wages while on the other hand we may have a person working 20 hours part time with thrice the hourly minimum wage and in such a case the salary of the person working part-time is more than his full time counterpart. Hence the hours_per_week feature is subjective and it depends more on the occupation of the person.
CAPITAL_GAIN (5): Capital gain indicates a profit from a sale of property or an investment. Thus we can reasonably say that higer the capital gain higher is the income of that person and he is more likely to make an investment. I have ranked this feature at the bottom of the list because I think that a person other than a reasl estate businessman is less likely to sell his property or investments and hence capital gain is not an event that occurs as usually as other events.
# TODO: Import a supervised learning model that has 'feature_importances_'
# TODO: Train the supervised model on the training set
#AdaBoostClassifier(random_state=0)
model = AdaBoostClassifier(random_state=0,n_estimators=500).fit(X_train, y_train)
# TODO: Extract the feature importances
importances = model.feature_importances_
# Plot
vs.feature_plot(importances, X_train, y_train)
Observing the visualization created above which displays the five most relevant features for predicting if an individual makes at most or above \$50,000, we will try to answer the following questions.
Answer:
The visualizations above are quite different than the ones predicted by me. My prediction was only partially right. Out of the five features predicted by me , 3 of them seem to pop up in the visualization above, though not in the same order.
I was not that close to the answer as my prediction's order were far off from the order presented in the visualization.
The reason I think I could not capture the truly important features is because I did not have a good insight of the data. Since the algorithm that I have performed above takes the insight of the data with mathematical manipulations, I think these machine learning algorithms better capture the true underlying importance of the individual features. Also as mentioned earlier I think capital-gain and capital-loss are events that do not occur often for a normal person and as a result they are given the least cumulative feature weight from the top five features selected. A younger person will definitely have lesser experience than a person who is older and we have seen in job market that people with more experience tend to make more money than people with less experience. After this no matter what the experience of the person, if a person with higher experience works less hours per week while a person with less experience works more hours, there are chances that a less experienced person will make more money than his counterpart and hence 'hours_per_week' has higher feature importance than 'age'. Finally the education number has highest cumulaive feature weight from the top five selected feature and it makes sense because a person with a higher education number will be highly qualified than person with lower education number and no matter how many hours per week he works or what his age is, he is qoing to make more money than his counterparts.
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 we found earlier, and train it on the same training set with only the top five important features.
# 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)))
Answer:
Metric | Final Model(Full data) | Final Model(Reduced data) |
---|---|---|
Accuracy Score | 0.8677 | 0.8421 |
F-score | 0.7457 | 0.7017 |
As we can see from the table above the accuracy of the final model with reduced data is almost 3% lesser than the model with full data whereas the F-score of reduced model is approximately 4% less than the F-score of model with full data. However the accuracy and f-score of the reduced data model is still very high as compared to the naive model. This reduction in model performance should not come as a shock, because what we are doing with reduced data model is removing or reducing information. Intuitively anything which has less information is always going to perform poorly than anything that has comparitivly more information. Thus no matter how less important the other features are, if we remove those features the model performance will be affected negatively to some level.
Feature removal should never be done when training the data does not take more time because removing information without any reason makes no sense. However in real world some datasets are huge and as we saw above there are certain algorithms like SVM which take a lot of time to train on large datasets and if we are working with real time applications we cannot afford such high training time, under such circumstances we should trade performance in favour of training time, however if the applications are life altering(For eg. Medical applications) then we should never compromise the performance of the model. Thus feature reduction is subjective and it depends highly on the application
!!jupyter nbconvert *.ipynb