sassoftware / sassoftware/dpmm
Clarification regarding domain extraction for categorical variables ("PrivacyLeakage" warning)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
@ #18
As previously stated, the documentation now suggests that setting domain=None would handle domain extraction automtically in a DP way, which would be indeed a great feature.
For numerical variables, I found the approx_bounds function which I suppose to handle this if no domain is specified?
Could you please clarify what happens for categorical columns? Without domain specification, these kind of warnings are printed: PrivacyLeakage: No categorical domain provided for Column - will be imputed. The wording "PrivacyLeakage" sort of suggests that the domain for categorical variables is not extracted in a DP-manner as opposed to the statement in the documentation.Would you please clarify this?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the documentation referenced in the issue and the handling of domain=None for numerical and categorical columns. Verify what the PrivacyLeakage warning means for categorical domains, then update the documentation so the behavior and any differential-privacy guarantees are stated unambiguously.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100