<?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/"
		>
<channel>
	<title>Comments on: Reviewing PrOPS</title>
	<atom:link href="http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/</link>
	<description>Economic Thinking about Baseball</description>
	<lastBuildDate>Sun, 09 Jan 2011 17:16:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: JC</title>
		<link>http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/comment-page-1/#comment-24947</link>
		<dc:creator>JC</dc:creator>
		<pubDate>Wed, 20 Dec 2006 05:14:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/#comment-24947</guid>
		<description>No, post number 9 shows that if you take a completely bastardized version of my model (GPA = f(GB, FB)) and look at the extremes, that the predicted outcome fluctuates for two players. And  your mini-model is likely suffering from massive omitted variable bias (something you were worried about on my behalf earlier). Your fluctuations could show something important OR they could reflect the fact that when you don&#039;t include line drive, walk rates, etc. the model is extremely sensitive to the change in specification.

You are right that there is zero opportunity cost to using another method if it is superior. I spent numerous hours judging specifications based on many factors. Usually, I do not like to use ratios as variables, but I found that when I did, the model predicted better and helped me avoid some collineariarity problems. I didn&#039;t make the choice to piss you off, nor do I continue to do so for this reason. I haven&#039;t merely dismissed your argument. I responded, and when you kept pressing an incorrect point, I decided it wasn&#039;t worth continuing the discussion.

I make mistakes all the time, and I am always willing to admit them and change my mind. After all, it was you who pointed out to me a few weeks ago that a 10% growth in salary was in fact sustainable, and I changed my mind to agree with you. You were right, and I would be stupid to disagree with you on that. The reason I&#039;m not bending here, is that you&#039;re not telling me anything useful.

We can argue all day about what is the proper specification to use. It&#039;s very easy to be the  guy in the audience who says &quot;did you control for X or Y?&quot; I could do an infinite number of things to this model. I waded through all of the possible models, weighed the costs and benefits of different specification, and ultimately chose the one that I felt to be the best. I took the time to develop this and publish this with my name and reputation on the line. I don&#039;t have the time to go back and show what happens every time someone things one little thing could make a big difference. No one does.

This is why it&#039;s necessary for someone to take the next step and make PrOPS obsolete. There&#039;s not much to be gained by obsessing over the minutia of potential imperfections in the model. Quit bitching about LPs and invent the CD.

All I&#039;m saying is &quot;here&#039;s PrOPS, here&#039;s how it predicts, let&#039;s see someone do better.&quot; You&#039;ve got the data, you&#039;ve got your own idea as to what ought to be done. Why not give it a shot? Generate TtOPS. If it predicts better than PrOPS, I&#039;ll use it with glee. That&#039;s how progress happens.</description>
		<content:encoded><![CDATA[<p>No, post number 9 shows that if you take a completely bastardized version of my model (GPA = f(GB, FB)) and look at the extremes, that the predicted outcome fluctuates for two players. And  your mini-model is likely suffering from massive omitted variable bias (something you were worried about on my behalf earlier). Your fluctuations could show something important OR they could reflect the fact that when you don&#8217;t include line drive, walk rates, etc. the model is extremely sensitive to the change in specification.</p>
<p>You are right that there is zero opportunity cost to using another method if it is superior. I spent numerous hours judging specifications based on many factors. Usually, I do not like to use ratios as variables, but I found that when I did, the model predicted better and helped me avoid some collineariarity problems. I didn&#8217;t make the choice to piss you off, nor do I continue to do so for this reason. I haven&#8217;t merely dismissed your argument. I responded, and when you kept pressing an incorrect point, I decided it wasn&#8217;t worth continuing the discussion.</p>
<p>I make mistakes all the time, and I am always willing to admit them and change my mind. After all, it was you who pointed out to me a few weeks ago that a 10% growth in salary was in fact sustainable, and I changed my mind to agree with you. You were right, and I would be stupid to disagree with you on that. The reason I&#8217;m not bending here, is that you&#8217;re not telling me anything useful.</p>
<p>We can argue all day about what is the proper specification to use. It&#8217;s very easy to be the  guy in the audience who says &#8220;did you control for X or Y?&#8221; I could do an infinite number of things to this model. I waded through all of the possible models, weighed the costs and benefits of different specification, and ultimately chose the one that I felt to be the best. I took the time to develop this and publish this with my name and reputation on the line. I don&#8217;t have the time to go back and show what happens every time someone things one little thing could make a big difference. No one does.</p>
<p>This is why it&#8217;s necessary for someone to take the next step and make PrOPS obsolete. There&#8217;s not much to be gained by obsessing over the minutia of potential imperfections in the model. Quit bitching about LPs and invent the CD.</p>
<p>All I&#8217;m saying is &#8220;here&#8217;s PrOPS, here&#8217;s how it predicts, let&#8217;s see someone do better.&#8221; You&#8217;ve got the data, you&#8217;ve got your own idea as to what ought to be done. Why not give it a shot? Generate TtOPS. If it predicts better than PrOPS, I&#8217;ll use it with glee. That&#8217;s how progress happens.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tangotiger</title>
		<link>http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/comment-page-1/#comment-24924</link>
		<dc:creator>tangotiger</dc:creator>
		<pubDate>Wed, 20 Dec 2006 03:04:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/#comment-24924</guid>
		<description>My post #9 clearly shows that it makes a huge difference for the extreme GB and FB hitters, if you use GB/FB or FB/GB.  However, there is no change whatsoever if you use GB/(GB+FB) or FB/(GB+FB).

There is no justitication for using one ratio (GB/FB) over the other (FB/GB), even though they absolutely give you different results.  In fact, you are not even justifying it.  Just deciding to use it.

There is zero opportunity cost to changing from ratios to rates, since I was able to generate 3 different regression equations in 5 minutes.

Your thread started with a comment about fans being skeptical, and here I am, giving you a thoughtful and legitimate beef, and you are dismissing it with &quot;if you don&#039;t like it, don&#039;t use it&quot;.</description>
		<content:encoded><![CDATA[<p>My post #9 clearly shows that it makes a huge difference for the extreme GB and FB hitters, if you use GB/FB or FB/GB.  However, there is no change whatsoever if you use GB/(GB+FB) or FB/(GB+FB).</p>
<p>There is no justitication for using one ratio (GB/FB) over the other (FB/GB), even though they absolutely give you different results.  In fact, you are not even justifying it.  Just deciding to use it.</p>
<p>There is zero opportunity cost to changing from ratios to rates, since I was able to generate 3 different regression equations in 5 minutes.</p>
<p>Your thread started with a comment about fans being skeptical, and here I am, giving you a thoughtful and legitimate beef, and you are dismissing it with &#8220;if you don&#8217;t like it, don&#8217;t use it&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JC</title>
		<link>http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/comment-page-1/#comment-24889</link>
		<dc:creator>JC</dc:creator>
		<pubDate>Wed, 20 Dec 2006 01:26:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/#comment-24889</guid>
		<description>Didn&#039;t control for handedness or shifts, so it could be an issue. 

PrOPS correlate more highly from year to year than OPS, about .1 more in terms of R2.</description>
		<content:encoded><![CDATA[<p>Didn&#8217;t control for handedness or shifts, so it could be an issue. </p>
<p>PrOPS correlate more highly from year to year than OPS, about .1 more in terms of R2.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J. Cross</title>
		<link>http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/comment-page-1/#comment-24856</link>
		<dc:creator>J. Cross</dc:creator>
		<pubDate>Tue, 19 Dec 2006 23:36:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/#comment-24856</guid>
		<description>Oh, the other thing I&#039;d be interested in is whether there&#039;s any y-to-y correlation in PrOPS - OPS.</description>
		<content:encoded><![CDATA[<p>Oh, the other thing I&#8217;d be interested in is whether there&#8217;s any y-to-y correlation in PrOPS &#8211; OPS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J. Cross</title>
		<link>http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/comment-page-1/#comment-24855</link>
		<dc:creator>J. Cross</dc:creator>
		<pubDate>Tue, 19 Dec 2006 23:33:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/#comment-24855</guid>
		<description>JCB,

I may have posted about this before but looking at the top Props-OPS guys I wonder if the shift is playing a role and whether left handed sluggers tend to under perform their PrOPS.  Is this something you&#039;ve considered?

Jared</description>
		<content:encoded><![CDATA[<p>JCB,</p>
<p>I may have posted about this before but looking at the top Props-OPS guys I wonder if the shift is playing a role and whether left handed sluggers tend to under perform their PrOPS.  Is this something you&#8217;ve considered?</p>
<p>Jared</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JC</title>
		<link>http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/comment-page-1/#comment-24849</link>
		<dc:creator>JC</dc:creator>
		<pubDate>Tue, 19 Dec 2006 22:45:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/#comment-24849</guid>
		<description>&lt;blockquote&gt;Ah, but the coefficient will not change accordingly. What will happen is this: mow the guys with the highest FB/GB ratio will move *more* than the high GB/FB ratio players.&lt;/blockquote&gt;
This is incorrect.  The coefficients (including the constant) will adjust in magnitude, not just in sign. That&#039;s how multiple regression analysis works.

&lt;em&gt;EDIT: Text Removed
[Part of a comment was marked as spam, so I was commenting on something that was previously confusing.]&lt;/em&gt;

In any event, I don&#039;t mean to be rude, but I&#039;m tired of discussing this with you. There is an opportunity cost to refining things, and I&#039;m done with PrOPS until the data improves significantly. If you don&#039;t see any value to it, don&#039;t use it. I&#039;m comfortable with it.  I welcome you, or anyone else, to generate your own version/improvement. I have no doubt that the system could be improved, and I would be happy to see it done rather than quibble over minor details of the model that are irrelevant.</description>
		<content:encoded><![CDATA[<blockquote><p>Ah, but the coefficient will not change accordingly. What will happen is this: mow the guys with the highest FB/GB ratio will move *more* than the high GB/FB ratio players.</p></blockquote>
<p>This is incorrect.  The coefficients (including the constant) will adjust in magnitude, not just in sign. That&#8217;s how multiple regression analysis works.</p>
<p><em>EDIT: Text Removed<br />
[Part of a comment was marked as spam, so I was commenting on something that was previously confusing.]</em></p>
<p>In any event, I don&#8217;t mean to be rude, but I&#8217;m tired of discussing this with you. There is an opportunity cost to refining things, and I&#8217;m done with PrOPS until the data improves significantly. If you don&#8217;t see any value to it, don&#8217;t use it. I&#8217;m comfortable with it.  I welcome you, or anyone else, to generate your own version/improvement. I have no doubt that the system could be improved, and I would be happy to see it done rather than quibble over minor details of the model that are irrelevant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tangotiger</title>
		<link>http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/comment-page-1/#comment-24841</link>
		<dc:creator>tangotiger</dc:creator>
		<pubDate>Tue, 19 Dec 2006 22:09:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/#comment-24841</guid>
		<description>The correlation coefficients were (r) were .21, .26, .26.  And, it should go without saying, that using FB/(GB+FB) produced the exact same estimated GPA for each player as the GB rate, as well as the exact same r.</description>
		<content:encoded><![CDATA[<p>The correlation coefficients were (r) were .21, .26, .26.  And, it should go without saying, that using FB/(GB+FB) produced the exact same estimated GPA for each player as the GB rate, as well as the exact same r.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tangotiger</title>
		<link>http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/comment-page-1/#comment-24840</link>
		<dc:creator>tangotiger</dc:creator>
		<pubDate>Tue, 19 Dec 2006 21:58:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/#comment-24840</guid>
		<description>I just ran three different regressions, using GB/FB ratio, FB/GB ratio, and GB/(GB+FB) or GB rate.  This was ran against GPA on the THT site.  (The use of GPA, or OPS, etc, doesn&#039;t really matter.)  I used 2004-2006 data of all players with at least 502 PA.

The 2006 Frank Thomas is the most extreme, with a FB/GB of 2.44.  His resulting regression yielded results of: .287, .313, .298.

At the other end is the 2004 Ichiro, with a GB/FB of 3.55.  His results are: .247, .261, .255.

The sample standard deviations are: .0057, .0072, .0071

In all cases, the mean was .276.

GPA is analogous to batting average.  Those are some HUGE differences, don&#039;t you think?</description>
		<content:encoded><![CDATA[<p>I just ran three different regressions, using GB/FB ratio, FB/GB ratio, and GB/(GB+FB) or GB rate.  This was ran against GPA on the THT site.  (The use of GPA, or OPS, etc, doesn&#8217;t really matter.)  I used 2004-2006 data of all players with at least 502 PA.</p>
<p>The 2006 Frank Thomas is the most extreme, with a FB/GB of 2.44.  His resulting regression yielded results of: .287, .313, .298.</p>
<p>At the other end is the 2004 Ichiro, with a GB/FB of 3.55.  His results are: .247, .261, .255.</p>
<p>The sample standard deviations are: .0057, .0072, .0071</p>
<p>In all cases, the mean was .276.</p>
<p>GPA is analogous to batting average.  Those are some HUGE differences, don&#8217;t you think?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tangotiger</title>
		<link>http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/comment-page-1/#comment-24833</link>
		<dc:creator>tangotiger</dc:creator>
		<pubDate>Tue, 19 Dec 2006 21:02:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/#comment-24833</guid>
		<description>Ah, but the coefficient will not change accordingly.  What will happen is this: mow the guys with the highest FB/GB ratio will move *more* than the high GB/FB ratio players.

Think of it in an extreme situation: you have a guy with 100 GB and 1 FB.  In your current PrOps, this guy has a 100.00 value, which you multiply by some coefficient, say &quot;.002&quot;.  So, he moves +.20 points up.  If on the other hand you used FB/GB ratio, your coefficient may be &quot;-.002&quot;, which multiplied to 1/100 (or .01) will be zero.

From where I sit, using GB/FB taints your process whereby the higher the GB, the more impact than the higher the FB.

If you create a FB/GB version of PrOps, show your results both way (old Props, new Props) for Frank Thomas and Derek Jeter, and you will see the impact of this bias.</description>
		<content:encoded><![CDATA[<p>Ah, but the coefficient will not change accordingly.  What will happen is this: mow the guys with the highest FB/GB ratio will move *more* than the high GB/FB ratio players.</p>
<p>Think of it in an extreme situation: you have a guy with 100 GB and 1 FB.  In your current PrOps, this guy has a 100.00 value, which you multiply by some coefficient, say &#8220;.002&#8243;.  So, he moves +.20 points up.  If on the other hand you used FB/GB ratio, your coefficient may be &#8220;-.002&#8243;, which multiplied to 1/100 (or .01) will be zero.</p>
<p>From where I sit, using GB/FB taints your process whereby the higher the GB, the more impact than the higher the FB.</p>
<p>If you create a FB/GB version of PrOps, show your results both way (old Props, new Props) for Frank Thomas and Derek Jeter, and you will see the impact of this bias.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JC</title>
		<link>http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/comment-page-1/#comment-24821</link>
		<dc:creator>JC</dc:creator>
		<pubDate>Tue, 19 Dec 2006 20:38:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.sabernomics.com/sabernomics/index.php/2006/12/reviewing-props/#comment-24821</guid>
		<description>&lt;blockquote&gt;
As for using the ratio, then how to justify using GB/FB instead of the reverse?
&lt;/blockquote&gt;

There is nothing wrong with using the reverse. The coefficient will change accordingly.

&lt;blockquote&gt;
Just because something best-fits better on the sample doesn’t mean that it’s the right thing. A best-fit analysis would give the run value of a double .66 and the single .52 (instead of the more true .77, .47).
&lt;/blockquote&gt;

That should read &lt;i&gt;a mis-specified&lt;/i&gt; best-fit analysis. I don&#039;t understand how pointing out that it&#039;s possible to mis-specify a regression sheds any light on the situation. I&#039;m certainly aware of this, and I always bend over backwards in an effort to avoid such problems. 

In any event, any mis-specification in this model, and the corresponding omitted variable bias that would result, would apply when including GB and FB as a ratio or if I included only one.  

All else being equal, I&#039;ll pick the model with the  better fit.</description>
		<content:encoded><![CDATA[<blockquote><p>
As for using the ratio, then how to justify using GB/FB instead of the reverse?
</p></blockquote>
<p>There is nothing wrong with using the reverse. The coefficient will change accordingly.</p>
<blockquote><p>
Just because something best-fits better on the sample doesn’t mean that it’s the right thing. A best-fit analysis would give the run value of a double .66 and the single .52 (instead of the more true .77, .47).
</p></blockquote>
<p>That should read <i>a mis-specified</i> best-fit analysis. I don&#8217;t understand how pointing out that it&#8217;s possible to mis-specify a regression sheds any light on the situation. I&#8217;m certainly aware of this, and I always bend over backwards in an effort to avoid such problems. </p>
<p>In any event, any mis-specification in this model, and the corresponding omitted variable bias that would result, would apply when including GB and FB as a ratio or if I included only one.  </p>
<p>All else being equal, I&#8217;ll pick the model with the  better fit.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

