Case Study

Choosing Feature Reduction for a Sensor Fault Classifier

Case context: You are building a fault-detection model for industrial sensors using only 300 labeled machine records. Each record has 8,000 candidate features. The model is overfitting, so your teammate proposes either removing just 300 features or compressing the feature set by a factor of 10 to about 800 features.

Question: As a practitioner, how should you assess these two feature-reduction ideas, and which option is more defensible given the small training set?

Sample answer: With such a small training set, feature selection or feature reduction is a sensible way to lower variance. That said, removing only 300 of 8,000 features is unlikely to change model behavior very much, so it probably will not solve the overfitting problem. Cutting the feature set to about 800 features is much more likely to reduce variance in a noticeable way, but it must be done carefully because dropping useful predictors can raise bias. In this situation, the larger reduction is the stronger choice, as long as the retained features still capture the important signal.

Key points:

  • Feature reduction is especially useful when labeled data is scarce.
  • A tiny reduction usually has little effect on variance.
  • A much larger reduction is more likely to change generalization noticeably.
  • Aggressive reduction must be done carefully to avoid losing important information and increasing bias.

Rubric: Award full credit if the response explains that feature reduction is appropriate for a small dataset, notes that a minor reduction will probably not help much, and states that a larger reduction is more likely to address variance but may increase bias if important features are removed.

0

1

Updated 2026-08-12

Contributors are:

Who are from:

Tags

Machine Learning

Deep Learning

Supervised Learning

Dive into Deep Learning @ D2L

Data Science

Machine Learning Strategy

Machine Learning Yearning @ DeepLearning.AI