GithubHelp home page GithubHelp logo

an0moly / ncaa_hoops Goto Github PK

View Code? Open in Web Editor NEW

This project forked from lbenz730/ncaa_hoops

0.0 0.0 0.0 4.23 GB

All the files used in my NCAA Men's Basketball modeling, predictions, bracketology, and Ivy League simulations.

R 93.84% Shell 0.18% HTML 5.98%

ncaa_hoops's Introduction

NCAA_Hoops

All the code that powers my NCAA Men's Basketball R Shiny Web Application application.

Application Files:

  • ui.R: User Interface for web application
  • sever.R: Backend for web application
  • global.R: Pre-loads data/helper functions for web application.

Other Files:

Model_3.0.R: Control panel for everything NCAA Hoops related that the application ultimately shows:

  • Power Rankings
  • Predictions
  • Conference simulations and distributions
  • Bracketology
  • Ivy League simulations/playoff swing factor (not in application)

ncaa_hoop_scraper.R: An algorithim to scrape game schedule/result data from the NCAA website. This script is mostly copied (with slight modifications) from a scrape written by Prof. Jay Emerson and used in STAT 230: Introductory Data Analysis (Spring 2016).

3.0_Files/: A collection of files that are essentially the "inner workings" of everything done in this project. Every script in this directory contains functions. Those functions are executed in the master file, Model_3.0.R.

  • Ivy_Sims.R: Simulates the Ivy League Basketball season in order to estimate playoff odds and calcuates the "Playoff Swing Factor" of each conference game.
  • bracketology.R: Assembles the predicted bracket:
  • helpers.R: A file with miscellanious functions used throughout the project.
  • powerrankings.R: Computes the team rankings.
  • record_evaluator.R: Examines the quality of each team's resume by computing Quality Wins (as recently redefinined by the NCAA tournament selection committee), Strength of Record, and Wins Above Bubble.
  • rpi.R: Predictions end of season RPI for each team.
  • tourney_sim.R: Function for simulating college basketball tournaments with parameters left to the user. The user specifies teams (from best seed to worst seed), along with a vector of seeds. Note that after games have been played, the seeds vector must be entered in the order of highest possible seed for each given slot. For example, if we have quarterfinals where the matchups are 1 vs. 9, 2 vs. 7, 3 vs. 14, and 4 vs. 12, we'd set seeds = (1, 2, 3, 4, 12, 14, 7, 9), as 5, 6, 7, 8 are the "chalk" seeds occupied by 12, 14, 7, and 9 in this hypothetical 15 team tournament. The user must also enter the number of single byes, the number of double_byes, the number of simulations to run nsims, and a parameter for home court advantage, hca. If the tournament is played at a neutral site, set hca = NA. If the higher seed is always given home court advantage, set hca = "seed". If one team hosts the tournament (even if not the top seed), set hca = INSERT_TEAM_NAME.
  • Bracketology/: Collection of .csv files used in bracket creation
    • bids.csv: Table of tournament bids broken down by conference.
    • bracket.csv: The final bracket produced.
    • bracket_math.csv: Table of bracket metrics for all 357 Division-1 teams.
    • bubble.csv: Bracket metrics for the first 16 teams missing the field as at-large bids.
    • resumes.csv: Subset of bracket metrics (resume evaluation, strength of record, wins above bubble) produced by record_evaluator.R.
    • rpi.csv: Projected end of season RPI for each team. Produced by rpi.R.
    • historical/: A collection of files used to predict NCAA Tournament seed from the various metrics in this directory.
  • Info/: A collection of information used to adjust model weights and determine postseason status.
    • conferences.csv: List of teams with their conference, postseason eligibility status, and elimination status from automatic bid contention.
    • mins_YYYY.csv: Percentage of team's minutes returning during the next season. Acquired from Bart Tovrik.
    • recruiting.csv: 247Sports recruiting scores for each team's incoming freshman class.
    • transfers.csv: Data on transfers eligible to play in the 2017-18 season, pulled from http://www.barttorvik.com/trankpre.php.
  • History/: Some historical files of interest.
  • Power_Rankings/: Collection of .csv files produced by powerrankings.R.
    • power_rankings.csv: Ranking of all 357 teams
    • conf_summary.csv: Ranking of the 32 Division 1 conferences, by median ranking.
    • pr_by_conf.csv: Ranking of teams by YUSAG Coefficient, sorted by conference.
  • Predictions/:
    • playoffs.csv: Ivy League playoff odds.
    • psf.csv: Playoff Swing Factor for most recent week of Ivy League conference games.
  • Results/: Complete NCAA Basketball schedule/results through a given date. Sub-directories indicate the year/season, with .csv files given in NCAA_Hoops_results_day_month_year.csv format.

ncaa_hoops's People

Contributors

lbenz730 avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.