Skip to content

feat: show pitch locations on a strike zone diagram#75

Open
alex-monroe wants to merge 1 commit into
paaatrick:mainfrom
alex-monroe:strike-zone-display
Open

feat: show pitch locations on a strike zone diagram#75
alex-monroe wants to merge 1 commit into
paaatrick:mainfrom
alex-monroe:strike-zone-display

Conversation

@alex-monroe

Copy link
Copy Markdown

Renders the current at-bat's pitches as numbered, color-coded markers plotted against the per-pitch strike zone bounds from MLB Stats API (pitchData.coordinates.pX/pZ + strikeZoneTop/Bottom). Sits between the matchup and at-bat panes in the live game view.
Screenshot 2026-04-29 at 8 14 25 PM

Renders the current at-bat's pitches as numbered, color-coded markers
plotted against the per-pitch strike zone bounds from MLB Stats API
(pitchData.coordinates.pX/pZ + strikeZoneTop/Bottom). Sits between the
matchup and at-bat panes in the live game view.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@paaatrick

Copy link
Copy Markdown
Owner

Hey thanks for the contribution. I like the compactness of this display a bit better than the previous attempt in the draft #54. A few comments and questions:

  1. It looks like pitches outside of the grid area get clamped to the edges. Is it possible to add an indicator (perhaps with ▲, ▶, etc characters) that the pitch is actually further out than indicated?
  2. Can you add the corresponding pitch numbers (same colors would be nice) to the list of pitches? So for example:
    3 [Foul] ...
    2 [Ball] ...
    1 [Ball] ...
    
  3. There was an issue in Pitch location visualization #54 where the vertical placement of pitches in the text grid didn't seem to track very well with what was shown in the MLB Gameday interface (even when taking the necessary lower "resolution" of the text grid into account). Have you manually verified that the pitch placements in the text grid look reasonable?

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.

2 participants