Feature Crosses

By: Sören Dobberschütz

Re-posted from: https://tensorflowjulia.blogspot.com/2018/08/feature-crosses.html

The next part of the Machine Learning Crash Course deals with constructing bucketized features and feature crosses. The Jupyter notebook can be downloaded here

We use quantiles to put the feature data into different categories. This is done in the functions get_quantile_based_boundaries and construct_bucketized_column. To construct one hot feature columns, we use construct_bucketized_onehot_column. The drawback of these methods is that they loop through the whole dataset for conversion, which is computationally very expensive. Leave a comment if you have an idea for a better method!

Another difference from the original programming exercise is the use of the Adam Optimizer instead of the FTLR Optimizer. To my knowledge, TensorFlow.jl exposes only the following optimizers:

  • Gradient Descent
  • Momentum Optimizer
  • Adam Optimizer
On the other hand, (at least) the following possibilities are available in TensorFlow itself:
  • Gradient Descent
  • Momentum Optimizer
  • Adagrad Optimizer
  • Adadelta Optimizer
  • Adam Optimizer
  • Ftrl Optimizer
  • RMSProp Optimizer

Some information on those can be found here. For a more technical discussion with lots of background infos, have a look at this excellent blog post. If you know how to get other optimizers to work in Julia, I would be very interested.











This notebook is based on the file Feature crosses programming exercise, which is part of Google’s Machine Learning Crash Course.
In [0]:
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# https://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

Feature Crosses

Learning Objectives:
  • Improve a linear regression model with the addition of additional synthetic features (this is a continuation of the previous exercise)
  • Use an input function to convert DataFrame objects to feature columns
  • Use the Adam optimization algorithm for model training
  • Create new synthetic features through one-hot encoding, binning, and feature crosses

Setup

First, as we’ve done in previous exercises, let’s define the input and create the data-loading code.
In [1]:
using Plots
gr()
using DataFrames
using TensorFlow
import CSV
import StatsBase

sess=Session()
california_housing_dataframe = CSV.read("california_housing_train.csv", delim=",");
california_housing_dataframe = california_housing_dataframe[shuffle(1:size(california_housing_dataframe, 1)),:];
In [2]:
function preprocess_features(california_housing_dataframe)
"""Prepares input features from California housing data set.

Args:
california_housing_dataframe: A DataFrame expected to contain data
from the California housing data set.
Returns:
A DataFrame that contains the features to be used for the model, including
synthetic features.
"""
selected_features = california_housing_dataframe[
[:latitude,
:longitude,
:housing_median_age,
#:total_rooms,
#:total_bedrooms,
#:population,
:households,
:median_income]]
processed_features = selected_features
# Create a synthetic feature.
processed_features[:rooms_per_person] = (
california_housing_dataframe[:total_rooms] ./
california_housing_dataframe[:population])
return processed_features
end

function preprocess_targets(california_housing_dataframe)
"""Prepares target features (i.e., labels) from California housing data set.

Args:
california_housing_dataframe: A DataFrame expected to contain data
from the California housing data set.
Returns:
A DataFrame that contains the target feature.
"""
output_targets = DataFrame()
# Scale the target to be in units of thousands of dollars.
output_targets[:median_house_value] = (
california_housing_dataframe[:median_house_value] ./ 1000.0)
return output_targets
end
Out[2]:
preprocess_targets (generic function with 1 method)
2018-08-20 19:01:33.349400: I tensorflow/core/platform/cpu_feature_guard.cc:140] Your CPU supports instructions that this TensorFlow binary was not compiled to use: SSE4.2 AVX AVX2 FMA
In [3]:
# Choose the first 12000 (out of 17000) examples for training.
training_examples = preprocess_features(head(california_housing_dataframe,12000))
training_targets = preprocess_targets(head(california_housing_dataframe,12000))

# Choose the last 5000 (out of 17000) examples for validation.
validation_examples = preprocess_features(tail(california_housing_dataframe,5000))
validation_targets = preprocess_targets(tail(california_housing_dataframe,5000))

# Double-check that we've done the right thing.
println("Training examples summary:")
describe(training_examples)
println("Validation examples summary:")
describe(validation_examples)

println("Training targets summary:")
describe(training_targets)
println("Validation targets summary:")
describe(validation_targets)
Training examples summary:
Out[3]:
variable mean min median max nunique nmissing eltype
1 median_house_value 206.395 22.5 179.55 500.001 Float64
Validation examples summary:
Training targets summary:
Validation targets summary:
In [4]:
function construct_feature_columns(input_features)
"""Construct the TensorFlow Feature Columns.

Args:
input_features: The names of the numerical input features to use.
Returns:
A set of feature columns
"""
out=convert(Array, input_features[:,:])
return convert.(Float64,out)
end
Out[4]:
construct_feature_columns (generic function with 1 method)
In [5]:
function create_batches(features, targets, steps, batch_size=5, num_epochs=0)
"""Create batches.

Args:
features: Input features.
targets: Target column.
steps: Number of steps.
batch_size: Batch size.
num_epochs: Number of epochs, 0 will let TF automatically calculate the correct number
Returns:
An extended set of feature and target columns from which batches can be extracted.
"""
if(num_epochs==0)
num_epochs=ceil(batch_size*steps/size(features,1))
end

names_features=names(features);
names_targets=names(targets);

features_batches=copy(features)
target_batches=copy(targets)


for i=1:num_epochs

select=shuffle(1:size(features,1))

if i==1
features_batches=(features[select,:])
target_batches=(targets[select,:])
else

append!(features_batches, features[select,:])
append!(target_batches, targets[select,:])
end
end

return features_batches, target_batches
end
Out[5]:
create_batches (generic function with 3 methods)
In [6]:
function next_batch(features_batches, targets_batches, batch_size, iter)
"""Next batch.

Args:
features_batches: Features batches from create_batches.
targets_batches: Target batches from create_batches.
batch_size: Batch size.
iter: Number of the current iteration
Returns:
An extended set of feature and target columns from which batches can be extracted.
"""
select=mod((iter-1)*batch_size+1, size(features_batches,1)):mod(iter*batch_size, size(features_batches,1));

ds=features_batches[select,:];
target=targets_batches[select,:];

return ds, target
end
Out[6]:
next_batch (generic function with 1 method)
In [7]:
function my_input_fn(features_batches, targets_batches, iter, batch_size=5, shuffle_flag=1):
"""Trains a linear regression model of one feature.

Args:
features: DataFrame of features
targets: DataFrame of targets
batch_size: Size of batches to be passed to the model
shuffle: True or False. Whether to shuffle the data.
num_epochs: Number of epochs for which data should be repeated. None = repeat indefinitely
Returns:
Tuple of (features, labels) for next data batch
"""

# Construct a dataset, and configure batching/repeating.
#ds = Dataset.from_tensor_slices((features,targets)) # warning: 2GB limit
ds, target = next_batch(features_batches, targets_batches, batch_size, iter)

# Shuffle the data, if specified.
if shuffle_flag==1
select=shuffle(1:size(ds, 1));
ds = ds[select,:]
target = target[select, :]
end

# Return the next batch of data.
# features, labels = ds.make_one_shot_iterator().get_next()
return ds, target
end
Out[7]:
my_input_fn (generic function with 3 methods)

Adam Optimization Algorithm

High dimensional linear models benefit from using a variant of gradient-based optimization called Adam optimization. This algorithm has the benefit of scaling the learning rate differently for different coefficients, which can be useful if some features rarely take non-zero values.
In [8]:
function train_model(learning_rate,
steps,
batch_size,
feature_column_function::Function,
training_examples,
training_targets,
validation_examples,
validation_targets)
"""Trains a linear regression model of one feature.

Args:
learning_rate: A `float`, the learning rate.
steps: A non-zero `int`, the total number of training steps. A training step
consists of a forward and backward pass using a single batch.
batch_size: A non-zero `int`, the batch size.
feature_column_function: Function for transforming the feature columns.
training_examples:
training_targets:
validation_examples:
validation_targets:
Returns:
weight: The weights of the model.
bias: Bias of the model.
p1: Graph containing the loss function values for the different iterations.
"""

periods = 10
steps_per_period = steps / periods

# Create feature columns.
feature_columns = placeholder(Float32)
target_columns = placeholder(Float32)

# Create a linear regressor object.
m=Variable(zeros(size(feature_column_function(training_examples),2),1))
b=Variable(0.0)
y=(feature_columns*m) .+ b
loss=reduce_sum((target_columns - y).^2)

features_batches, targets_batches = create_batches(training_examples, training_targets, steps, batch_size)

# Set up Adam optimizer
my_optimizer=(train.AdamOptimizer(learning_rate))
gvs = train.compute_gradients(my_optimizer, loss)
capped_gvs = [(clip_by_norm(grad, 5.), var) for (grad, var) in gvs]
my_optimizer = train.apply_gradients(my_optimizer,capped_gvs)
run(sess, global_variables_initializer())

# Train the model, but do so inside a loop so that we can periodically assess
# loss metrics.
println("Training model...")
println("RMSE (on training data):")
training_rmse = []
validation_rmse=[]
for period in 1:periods
# Train the model, starting from the prior state.
for i=1:steps_per_period
features, labels = my_input_fn(features_batches, targets_batches, convert(Int,(period-1)*steps_per_period+i), batch_size)
run(sess, my_optimizer, Dict(feature_columns=>feature_column_function(features), target_columns=>construct_feature_columns(labels)))
end
# Take a break and compute predictions.
training_predictions = run(sess, y, Dict(feature_columns=> feature_column_function(training_examples)));
validation_predictions = run(sess, y, Dict(feature_columns=> feature_column_function(validation_examples)));

# Compute loss.
training_mean_squared_error = mean((training_predictions- construct_feature_columns(training_targets)).^2)
training_root_mean_squared_error = sqrt(training_mean_squared_error)
validation_mean_squared_error = mean((validation_predictions- construct_feature_columns(validation_targets)).^2)
validation_root_mean_squared_error = sqrt(validation_mean_squared_error)
# Occasionally print the current loss.
println(" period ", period, ": ", training_root_mean_squared_error)
# Add the loss metrics from this period to our list.
push!(training_rmse, training_root_mean_squared_error)
push!(validation_rmse, validation_root_mean_squared_error)
end

weight = run(sess,m)
bias = run(sess,b)

println("Model training finished.")

# Output a graph of loss metrics over periods.
p1=plot(training_rmse, label="training", title="Root Mean Squared Error vs. Periods", ylabel="RMSE", xlabel="Periods")
p1=plot!(validation_rmse, label="validation")

println("Final RMSE (on training data): ", training_rmse[end])
println("Final Weight (on training data): ", weight)
println("Final Bias (on training data): ", bias)

return weight, bias, p1 #, calibration_data
end
Out[8]:
train_model (generic function with 1 method)
In [9]:
weight, bias, p1 = train_model(
# TWEAK THESE VALUES TO SEE HOW MUCH YOU CAN IMPROVE THE RMSE
0.003, #learning rate
500, #steps
5, #batch_size
construct_feature_columns, # feature column function
training_examples,
training_targets,
validation_examples,
validation_targets)
Training model...
RMSE (on training data):
period 1: 165.18692421457004
period 2: 145.60713458568068
period 3: 142.433078624291
period 4: 134.75421062357708
period 5: 130.1562366092935
period 6: 127.09267658400229
period 7: 123.3747359316491
period 8: 120.42333195391147
period 9: 118.18552801954465
period 10: 117.1353141583384
Model training finished.
Final RMSE (on training data): 117.1353141583384
Final Weight (on training data):
Out[9]:
([0.762966; -0.789043; … ; 1.01543; 0.84879], 0.5041953427446556, Plot{Plots.GRBackend() n=2})
[0.762966; -0.789043; 0.750761; 0.099341; 1.01543; 0.84879]
Final Bias (on training data): 0.5041953427446556
In [10]:
plot(p1)
Out[10]:
246810120130140150160Root Mean Squared Error vs. PeriodsPeriodsRMSEtrainingvalidation

One-Hot Encoding for Discrete Features

Discrete (i.e. strings, enumerations, integers) features are usually converted into families of binary features before training a logistic regression model.
For example, suppose we created a synthetic feature that can take any of the values 01 or 2, and that we have a few training points:
# feature_value
0 2
1 0
2 1
For each possible categorical value, we make a new binary feature of real values that can take one of just two possible values: 1.0 if the example has that value, and 0.0 if not. In the example above, the categorical feature would be converted into three features, and the training points now look like:
# feature_value_0 feature_value_1 feature_value_2
0 0.0 0.0 1.0
1 1.0 0.0 0.0
2 0.0 1.0 0.0

Bucketized (Binned) Features

Bucketization is also known as binning.
We can bucketize population into the following 3 buckets (for instance):
  • bucket_0 (< 5000): corresponding to less populated blocks
  • bucket_1 (5000 - 25000): corresponding to mid populated blocks
  • bucket_2 (> 25000): corresponding to highly populated blocks
Given the preceding bucket definitions, the following population vector:
[[10001], [42004], [2500], [18000]]

becomes the following bucketized feature vector:
[[1], [2], [0], [1]]

The feature values are now the bucket indices. Note that these indices are considered to be discrete features. Typically, these will be further converted in one-hot representations as above, but this is done transparently.
The following code defines bucketized feature columns for households and longitude; the get_quantile_based_boundaries function calculates boundaries based on quantiles, so that each bucket contains an equal number of elements.
In [12]:
function get_quantile_based_boundaries(feature_values, num_buckets)
#Investigate why [:] is necessary - there is some conflict that construct_feature_columns
# spits out Array{Float64,2} where it should be Array{Float64,1}!!
quantiles = StatsBase.nquantile(construct_feature_columns(feature_values)[:], num_buckets)
return quantiles# [quantiles[q] for q in keys(quantiles)]
end
Out[12]:
get_quantile_based_boundaries (generic function with 1 method)
In [13]:
function construct_bucketized_column(input_features, boundaries)

data_out=zeros(size(input_features))

for i=1:size(input_features,2)
curr_feature=input_features[:,i]
curr_boundary=boundaries[i]

for k=1:length(curr_boundary)
for j=1:size(input_features,1)
if(curr_feature[j] >= curr_boundary[k] )
data_out[j,i]+=1
end
end
end

end
return data_out
end
Out[13]:
construct_bucketized_column (generic function with 1 method)
We need a special function to convert the bucketized columns into a one-hot encoding. Contrary to the high-level API of Python’s TensorFlow, the Julia verion does not transparently handle buckets.
In [14]:
function construct_bucketized_onehot_column(input_features, boundaries)

length_out=0
for i=1:length(boundaries)
length_out+=length(boundaries[i])-1
end

data_out=zeros(size(input_features,1), length_out)

curr_index=1;
for i=1:size(input_features,2)
curr_feature=input_features[:,i]
curr_boundary=boundaries[i]

for k=1:length(curr_boundary)-1
for j=1:size(input_features,1)
if((curr_feature[j] >= curr_boundary[k]) && (curr_feature[j] < curr_boundary[k+1] ))
data_out[j,curr_index]+=1
end
end
curr_index+=1;
end
end
return data_out
end
Out[14]:
construct_bucketized_onehot_column (generic function with 1 method)
Let’s divide the household and longitude data into buckets.
In [15]:
# Divide households into 7 buckets.
households = california_housing_dataframe[:households]
bucketized_households = construct_bucketized_onehot_column(
households, [get_quantile_based_boundaries(
california_housing_dataframe[:households], 7)])

# Divide longitude into 10 buckets.
longitude = california_housing_dataframe[:longitude]
bucketized_longitude = construct_bucketized_onehot_column(
longitude, [get_quantile_based_boundaries(
california_housing_dataframe[:longitude], 10)])
Out[15]:
17000×10 Array{Float64,2}:
0.0 0.0 0.0 0.0 0.0 0.0 0.0 1.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0 1.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 1.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0 1.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 1.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 1.0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 1.0
0.0 0.0 0.0 0.0 0.0 1.0 0.0 0.0 0.0 0.0
0.0 0.0 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 1.0 0.0 0.0
0.0 0.0 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
0.0 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 1.0 0.0 0.0 0.0 0.0 0.0
⋮ ⋮
0.0 0.0 0.0 0.0 0.0 1.0 0.0 0.0 0.0 0.0
0.0 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 1.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0 1.0 0.0 0.0 0.0
0.0 0.0 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0 1.0 0.0 0.0 0.0
0.0 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 1.0 0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0 1.0 0.0 0.0 0.0
0.0 0.0 0.0 1.0 0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 1.0 0.0 0.0 0.0 0.0 0.0
1.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

Task 1: Train the Model on Bucketized Feature Columns

Bucketize all the real valued features in our example, train the model and see if the results improve.
In the preceding code block, two real valued columns (namely households and longitude) have been transformed into bucketized feature columns. Your task is to bucketize the rest of the columns, then run the code to train the model. There are various heuristics to find the range of the buckets. This exercise uses a quantile-based technique, which chooses the bucket boundaries in such a way that each bucket has the same number of examples.
In [16]:
quantiles_latitude=get_quantile_based_boundaries(
training_examples[:latitude], 10)
quantiles_longitude=get_quantile_based_boundaries(
training_examples[:longitude], 10)
quantiles_housing_median_age=get_quantile_based_boundaries(
training_examples[:housing_median_age], 7)
quantiles_households=get_quantile_based_boundaries(
training_examples[:households], 7)
quantiles_median_income=get_quantile_based_boundaries(
training_examples[:median_income], 7)
quantiles_rooms_per_person=get_quantile_based_boundaries(
training_examples[:rooms_per_person], 7)

quantiles_vec=[quantiles_latitude,
quantiles_longitude,
quantiles_housing_median_age,
quantiles_households,
quantiles_median_income,
quantiles_rooms_per_person
]
Out[16]:
6-element Array{Array{Float64,1},1}:
[32.54, 33.61, 33.86, 33.99, 34.09, 34.23, 36.594, 37.45, 37.8, 38.46, 41.95]
[-124.3, -122.28, -121.96, -121.33, -119.82, -118.47, -118.29, -118.11, -117.88, -117.24, -114.31]
[1.0, 15.0, 20.0, 26.0, 32.0, 36.0, 43.0, 52.0]
[1.0, 219.0, 299.0, 370.429, 452.0, 567.0, 769.0, 5189.0]
[0.4999, 2.12161, 2.69576, 3.2396, 3.83023, 4.55251, 5.64087, 15.0001]
[0.0180649, 1.24429, 1.59343, 1.8458, 2.04249, 2.24242, 2.52746, 52.0333]
In [17]:
weight, bias, p1 = train_model(
# TWEAK THESE VALUES TO SEE HOW MUCH YOU CAN IMPROVE THE RMSE
0.03, #learning rate
2000, #steps
100, #batch_size
x -> construct_bucketized_onehot_column(x, quantiles_vec), # feature column function
training_examples,
training_targets,
validation_examples,
validation_targets)
Training model...
RMSE (on training data):
period 1: 203.99027582698028
period 2: 172.96922619791718
period 3: 146.28546842721346
period 4: 125.46594666991398
period 5: 110.82339478668447
period 6: 100.78134859112528
period 7: 93.67561117691986
period 8: 88.20419283221035
period 9: 84.03854619076178
period 10: 80.86092939616412
Model training finished.
Final RMSE (on training data): 80.86092939616412
Final Weight (on training data):
Out[17]:
([37.9549; 42.9262; … ; 49.6147; 61.6997], 49.13162981045757, Plot{Plots.GRBackend() n=2})
[37.9549; 42.9262; 21.6568; 45.2276; 45.7324; 11.1818; 38.2974; 49.1423; 22.5028; -26.9576; 50.5019; 44.7102; 25.9642; -13.2705; 19.3974; 57.7096; 31.1798; 34.2978; 22.4988; -7.29032; 19.5574; 24.064; 32.758; 32.8912; 32.5789; 30.6587; 32.3991; 31.8199; 30.078; 31.2015; 35.8298; 34.3732; 38.4314; 42.0378; -32.0522; -16.9641; 1.37737; 15.3621; 29.6987; 45.3425; 65.8817; -8.19134; -7.64355; 3.95525; 16.281; 34.7744; 49.6147; 61.6997]
Final Bias (on training data): 49.13162981045757
In [18]:
plot(p1)
Out[18]:
246810100125150175200Root Mean Squared Error vs. PeriodsPeriodsRMSEtrainingvalidation

Feature Crosses

Crossing two (or more) features is a clever way to learn non-linear relations using a linear model. In our problem, if we just use the feature latitude for learning, the model might learn that city blocks at a particular latitude (or within a particular range of latitudes since we have bucketized it) are more likely to be expensive than others. Similarly for the feature longitude. However, if we cross longitude by latitude, the crossed feature represents a well defined city block. If the model learns that certain city blocks (within range of latitudes and longitudes) are more likely to be more expensive than others, it is a stronger signal than two features considered individually.
If we cross the latitude and longitude features (supposing, for example, that longitude was bucketized into 2 buckets, while latitude has 3 buckets), we actually get six crossed binary features. Each of these features will get its own separate weight when we train the model.

Task 2: Train the Model Using Feature Crosses

Add a feature cross of longitude and latitude to your model, train it, and determine whether the results improve.
The following function creates a feature cross of latitude and longitude and then feeds it to the model.
In [19]:
function construct_latXlong_onehot_column(input_features, boundaries) 
#latitude and longitude are the first two columns - treat them separately

#initialization - calculate total length of feature_vec
length_out=0
# lat and long
length_lat=length(boundaries[1])-1
length_long= length(boundaries[2])-1
length_out+=length_lat*length_long
# all other features
for i=3:length(boundaries)
length_out+=length(boundaries[i])-1
end
data_out=zeros(size(input_features,1), length_out)

# all other features
curr_index=length_lat*length_long+1;
for i=3:size(input_features,2)
curr_feature=input_features[:,i]
curr_boundary=boundaries[i]
#println(curr_boundary)

for k=1:length(curr_boundary)-1
for j=1:size(input_features,1)
if((curr_feature[j] >= curr_boundary[k]) && (curr_feature[j] < curr_boundary[k+1] ))
data_out[j,curr_index]+=1
end
end
curr_index+=1;
end
end

# lat and long
data_temp=zeros(size(input_features,1), length_lat+length_long)
curr_index=1
for i=1:2
curr_feature=input_features[:,i]
curr_boundary=boundaries[i]
#println(curr_boundary)

for k=1:length(curr_boundary)-1
for j=1:size(input_features,1)
if((curr_feature[j] >= curr_boundary[k]) && (curr_feature[j] < curr_boundary[k+1] ))
data_temp[j,curr_index]+=1
end
end
curr_index+=1;
end
end

vec_temp=1
for j=1:size(input_features,1)
vec1=data_temp[j,1:length_lat]
vec2=data_temp[j, length_lat+1:length_lat+length_long]
vec_temp=vec1*vec2'
data_out[j, 1:length_lat*length_long]= (vec_temp)[:]
end

return data_out
end
Out[19]:
construct_latXlong_onehot_column (generic function with 1 method)
In [20]:
weight, bias, p1 = train_model(
# TWEAK THESE VALUES TO SEE HOW MUCH YOU CAN IMPROVE THE RMSE
0.03, #learning rate
2000, #steps
100, #batch_size
x -> construct_latXlong_onehot_column(x, quantiles_vec), # feature column function
training_examples,
training_targets,
validation_examples,
validation_targets)
Training model...
RMSE (on training data):
period 1: 209.21566659013052
period 2: 182.55539891794118
period 3: 158.44729613124915
period 4: 137.86642806744638
period 5: 121.32817880113157
period 6: 108.6493116164872
period 7: 99.09170377455486
period 8: 91.77973938058372
period 9: 86.04932155712561
period 10: 81.53891417185855
Model training finished.
Final RMSE (on training data): 81.53891417185855
Final Weight (on training data):
Out[20]:
([0.0; 0.0; … ; 52.3917; 62.3963], 55.198733343499036, Plot{Plots.GRBackend() n=2})
[0.0; 0.0; 0.0; 0.0; 0.0; 0.0; 12.8032; 59.9272; 42.0384; -21.4759; 0.0; 0.0; 0.0; 0.0; 0.0; 0.0; 55.85; 37.2605; 36.5099; -24.4953; 0.0; 0.0; 0.0; 0.0; 0.0; 28.3347; 45.555; 31.2541; 3.00366; -25.6861; 0.0; 0.0; 0.0; 0.0; 0.0; 17.133; -29.8488; -12.3567; -24.251; -11.0162; 0.0; 0.0; 11.5618; 41.1407; 43.5469; 10.7562; -37.9416; -1.07474; -5.6062; -3.0733; 12.6265; 43.9564; 42.7089; 56.6015; 50.1767; 16.5839; -5.31094; 0.0; 0.0; 0.0; 0.0; 36.2206; 6.0957; 23.758; 46.7966; 14.0951; -2.89199; 0.0; 0.0; 0.0; 8.96595; 41.1774; 27.788; 21.2633; 39.6985; -7.82365; -4.85104; 0.0; 0.0; 0.0; 47.293; 41.4496; 12.476; 0.323609; -1.33214; -22.7491; 0.0; 0.0; 0.0; 0.0; 9.07386; -7.64598; -15.8003; -1.22231; -22.7175; -20.1802; 0.0; 0.0; 0.0; 0.0; 26.6319; 29.5266; 37.746; 38.731; 39.474; 38.4757; 39.3764; 37.643; 37.0403; 38.1498; 40.8484; 40.4522; 42.6274; 46.9071; -22.2178; -6.88327; 11.3828; 24.7662; 36.8386; 49.2251; 66.1078; 4.34819; 3.83108; 14.7806; 25.4346; 40.8021; 52.3917; 62.3963]
Final Bias (on training data): 55.198733343499036
In [21]:
plot(p1)
Out[21]:
246810100125150175200Root Mean Squared Error vs. PeriodsPeriodsRMSEtrainingvalidation

Optional Challenge: Try Out More Synthetic Features

So far, we’ve tried simple bucketized columns and feature crosses, but there are many more combinations that could potentially improve the results. For example, you could cross multiple columns. What happens if you vary the number of buckets? What other synthetic features can you think of? Do they improve the model?