
A cheap, infrastructure-free way to catch the silent killer of validity — your eval set no longer matching what production actually sends your model.
“For years, I’ve relied on a straightforward method to identify sudden changes in model inputs or training data, known as “drift.””
“Your data for evaluations are materially different from the inputs your model receives in production, causing your evaluations to be misleading.”
“This method is so simple that it might seem uncool. You aren’t going to impress any data scientists. Despite this, it’s too valuable to ignore.”
“If the classifier demonstrates sufficient predictive power (ex: AUC >=0.60), we know there is drift.”
“If this process doesn’t detect drift, it doesn’t mean there isn’t drift. It just means that we couldn’t detect it with the model and features we used.”
Checking sign-in…
Loading comments…