Live data from Hacker News

We investigated Amsterdam's attempt to build a 'fair' fraud detection model

lighthousereports.com

21–30 of 87 posts

Re: We investigated Amsterdam's attempt to build a 'fair' fraud detection model

#21

A big part of the difficulty of such an attempt is that we don't know the ground truth. A model is fair or unbiased if its performance is equally good for all groups. Meaning e.g. if 90% of cases of Arabs committing fraud are flagged as fraud, then 90% of cases of Danish people committing fraud should be flagged as fraud. The paper agrees on this. The issue is that we don't know how many Danish commit fraud, and we d…

[dead]

Re: We investigated Amsterdam's attempt to build a 'fair' fraud detection model

#22
> A more concerning limitation is that when the city re-ran parts of its analysis, it did not fully replicate its own data and results. For example, the city was unable to replicate its train and test split. Furthermore, the data related to the model after reweighting is not identical to what the city published in its bias report and although the results are substantively the same, the differences cannot be explained by mere rounding errors.

Very well written, but that last part id concerning and point to one part: did they hire interns? How cone they do not have systems? It just cast a big doubt on the whole experiment.

Re: We investigated Amsterdam's attempt to build a 'fair' fraud detection model

#23
> But the model designers were aware that features could be correlated with demographic groups in a way that would make them proxies.

There's a huge problem with people trying to use umbrella usage to predict flooding. Some people are trying to develop a computer model that uses rainfall instead, but watchdog groups have raised concerns that rainfall may be used as a proxy for umbrella usage.

(It seems rather strange to expect a statistical model trained for accuracy to infer and indirect through a shadow variable that makes it less accurate, simply because it's something easy for humans to observe directly and then use as a lossy shortcut or to promote alternate goals that aren't part of the labels being trained for or whatever.)

> These are two sets of unavoidable tradeoffs: focusing on one fairness definition can lead to worse outcomes on others. Similarly, focusing on one group can lead to worse performance for other groups. In evaluating its model, the city made a choice to focus on false positives and on reducing ethnicity/nationality based disparities. Precisely because the reweighting procedure made some gains in this direction, the model did worse on other dimensions.

Nice to see an investigation that's serious enough to acknowledge this.

Re: We investigated Amsterdam's attempt to build a 'fair' fraud detection model

#24
Is this crazy or what? My take away is that the factors the city of Amsterdam is using to predict fraud are probably not actually predictors. For example if you use the last digit of someones phone number as a fraud predictor, you might discover there is a bias against low numbers. So you adjust your model to make it less likely that low numbers generate investigations. It is unlikely that your model will be any more fair after your adjustment.

One has to wonder if the study is more valid a predictor of the implementers' biases than that of the subjects.

Re: We investigated Amsterdam's attempt to build a 'fair' fraud detection model

#25

[flagged]

The goal is to avoid penalizing people for their skin color, or for gender/sex/ethnicity/whatever. If some group have higher rate of welfare fraud, the fair/unbiased system must keep false positives for that group at the same level as for general population. Ideally there should be no false positives at all, because they are costly for people, who were marked wrongly, but sadly real systems are not like that. So these false positives have to be spread over all groups proportionally to sizes of the groups.

Though the situation is more complex than that. What I described is named "False Positive Share" in the article (or at least I think so), but the article discusses other metrics too.

The problem is that the policy should make the world better, but if the policy penalizes some groups for law breaking, then it can push these groups to break the law even more. It is possible to create biases this way, and it is possible to do it accidentally. Or, rather, it is hard not to do it accidentally.

I'd recommend to read "Against Prediction", it has a lot of examples how it works. For example, biased False Negatives are also bad, they make it easier for some groups to break the law.

Re: We investigated Amsterdam's attempt to build a 'fair' fraud detection model

#26

[flagged]

There are multiple different ways to measure performance. If different groups have different rates of whatever you're predicting, it is not possible to have all of the different ways of measuring performance agree on whether your model is fair or not.

Re: We investigated Amsterdam's attempt to build a 'fair' fraud detection model

#27
Congrats Amsterdam: they funded a worthy and feasible project; put appropriate ethical guardrails in place; iterated scientifically; then didn’t deploy when they couldn’t achieve a result that satisfied their guardrails. We need more of this in the world.

Re: We investigated Amsterdam's attempt to build a 'fair' fraud detection model

#28
post #5

The article talks a lot about fairness metrics but never mentions whether the system actually catches fraud. Without figures for true positives, recall, or financial recoveries, its effectiveness remains completely in the dark. In short: great for moral grandstanding in the comments section, but zero evidence that taxpayer money or investigative time was ever saved.

[dead]

Re: We investigated Amsterdam's attempt to build a 'fair' fraud detection model

#29

Congrats Amsterdam: they funded a worthy and feasible project; put appropriate ethical guardrails in place; iterated scientifically; then didn’t deploy when they couldn’t achieve a result that satisfied their guardrails. We need more of this in the world.

What were the error rates for the various groups with the old process? Was the new process that included the model actually worse for any group, or was it just uneven in how much better it was?

Re: We investigated Amsterdam's attempt to build a 'fair' fraud detection model

#30

> But the model designers were aware that features could be correlated with demographic groups in a way that would make them proxies. There's a huge problem with people trying to use umbrella usage to predict flooding. Some people are trying to develop a computer model that uses rainfall instead, but watchdog groups have raised concerns that rainfall may be used as a proxy for umbrella usage. (It seems rather strange…

They correctly note the existence of a tradeoff, but I don't find their statement of it very clear. Ideally, a model would be fair in the senses that:

1. In aggregate over any nationality, people face the same probability of a false positive.

2. Two people who are identical except for their nationality face the same probability of a false positive.

In general, it's impossible to achieve both properties. If the output and at least one other input correlate with nationality, then a model that ignores nationality fails (1). We can add back nationality and reweight to fix that, but then it fails (2).

This tradeoff is most frequently discussed in the context of statistical models, since those make that explicit. It applies to any process for deciding though, including human decisions.

Post reply on HN