yolo/arr
3
0
Fork 0
Code Issues 12 Pull Requests Actions Packages Projects Releases Wiki Activity

Size-band scoring #63

Merged
naps62-yolo merged 2 commits from issue/13-size-scoring into main 2026-08-22 21:15:26 +01:00
Conversation 4 Commits 2 Files Changed 5
+494 -8
2 Commits
Author SHA1 Message Date
Miguel PalhasandClaude Opus 5 b1c11ae5f1 fix(db): put the scoring numbers in the policy rows
ci / web (pull_request) Successful in 23s
Details
ci / rust (pull_request) Successful in 1m18s
Details 
The size bands seeded before scoring existed carried a penalty on no
particular scale, and the weights that keep source tier and seeders
small against the size term had nowhere to live but a Default impl.
§5.5 says these are policy rows, tuned by hand.

`SizeBand::penalty_points_per_gib_over` names its unit, so a row and
the type it loads into agree on what the number means.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
 2026-08-22 21:12:50 +01:00
Miguel PalhasandClaude Opus 5 6b12656f01 feat(core): score by distance from target size
ci / web (pull_request) Successful in 24s
Details
ci / rust (pull_request) Successful in 1m29s
Details 
Source tier stops deciding grabs. Per resolution the policy carries a
floor, a target and a penalty per gigabyte over, so a 20 GB WEB-DL beats
a 60 GB remux while the remux keeps a score and stays eligible.

Below the floor is a hard filter rather than a low score: unbounded
"smaller is better" selects a 3 GB 4K encode that looks like mud.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
 2026-08-22 21:07:37 +01:00