Skip to content

Cleanly split single-epoch and multi-epoch attribution handling#461

Draft
apasel422 wants to merge 3 commits into
w3c:mainfrom
apasel422:split
Draft

Cleanly split single-epoch and multi-epoch attribution handling#461
apasel422 wants to merge 3 commits into
w3c:mainfrom
apasel422:split

Conversation

@apasel422

@apasel422 apasel422 commented Jul 8, 2026

Copy link
Copy Markdown
Collaborator

This makes it clear that the L1 norm computation is irrelevant for the latter, and inherently avoids the redundant common matching logic and histogram creation for the former.

Fixes #397.


Preview | Diff

apasel422 added 3 commits July 8, 2026 09:38
The "deduct privacy and safety budgets" algorithm is invoked exactly
once per epoch in the chosen range, so it is unconditionally true that
each epoch's global budget is deducted from at most once.
A given impression belongs to a single epoch, and the "deduct privacy
and safety budgets" algorithm is invoked exactly once per epoch in the
chosen range, so there is no need to maintain a set keyed by epoch
across invocations of that algorithm.
This makes it clear that the L1 norm computation is irrelevant for the
latter, and inherently avoids the redundant common matching logic and
histogram creation for the former.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[clean up] improve how we pass |isSingleEpoch| around

1 participant