Add per-dog distraction analytics and event annotations - #63
Merged
Conversation
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.
Summary
Why
Issue #55 asks for longitudinal distraction analytics without inventing zero-value observations or introducing false precision. A categorical distribution plus an observed median keeps the scale ordinal, while the single-series selector keeps the chart readable on small screens. Dated event annotations give trainers context for changes in behavior over time.
Data and compatibility
dogEventsto the shared database blob and Worker default blobdogEventsValidation
npm test— 28 tests passed, including ordinal aggregation and no-fabricated-observation coveragenpm run build— production TypeScript and Vite build passednpm run lint— passed with 3 pre-existing warningsnpm run typecheckinworker/— passedgit diff --check— passedCloses #55