GCU Baseball Analytics Dashboard

Pitch Usage vs. LHH / RHH
Pitch Arsenal
Player Percentile Rankings
vs. all pitchers in loaded data / date range
Movement Profile (Induced Break)
Velocity Distribution

Arsenal Summary

Reflects the current sidebar filters (date range, count, opponent) — unlike the Player Card's arsenal table, which is always full-season.

Sequencing

Sequencing Results

CSW% / Whiff% on a pitch given what preceded it — a stand-in for pitch-tunneling effectiveness. Rows with fewer than 5 occurrences are dropped.

Count Tendencies


Command by Pitch Type

Command by Count Situation

Release Point Consistency

SD columns are the standard deviation of that pitch's release point (feet) — a rising SD or a shifting weekly average is often an early mechanics/fatigue signal, not just noise.


Results vs LHH / RHH

By Pitch Type

By Pitch Type

Event Log

⬇ Download CSV

A pitch type can appear in the legend with no visible line if that pitch has no Location or Stuff values in the loaded data.

Movement by Pitch

Player Percentile Rankings
vs. all hitters in loaded data / date range
Hits Spray Chart
Rolling Batting Avg


⬇ Download CSV

xOBP isn't shown — it requires a trained expected-outcome model fit the same way xBA/xSLG are, and that model doesn't output an xOBP component. Spin/Extension are ranked assuming higher is better, which is a simplification (ideal spin and extension vary by pitch shape and arm slot).

Run Value is estimated from this dataset's own run expectancy by outs (0/1/2 outs before the play) — there's no base-occupancy column in this export, so it can't credit/penalize who was on base the way a full base+out (RE288) model would, but it does adapt to the loaded data's actual run environment instead of using fixed generic weights.

Sprint Speed, OAA, Arm Strength, Bat Speed, Squared-Up Rate, and Swing Length aren't shown — those require biomechanical/bat-sensor tracking (e.g. Hawk-Eye, Blast Motion) that isn't present in ball-flight-only Trackman exports.

Run Value is estimated from this dataset's own run expectancy by outs (0/1/2 outs before the play) — there's no base-occupancy column in this export, so it can't credit/penalize who was on base the way a full base+out (RE288) model would, but it does adapt to the loaded data's actual run environment instead of using fixed generic weights.

GCU Baseball Analytics Dashboard

Purpose

Advanced analytics for GCU Baseball using TrackMan pitch-tracking data.

Features

  • Pitcher: Pitch usage & sequencing, command & heatmaps, count tendencies, platoon splits, K/BB, Stuff+, velocity, plus season and daily reports.
  • Hitter: Summary, spray charts, heatmaps, zones, batted ball profile, game log.

Contact

GCU Baseball Analytics Team