07_tenant_screening_bias_audit.ipynb's Key Insight cites numbers that match nothing - not its own cells, not unfair.py/fair.py, not the README

Open Beginner friendly
#688 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
94/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
jupyter-notebook, python
Domain
documentation

Research direction

Open notebooks/07_tenant_screening_bias_audit.ipynb and compare cell 17 with the outputs in cells 12, 14, and 16. Verify the figures against Tenant Screening/unfair.py, fair.py, and the folder README.md, then update the Key Insight so its values match and confirm no unrelated notebook content changes.

Written by the indexing model from the issue text.

Description

documentation good first issue

Where: notebooks/07_tenant_screening_bias_audit.ipynb, cells 12/14/16 (code) vs. cell 17 (markdown "Key Insight").

The gap: cells 12/14/16 actually print:

Fairness Gap: 6.68%               (cell 12, biased)
New Fairness Gap: 5.16%, p=0.0004 (cell 14, fair)
Reduction: 23%                    (cell 16, summary)

These exactly match Tenant Screening/unfair.py/fair.py run directly, and the folder's README.md ("Race | 6.68% | 5.16% | 23%"). But cell 17's Key Insight claims: "Dropping Race and all twelve proxies cuts the gap from 7.17% to 5.07%, a 29% reduction... the residual disparity is significant (p=0.0007)." None of 7.17%, 5.07%, 29%, or p=0.0007 appear anywhere else - not in this notebook's own output, not in the reference scripts, not in the README.

Fix direction: correct the Key Insight text to "6.68% to 5.16%, a 23% reduction... (p=0.0004)".

Dominant language
HTML
Stars
47
Forks
45
Avg merge
1h 56m
Merged PRs (30d)
96

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from yakew7/Fair-Code

All issues in yakew7/Fair-Code

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.