Add jarrod tracking logic#106
Conversation
🔒 Security Scan Results✅ No critical security issues detected. The code has passed all critical security checks. |
8a53a1b to
7d528ad
Compare
🔒 Security Scan Results✅ No critical security issues detected. The code has passed all critical security checks. |
7d528ad to
f34567b
Compare
🔒 Security Scan Results✅ No critical security issues detected. The code has passed all critical security checks. |
🔒 Security Scan Results✅ No critical security issues detected. The code has passed all critical security checks. |
|
Updated gitignore and added README.md |
lperry022
left a comment
There was a problem hiding this comment.
The script runs, but the metric logic needs improvement before approval. Currently only one event_name column is used, so true positives/false positives/false negatives aren’t calculated correctly. fp is hard-coded to 0 and (no_event) always returns perfect scores, which makes the results misleading. Consider updating the script to compare separate ground truth vs predicted columns and compute TP/FP/FN properly.
🔒 Security Scan Results✅ No critical security issues detected. The code has passed all critical security checks. |
|
Thanks for the feedback! I’ve updated prediction_vs_truth.py so it now computes TP/FP/FN properly by comparing truth_event vs pred_event. |
Update to move annotation and analysis scripts into correct folder Player_Tracking/afl_player_tracking_and_crowd_monitoring/player_tracking_logic.
No changes made to code