<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Predicting a Playerâ€™s Impact on Teammatesâ€™ Three-Point Shooting</title>
	<atom:link href="http://www.hardwoodparoxysm.com/2009/11/05/predicting-a-player%e2%80%99s-impact-on-teammates%e2%80%99-three-point-shooting/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hardwoodparoxysm.com/2009/11/05/predicting-a-player%e2%80%99s-impact-on-teammates%e2%80%99-three-point-shooting/</link>
	<description>Unbiased opinions from extremely biased people</description>
	<lastBuildDate>Wed, 23 May 2012 04:55:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: JordanPushedOff</title>
		<link>http://www.hardwoodparoxysm.com/2009/11/05/predicting-a-player%e2%80%99s-impact-on-teammates%e2%80%99-three-point-shooting/comment-page-1/#comment-27313</link>
		<dc:creator>JordanPushedOff</dc:creator>
		<pubDate>Sat, 07 Nov 2009 01:31:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.hardwoodparoxysm.com/?p=3637#comment-27313</guid>
		<description>Jon,
Really interesting stuff.  

I&#039;m pretty sure that what you did here was compute 24 different simple bivariate correlations (or in other words, a regression with only one right-hand-side variable) -- i.e. you correlated MinutesPerGame against 3PA, then you correlated MinutesPerGame against 3P%, then you correlated PointsPer40 against 3PA, then you correlated MinutesPerGame against 3P%, etc.

The problem with this is that the &quot;true&quot; model of player performance should involve all 12 explanatory RHS variables simultaneously.  That&#039;s why your R-squared values are so low for each of those bivariate correlations.
...And in turn, the problem with the scenario I just described is (i) all the RHS variables [particularly PER, which is an artificial construct from other stats] would be mutually correlated, which the econometricians call &quot;multicollinearity&quot;, and (ii) you would have a reverse causality problem, which the econometricians call &quot;endogeneity&quot;.

So I don&#039;t have any good solutions (that&#039;s why I&#039;m not a professional statistician, or a professional NBA analyst!) but those are just some thoughts.</description>
		<content:encoded><![CDATA[<p>Jon,<br />
Really interesting stuff.  </p>
<p>I&#8217;m pretty sure that what you did here was compute 24 different simple bivariate correlations (or in other words, a regression with only one right-hand-side variable) &#8212; i.e. you correlated MinutesPerGame against 3PA, then you correlated MinutesPerGame against 3P%, then you correlated PointsPer40 against 3PA, then you correlated MinutesPerGame against 3P%, etc.</p>
<p>The problem with this is that the &#8220;true&#8221; model of player performance should involve all 12 explanatory RHS variables simultaneously.  That&#8217;s why your R-squared values are so low for each of those bivariate correlations.<br />
&#8230;And in turn, the problem with the scenario I just described is (i) all the RHS variables [particularly PER, which is an artificial construct from other stats] would be mutually correlated, which the econometricians call &#8220;multicollinearity&#8221;, and (ii) you would have a reverse causality problem, which the econometricians call &#8220;endogeneity&#8221;.</p>
<p>So I don&#8217;t have any good solutions (that&#8217;s why I&#8217;m not a professional statistician, or a professional NBA analyst!) but those are just some thoughts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mid-Afternoon Milk Mustache, featuring the secret Sports Guy phone call &#124; Stacheketball, an NBA Blog</title>
		<link>http://www.hardwoodparoxysm.com/2009/11/05/predicting-a-player%e2%80%99s-impact-on-teammates%e2%80%99-three-point-shooting/comment-page-1/#comment-27204</link>
		<dc:creator>Mid-Afternoon Milk Mustache, featuring the secret Sports Guy phone call &#124; Stacheketball, an NBA Blog</dc:creator>
		<pubDate>Thu, 05 Nov 2009 21:49:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.hardwoodparoxysm.com/?p=3637#comment-27204</guid>
		<description>[...] The Lampshade: Nichols on predicting a player&#8217;s impact on his teammates&#8217; three-point shooting [Hardwood Paroxysm] [...]</description>
		<content:encoded><![CDATA[<p>[...] The Lampshade: Nichols on predicting a player&#8217;s impact on his teammates&#8217; three-point shooting [Hardwood Paroxysm] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Nolan</title>
		<link>http://www.hardwoodparoxysm.com/2009/11/05/predicting-a-player%e2%80%99s-impact-on-teammates%e2%80%99-three-point-shooting/comment-page-1/#comment-27167</link>
		<dc:creator>Matt Nolan</dc:creator>
		<pubDate>Thu, 05 Nov 2009 17:02:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.hardwoodparoxysm.com/?p=3637#comment-27167</guid>
		<description>An interesting approach to things.  One stat that I think could provide some sort of better explanation would be how often said player takes shots at the basket (not makes) as this would mean that defenses are more likely to shade off players and collapse in on that player leading to more open three point attempts if the player is able to get the ball to an outside shooter.</description>
		<content:encoded><![CDATA[<p>An interesting approach to things.  One stat that I think could provide some sort of better explanation would be how often said player takes shots at the basket (not makes) as this would mean that defenses are more likely to shade off players and collapse in on that player leading to more open three point attempts if the player is able to get the ball to an outside shooter.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

