Repository navigation
fix(novelty): a capped run says how far the cap reached #299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
antonwolfy
wants to merge
17
commits into
intel:main
Choose a base branch
from
antonwolfy:fix/novelty-cap-reach
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+465
−59
Open
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
fa453d8
fix(novelty): a capped run says how far the cap reached
antonwolfy 92d41c7
fix(novelty): floor the reach share; a cap that met the last span say…
napetrov f5a21b7
fix(novelty): a cap that met the last span says any atoms past it wer…
napetrov 27dac86
fix(novelty): the cap reach counts only spans a call was sent
antonwolfy e089ea3
fix(novelty): the cap forfeit and gate reason stop calling atoms a sa…
antonwolfy 115edbc
fix(novelty): novelty atoms prints the cap warning analyze records
antonwolfy 8e133a5
fix(novelty): the floor warning on a capped run says the words went in
antonwolfy b9bf52b
fix(schemas): extraction.reached requires all four of its keys
antonwolfy 041a311
docs(novelty): describe the cap met on the artifact's last span
antonwolfy fa5347a
test(novelty): import cap_warning once; pin the mid-artifact header
antonwolfy b3e1032
fix(novelty): narrow max_atoms before the cap warning, for mypy
antonwolfy eb34b3f
Merge main into fix/novelty-cap-reach
antonwolfy 689c109
style(novelty): keep the FORFEITS comment to two lines
antonwolfy 3e576e0
fix(novelty): word the cap reach as the input's, not the artifact's
antonwolfy 72bab67
fix(novelty): the cap forfeit and gate reason name the input's opening
antonwolfy 50c2711
fix(novelty): the cap forfeit and gate reason hold for any cap reach
antonwolfy d6116ef
docs(changelog): say which share triggers the coverage warning
antonwolfy File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
20 changes: 20 additions & 0 deletions
20
dokimi/changelog.d/20261029_120000_antonwolfy_novelty-cap-reach.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,20 @@ | ||
| ### Fixed | ||
|
|
||
| - **A capped novelty run says how far the cap reached** — extraction stops at | ||
| the atom cap in document order, so a capped run measures the input up to the span | ||
| the cap stopped at; the input is the text that was segmented, which leaves out | ||
| the bundled files a run did not select. The cap warning of `novelty analyze` now names the span it | ||
| stopped at, the input's spans up to it and their share of the input's | ||
| tokens, instead of calling the atoms a sample, and `novelty atoms` now | ||
| prints it too; `extraction.reached` records the same in `novelty.json` and | ||
| `atoms.json` (`null` when the cap did not bind); the `novelty.md` header | ||
| states it; and on a capped run the headline's `coverage:` line says the | ||
| readable words went into the input and the capped atoms come from the first | ||
| N% of the input's tokens, instead of saying they were measured (as does the | ||
| warning printed under it when half or less of the artifact's readable words | ||
| went into the input). A cap met on the input's last span says instead that | ||
| the atoms reach it and any atoms past the cap in the last reply were dropped, in the warning, the header and the | ||
| `coverage:` line. The tier forfeit (`added` is a rate over the atoms the | ||
| cap kept, not the whole input) and the `harmful_atoms` gate reason (0 | ||
| conflicts among the capped atoms) no longer call the capped atoms a sample | ||
| either, and hold however far the cap reached. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.