Update README.md

README.md

@@ -24,10 +24,15 @@ Research and development for automated ball-strike officiating systems
 
 2. Training Data
 Dataset Source
+
 Base dataset: ROBO ump  Roboflow Universe, accessed 2025
+
 https://universe.roboflow.com/toasty-workspace/roboump
+
 Platform: Roboflow Universe (roboflow.com/universe)
+
 Collection: Broadcast MLB footage (center-field fixed-angle camera)
+
 Resolution: 640 × 640 px (resized)
 
 Class Distribution
@@ -69,22 +74,30 @@ Overall Metrics
 
 
 mAP@50: 0.92 (target > 0.85)
+
 Overall F1: 0.91 (target >= 0.80)
 
 Per-Class Breakdown
 
 ball: mAP@50 = 0.72, F1 = 0.76
+
 batter: mAP@50 = 0.97, F1 = 0.95
+
 pitcher: mAP@50 = 0.97, F1 = 0.84
+
 strike_zone: mAP@50 = 0.82, F1 = 0.88
 
 Confusion Matrix Summary
 ![confusion_matrix](https://cdn-uploads.huggingface.co/production/uploads/697294cf06dbc59ddb0601f0/5PMZO_0lhXkPzC452UcQB.png)
 
 Ball: 69 correctly predicted, 33 missed as background (~32% miss rate)
+
 Batter: 145/145 correct
+
 Pitcher: 145/145 correct
+
 Strike_zone: 44/47 correct, 3 missed as background
+
 Background false positives: 9 labeled as ball, 4 as strike_zone
 
 Performance Analysis
@@ -94,12 +107,13 @@ The ball class is the most critical failure point. A mAP@50 of 0.72 means roughl
 
 
 5. Limitations and Biases
+
 Known Failure Cases
 
 Ball near white uniforms: Low contrast causes false negatives when the ball overlaps light-colored jerseys
 Strike zone partially off-frame: Bounding box gets truncated when the batter stands near the frame edge
 Occlusion: When the catcher, batter, or pitcher obscures the ball at the plate, recall drops significantly
-Low-light or compressed frames: JPEG artifacts confuse the detector, especially for the small ball class
+Low-light or compressed frames: JPEG artifacts confuse the detector, especially for the small ball class: After a pitch is completed the broadcast will visualize where the ball landed, this was a cause of false positives.
 
 Poor-Performing Class: Ball
 The ball class is the weakest performer (mAP@50 = 0.72) because the ball is typically only 10-20 pixels across at broadcast resolution and moves at 80-100 mph, causing motion blur in standard 30fps footage. Background crowd balls and logos also created false positives requiring manual cleanup.