nba-player-compatibility/about.html at master · zanderchase/nba-player-compatibility · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
<!DOCTYPE html>
<html>
  <head>
    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
    <meta name="description" content="">
    <meta name="author" content="">
    <title>Chasing Insights</title>
    <link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/4.1.3/css/bootstrap.min.css" integrity="sha384-MCw98/SFnGE8fJT3GXwEOngsV7Zt27NXFoaoApmYm81iuXoPkFOJwJ8ERdknLPMO" crossorigin="anonymous">
    <link rel='stylesheet' href='style.css'>
    <link rel='stylesheet' href='searchbox.css'>
    <link href="https://fonts.googleapis.com/css?family=Montserrat:400,700" rel="stylesheet" type="text/css">
    <link href="https://fonts.googleapis.com/css?family=Lato:400,700,400italic,700italic" rel="stylesheet" type="text/css">
    <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.3.0/css/font-awesome.min.css">
  </head>
  <body id="page-top">

    <!-- Nav Bar -->
    <nav class="navbar navbar-expand-lg bg-secondary fixed-top text-uppercase" id="mainNav">
      <div class="container">
        <a class="navbar-brand js-scroll-trigger" href="#page-top">Chasing Insights</a>
        <button class="navbar-toggler navbar-toggler-right text-uppercase bg-primary text-white rounded" type="button" data-toggle="collapse" data-target="#navbarResponsive" aria-controls="navbarResponsive" aria-expanded="false" aria-label="Toggle navigation">
          Menu
          <i class="fa fa-bars"></i>
        </button>
        <div class="collapse navbar-collapse" id="navbarResponsive">
          <ul class="navbar-nav ml-auto">
            <li class="nav-item mx-0 mx-lg-1">
              <a class="nav-link py-3 px-0 px-lg-3 rounded js-scroll-trigger" href="index.html">Home</a>
            </li>
            <li class="nav-item mx-0 mx-lg-1">
              <a class="nav-link py-3 px-0 px-lg-3 rounded js-scroll-trigger" href="about.html">About</a>
            </li>
            <li class="nav-item mx-0 mx-lg-1">
              <a class="nav-link py-3 px-0 px-lg-3 rounded js-scroll-trigger" href="future_projects.html">Future Projects</a>
            </li>
            <li class="nav-item mx-0 mx-lg-1">
              <a class="nav-link py-3 px-0 px-lg-3 rounded js-scroll-trigger" href="contact.html">Contact</a>
            </li>
          </ul>
        </div>
      </div>
    </nav>


    <!-- About Section -->
    <section id="about">
      <div class="container">
        <h2 class="text-center text-uppercase text-secondary mb-0">About</h2>
        <hr class="star-dark mb-5">
        <div class="row">
          <div class="col-lg-5 ml-auto">
            <h4>Goal:</h4>
            <p class="lead">This works attempts to answer the question of how compatible two players are when they are on the court at the same time. For a more in depth explanation, see <a href=https://hwchase17.github.io/sports/>here</a>.</p>
          </div>
          <div class="col-lg-5 mr-auto">
            <h4>Open Source Code:</h4>
            <p class="lead">For all the code needed to reproduce (and improve on!) this analysis, see <a href=https://github.com/hwchase17/sports> https://github.com/hwchase17/sports</a>.</p>
          </div>
        </div>
      </div>
    </section>


    <!-- About Section -->
    <section class="bg-primary text-white mb-0" id="faq">
      <div class="container">
        <h2 class="text-center text-uppercase text-white">FAQ</h2>
        <hr class="star-light mb-5">
        <div class="row">
          <div class="col-lg-6 ml-auto">
            <h4 class="question">What is this?</h4>
            <p class="lead">Short answer: an attempt to model how compatible two players are. See <a class='darklink' href=https://hwchase17.github.io/sports> https://hwchase17.github.io/sports </a> for a longer answer.</p>

            <h4 class="question">What season is this data for?</h4>
            <p class="lead">2017-18 NBA season</p>

            <h4 class="question">What is the target that you measuring?</h4>
            <p class="lead">Points per shot (PPS). Notably, PPS does NOT attempt to account for things like turnovers and rebounds.</p>

            <h4 class="question">How you estimate compatibility?</h4>
            <p class="lead">Let’s walk through an example of estimating player A’s compatibility with player B. We first estimate PPS when player A is shooting with an average lineup on the court (call this estimate X). We then estimate PPS when player B is on the court (with an otherwise average lineup) and an average player of the same position as player A is shooting (call this estimate Y). Finally, we estimate the PPS when player A is shooting and player B is also on the court (call this estimate Z). The compatibility of two players is Z - (Y + X) / 2.</p>

            <h4 class="question">What else is coming?</h4>
            <p class="lead"> A few things. In order of priority:
              <br> 1) Which players are most compatible with player A?
              <br> 2) Which players are most similar with player B?
              <br> 3) Estimates of value/compatibility that include turnovers/rebounds
              <br> 4) More seasons worth of data
              <br> 5) More robust estimation techniques
            </p>

            <h4 class="question">Your site is wrong and stupid.</h4>
            <p class="lead">That’s not a question.</p>


          </div>
          <div class="col-lg-6 mr-auto">
            <h4 class="question">I have this weird result! Why is this so?</h4>
            <p class="lead">I don’t know exactly, but here’s how you can figure out!
              <br> 1) Read the rest of the FAQ (might be answered)
              <br> 2) Reach out to us (either twitter or email, both can be found on the Contact page) and ask
              <br> 3) It is possible that that our estimates produce some counterintuitive(/wrong) results, that is definitely not out of the question!
            </p>
            <h4 class="question">Why do you not account for turnovers/rebounds? Will you in the future?</h4>
            <p class="lead">Because the methods we would use there are not that novel and so aren’t as interesting. We do have plans to do so in the future.</p>

            <h4 class="question">What is this ‘average lineup’?</h4>
            <p class="lead">Two guards, two forwards, one center - all with skills of the average player at their position</p>

            <h4 class="question">Why do you do everything relative to positional average?</h4>
            <p class="lead">It presents more intuitive results. For example, centers have a very high PPS estimate (cause they usually get easier shots than guards). So if we didn’t account for position, all centers would look like offensive gods and all guards would look like scrubs. For the actual calculation of compatibility it is irrelevant.</p>

            <h4 class="question">I want you guys to do {INSERT REASONABLE DEMAND HERE}! Can you do it?</h4>
            <p class="lead">Maybe! If you reach out to us, ask nicely, and it seems like something there would be demand for.</p>

          </div>
        </div>
      </div>
    </section>

    <!-- Footer -->
    <footer class="footer text-center">
          <div class="col-sm-12 row align-items-center justify-content-center">
              <li class="list-inline-item">
                <a class="btn btn-outline-light btn-social text-center rounded-circle" href="https://twitter.com/aabsblog?lang=en">
                  <i class="fa fa-fw fa-twitter"></i>
                </a>
              </li>
          </div>
    </footer>

  </body>
</html>