ageron / ageron/handson-ml2

highly biased training/test split? (Chapter 2 - page 51)

Open
#344 1 comment 0 reactions 1 assignee Claimed by @ageron View on GitHub
Dominant language
Jupyter Notebook
Stars
30k
Forks
13.1k
PR merge metrics
No merged PRs in 30d

Description

On page 53, the author mentions

> [...] you can try to use the most stable features to build a unique identifier.

and then proceeds to build an id based on the latitude and longitude. However, several instances in the dataset have the same latitude and longitude and hence the same identifier, and therefore the same hash. Maybe I'm missing something, but doesn't this introduce a very strong algorithmic bias (if that's the right term) in the training set selection, in that instances with the same (latitude, longitude) will either always get placed in the same set (whether training or test)? Shouldn't we be using more features to compute a unique identifier?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.