<?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: Examining Games with More than 15 Carries	</title>
	<atom:link href="http://www.footballperspective.com/examining-games-with-more-than-15-carries/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.footballperspective.com/examining-games-with-more-than-15-carries/</link>
	<description>NFL History and Stats</description>
	<lastBuildDate>Mon, 19 Aug 2013 21:19:35 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: shawn		</title>
		<link>http://www.footballperspective.com/examining-games-with-more-than-15-carries/#comment-36739</link>

		<dc:creator><![CDATA[shawn]]></dc:creator>
		<pubDate>Mon, 19 Aug 2013 21:19:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.footballperspective.com/?p=12809#comment-36739</guid>

					<description><![CDATA[I&#039;m currious how the number of 15+ carries as a percentage of total carries impacts n+1. Maybe the problem isn&#039;t the 370 &#039;threshold&#039;, rather a percentage threshold. For example Larry Johnson&#039;s 15+ carries amounted to 42.3% of his total usage in 2006. Similar percentage for Jamaal Lewis in 2003.]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m currious how the number of 15+ carries as a percentage of total carries impacts n+1. Maybe the problem isn&#8217;t the 370 &#8216;threshold&#8217;, rather a percentage threshold. For example Larry Johnson&#8217;s 15+ carries amounted to 42.3% of his total usage in 2006. Similar percentage for Jamaal Lewis in 2003.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Kibbles		</title>
		<link>http://www.footballperspective.com/examining-games-with-more-than-15-carries/#comment-35676</link>

		<dc:creator><![CDATA[Kibbles]]></dc:creator>
		<pubDate>Tue, 13 Aug 2013 01:06:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.footballperspective.com/?p=12809#comment-35676</guid>

					<description><![CDATA[Your results don&#039;t surprise me, because they match what I&#039;ve seen when I&#039;ve taken a look at it over the years. The backs who get the most carries don&#039;t tend to get hurt more frequently than the backs who don&#039;t.

I would like to say that there are some selection effects at play here. This isn&#039;t to say that more carries don&#039;t lead to injury, it&#039;s to say that the backs that get more carries don&#039;t tend to get injured more. If you took a random player from the &quot;low carry&quot; group and gave him a Dickerson-like workload, he might snap in half within a month. Coaches, however, are very smart people who have access to lots of data and who get paid big bucks to know their players&#039; limitations, so when they give an RB a bunch of carries, that serves as a signal that the coach believes he can handle them.

I think this explains the career of a guy like Mewelde Moore. Moore was a backup for the Vikings and the Steelers, and every time injuries ahead of him pressed him into service, he always wound up outperforming the guys ahead of him on the depth chart... but he never got a starting job. In fact, I believe four different coaching staffs all had Mewelde Moore, and they all used him exactly the same way- change of pace back and emergency backup. The fact that those different coaching staffs all refused to give him a larger workload is indirect evidence that those coaching staffs, who all saw him in practice every day and had a good idea of what he was capable of, all agreed that he couldn&#039;t handle it.

In other words, a large workload might wear a runner down, but you shouldn&#039;t downgrade backs that receive a large workload under the assumption that they&#039;re going to get worn down.]]></description>
			<content:encoded><![CDATA[<p>Your results don&#8217;t surprise me, because they match what I&#8217;ve seen when I&#8217;ve taken a look at it over the years. The backs who get the most carries don&#8217;t tend to get hurt more frequently than the backs who don&#8217;t.</p>
<p>I would like to say that there are some selection effects at play here. This isn&#8217;t to say that more carries don&#8217;t lead to injury, it&#8217;s to say that the backs that get more carries don&#8217;t tend to get injured more. If you took a random player from the &#8220;low carry&#8221; group and gave him a Dickerson-like workload, he might snap in half within a month. Coaches, however, are very smart people who have access to lots of data and who get paid big bucks to know their players&#8217; limitations, so when they give an RB a bunch of carries, that serves as a signal that the coach believes he can handle them.</p>
<p>I think this explains the career of a guy like Mewelde Moore. Moore was a backup for the Vikings and the Steelers, and every time injuries ahead of him pressed him into service, he always wound up outperforming the guys ahead of him on the depth chart&#8230; but he never got a starting job. In fact, I believe four different coaching staffs all had Mewelde Moore, and they all used him exactly the same way- change of pace back and emergency backup. The fact that those different coaching staffs all refused to give him a larger workload is indirect evidence that those coaching staffs, who all saw him in practice every day and had a good idea of what he was capable of, all agreed that he couldn&#8217;t handle it.</p>
<p>In other words, a large workload might wear a runner down, but you shouldn&#8217;t downgrade backs that receive a large workload under the assumption that they&#8217;re going to get worn down.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
