294 lines
10 KiB
Markdown
294 lines
10 KiB
Markdown
# Data analytics: Feature engineering
|
||
|
||
<!--toc:start-->
|
||
- [Data analytics: Feature engineering](#data-analytics-feature-engineering)
|
||
- [Definition](#definition)
|
||
- [Sources of features](#sources-of-features)
|
||
- [Feature engineering in ML](#feature-engineering-in-ml)
|
||
- [Types of feature engineering](#types-of-feature-engineering)
|
||
- [Good feature:](#good-feature)
|
||
- [Related to objective (important)](#related-to-objective-important)
|
||
- [Known at prediction-time](#known-at-prediction-time)
|
||
- [Numeric with meaningful magnitude:](#numeric-with-meaningful-magnitude)
|
||
- [Have enough samples](#have-enough-samples)
|
||
- [Bring human insight to problem](#bring-human-insight-to-problem)
|
||
- [Methods of Feature Engineering](#methods-of-feature-engineering)
|
||
- [Scaling](#scaling)
|
||
- [Rationale:](#rationale)
|
||
- [Methods:](#methods)
|
||
- [Normalization or Standardization:](#normalization-or-standardization)
|
||
- [Min-max scaling:](#min-max-scaling)
|
||
- [Robust scaling:](#robust-scaling)
|
||
- [Choosing](#choosing)
|
||
- [Discretization / Binning / Bucketing](#discretization-binning-bucketing)
|
||
- [Definition](#definition)
|
||
- [Reason for binning](#reason-for-binning)
|
||
- [Methods](#methods)
|
||
- [Equal width binning](#equal-width-binning)
|
||
- [Equal frequency binning](#equal-frequency-binning)
|
||
- [k means binning](#k-means-binning)
|
||
- [decision trees](#decision-trees)
|
||
- [Encoding](#encoding)
|
||
- [Definition](#definition)
|
||
- [Reason](#reason)
|
||
- [Methods](#methods)
|
||
- [One hot encoding](#one-hot-encoding)
|
||
- [Ordinal encoding](#ordinal-encoding)
|
||
- [Count / frequency encoding](#count-frequency-encoding)
|
||
- [Mean / target encoding](#mean-target-encoding)
|
||
- [Transformation](#transformation)
|
||
- [Reasons](#reasons)
|
||
- [Methods](#methods)
|
||
- [Generation](#generation)
|
||
<!--toc:end-->
|
||
|
||
## Definition
|
||
|
||
- The process that attempts to create **additional** relevant features from
|
||
**existing** raw features, to increase the predictive power of **algorithms**
|
||
- Alternative definition: transfer raw data into features that **better
|
||
represent** the underlying problem, such that the accuracy of predictive model
|
||
is improved.
|
||
- Important to machine learning
|
||
|
||
## Sources of features
|
||
|
||
- Different features are needed for different problems, even in the same domain
|
||
|
||
## Feature engineering in ML
|
||
|
||
- Process of ML iterations:
|
||
- Baseline model -> Feature engineering -> Model 2 -> Feature engineering ->
|
||
Final
|
||
- Example: data needed to predict house price
|
||
- ML can do that with sufficient feature
|
||
- Reason for feature engineering: Raw data are rarely useful
|
||
- Must be mapped into a feature vector
|
||
- Good feature engineering takes the most time out of ML
|
||
|
||
### Types of feature engineering
|
||
|
||
- **Indicator** variable to isolate information
|
||
- Highlighting **interactions** between features
|
||
- Representing the feature in a **different** way
|
||
|
||
## Good feature:
|
||
|
||
### Related to objective (important)
|
||
|
||
- Example: the number of concrete blocks around it is not related to house
|
||
prices
|
||
|
||
### Known at prediction-time
|
||
|
||
- Some data could be known **immediately**, and some other data is not known in
|
||
**real time**: Can't feed the feature to a model, if it isn't present at
|
||
prediction time
|
||
- Feature definition shouldn't **change** over time
|
||
- Example: If the sales data at prediction time is only available within 3 days,
|
||
with a 3 day lag, then current sale data can't be used for training (that has
|
||
to predict with a 3-day old data)
|
||
|
||
### Numeric with meaningful magnitude:
|
||
|
||
- It does not mean that **categorical** features can't be used in training:
|
||
simply, they will need to be **transformed** through a process called
|
||
[encoding](#encoding)
|
||
- Example: Font category: (Arial, Times New Roman)
|
||
|
||
### Have enough samples
|
||
|
||
- Have at least five examples of any value before using it in your model
|
||
- If features tend to be poorly assorted and are unbalanced, then the trained
|
||
model will be biased
|
||
|
||
### Bring human insight to problem
|
||
|
||
- Must have a reason for this feature to be useful, needs **subject matter** and
|
||
**curious mind**
|
||
- This is an iterative process, need to use **feedback** from production usage
|
||
|
||
## Methods of Feature Engineering
|
||
|
||
### Scaling
|
||
|
||
#### Rationale:
|
||
|
||
- Leads to a better model, useful when data is uneven: $X1 >> X2$
|
||
|
||
#### Methods:
|
||
|
||
##### Normalization or Standardization:
|
||
|
||
- $𝑍 = \frac{𝑋−𝜇}{\sigma}$
|
||
- Re-scaled to have a standard normal distribution that centered around 0 with
|
||
SD of 1
|
||
- Will **compress** the value in the narrow range, if the variable is skewed, or
|
||
has outliers.
|
||
- This may impair the prediction
|
||
|
||
##### Min-max scaling:
|
||
|
||
- $X_{scaled} = \frac{X - min}{max - min}$
|
||
- Also will compress observation
|
||
|
||
##### Robust scaling:
|
||
|
||
- $X_{scaled} = \frac{X - median}{IQR}$
|
||
- IQR: Interquartile range
|
||
- Better at **preserving** the spread
|
||
|
||
#### Choosing
|
||
|
||
- If data is **not guassain like**, and has a **skewed distribution** or
|
||
outliers : Use **robust** scaling, as the other two will compress the data to
|
||
a narrow range, which is not ideal
|
||
- For **PCA or LDA**(distance or covariance calculation), better to use
|
||
**Normalization or Standardization**, since it will remove the effect of
|
||
numerical scale, on variance and covariance
|
||
- Min-Max scaling: is bound to 0-1, has same drawback as normalization, and new
|
||
data may be out of bound (out of original range). This is preferred when the
|
||
network prefer a 0-1 **scale**
|
||
|
||
### Discretization / Binning / Bucketing
|
||
|
||
#### Definition
|
||
|
||
- The process of transforming **continuous** variable into **discrete** ones, by
|
||
creating a set of continuous interval, that spans over the range of variable's
|
||
values
|
||
- ![binning diagram](./assets/4-analytics-binning.webp)
|
||
|
||
#### Reason for binning
|
||
|
||
- Example: Solar energy modeling
|
||
- Acceleration calculation, by binning, and reduce the number of simulation
|
||
needed
|
||
- Improves **performance** by grouping data with **similar attributes** and has
|
||
**similar predictive strength**
|
||
- Improve **non-linearity**, by being able to capture **non-linear patterns** ,
|
||
thus improving fitting power of model
|
||
- **Interpretability** is enhanced by grouping
|
||
- Reduce the impact of **outliers**
|
||
- Prevent **overfitting**
|
||
- Allow feature **interaction**, with **continuous** variables
|
||
|
||
#### Methods
|
||
|
||
##### Equal width binning
|
||
|
||
- Divide the scope into bins of the same width
|
||
- Con: is sensitive to skewed distribution
|
||
|
||
##### Equal frequency binning
|
||
|
||
- Divides the scope of possible values of variable into N bins, where each bin
|
||
carries the same **number** of observations
|
||
- Con: May disrupt the relationship with target
|
||
|
||
##### k means binning
|
||
|
||
- Use k-means to partition the values into clusters
|
||
- Con: need hyper-parameter tuning
|
||
|
||
##### decision trees
|
||
|
||
- Using decision trees to decide the best splitting points
|
||
- Observes which bin is more similar than other bins
|
||
- Con:
|
||
- may cause overfitting
|
||
- have a chance of failing: bad performance
|
||
|
||
### Encoding
|
||
|
||
#### Definition
|
||
|
||
- The inverse of binning: creating numerical values from categorical variables
|
||
|
||
#### Reason
|
||
|
||
- Machine learning algorithms require **numerical** input data, and this
|
||
converts **categorical** data to **numerical** data
|
||
|
||
#### Methods
|
||
|
||
##### One hot encoding
|
||
|
||
- Replace categorical variable (nominal) with different binary variables
|
||
- **Eliminates** **ordinality**: since categorical variables shouldn't be
|
||
ranked, otherwise the algorithm may think there's ordering between the
|
||
variables
|
||
- Improve performance by allowing model to capture the complex relationship
|
||
within the data, that may be **missed** if categorical variables are treated
|
||
as **single** entities
|
||
- Cons
|
||
- High dimensionality: make the model more complex, and slower to train
|
||
- Is sparse data
|
||
- May lead to overfitting, especially if there's too many categories and
|
||
sample size is small
|
||
- Usage:
|
||
- Good for algorithms that look at all features at the same time: neural
|
||
network, clustering, SVM
|
||
- Used for linear regression, but **keep k-1** binary variable to avoid
|
||
**multicollinearity**:
|
||
- In linear regression, the presence of all k binary variables for a
|
||
categorical feature (where k is the number of categories) introduces
|
||
perfect multicollinearity. This happens because the k-th variable is a
|
||
linear **combination** of the others (e.g., if "Red" and "Blue" are 0,
|
||
"Green" must be 1).
|
||
- Don't use for tree algorithms
|
||
|
||
##### Ordinal encoding
|
||
|
||
- Ordinal variable: comprises a finite set of discrete values with a **ranked**
|
||
ordering
|
||
- Ordinal encoding replaces the label by ordered number
|
||
- Does not add value to give the variable more predictive power
|
||
- Usage:
|
||
- For categorical data with ordinal meaning
|
||
|
||
##### Count / frequency encoding
|
||
|
||
- Replace occurrences of label with the count of occurrences
|
||
- Cons:
|
||
- Will have loss of unique categories: (if the two categories have same
|
||
frequency, they will be treated as the same)
|
||
- Doesn't handle unseen categories
|
||
- Overfitting, if low frequency in general
|
||
|
||
##### Mean / target encoding
|
||
|
||
- Replace the _value_ for every categories with the avg of _values_ for every
|
||
_category-value_ pair
|
||
- monotonic relationship between variable and target
|
||
- Don't expand the feature space
|
||
- Con: prone to overfitting
|
||
- Usage:
|
||
- High cardinality (the number of elements in a mathematical set) data, by
|
||
leveraging the target variable's statistics to retain predictive power
|
||
|
||
### Transformation
|
||
|
||
#### Reasons
|
||
|
||
- Linear/Logistic regression models has assumption between the predictors and
|
||
the outcome.
|
||
- Transformation may help create this relationship to avoid poor
|
||
performance.
|
||
- Assumptions:
|
||
- Linear dependency between the predictors and the outcome.
|
||
- Multivariate normality (every variable X should follow a Gaussian
|
||
distribution)
|
||
- No or little multicollinearity
|
||
- homogeneity of variance
|
||
- Example:
|
||
- assuming y > 0.5 lead to class 1, otherwise class 2
|
||
- ![page 1](./assets/4-analytics-line-regression.webp)
|
||
- ![page 2](./assets/4-analytics-line-regression-2.webp)
|
||
- Some other ML algorithms do not make any assumption, but still may benefit
|
||
from a better distributed data
|
||
|
||
#### Methods
|
||
|
||
### Generation
|