Measuring Fairness in Machine Learning Systems
Key Takeaways
The video discusses methods for evaluating algorithmic fairness in machine learning systems, highlighting the importance of fairness in AI systems and the need for interdisciplinary expertise to address bias. It also explores the concept of fairness definitions and their inherent trade-offs, using the example of the Compass recidivism risk assessment software.
Full Transcript
hi my name is Melissa Hall and I work on a team whose mission is to ensure the responsible use of AI at Facebook at Facebook we believe that it's essential to evaluate machine learning nai systems to ensure that they are not biased against users this presentation gives an overview of algorithmic fairness including an explanation of the intricacies within large-scale systems that make them vulnerable to biases and the multiple ways of measuring fairness I'll focus is talk on developing ethical AI systems with a focus on safety and equity for users I'll begin with a bird's eye view of machine learning systems and discuss the ways that fairness concerns could manifest throughout the development process I'll share a commonly cited fairness case study to highlight biases in machine learning systems I'll then give an overview of the multiple conflicting methods of measuring bias and models I'll conclude by sharing additional points of consideration when building machine learning systems that have human impact to begin before we can understand whether a system is fair it's important to have a clear sense of what's at stake fairness is not just an engineering problem but it is crucial for engineers to think about the ways their products interact with society when someone interacts with a given system what are they getting out of it what are the benefits it's also important to understand the risks and in particular a few kinds of potential harms consider does the system restrict access to resources or opportunities for certain subgroups does the system reinforce harmful stereotypes does it perform reasonably well for everyone and beyond the impact to individual end-users it's also important to ask what kinds of unintended impacts might this system have on society as a whole fairness is a process as I said before not just an engineering problem it requires different kinds of expertise as well as input from a range of stakeholders if we zoom out this is what the process looks like first it's important to understand the product goals policy and implementation within the broader social texts where the system will be used next hold conversations with stakeholders to reach consensus to outline measurement and mitigation plans how is the system performing and why does it perform that way to measure fairness with robustness it's important to look at different points in the process of developing a machine learning system started the process of defining the policy ground truth with the intention of understanding whether this policy has been designed such that specific groups are systematically favored or disfavored in the process of collecting labels the developer needs to look at how the human labeling along the policy lines matches the actual content it's important to understand whether the human labeling program is robust against labelers who might be inclined to introduce their own social or ideological biases then of course there's a step of an understanding whether the AI systems introduce fairness concerns finally it's important to examine the intervention step I'll focus this talk on the ways of measuring fairness and the algorithmic step of the workflow but there are a lot of metrics that people have proposed for measuring fairness and it can get pretty contentious let's talk about an example a commonly cited case study I Pro Publica researchers and 2016 focused on the compass recidivism risk assessment which is developed by a company called North Point this software is used by US courts to determine the likelihood that a defendant recidivate meaning the likelihood that a defendant relapses into behavior that led them to court in the first place at the time of the study defendants would complete a compass questionnaire that would then be fed into the compass software to determine prediction scores for things like the risk of recidivism and risk of violent recidivism which were later surfaced to judges Republicans analysis found evidence of bias against black defendants in the compass system specifically they claim that among defendants who did not go on to reoffended pendants were often predicted to be at a higher risk of recidivism than they actually were all white defendants were often predicted to be less risky than they were according to Republican work black defendants who did not reoffended likely as their white counterparts to be misclassified is a higher risk this demonstrates the concern for equality of outcome Northpoint the company that created the compass assessment responded Republicans concerns by claiming that for any given score on its ten-point scale why am black defendants were just as likely to reoffend as each other they're essentially saying that their system demonstrated a quality of treat there a variety of metrics used to measure fairness and bias in machine learning systems in this case república used the false positive rate across black and white defendants to determine that they compass assessment was unfair while Northpoint used calibration measurements to claim that this system was there it's worth also pointing out that the data they trained on may embed biases the likelihood of recidivism in the training data was possibly the outcome of a biased justice system and our framework that would be considered label bias but for the rest of this presentation we'll be focusing on the question of model bias and assuming that we're discussing systems with correct labels across academia industry there are multiple and oftentimes conflicting notions of fairness for example one fairness goal could be a quality of treatment where similar samples from two different groups are treated the same on the other hand a fairness goal could be to ensure equality of outcome which means that samples from different groups have the same likelihood of a certain outcome this might require an equal treatment since oftentimes their external confounding factors such as historical biases that mean correcting for there are a few ways we could compare how a model performs for different groups the first is demographic parity meaning that the proportion of positive decisions should be the same across all groups when applied to our pretrial example demographic parity means that the rate of labeling a defendant as high-risk is equal across both black and white defendants however when the true underlying distribution of risk varies across groups differences in group level error rates can happen when algorithms accurately captured each individual's risk attempts to adjust for these differences often require implicitly or explicitly misclassifying low-risk members of one group as high risk and high risk members of another is lowest potentially harming members of all groups in the process another metric is a concept of equal opportunity which focuses on the advantaged outcome this would mean that the compass assessment would correctly classify defendants who don't really risk at equal rates for both black and white defendants in other settings in which the advantage outcome is a positive classification they'd need to be equal to positive rates there's also equalized odds which is a stricter fairness condition than equal opportunity in equalized odds for the compass assessment both the false negative rates and the true negative rate should be equal across groups this punishes models that perform only well in the majority like with equal opportunity the choice to require equality of false and true positive versus negative rates is dependent on the advantaged classification in your setting note that a drawback of equalised on to equal opportunity but that it's possible to gain these rates by introducing more examples or spores are extreme further warm equalized odds is usually possible by introducing randomness into the decision-making procedure finally there's calibration calibration means that regardless of the group that a sample is in the models predicted probability for the sample represents the true probability of occurrence in the context of the compass risk assessment calibration means that among the defendants with a given risks for the proportion that would be offended for at least is the same for both groups while calibration is generally desirable it has been shown to prove only a weak provide only a weak guarantee of equity in particular it is often straightforward to satisfy calibration also teaches we miss classifying individuals who order to discriminate now of course it would be great if we could simultaneously satisfy all fairness definitions however this is only possible under certain highly unlikely circumstances like when there's a perfect predictor or equivalent base rate across subgroups therefore it's important for developers and organizations to understand the different ways to measure fairness and the inherent trade-offs they have the mathematical conceptions of parents are grounded in contextual and philosophical perspectives that are often unique to specific individuals it's important to consider these perspectives among builders and stakeholders when establishing definitions and metrics for measuring fairness some questions to think about fairness could include what is a person's source of value from the decision but can we expect a system to guarantee for its users what groups matter when measuring and ensuring the fairness of a system what information about systematic differences between groups should be available to the model and what should be excluded what privacy trade-off do these decisions imply sometimes and may be more useful to revisit what the model is designed to do in other words to interrogate the target metric product goals and policy it's a system something that should exist at all and she can see measuring and evaluating fairness even at just the model stage it's not an easy task fairness is a process that requires systematic thinking and in every step of the implementation of the system we must surface two risks and hard questions of fairness processes need to be built for resolving these questions and a record of the decisions should be maintained along the way for this hackathon we ask you to build tools that make these evaluations easy but also not oversimplifying the complexity of fairness thank you
Original Description
All large-scale AI systems have intricacies that can make them vulnerable to bias.
Melissa Hall is part of the team that ensures the responsible use of AI at Facebook. In this presentation, she provides an overview of methods for evaluating algorithmic fairness to ensure that machine learning systems of all sizes are not biased against users.
Subscribe to this page to get the latest news, updates, and weekly tutorials planned for the full duration of the Hackathon.
Haven't signed up yet? Get involved, and learn how you could build with the community and also have a chance to win up to $25,000: https://bit.ly/2ZwLYKX
Watch on YouTube ↗
(saves to browser)
Sign in to unlock AI tutor explanation · ⚡30
Playlist
Uploads from PyTorch · PyTorch · 59 of 60
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
▶
60
What is PyTorch?
PyTorch
PyTorch Tutorial: A Quick Preview
PyTorch
PyTorch Summer Hackathon 2019
PyTorch
Tips and Tricks on Hacking with PyTorch: A Quick Tutorial by Brad Heintz
PyTorch
PyTorch 1.2 and PyTorch Hub: A Quick Introduction by Soumith Chintala and Ailing Zhang
PyTorch
Torchtext 0.4 with Supervised Learning Datasets: A Quick Introduction by George Zhang
PyTorch
Torchaudio 0.3 with Kaldi Compatibility, New Transforms: A Quick Introduction by Jason Lian
PyTorch
Torchvision 0.4 with Support for Video: A Quick Introduction by Francisco Massa
PyTorch
Introduction to Machine Learning for Developers at F8 2019
PyTorch
Powered by PyTorch at F8 2019
PyTorch
Developing and Scaling AI Experiences at Facebook with PyTorch at F8 2019
PyTorch
New Approaches to Image and Video Reconstruction Using Deep Learning at Facebook at F8 2019
PyTorch
PyTorch Developer Conference 2018: Recap
PyTorch
PyTorch Developer Conference 2018: Keynote & Deep Dive
PyTorch
PyTorch Developer Conference 2018: Production & Research Sessions
PyTorch
PyTorch Developer Conference 2018: Cloud & Academia Sessions
PyTorch
PyTorch Developer Conference 2018: Enterprise, Education, & Future of AI Panel
PyTorch
PyTorch Developer Conference 2019 | Full Livestream
PyTorch
PyTorch Developer Conference 2019: Recap
PyTorch
PyTorch Developer Conference Keynote - Mike Schroepfer
PyTorch
What’s new in PyTorch 1.3 - Lin Qiao
PyTorch
PyTorch Front-End Features: Named Tensors and Type Promotion - Gregory Chanan
PyTorch
Research to Production: PyTorch JIT/TorchScript Updates - Michael Suo
PyTorch
Quantization - Dmytro Dzhulgakov
PyTorch
PyTorch ONNX Export Support - Lara Haidar, Microsoft
PyTorch
Apex - Michael Carilli, NVIDIA
PyTorch
Dataloader Design for PyTorch - Tongzhou Wang, MIT
PyTorch
Linear Algebra in PyTorch - Vishwak Srinivasan, CMU
PyTorch
PyTorch Mobile - David Reiss
PyTorch
Model Interpretability with Captum - Narine Kokhilkyan
PyTorch
Detectron2 - Next Gen Object Detection Library - Yuxin Wu
PyTorch
Speech Extensions to Fairseq - Dmytro Okhonko
PyTorch
PyTorch on Google Cloud TPUs - Google, Salesforce, Facebook
PyTorch
PyTorch Summer Hackathon Winners - Joe Spisak, Sebastien Arnold, Tristan Deleu
PyTorch
PyTorch in Robotics - Yisong Yue, Caltech
PyTorch
StanfordNLP - Yuhao Zhang, Stanford
PyTorch
Sotabench for Reproducible Research - Robert Stojnic, Papers with Code
PyTorch
Collaborative Natural Language Inference - Sasha Rush, Cornell
PyTorch
Privacy Preserving AI - Andrew Trask, OpenMined
PyTorch
CrypTen - Laurens van der Maaten
PyTorch
PyTorch at Uber - Sidney Zhang, Uber
PyTorch
PyTorch at Tesla - Andrej Karpathy, Tesla
PyTorch
PyTorch at Microsoft - Saurabh Tiwary, Microsoft
PyTorch
PyTorch at Dolby Labs - Vivek Kumar, Dolby Labs
PyTorch
PyTorch Developer Conference 2019 - Panel Discussion
PyTorch
Using deep learning and PyTorch to power next gen aircraft at Caltech
PyTorch
Named Tensors, Model Quantization, and the Latest PyTorch Features - Part 1
PyTorch
TorchScript and PyTorch JIT | Deep Dive
PyTorch
Announcing the PyTorch Global Summer Hackathon 2020
PyTorch
Opening Up the Black Box: Model Understanding with Captum and PyTorch
PyTorch
PyTorch Mobile Runtime for Android
PyTorch
Torchvision in 5 minutes
PyTorch
3D Deep Learning with PyTorch3D
PyTorch
What is Torchtext?
PyTorch
TorchAudio: A Quick Intro
PyTorch
PyTorch Mobile Runtime for iOS
PyTorch
PySlowFast: Deep learning with Video
PyTorch
PyTorch Pruning | How it's Made by Michela Paganini
PyTorch
Measuring Fairness in Machine Learning Systems
PyTorch
PyTorch for Hackathons
PyTorch
More on: AI Alignment Basics
View skill →Related Reads
📰
📰
📰
📰
Elon Musk’s Grok Faces a Trust Crisis After Developers Flag a Major Privacy Concern
Reddit r/artificial
FullAgenticStack: Semantic Behavior Type: LinearAutoDestroy
Dev.to · suissAI
Texas AI Law Compliance: A Guide for Businesses
Hackernoon
An AI Science Workbench Needs a Reproducibility Graph, Not Just Chat History
Dev.to · Robin
🎓
Tutor Explanation
DeepCamp AI