diff --git a/.DS_Store b/.DS_Store new file mode 100644 index 0000000..c1aad7c Binary files /dev/null and b/.DS_Store differ diff --git a/Ideas/.DS_Store b/Ideas/.DS_Store new file mode 100644 index 0000000..03346be Binary files /dev/null and b/Ideas/.DS_Store differ diff --git a/Ideas/.Rhistory b/Ideas/.Rhistory new file mode 100644 index 0000000..e69de29 diff --git "a/Ideas/Idea 2 NBA Player Props Proposal 1.29.25\342\200\257PM.md" "b/Ideas/Idea 2 NBA Player Props Proposal 1.29.25\342\200\257PM.md" new file mode 100644 index 0000000..1dfe53e --- /dev/null +++ "b/Ideas/Idea 2 NBA Player Props Proposal 1.29.25\342\200\257PM.md" @@ -0,0 +1,53 @@ +# Luke Finkielstein Mini Project Idea Proposal 2: +# NBA Player Props Prediction + +Research Question: Can we predict NBA player point totals with reasonable accuracy using historical performance, matchup data, and contextual factors? + +Approach: Develop a regression model to predict individual player point totals in NBA games using historical player statistics and game context. The model will help identify player prop betting opportunities. + +## Gathering Tractable Data + +**Target:** Individual player point totals per game + +**Key Features:** +- Player historical scoring average (season, last 10 games, vs. specific opponents) +- Opponent defensive rating (points allowed per game) +- Game context (home/away, back-to-back games, rest days) +- Player usage rate and minutes played trends +- Opponent pace of play +- Player injury/availability status + +**Data sources:** ESPN, Basketball-reference.com, NBA.com, Kaggle datasets with historical player-game logs. Feasibility is high—player statistics are publicly available and well-documented. + +## Retrieval & Preparation + +Two approaches: +- Use existing player-game log datasets (faster, reduces timeline) +- Web scrape player statistics from ESPN/Basketball-reference (more control, more time-intensive) + +## EDA & Insights + +Analyze how player scoring varies by opponent strength, rest status, and usage rate. Identify key predictive features (recent form, matchup difficulty). Calculate correlations between candidate features and player point totals. Visualizations will include scatter plots of usage rate vs. scoring, distribution plots of scoring by opponent defense rating, and time-series analysis of individual player trends. Compare model performance against a simple baseline (e.g., using season average) to ensure meaningful predictive value. + +## Potential Limitations + +- **Game-to-game variance:** Player performance is highly variable; some games are outliers due to hot/cold shooting. +- **Injury uncertainty:** Last-minute injuries or load management decisions affect playing time unpredictably. +- **Small sample sizes:** Some matchups may have limited historical data. +- **Model assumes consistency:** Player form and roles can change mid-season due to trades or coaching changes. + +## Implications for Stakeholders + +**Sports Bettors:** Help identify player prop bets with positive expected value. + +**Sportsbooks:** Understand what drives player prop lines and refine odds-setting. + +**NBA Analysts:** Identify which factors most influence individual player performance. + +## Responsible Deployment & Ethics + +**Concerns:** Model could encourage problem gambling; predictions are probabilistic. + +**Legal:** Gambling laws vary by state. This model is for analysis only, not financial advice. + +**Mitigation:** Include gambling risk disclaimers; frame as educational/analytical exercise. \ No newline at end of file diff --git "a/Ideas/Idea 2 NBA Player Props Proposal 1.29.25\342\200\257PM.md.html" "b/Ideas/Idea 2 NBA Player Props Proposal 1.29.25\342\200\257PM.md.html" new file mode 100644 index 0000000..cc52f17 --- /dev/null +++ "b/Ideas/Idea 2 NBA Player Props Proposal 1.29.25\342\200\257PM.md.html" @@ -0,0 +1,42 @@ +
Research Question: Can we predict NBA player point totals with reasonable accuracy using historical performance, matchup data, and contextual factors?
+Approach: Develop a regression model to predict individual player point totals in NBA games using historical player statistics and game context. The model will help identify player prop betting opportunities.
+Target: Individual player point totals per game
+Key Features:
+Data sources: ESPN, Basketball-reference.com, NBA.com, Kaggle datasets with historical player-game logs. Feasibility is high—player statistics are publicly available and well-documented.
+Two approaches:
+Analyze how player scoring varies by opponent strength, rest status, and usage rate. Identify key predictive features (recent form, matchup difficulty). Calculate correlations between candidate features and player point totals. Visualizations will include scatter plots of usage rate vs. scoring, distribution plots of scoring by opponent defense rating, and time-series analysis of individual player trends. Compare model performance against a simple baseline (e.g., using season average) to ensure meaningful predictive value.
+Sports Bettors: Help identify player prop bets with positive expected value.
+Sportsbooks: Understand what drives player prop lines and refine odds-setting.
+NBA Analysts: Identify which factors most influence individual player performance.
+Concerns: Model could encourage problem gambling; predictions are probabilistic.
+Legal: Gambling laws vary by state. This model is for analysis only, not financial advice.
+Mitigation: Include gambling risk disclaimers; frame as educational/analytical exercise.
+ + \ No newline at end of file diff --git a/Ideas/NBA_Game_Prediction_Proposal.md b/Ideas/NBA_Game_Prediction_Proposal.md new file mode 100644 index 0000000..790a121 --- /dev/null +++ b/Ideas/NBA_Game_Prediction_Proposal.md @@ -0,0 +1,64 @@ +# Luke Finkielstein Mini Project Idea Proposal: +# NBA Game & Stat Prediction + + +Research Question: How can we predict the outcome of NBA games with better than 60% accuracy? + +Approach: Develop a classification model (probably logistic regression) to predict NBA game outcomes using historical game statistics and betting odds. The model will identify games with favorable edges to inform predictions. + + +## Gathering Tractable Data + +**Target:** Game outcomes (win/loss) + +**Key Features:** +- Team performance metrics (record, scoring, defense) +- Player availability/injury status +- Opponent strength ranking +- Game context (home/away, back-to-back games) +- Betting odds from sportsbooks (BetGM, DraftKings, Fanduel, etc.) + +**Data sources:** ESPN, NBA.com, Basektball-reference.com, Kaggle all have pre-compiled datasets of real games going back 20+ years. Additional data can be scraped from these websites if necessary. Feasibility is high—game data and odds are publicly available. + +## Retrieval & Preparation + +Two viable approaches: + +- Use existing public dataset (faster, reduces timeline overhead) +- Web scrape/API calls for game stats and odds (more control, more time-intensive) + + +## EDA & Insights + +Analyze outcome variation by team strength, matchups, injuries, and game context. Identify predictive features (home-court advantage, efficiency metrics). Perform EDA and visualize feature correlations with game outcomes. Calculate correlations between candidate features and game outcomes to determine which have the strongest predictive signals. Visualizations will include scatter plots of team efficiency metrics, heatmaps of feature correlations, and distribution plots comparing home vs. away performance. I can compare the model performance against a simple baseline (like always predicting the higher-seeded team) to ensure the model adds meaningful value. + +## Potential Limitations + +- **Unpredictable events:** Model cannot account for unexpected injuries, trades, coaching changes, or rest decisions made close to game time. +- **Probabilistic predictions:** Accuracy >50% does not guarantee profit; individual game predictions are probabilistic and subject to variance. +- **Data limitations:** Historical data may not fully capture changes in league dynamics, rule changes, or roster composition over 20+ years. +- **Sample size:** Model performance is limited by the number of games available for training and testing. + +## Implications for Stakeholders + +**Sports Bettors/Fans:** Would help make informed decisions on predicting winners and increase profitability. + +**Sportsbooks:** Understand what drives betting patterns and refine odds-setting. + +**NBA Teams**: Understanding which factors affect a team's ability to win would be very interesting to coaches/players/owners. + +## Responsible Deployment & Ethics + +**Concerns:** Model could encourage problem gambling; predictions are probabilistic and not deterministic. + +**Legal:** Gambling laws vary by state (sports betting is legal in PA, both online and in person). This model would be for analysis only, not financial advice. + +**Mitigation:** Include gambling risk disclaimers, talk about it as purely academic. + +## Timeline + +- Weeks 1-2: Data collection/preparation +- Week 3: EDA and feature engineering +- Weeks 4-5: Model development and evaluation + +**Deliverable:** Trained model with accuracy metrics and feature importance analysis. \ No newline at end of file diff --git a/Ideas/NBA_Game_Prediction_Proposal.md.html b/Ideas/NBA_Game_Prediction_Proposal.md.html new file mode 100644 index 0000000..7377431 --- /dev/null +++ b/Ideas/NBA_Game_Prediction_Proposal.md.html @@ -0,0 +1,48 @@ +Research Question: How can we predict the outcome of NBA games with better than 60% accuracy?
+Approach: Develop a classification model (probably logistic regression) to predict NBA game outcomes using historical game statistics and betting odds. The model will identify games with favorable edges to inform predictions.
+Target: Game outcomes (win/loss)
+Key Features:
+Data sources: ESPN, NBA.com, Basektball-reference.com, Kaggle all have pre-compiled datasets of real games going back 20+ years. Additional data can be scraped from these websites if necessary. Feasibility is high—game data and odds are publicly available.
+Two viable approaches:
+Analyze outcome variation by team strength, matchups, injuries, and game context. Identify predictive features (home-court advantage, efficiency metrics). Perform EDA and visualize feature correlations with game outcomes. Calculate correlations between candidate features and game outcomes to determine which have the strongest predictive signals. Visualizations will include scatter plots of team efficiency metrics, heatmaps of feature correlations, and distribution plots comparing home vs. away performance. I can compare the model performance against a simple baseline (like always predicting the higher-seeded team) to ensure the model adds meaningful value.
+Sports Bettors/Fans: Would help make informed decisions on predicting winners and increase profitability.
+Sportsbooks: Understand what drives betting patterns and refine odds-setting.
+NBA Teams: Understanding which factors affect a team’s ability to win would be very interesting to coaches/players/owners.
+Concerns: Model could encourage problem gambling; predictions are probabilistic and not deterministic.
+Legal: Gambling laws vary by state (sports betting is legal in PA, both online and in person). This model would be for analysis only, not financial advice.
+Mitigation: Include gambling risk disclaimers, talk about it as purely academic.
+Deliverable: Trained model with accuracy metrics and feature importance analysis.
+ + \ No newline at end of file diff --git a/presentations/DATA400TestPrez.Rmd b/presentations/DATA400TestPrez.Rmd new file mode 100644 index 0000000..b27708b --- /dev/null +++ b/presentations/DATA400TestPrez.Rmd @@ -0,0 +1,23 @@ +--- +title: "Test Presentation Ninja" +subtitle: "⚔