Skip to content

Pipeline numerical derivation uses exact data min/max before DP quantiles #34

Description

@vvv214

The pipeline numerical derivation path currently computes exact min/max from sensitive data before running DP quantiles. Those exact bounds are not noised, but they are written into the returned DatasetDescriptor and can also surface as decoded interval edges.

Numerical bounds should be public caller-provided metadata; DPSynth should only compute quantile cut points under DP within those bounds.

Draft fix: #30.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions