Repository navigation
feat: detect event channels and report them (#175, event slice 1) - #252
Merged
Merged
Conversation
Add a detector that rates channels high, medium or low as event channels (PPV, Pay Per View and similar) from the channel name, category and how the provider guide titles behave, tuned on measured real guides. Report only: one section in the build report, nothing hashed, no guide or playlist byte changes. Update the design note signals to match what was measured. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NzHAckAcs78Lu3rv8Gqgrf
Owner
Author
|
Real-guide check of the detector (read only, EPG Ripper and Jesmann US): 21 channels rated high, no false positives seen. Every channel with PPV or Pay Per View as a whole word was rated high (9 of 9). Two small misses: names like "PPV1" to "PPV4" are not matched, and a title that echoes the channel name with a small difference counts as real. Both are one-line fixes, planned as a small follow-up PR after this one merges. The medium-confidence rule behaved as intended: channels with real schedules stayed at medium. Not verified on real data: the "low" rule (XMLTV has no category). |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Slice 1 of docs/planning/EVENT-AWARE-CHANNELS-DESIGN-NOTE.md (issue #175, contract event-channel/v2). Report only.
Get-ChannelForgeEventChannelCandidaterates each channelhigh,mediumorlowas an event channel, with plain reasons. Rules come from a read-only measurement of two real guides (28,239 and 6,100 channels):high(lowered tomediumonly with 3 or more different real titles and at most half placeholder time).high; otherwisemedium.Get-ChannelForgeEventChannelSummaryLinesand one report block inscripts/Build-Lineup.ps1. A failure is one warning and never changes the build.About 128 product lines plus 5 tests. Verified locally (pwsh): EventChannelCandidate 5, CategorySummary 3, XguideSummary 9, BuildLineupCandidateOnly 3, BuildLineupIdentityBinding 9, BuildLineupFailedGuideSource 3, all 0 failed. Not verified: full suite (CI), Windows PowerShell 5.1, and the detector on the real guides themselves (synthetic fixtures only). The 6-hour limit for the low rating is a guess.
Part of #175.
🤖 Generated with Claude Code
https://claude.ai/code/session_01NzHAckAcs78Lu3rv8Gqgrf