<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-8734744291040505450</id><updated>2011-10-05T12:10:35.823-04:00</updated><category term='inequalities'/><category term='cyclical graphs'/><category term='side constraints'/><category term='elimination brackets'/><category term='significance'/><category term='significance test'/><category term='NCAA'/><category term='courses'/><category term='weighted wins'/><category term='cross-examination debate'/><category term='geographic mixing'/><category term='ordered set'/><category term='lower boundary'/><category term='convergence'/><category term='power-matching'/><category term='infinite series'/><category term='chain rule'/><category term='Cartesian coordinates'/><category term='pre-calculus'/><category term='driving vs. flying'/><category term='debate'/><category term='public speaking'/><category term='network graph theory'/><category term='values'/><category term='regression'/><category term='bell curve'/><category term='pairing methods'/><category term='balancing'/><category term='slope'/><category term='high school debate'/><category term='combinatorics'/><category term='standard deviation'/><category term='normal distribution'/><category term='trigonometric identities'/><category term='debate tournaments'/><category term='mautam'/><category term='swiss system'/><category term='trigonometry'/><category term='rankings'/><category term='seed'/><category term='bias'/><category term='cause and effect'/><category term='syllogism'/><category term='histogram'/><category term='schedule strength'/><category term='tabulation program'/><category term='mautaam'/><category term='Nationals'/><category term='brackets'/><category term='logic'/><category term='judge'/><category term='definitions'/><category term='matrices'/><category term='tournament'/><category term='partial elimination round'/><category term='recursive functions'/><category term='parametric equations'/><category term='fairness'/><category term='black rats'/><category term='philosophy'/><category term='algorithm'/><category term='student groups'/><category term='round robin'/><category term='cycles'/><category term='Pascal&apos;s triangle'/><category term='Venn diagram'/><category term='matched pairs'/><category term='derivatives'/><category term='network graph'/><category term='Gaussian distribution'/><category term='exponential growth'/><category term='side bias'/><category term='round robins'/><category term='tangents'/><category term='incidence matrix'/><category term='Aristotle'/><category term='co-functions'/><category term='facts'/><category term='ellipses'/><category term='team strength'/><category term='strength of schedule'/><category term='interstates'/><category term='hockey'/><category term='NFL'/><category term='statistics'/><category term='opponent wins'/><category term='breaks'/><category term='circles'/><title type='text'>The Art of Logic</title><subtitle type='html'>Thoughts and notes on teaching mathematics, logic, and debate to high school students: clear communication, good representations, analytical thinking, and argumentation.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>31</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-5848967506716519807</id><published>2011-08-09T10:41:00.010-04:00</published><updated>2011-08-09T14:07:09.936-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='NFL'/><category scheme='http://www.blogger.com/atom/ns#' term='debate'/><category scheme='http://www.blogger.com/atom/ns#' term='high school debate'/><category scheme='http://www.blogger.com/atom/ns#' term='geographic mixing'/><category scheme='http://www.blogger.com/atom/ns#' term='Nationals'/><title type='text'>A modest proposal to ensure geographic mixing at Nationals</title><content type='html'>I wrote an article for the &lt;span style="font-style: italic;"&gt;Rostrum&lt;/span&gt; (which I'll link to once it comes out in September) about using geographic and strength criteria to mix teams in preliminary rounds at NFL Nationals. In other words, I advocate the use of a system that ensures that each team will debate a broad cross-section of different opponents, from different parts of the country and at different skill/experience levels, as measured by NFL debate points. I won't repeat the arguments here about &lt;span style="font-weight: bold;"&gt;why&lt;/span&gt; I think this is a worthwhile goal, except for this one thought: Geographic mixing makes it likely that the less experienced teams -- who probably have not travelled far afield -- will debate opponents at Nationals they have never seen before. Even with geographic mixing, there is still a chance that national circuit teams might face an opponent in preliminary rounds at Nationals they have debated many times during the invitational season. That is why there is also a need for skill/experience level mixing. Both are necessary to make it likely every team will see "new" opponents at Nationals.&lt;br /&gt;&lt;br /&gt;I will focus on two technical concerns about my proposal in this blog post.&lt;br /&gt;&lt;br /&gt;Concern 1: Can two criteria really be maximized at the same time?&lt;br /&gt;&lt;br /&gt;Yes and no. In a strict sense, no: only one variable can truly be maximized at a time. That is to say, you can have a round where the average geographic distance between opponents is maximized, or you can have a round where the average difference of skill/experience between opponents is maximized, but you can not have both at the same time. However, in a looser, more practical sense, the answer is yes: you can have a round where opponents are well-mixed geographically (even though not maximally mixed) AND well-mixed skill/experience-wise (even though not maximally mixed). Let me show you with the sample data I used in the &lt;span style="font-style: italic;"&gt;Rostrum&lt;/span&gt; article.&lt;br /&gt;&lt;br /&gt;Here are 26 fictitious teams, spread throughout the country in geographic clusters, and at different skill/experience levels (normally distributed from 0 to 1 in my sample data). I imagined that the NFL points could be scaled so the weakest team to qualify was given a rating of 0 and the most experienced a 1, but they do not need to be scaled at all for this method to work. The median distance between every possible pairing in the whole set is 2138 miles. The median difference in experience is 0.28 units.&lt;br /&gt;&lt;br /&gt;If one tries to maximize geographic spread, the round 1 pairings that are selected would look like this:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" style="font-weight: bold;" href="http://3.bp.blogspot.com/-KY1NjxksN0U/TkF2ghHBMRI/AAAAAAAAAPM/AYPUEP-zYDE/s1600/g1.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 183px;" src="http://3.bp.blogspot.com/-KY1NjxksN0U/TkF2ghHBMRI/AAAAAAAAAPM/AYPUEP-zYDE/s320/g1.jpg" alt="" id="BLOGGER_PHOTO_ID_5638918509460271378" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;The median distance between two opponents in each pairing is 3333 miles, and the shortest distance is 2452 miles. In other words, every match chosen is above the average of 2138 miles. This is maximized; it is a Pareto optimal solution, meaning that any change to improve a pairing by swapping opponents would have to make another pairing worse. The net result can not be improved. In the first round, teams in the middle of the country would debate coastal teams. As the tournament proceeds, each team would get opponents from every geographic region of the country.&lt;br /&gt;&lt;br /&gt;If one tries to maximize the differences of skill/experience levels, the round 1 pairing would look like this:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" style="font-weight: bold;" href="http://4.bp.blogspot.com/-fEDkntHtYRU/TkF2vmZSgYI/AAAAAAAAAPU/n53U2Yv_vlc/s1600/s1.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 170px;" src="http://4.bp.blogspot.com/-fEDkntHtYRU/TkF2vmZSgYI/AAAAAAAAAPU/n53U2Yv_vlc/s320/s1.jpg" alt="" id="BLOGGER_PHOTO_ID_5638918768577118594" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;The median difference between opponents is 0.45 units, and the least difference is 0.42 units. Every match chosen is above the average of 0.28 units. Again, this is a Pareto optimal solution. In the first round, mid-level teams would debate either inexperienced or highly experienced teams. No inexperienced team would be matched against a highly experienced team -- this would force two mid-level teams to debate. However, in further rounds, each team would get opponents at every different level.&lt;br /&gt;&lt;br /&gt;What happens if you try to maximize both? The resulting pairings (which were published in the &lt;span style="font-style: italic;"&gt;Rostrum&lt;/span&gt;) would look like this:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" style="font-weight: bold;" href="http://4.bp.blogspot.com/-zng4l0827Tg/TkF28GBUs7I/AAAAAAAAAPc/EtOQajkoEDc/s1600/c1.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 185px;" src="http://4.bp.blogspot.com/-zng4l0827Tg/TkF28GBUs7I/AAAAAAAAAPc/EtOQajkoEDc/s320/c1.jpg" alt="" id="BLOGGER_PHOTO_ID_5638918983224964018" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;The median distance is 3092 miles, and the shortest distance is 2003 miles (with only 15% of matches below the average of 2138 miles). The median difference is 0.45 units, and the least difference is 0.23 units (with 23% of matches below the average of 0.28 units). Although these pairings do not maximally mix for geography, they do pretty well. And likewise for difference in skill/experience level. This represents a lower boundary of how well this method could work. If we use a larger data set, such as the 200+ teams at Nationals, then it becomes easier to find pairings that maximize both criteria.&lt;br /&gt;&lt;br /&gt;Concern 2: Would this method create the same pairing year after year?&lt;br /&gt;&lt;br /&gt;It seems like it might: an optimal solution for one year seems like it might be the same, or very similar, the next year. No one wants to see the same opponent in preliminary rounds two (or more) years in a row at Nationals.&lt;br /&gt;&lt;br /&gt;However, this kind of optimization is chaotic, meaning it is extremely sensitive to small changes.&lt;br /&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-5848967506716519807?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/5848967506716519807/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2011/08/modest-proposal-to-ensure-geographic.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/5848967506716519807'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/5848967506716519807'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2011/08/modest-proposal-to-ensure-geographic.html' title='A modest proposal to ensure geographic mixing at Nationals'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/-KY1NjxksN0U/TkF2ghHBMRI/AAAAAAAAAPM/AYPUEP-zYDE/s72-c/g1.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-9189183273866117587</id><published>2011-05-31T11:17:00.012-04:00</published><updated>2011-06-01T12:05:29.157-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='statistics'/><category scheme='http://www.blogger.com/atom/ns#' term='bell curve'/><category scheme='http://www.blogger.com/atom/ns#' term='histogram'/><category scheme='http://www.blogger.com/atom/ns#' term='Gaussian distribution'/><category scheme='http://www.blogger.com/atom/ns#' term='normal distribution'/><category scheme='http://www.blogger.com/atom/ns#' term='regression'/><title type='text'>Fitting a normal curve</title><content type='html'>I show my students histograms of more or less normally distributed real-life data. I have found it difficult, though, to get a Normal curve that fits nicely on top of the histogram. Is there a way to do a best-fit regression in this situation? I looked around and can't find one, so here's a procedure I came up with. I'm not sure if it's the best possible fit, but it's a good fit.&lt;br /&gt;&lt;br /&gt;Using the fact that a normal distribution is given by the equation &lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/-A0PKXgHB6Ok/TeUgZL-saTI/AAAAAAAAAOA/8NYp6j7wFXA/s1600/img%2B1.tiff"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 133px; height: 52px;" src="http://4.bp.blogspot.com/-A0PKXgHB6Ok/TeUgZL-saTI/AAAAAAAAAOA/8NYp6j7wFXA/s320/img%2B1.tiff" alt="" id="BLOGGER_PHOTO_ID_5612928127671757106" border="0" /&gt;&lt;/a&gt; you can work backwards to see how to make the data linear. That is, &lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/-MSml2SK4FDA/TeUgZNQijfI/AAAAAAAAAOI/5MpBtjVo7Ws/s1600/img%2B2.tiff"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 124px; height: 46px;" src="http://2.bp.blogspot.com/-MSml2SK4FDA/TeUgZNQijfI/AAAAAAAAAOI/5MpBtjVo7Ws/s320/img%2B2.tiff" alt="" id="BLOGGER_PHOTO_ID_5612928128015044082" border="0" /&gt;&lt;/a&gt; is a linear transformation of normally distributed data. Here is a histogram.&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/-r7fdQvNrD-s/TeUhB4V4n1I/AAAAAAAAAOw/UPQJ83BsPu4/s1600/hist.tiff"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 181px;" src="http://3.bp.blogspot.com/-r7fdQvNrD-s/TeUhB4V4n1I/AAAAAAAAAOw/UPQJ83BsPu4/s320/hist.tiff" alt="" id="BLOGGER_PHOTO_ID_5612928826774953810" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;I used the midpoint of each bin as the &lt;span style="font-style: italic;"&gt;x&lt;/span&gt; data, and then I transformed the &lt;span style="font-style: italic;"&gt;y&lt;/span&gt; data as described.&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/-vE5Sy5mMoiQ/TeUhCEb6TzI/AAAAAAAAAPA/6gJqHblzWRU/s1600/table.tiff"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 131px; height: 120px;" src="http://2.bp.blogspot.com/-vE5Sy5mMoiQ/TeUhCEb6TzI/AAAAAAAAAPA/6gJqHblzWRU/s320/table.tiff" alt="" id="BLOGGER_PHOTO_ID_5612928830021455666" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;The one trick is that, for &lt;span style="font-style: italic;"&gt;x&lt;/span&gt; values below the mean, the transformed &lt;span style="font-style: italic;"&gt;y&lt;/span&gt; data points need to be negative. That can create a little ambiguity for the middle bin, but it's not too hard to tell here that 2.5 is a little below the mean. If in doubt, try both. I ran a linear regression on &lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/-tVljSxiljeU/TeUgZhGTp_I/AAAAAAAAAOQ/yugjZz3EMX8/s1600/img%2B3.tiff"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 90px; height: 37px;" src="http://1.bp.blogspot.com/-tVljSxiljeU/TeUgZhGTp_I/AAAAAAAAAOQ/yugjZz3EMX8/s320/img%2B3.tiff" alt="" id="BLOGGER_PHOTO_ID_5612928133340833778" border="0" /&gt;&lt;/a&gt; and found that &lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/-JlXTlMHJl-g/TeUgZooLTEI/AAAAAAAAAOY/s4gk_FrfskA/s1600/img%2B4.tiff"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 152px; height: 38px;" src="http://1.bp.blogspot.com/-JlXTlMHJl-g/TeUgZooLTEI/AAAAAAAAAOY/s4gk_FrfskA/s320/img%2B4.tiff" alt="" id="BLOGGER_PHOTO_ID_5612928135361940546" border="0" /&gt;&lt;/a&gt;This can be transformed back into &lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/-uQNAG9buywk/TeUgaJwGwII/AAAAAAAAAOg/ogDbwbdHHD4/s1600/img%2B5.tiff"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 116px; height: 46px;" src="http://2.bp.blogspot.com/-uQNAG9buywk/TeUgaJwGwII/AAAAAAAAAOg/ogDbwbdHHD4/s320/img%2B5.tiff" alt="" id="BLOGGER_PHOTO_ID_5612928144253567106" border="0" /&gt;&lt;/a&gt; which is almost ready to graph. All it's missing is the leading coefficient. A little work shows that the standard deviation is 0.88, and therefore the final equation is &lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/-uTVHiRUJ1Ek/TeUhB7LkDGI/AAAAAAAAAOo/4s4oRHBGvzI/s1600/img%2B6.tiff"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 132px; height: 42px;" src="http://3.bp.blogspot.com/-uTVHiRUJ1Ek/TeUhB7LkDGI/AAAAAAAAAOo/4s4oRHBGvzI/s320/img%2B6.tiff" alt="" id="BLOGGER_PHOTO_ID_5612928827536968802" border="0" /&gt;&lt;/a&gt;Here's the histogram, with the overlaid normal curve, which does not fit especially well.&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/-MN4A7tFYPe8/TeUhCNsEWmI/AAAAAAAAAO4/useOJFa50qg/s1600/curve.tiff"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 162px;" src="http://4.bp.blogspot.com/-MN4A7tFYPe8/TeUhCNsEWmI/AAAAAAAAAO4/useOJFa50qg/s320/curve.tiff" alt="" id="BLOGGER_PHOTO_ID_5612928832505141858" border="0" /&gt;&lt;/a&gt;However, this shows that this real-life data does not exactly follow a normal distribution, since this is about as well as we could hope it would fit.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-9189183273866117587?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/9189183273866117587/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2011/05/fitting-normal-curve.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/9189183273866117587'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/9189183273866117587'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2011/05/fitting-normal-curve.html' title='Fitting a normal curve'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/-A0PKXgHB6Ok/TeUgZL-saTI/AAAAAAAAAOA/8NYp6j7wFXA/s72-c/img%2B1.tiff' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-448097828738877313</id><published>2011-04-05T20:00:00.006-04:00</published><updated>2011-04-05T20:18:20.842-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='statistics'/><category scheme='http://www.blogger.com/atom/ns#' term='driving vs. flying'/><category scheme='http://www.blogger.com/atom/ns#' term='interstates'/><category scheme='http://www.blogger.com/atom/ns#' term='significance test'/><title type='text'>I-85 %</title><content type='html'>The U.S. interstate system takes remarkably straight paths between major cities: specifically, I believe that the true distance between two cities is, on average, only 6/7 of the interstate driving distance. Here's a statistical activity I made for my students:&lt;br /&gt;&lt;br /&gt;http://www.mediafire.com/file/h29bsfs2cgoiro0/interstates.doc&lt;br /&gt;&lt;br /&gt;If they do a decent sample size, say n = 25, they will almost certainly reject the null hypothesis I state in the problem.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-448097828738877313?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/448097828738877313/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2011/04/i-85.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/448097828738877313'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/448097828738877313'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2011/04/i-85.html' title='I-85 %'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-2941212315036243826</id><published>2011-03-25T10:11:00.014-04:00</published><updated>2011-09-01T12:13:36.048-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='facts'/><category scheme='http://www.blogger.com/atom/ns#' term='courses'/><category scheme='http://www.blogger.com/atom/ns#' term='debate'/><category scheme='http://www.blogger.com/atom/ns#' term='philosophy'/><category scheme='http://www.blogger.com/atom/ns#' term='cause and effect'/><category scheme='http://www.blogger.com/atom/ns#' term='values'/><category scheme='http://www.blogger.com/atom/ns#' term='public speaking'/><category scheme='http://www.blogger.com/atom/ns#' term='logic'/><category scheme='http://www.blogger.com/atom/ns#' term='definitions'/><title type='text'>Critical thinking course</title><content type='html'>There are a few methods for teaching critical thinking skills to public speaking and/or debate students.&lt;br /&gt;&lt;br /&gt;One approach is to include a unit on critical thinking within a public speaking course (usually near the end) or an introduction to debate course (usually near the beginning). The unit might include Toulmin's simple framework for analyzing the claim, evidence, and warrants of arguments; it might teach students to identify informal fallacies; or perhaps the instructor gives students a checklist of basic questions to ask themselves about their arguments, e.g., "Who is the source of this information?", "How was this information collected?", etc. This approach tends to be informal (lacking strict logical rigor), simple to understand and apply, and not specific to any content domain. This is the approach I use in my debate &lt;a href="http://www.lulu.com/product/paperback/the-how-to-of-debate/15387254"&gt;textbook&lt;/a&gt;: I have an early chapter on Toulmin's framework.&lt;br /&gt;&lt;br /&gt;Another approach is to require would-be debaters to take a separate course to improve their critical thinking skills. Some debate teams require debaters to take an additional course in logic (often in the philosophy department), which tends to be very mathematical and rigorous, perhaps even confusing, and hardly ever useful for debate contexts. I recently saw a team that requires debaters to take an additional course that surveys argumentation in different fields: legal and constitutional reasoning, political science, economics, critical theory, etc. The debaters get a primer on each topic, and some exposure to what constitutes good arguments in each field. This approach certainly gives debaters deep knowledge about various fields, but it leaves them weak on the general evaluation of new arguments in other fields.&lt;br /&gt;&lt;br /&gt;Instead, I believe the best approach is to take the informal model but cover it as a stand-alone course (in the Communications department). I imagine this course would usually be taken by second-year debaters, but there's no reason it couldn't be open to other students as well. Perhaps the best way to organize such a critical thinking course would be:&lt;br /&gt;&lt;br /&gt;- arguments about definitions&lt;br /&gt;- arguments about facts&lt;br /&gt;- arguments about cause and effect&lt;br /&gt;- arguments about values&lt;br /&gt;&lt;br /&gt;And I think the best way to treat it would be, as Neil Postman suggested in &lt;span style="font-style: italic;"&gt;Teaching as a Subverse Activity&lt;/span&gt;, a collection of questions upon which to discuss. The teacher could ask framing questions, provide key readings, and open the discussion up. Here's what I envision in each section.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Definitions&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;There needs to be a discussion about language. Specifically, students should discuss the arbitrariness of signs, the inherent ambiguity of language, and the tempting but ultimately false notion of essentialism. A simple example can spark a great discussion: "Define 'table'" or "Define 'bed'" seem so simple but become so difficult as you start to unpack it. It might even be worth starting a discussion about "discourses": how definitions are field-contextual and make sense only relative to other concepts in that field. A great example is the word "reduction" -- you should look at the Wikipedia disambiguation page to see how many different meanings there are.&lt;br /&gt;&lt;br /&gt;The students need to discuss how to resolve definitional disputes: etymological-historical, current usage, explicit agreement, etc. It might be worth spending some time looking at Venn diagrams to compare definitions and to model syllogisms; it's good to make sure that students leave this unit clearly understanding that definitions (and syllogisms) never provide us new information about the world.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Facts&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Orwell's "Politics and the English Language" makes a great transition from discussing language to discussing facts, since his main point was in how bad actors could intentional mislead with ambiguous language. It's perhaps worth having a more general discussion about the trustworthiness of sources, intentional and unintentional bias, and the appeal to authority. I've always thought it a good idea to fuse the topics of small-"m" cultural marxism and media literacy in one discussion: in other words, discuss biases of class as well as reportorial laziness, enthusiasm for expert sources (government or science), and the herd mentality. Focusing students on what isn't reported is often more effective than letting them getting bogged down in discussions about whether the stories that are reported are biased. All this is an elaboration on the trustworthiness of sources.&lt;br /&gt;&lt;br /&gt;Getting into the nitty-gritty of the facts themselves, I think it's wise to spend time talking about the logical process of generalizing. When can we go from limited, anecdotal experience to say safely that something is usually or always true? This can lead nicely into a discussion about surveys, sampling, and statistical concepts about generalizing -- at a non-technical level. If students understand how to interpret surveys and margins of error, understand the basic logic of them, and know what to look out for (biased questions, biased sampling frames, sample size), then they're doing quite well. As a final note, Stephen Budiansky wrote a fascinating article called, "The numbers racket: how polls and statistics lie" (&lt;span style="font-style: italic;"&gt;US News and World Report&lt;/span&gt;, July 11, 1988). He provides great examples of commonly circulated statistics that are just plain made up. There are books out there, too, such as &lt;span style="font-style: italic;"&gt;Lies, Damned Lies, and Statistics&lt;/span&gt; that have good chapters for excerpting on this point.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Cause and Effect&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;First of all, it's worth discussing how statisticians and scientists set up experiments to prove cause and effect.&lt;br /&gt;&lt;br /&gt;From logic, it's also worth discussing necessary versus sufficient causes. And, of course, the slippery slope fallacy. I like to get them diagramming causal arguments early, and once we start talking about the slippery slope fallacy, I introduce them to Ishikawa fish diagrams. I think it's also important to show them with several examples how cause and effect can easily run opposite to their intuition. A good example: kids who drink more milk have bigger feet. Is it because (a) milk causes bigger feet? (b) bigger feet cause kids to drink more milk? or (c) there's a third variable at play -- age? Self-selection is a wonderful example, too: kids who take the Princeton Review do better, on average, on their SATs. Is it because (a) Princeton Review helps? or (b) kids who take the SAT seriously also self-select to take the prep course?&lt;br /&gt;&lt;br /&gt;From a systems perspective, students should learn a little about chaos theory (a system where initial conditions matter hugely, not one that is chaotic, thank you very much Jurassic Park), feedback loops, and the like. Economics provides a useful field here, to discuss how all the various parts of a system might push and pull on each other.&lt;br /&gt;&lt;br /&gt;And from a real-world perspective, students should discuss what makes everyday predictions about politics, economics, and international relations credible or not. Is it reasoning by historical analogy? Is it clear analysis?&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Values&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Students can get overwhelmed with the details of different philosophies, so to try to alleviate their confusion, I kept readings short (or just stick to secondary sources); I keep the number of philosophers I introduce them to at a minimum; I choose the more straightforward philosophers only. No Nietzsche, no Habermas, etc. This doesn't need to be a survey course. Instead, I frame it for them as simply as possible: "What is the right thing to do?" I tell them that the particular language and details of each philosophy are less important than understanding the philosopher's answer to my question. I stress for them that there are really only three kinds of answer to my question: (1) what some set of rules tells us is right (the dogmatists), (2) there is no such thing as a right thing to do (the nihilists); and (3) we don't know what the right thing to do is, but we do our best each time to figure it out (the pragmatists). Realizing that most moral philosophers fall into one of three temperaments is a relief. Furthermore, I make sure to bring in lots of ethical and policy dilemmas, and I encourage them to answer wearing each philosopher's hat, as it were.&lt;br /&gt;&lt;br /&gt;For dogmatists, I might start with natural law (perhaps Aristotle or Aquinas), leading into a discussion of the appeal to nature fallacy. Of course, you also have to discuss the utilitarians, Kant, and the social contractarians (Hobbes and Rawls -- it's nice for students to see a conservative and a liberal contract view). All together that makes five philosophers to discuss, and I think it's good for students to see how one dogmatic philosophy can completely oppose another. Given an ethical or policy dilemma, it's very interesting to set up five-way debates.&lt;br /&gt;&lt;br /&gt;For nihilists, I would tend to focus on criticisms more generally, rather than specific philosophers. There are the criticisms that no universal moral &lt;span style="font-style: italic;"&gt;system&lt;/span&gt; can be formulated (but there is such a thing as justice). Then there are the moral relativists who would argue that there is no such thing as morality, period; it's just a social construct. I find that this part of the unit isn't especially interesting and one moves quickly into the pragmatists.&lt;br /&gt;&lt;br /&gt;For pragmatists, I think I would start with a little Hume, before discussing the existentialists. (I find Sartre's ideas are fairly comprehensible to students.) Then I would move on to the "democrats": those would argue that morality should be defined by agreement and consent. Again, with two nihilistic positions (moderate and extreme) and three pragmatic positions, one can set up interesting five-way debates.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Those are my recommendations. There are good books out there that support a structure like I've suggested, such as William Hughes' excellent &lt;span style="font-style: italic;"&gt;Critical Thinking&lt;/span&gt;, but I'd honestly rather piece it together with readings, real-world examples, and &lt;span style="font-weight: bold;"&gt;discussions&lt;/span&gt;. With a typical 12-13 week semester, that would give you three weeks per unit. Debaters would leave with a better sense of how to argue topicality (definitions), disadvantages (cause and effect), and critiques (values) -- and would hopefully be more careful researchers after the unit about facts.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-2941212315036243826?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/2941212315036243826/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2011/03/critical-thinking-course.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/2941212315036243826'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/2941212315036243826'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2011/03/critical-thinking-course.html' title='Critical thinking course'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-4428313167071936904</id><published>2011-03-21T22:27:00.003-04:00</published><updated>2011-03-22T20:04:14.424-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='debate tournaments'/><category scheme='http://www.blogger.com/atom/ns#' term='hockey'/><category scheme='http://www.blogger.com/atom/ns#' term='NCAA'/><category scheme='http://www.blogger.com/atom/ns#' term='elimination brackets'/><title type='text'>Bracketology</title><content type='html'>Nate Silver, who does the NY Times blog fivethirtyeight (usually on elections, but now on more), did an analysis and reports that the elimination bracket style used by the NCAA (and debate tournaments) isn't exactly fair:&lt;br /&gt;&lt;br /&gt;&lt;a href="http://fivethirtyeight.blogs.nytimes.com/2011/03/15/when-15th-is-better-than-8th-the-math-shows-the-bracket-is-backward/"&gt;http://fivethirtyeight.blogs.nytimes.com/2011/03/15/when-15th-is-better-than-8th-the-math-shows-the-bracket-is-backward/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Specifically, it makes me wonder why we don't go to the style used by the NHL: amongst whichever teams are left, top seed plays bottom seed, second seed plays second worst, etc. In the NCAA, fixed brackets style, if the bottom seed upsets the top seed, suddenly the bottom seed now has an easier schedule than it deserves. In the NHL, re-seeding style, the bottom seed would have to keep upsetting all the top seeds to keep going.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-4428313167071936904?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/4428313167071936904/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2011/03/bracketology.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/4428313167071936904'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/4428313167071936904'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2011/03/bracketology.html' title='Bracketology'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-5111618067220897523</id><published>2011-02-03T19:59:00.006-05:00</published><updated>2011-02-04T13:52:32.982-05:00</updated><title type='text'>Lock-in</title><content type='html'>I thought the writer Neal Stephenson did an excellent job of explaining the phenomenon of lock-in with regards to rocket technology in this article: &lt;a href="http://www.slate.com/id/2283469/pagenum/all/"&gt;http://www.slate.com/id/2283469/pagenum/all&lt;/a&gt;. It is an excellent reminder that the technologies we have are often the result of contingent (historical) factors rather than rational ones. Here are two examples of lock-in that are near and dear to my heart -- that is, they drive me crazy:&lt;br /&gt;&lt;br /&gt;1. Have you ever wondered why the US math curriculum goes Algebra 1, Geometry, Algebra 2? It's a completely irrational system that no sane person would design. Algebra 2 classes start off with an extensive review of algebra since it's been 15 months since the students last saw algebra. In fact, the review can last nearly a quarter of the year. Perhaps the review period would last only a few weeks if the students were to go directly from Algebra 1 to Algebra 2. What's worse, many students aren't really developmentally ready for Algebra 1 when they take it; many need a more robust pre-algebra course. A more rational sequence would be Geometry/Pre-Algebra, Algebra 1, Algebra 2. Geometry is developmentally appropriate in 8th grade and serves as a perfect medium for pre-algebra concepts: that &lt;span style="font-style: italic;"&gt;x&lt;/span&gt; stands for something that is unknown but fixed, and that one can use geometric properties to deduce &lt;span style="font-style: italic;"&gt;x&lt;/span&gt;, makes sense in a geometric context. One can even get at the idea of &lt;span style="font-style: italic;"&gt;x&lt;/span&gt; as a variable with similarity and ratios. And yet, year after year, school district after school district decides to keep the irrational sequence unchanged.&lt;br /&gt;&lt;br /&gt;Why? At around the turn of the last century, when high schools were the new thing, students took Algebra and Geometry. Period. Geometry, with its logical proofs, was deemed material for seniors. As time went on, more classes were added on, always at the end. First, Algebra 2/Trigonometry was added. Then, Pre-Calculus was the senior math class. Now it's Calculus -- and thus, Algebra 1 got pushed down to 8th grade.&lt;br /&gt;&lt;br /&gt;2. You know I'm going to talk about debate tab. I have never tabbed a tournament on notecards, but I know exactly how to do it because I've used the current generation of debate tab programs. The programs are electronic notecards. Don't get me wrong -- I'm very glad that we have the programs! They automate the mindless tasks and don't make careless mistakes like people do. My point is that when the tab programs came along, they were designed to do the existing tournament practices, only more efficiently. The debate community hasn't seriously thought about whether we can design better practices that can &lt;span style="font-style: italic;"&gt;only&lt;/span&gt; be done by computers. In other words, we are locked-in to tournament procedures (brackets, speaker points, dropped high-low speaker points) that were designed to be (relatively) easy to do by hand, even though we have phenomenally powerful optimizing devices at our fingertips.&lt;br /&gt;&lt;br /&gt;A high-low pairing algorithm literally ranks all the teams and then pairs them off two-by-two. Why not have a computer run 10,000 possible pairings and pick the best one?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-5111618067220897523?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/5111618067220897523/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2011/02/lock-in.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/5111618067220897523'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/5111618067220897523'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2011/02/lock-in.html' title='Lock-in'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-6768511886414832455</id><published>2011-02-02T13:34:00.014-05:00</published><updated>2011-02-02T20:44:12.511-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='round robin'/><category scheme='http://www.blogger.com/atom/ns#' term='balancing'/><category scheme='http://www.blogger.com/atom/ns#' term='student groups'/><category scheme='http://www.blogger.com/atom/ns#' term='standard deviation'/><title type='text'>A method to create balanced groups</title><content type='html'>I like for my students to work together in groups. Unfortunately, they always choose to sit with their friends. So I have to assign their groups.&lt;br /&gt;&lt;br /&gt;Let's say on the first day of class, I give them a 20 point quiz to see how much of last year's math they remember. I can also use that information to create balanced groups; I don't want to put all the weak students in one group and all the strong students in another. Rather, I would like each group to include weak students, strong students, and average students.&lt;br /&gt;&lt;br /&gt;One way to look at this problem is that I want each group's average to be close to the class average. One could design an algorithm to create the groups this way. But I realized as I was designing it that one has to make ad hoc rules that throw out (a) groups composed of entirely average students and (b) groups composed evenly of strong and weak students but no average ones. I wanted a more elegant algorithm.&lt;br /&gt;&lt;br /&gt;The other way to look at the problem is that I want each group to be as diverse as possible. If one maximizes each group's standard deviation, then (a) groups are ruled out. It is true that (b) groups would have the largest standard deviation possible -- but the magic here is that standard deviation is non-linear. Let's say that you have starting forming two groups -- group 1 {S, W, W} and group 2 {S, A, A} -- you have two more students to assign {S, A}. It is true that assigning the strong student to group 1 {S, S, W, W} makes its standard deviation bigger than assigning to it the average student {S, A, W, W}. In other words, std. dev. 1s &gt; std. dev. 1a. But the key is that it makes a much bigger difference to group 2: std. dev. 2s is much, much bigger than std. dev. 2a.&lt;br /&gt;&lt;br /&gt;Algebraically, (std. dev. 1s - std. dev. 1a) &lt; (std. dev. 2s - std. dev. 2a). Equivalently, (std. dev. 1s + std. dev. 2a) &lt; (std. dev. 2s + std. dev. 1a).  Without algebra, the point is that (b) groups would never happen if you try to maximize the standard deviation of each group -- overall, you're always better to maximize the standard deviation of the least diverse group first.  With this fact in mind, this becomes a simple maximization problem. This is an extremely powerful idea: to create the most balanced groupings, you make each group as diverse as possible.  Below is an example. A fictional class of six will be divided into two groups.&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_5RAO7k_azLU/TUnO2S-vuQI/AAAAAAAAAMo/imxFE1RlbQg/s1600/trial.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 158px; height: 320px;" src="http://4.bp.blogspot.com/_5RAO7k_azLU/TUnO2S-vuQI/AAAAAAAAAMo/imxFE1RlbQg/s320/trial.jpg" alt="" id="BLOGGER_PHOTO_ID_5569209846423599362" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;As you can see, each colored line represents a possible set of groupings. The worst groupings are highlighted in red, the mediocre groupings are highlighted in yellow, and the good groupings are highlighted in green. The first cell under a group is its standard deviation, and the second cell is the group's average. I ranked the groupings by creating a geometric average (&lt;span style="font-style: italic;"&gt;a&lt;/span&gt; &lt;span style="font-style: italic;"&gt;b&lt;/span&gt;) ^ 0.5 of the two groups' standard deviations. I do generally agree with the rankings. In the red groupings, the groups are skewed: all strong students in one, all weak students in the other. As a result, both groups have low standard deviations. In the yellow groupings, one group is skewed, and the other group includes too many average students. As a result, one group has a high standard deviation, while the other has a low standard deviation. In the green groupings, both groups are balanced, so both have decent standard deviations.&lt;br /&gt;&lt;br /&gt;As you'll notice, even for the best groupings, the average standard deviation of the groups doesn't exceed the standard deviation of the entire class. That's as it should be, but I'll leave that proof to an industrious reader.&lt;br /&gt;&lt;br /&gt;Another, more realistic (though still fictional) example follows: dividing a 16-student class into four groups. There are too many possible groupings to list (more than 2.6 million), so I used an algorithm to pick a reasonably good solution. (I started by putting the four students in the very middle in different groups, then given that initial condition, the algorithm then assigned the remaining students in a way that attempted to maximize each group's standard deviation.) You can see the results below:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_5RAO7k_azLU/TUoCaDSuuhI/AAAAAAAAAMw/KFYL3XYS0KA/s1600/geo%2Bgroups.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 84px;" src="http://3.bp.blogspot.com/_5RAO7k_azLU/TUoCaDSuuhI/AAAAAAAAAMw/KFYL3XYS0KA/s320/geo%2Bgroups.jpg" alt="" id="BLOGGER_PHOTO_ID_5569266535780760082" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;I lettered the students from A to P, strongest to weakest, and indicated a percentage grade for each. The four middle students were G, H, I, and J. You can see that the algorithm was able to do a decent job of maximizing each group's standard deviation (its explicit task); some came out slightly ahead, but they're all relatively large. But you can see how well the algorithm did creating balanced groups: 82.2, 82.4, 84, and 84.2. Remember, this result is an accidental byproduct of trying to create a solution that maximizes each group's standard deviation.&lt;br /&gt;&lt;br /&gt;Why do I care so much about this? For one, I really do like having an algorithm that creates evenly balanced groups in my class. But two, I want build this algorithm into a tabulation program -- for partial round robins. In a partial round robin, each team should hit a representative cross-section of the pool. Consider a 12-team round robin with 6 preliminary rounds. It's too tight to run a regular tournament and respect win-loss brackets. But if you can rank the teams before they arrive, then using my algorithm, each team could debate six opponents that are strong, mediocre, and weak.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-6768511886414832455?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/6768511886414832455/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2011/02/method-to-create-balanced-groups.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/6768511886414832455'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/6768511886414832455'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2011/02/method-to-create-balanced-groups.html' title='A method to create balanced groups'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_5RAO7k_azLU/TUnO2S-vuQI/AAAAAAAAAMo/imxFE1RlbQg/s72-c/trial.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-1035757444553210706</id><published>2010-01-20T13:34:00.012-05:00</published><updated>2011-03-08T15:44:25.808-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='rankings'/><category scheme='http://www.blogger.com/atom/ns#' term='high school debate'/><category scheme='http://www.blogger.com/atom/ns#' term='fairness'/><category scheme='http://www.blogger.com/atom/ns#' term='brackets'/><category scheme='http://www.blogger.com/atom/ns#' term='round robins'/><title type='text'>Differing opponent strengths</title><content type='html'>&lt;span style="text-decoration: underline;"&gt;&lt;/span&gt;Below is a graphic of a traditionally-run tournament.&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/S1dNU-5sAxI/AAAAAAAAALI/yRLwsYIbr-Q/s1600-h/sch+str+method.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 246px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/S1dNU-5sAxI/AAAAAAAAALI/yRLwsYIbr-Q/s320/sch+str+method.jpg" alt="" id="BLOGGER_PHOTO_ID_5428892898696102674" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;The horizontal axis shows each team's final strength; the vertical axis shows each team's average opponent strength; the size of the bubble shows, for each team, the standard deviation of its opponents' strengths. A small bubble represents a team that debated opponents that were all very close together in strength. A large bubble represents a team that debated a wide cross-section of opponents, some weak and some strong.&lt;br /&gt;&lt;br /&gt;I think about how a debate tournament ought to look, if it's paired fairly. It seems to me that every team ought to have a good cross-section of opponents. Thus, a fair tournament would be like a partial round robin. We would know that 3-3 teams were truly middle-of-the-pack because of their abilities, not because they got an unfair draw. The bubbles in the diagram would be bigger (each team sees a true cross-sections of opponents) and closer to the horizontal line (average opponent strength for each team would be closer to the overall average opponent strength).&lt;br /&gt;&lt;br /&gt;It's relatively easy to pair a tournament like this, even on the fly. To pair a round, you can look at each team's opponents and decide what is missing so far. After three rounds, a team might have debated a 0-3, a 2-1, and a 3-0 opponent; they would now debate a 1-2 opponent. It is true that the opponent records change after the fourth round, but the process is repeated, and by the end, most teams will debate a decent cross-section of opponents from 0-6 to 6-0. Of course, traditional tournaments do not do this; teams debate opponents within brackets. Why?&lt;br /&gt;&lt;br /&gt;The reason is that brackets increase the accuracy of rankings. Consider a 4-2 team. Does it deserve to break? If the tournament pairs it against a representative cross-section, this team would debate a 6-0 opponent, a 5-1, a 4-2, a 3-3, etc. There's only one opponent with an equal record -- but it's precisely the comparisons to very similarly-abled opponents that shed the most accurate information about a team's true strength. In a brackets system, the same team would likely debate several 4-2 opponents. There are more points of comparison, allowing for finer rankings. The downside, though, is that a team could go through the preliminary rounds of the tournament debating opponents that are all at exactly the same level. It seems to me like something valuable would be lost.&lt;br /&gt;&lt;br /&gt;Of course, these two virtues -- fairness and accuracy -- trade off. You can't maximize both. But there are several ways to get a reasonable equilibrium. For example, pair odd rounds to have every team debate a reasonable cross-section of opponents (i.e., across brackets), and pair even rounds to increase accuracy of rankings (i.e., within brackets).&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-1035757444553210706?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/1035757444553210706/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2010/01/different-opponent-strength.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/1035757444553210706'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/1035757444553210706'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2010/01/different-opponent-strength.html' title='Differing opponent strengths'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/_5RAO7k_azLU/S1dNU-5sAxI/AAAAAAAAALI/yRLwsYIbr-Q/s72-c/sch+str+method.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-2867959700109425901</id><published>2009-12-31T10:44:00.049-05:00</published><updated>2011-01-14T20:35:17.003-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='matrices'/><category scheme='http://www.blogger.com/atom/ns#' term='weighted wins'/><category scheme='http://www.blogger.com/atom/ns#' term='incidence matrix'/><category scheme='http://www.blogger.com/atom/ns#' term='team strength'/><title type='text'>A new measure of team strength: weighted wins</title><content type='html'>I've been thinking about and working for a while on a more accurate method of estimating a team's strength. Bear in mind, I'm &lt;span style="font-weight: bold; font-style: italic;"&gt;not&lt;/span&gt; talking about the method for generating final preliminary rankings. The final ranking method is unlikely to ever change, which is not really a bad thing. There's a reason we're all rightfully attached to it: wins and total speaker points may not be the most accurate way to assess a team's strength, but it does seem the most just: those are the wins and points a team &lt;span&gt;earned&lt;/span&gt;. So, I'm interested in how to estimate a team's strength only in order to make better power matches during the prelims, not to decide which teams break or don't break. As a second caveat, let me state that there's no way to say objectively that rankings are "correct"; a good ranking method is a good estimate of team strength, which varies anyway from round to round. All you can do is look at whether a ranking method yields some common sense results.&lt;br /&gt;&lt;br /&gt;With those caveats stated, here's the first problem with win/loss record as a measure of team strength: no team debates a representative sample of the teams at the tournament. Every team debates six opponents out of &lt;span style="font-style: italic;"&gt;n&lt;/span&gt; teams at the tournament. Except for round robins and very small tournaments, the proportion isn't very large. At a normal-sized tournament, it might be under 10%. Recognizing this, tournaments do not use randomly selected opponents. Brackets select a subset of opponents for teams to debate, and the results are more informative than if opponent selection is random. While there are many pathways through the tournament (e.g., WWWLLL versus WLWLWL), usually the key is what caliber of opponent a team beats and by what caliber of opponent a team is beaten. For example, a team who beats a 2-4 and loses to a 4-2 will, because of the way the brackets work, most often end up with a 3-3 record, revealing that this team is probably in the middle third of the tournament. Of course, sometimes the brackets don't work perfectly in this way; for example, a team that beats a 4-2 might end up with a 3-3 record. Clearly, in this case, the overall win/loss record is not an accurate reflection of one or both teams' strength.&lt;br /&gt;&lt;br /&gt;It is possible to create many different, more accurate measures of team strength that account for schedule strength using complicated formulas. But I think a measure needs to be relatively easy to understand and transparent, if it's to be adopted. The measure I developed (from a suggestion from Steve Gray) is weighted wins/weighted losses. Let's say team A beats teams B, C, and D, and loses to team G: 3 wins, 1 loss. But what if team B was a 3-1 team, team C was a 2-2 team, team D was an 0-4 team, and team G was a 3-1 team? The win against B ought to count for more than the win against D. The weighted measures would give team A exactly 8 "wins" (3 wins + 3 + 2 + 0) and 2 "losses" (1 loss + 1): it gains an extra "win" for every win of each opponent it beats (B, +3; C + 2; and D, + 0) and incurs an extra "loss" for every loss of each opponent that defeats it (G, - 1). As a first step, this already makes an enormous difference in assessing a team's true strength. Teams that defeat good opponents have more weighted wins than teams that defeat mediocre opponents, even if they have the same win/loss record. (Of course, it's possible that a team that has only been paired against mediocre opponents is actually very good -- which will get sorted out through power-matching!)&lt;br /&gt;&lt;br /&gt;The method becomes enormously powerful if it re-iterates: for example, team A is now treated as having 8 wins and 2 losses, just as all its opponents are shown with their weighted wins and losses. Let's say B has a weighted record of 5-2; C, 4-4; D, 0-7; and G, 6-2. In the second iteration, team A will have 12 re-weighted wins (3 wins + 5 + 4 + 0) and 3 losses (1 loss + 2). The process can continue to be re-iterated until a reasonable stopping point, say, a team has as many or more weighted wins than there are teams at the tournament (or as many losses)! Based on this rule, the process will re-iterate about log(&lt;span style="font-style: italic;"&gt;n&lt;/span&gt;) times for an &lt;span style="font-style: italic;"&gt;n&lt;/span&gt;-team tournament.&lt;br /&gt;&lt;br /&gt;For simplicity's sake, I would turn the weighted wins and weighted losses into one statistic:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_5RAO7k_azLU/TTD5MmhVM_I/AAAAAAAAAMY/2HqAKxkY_KA/s1600/Document1.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 138px; height: 49px;" src="http://2.bp.blogspot.com/_5RAO7k_azLU/TTD5MmhVM_I/AAAAAAAAAMY/2HqAKxkY_KA/s320/Document1.jpg" alt="" id="BLOGGER_PHOTO_ID_5562219534696657906" border="0" /&gt;&lt;/a&gt;where &lt;span style="font-style: italic;"&gt;r&lt;/span&gt; is the number of rounds at the tournament. The first term will create something like a handicapped win percentage.&lt;br /&gt;&lt;br /&gt;I ran this method on a small four-round tournament, which took only three iterations. You can see the results here:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_5RAO7k_azLU/TNitcM9QtZI/AAAAAAAAALw/P8cb-Rt10iY/s1600/weighted+wins.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 424px; height: 202px;" src="http://3.bp.blogspot.com/_5RAO7k_azLU/TNitcM9QtZI/AAAAAAAAALw/P8cb-Rt10iY/s320/weighted+wins.jpg" alt="" id="BLOGGER_PHOTO_ID_5537366441878140306" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;In only one case, highlighted yellow, did the method rank a team above someone that it beat. I highlighted in green three teams that dramatically moved up under this ranking and in pink four teams that dramatically moved down. Based on their schedule strengths, these all seem pretty defensible to me.&lt;br /&gt;&lt;br /&gt;Some might point out that there's an inherent difficulty created by "upsets," where good teams happen to get knocked off by bad teams. How much is the good team "punished," or pushed down in the rankings, by that loss? I thought a different kind of data set, where the teams play a much more representative sample, would show the basic sanity of the weighted wins approach. I used it to rank the 2009 NFL regular season because there are so many "upsets" in football (about 25%! -- much higher than debate tournaments, where there are about 5%). You can see how well the method I described handles the unusual losses:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_5RAO7k_azLU/TNix_SzuwQI/AAAAAAAAAL4/FTYVLhTu4JU/s1600/2009nfl.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 400px; height: 220px;" src="http://2.bp.blogspot.com/_5RAO7k_azLU/TNix_SzuwQI/AAAAAAAAAL4/FTYVLhTu4JU/s320/2009nfl.jpg" alt="" id="BLOGGER_PHOTO_ID_5537371442790711554" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;As you can see, it does a reasonable job, despite lots of unusual losses.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-2867959700109425901?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/2867959700109425901/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/12/new-measure-of-team-strength-transitive.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/2867959700109425901'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/2867959700109425901'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/12/new-measure-of-team-strength-transitive.html' title='A new measure of team strength: weighted wins'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_5RAO7k_azLU/TTD5MmhVM_I/AAAAAAAAAMY/2HqAKxkY_KA/s72-c/Document1.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-4905152833748094581</id><published>2009-12-15T18:35:00.019-05:00</published><updated>2009-12-16T15:22:31.153-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='debate tournaments'/><category scheme='http://www.blogger.com/atom/ns#' term='Pascal&apos;s triangle'/><category scheme='http://www.blogger.com/atom/ns#' term='infinite series'/><category scheme='http://www.blogger.com/atom/ns#' term='high school debate'/><category scheme='http://www.blogger.com/atom/ns#' term='weighted wins'/><category scheme='http://www.blogger.com/atom/ns#' term='ordered set'/><category scheme='http://www.blogger.com/atom/ns#' term='inequalities'/><title type='text'>Pascal's triangle (modified)</title><content type='html'>I started thinking about this problem in a specific debate context (for a specific application), before realizing that it isn't so useful after all. Still, the math is quite interesting.&lt;br /&gt;&lt;br /&gt;Here's the original question that got me thinking: Is there a way to assign weighted wins -- round 1 wins count for so much, round 2 wins count for something different, and so on -- such that a tournament can produce a ranking that is consistent with the actual results, such that if team A beats team B, and they finish with the same win-loss record, A must be ranked above B? (Thanks to Steve Gray for coming up with the original idea to use weighted wins this way.) The point values for each round must be decreasing for this to work. If team A beats team B in round 1 for 1 point, then all subsequent point values must be smaller, or else B would have the chance to tie (with an equal number of wins) or surpass A (with an equal number of wins -- of course, B should surpass A if it wins more total rounds than A). I tested out a specific set of weighted win points that meets both of these conditions: {1, 0.9, 0.89, 0.889, 0.8889, 0.88889}. I'll write more on why this particular set works later in this post. The results of the test follows:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_5RAO7k_azLU/Sygr8hfSEcI/AAAAAAAAAKY/xlZPxkZcWQ0/s1600-h/pascal%27s+revised.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 247px;" src="http://3.bp.blogspot.com/_5RAO7k_azLU/Sygr8hfSEcI/AAAAAAAAAKY/xlZPxkZcWQ0/s320/pascal%27s+revised.jpg" alt="" id="BLOGGER_PHOTO_ID_5415626870694744514" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;Pick any point where you might compare two teams, and you can see that you can always tell who got there by winning the earlier round(s). As you can see from the bottom row, it is possible to distinguish every one of the 64 possible pathways (2^6) that a team could take through the tournament (e.g., WLLWWL), and the results line up nicely in order -- that is, an earlier win always ranks a team higher (e.g., WWLWLL is ranked higher than WLLWWL). The earlier win is ranked higher, because that way, there is no possibility a team is ranked lower than someone they beat. &lt;span style="font-weight: bold; font-style: italic;"&gt;NB&lt;/span&gt;: This only works if everyone debates within brackets. It fails to hold as a true assumption for pull-up rounds, so this system would fail utterly for round robins.&lt;br /&gt;&lt;br /&gt;However, it is not the pull-up problem that scuppers this system (I think it's somewhat solvable for one-win pull-up rounds with half-points). The problem is that this system produces &lt;span style="font-style: italic; font-weight: bold;"&gt;a&lt;/span&gt; ranking that is consistent with the actual win-loss results; it does not necessarily produce &lt;span style="font-style: italic; font-weight: bold;"&gt;the&lt;/span&gt; most desirable ranking. True, teams are never ranked below someone they beat, but this system overdoes it: teams are ranked by the order in which they won rounds. What about an excellent 4-2 team with great speaker points who loses the first two random rounds to the top 4-2 teams? To the good, this excellent 4-2 team will be ranked below the top two 4-2 teams (because LLWWWW is worth fewer points than, for example, WLWWWL and LWWWLW); to the excess, this team will be ranked below &lt;span style="font-style: italic;"&gt;EVERY&lt;/span&gt; 4-2 team who happened to win either of the first two rounds. It's throwing the baby out with the bath water. Furthermore, it makes no sense to use weighted wins as a third or fourth tie-breaker. If speaker points are the first tie-breaker, then it becomes possible to rank a team below someone they have beaten. It's an all-or-nothing solution, and no one would think that the rankings it produces are good.&lt;br /&gt;&lt;br /&gt;The math behind this problem turns out to be more interesting than the originally intended application. Some patterns emerge in any set of numbers that work for weighted wins. In the set of numbers {&lt;span style="font-style: italic;"&gt;a&lt;/span&gt;, &lt;span style="font-style: italic;"&gt;b&lt;/span&gt;, &lt;span style="font-style: italic;"&gt;c&lt;/span&gt;, &lt;span style="font-style: italic;"&gt;d&lt;/span&gt;, &lt;span style="font-style: italic;"&gt;e&lt;/span&gt;, &lt;span style="font-style: italic;"&gt;f&lt;/span&gt;}, the terms must be decreasing, so &lt;span style="font-style: italic;"&gt;a&lt;/span&gt; &gt; &lt;span style="font-style: italic;"&gt;b&lt;/span&gt; &gt; &lt;span style="font-style: italic;"&gt;c&lt;/span&gt; &gt; &lt;span style="font-style: italic;"&gt;d&lt;/span&gt; &gt; &lt;span style="font-style: italic;"&gt;e&lt;/span&gt; &gt; &lt;span style="font-style: italic;"&gt;f&lt;/span&gt; is the first condition. However, not just any set of decreasing terms will work. For example, if the weighted win points were {1, 0.9, 0.8, 0.7, 0.6, 0.5}, the system breaks down: for two 2-0 teams, a round 1 and round 6 win totals 1.5 points, but it should beat a round 2 and round 3 win, which totals 1.7 points. Therefore, the second, trickier condition is that the decreases must decrease, that is, while the slope is negative (negative first derivative) the set must have upward concavity (positive second derivative). Going to my original set of numbers {1, 0.9, 0.89, 0.889, 0.8889, 0.88889}, the terms are decreasing, meeting the first condition, and the decrease is decreasing {-0.1, -0.01, -0.001, -0.0001, -0.00001}, meeting the second condition.&lt;br /&gt;&lt;br /&gt;Looking at the chart, every unmarked place is one where any set of numbers that meets only the first condition will be true. For example, on the line of round 3, as long as &lt;span style="font-style: italic;"&gt;a&lt;/span&gt; &gt; &lt;span style="font-style: italic;"&gt;b&lt;/span&gt; &gt; &lt;span style="font-style: italic;"&gt;c&lt;/span&gt;, then &lt;span style="font-style: italic;"&gt;a&lt;/span&gt;+&lt;span style="font-style: italic;"&gt;b&lt;/span&gt; &gt; &lt;span style="font-style: italic;"&gt;a&lt;/span&gt;+&lt;span style="font-style: italic;"&gt;c&lt;/span&gt; &gt; &lt;span style="font-style: italic;"&gt;b&lt;/span&gt;+&lt;span style="font-style: italic;"&gt;c&lt;/span&gt;; it's analytically true. Every marked place is one where a set of numbers that meets only the first condition might fail; only sets meeting both conditions must be true. For example, on the line of round 4, &lt;span style="font-style: italic;"&gt;a&lt;/span&gt;+&lt;span style="font-style: italic;"&gt;d&lt;/span&gt; must be &gt; &lt;span style="font-style: italic;"&gt;b&lt;/span&gt;+&lt;span style="font-style: italic;"&gt;c&lt;/span&gt; only if the second condition is also met. I made up a term for a set that meets the conditions of this problem: an "inequality ordered set." The definition would be: a set of numbers, such that for any two equally-sized subsets created without repetition of terms, the subset with the single largest term always has the largest sum. For example, &lt;span style="font-style: italic;"&gt;a&lt;/span&gt;+&lt;span style="font-style: italic;"&gt;f&lt;/span&gt; &gt; &lt;span style="font-style: italic;"&gt;b&lt;/span&gt;+&lt;span style="font-style: italic;"&gt;c&lt;/span&gt; and &lt;span style="font-style: italic;"&gt;a&lt;/span&gt;+&lt;span style="font-style: italic;"&gt;e&lt;/span&gt;+&lt;span style="font-style: italic;"&gt;f&lt;/span&gt; &gt; &lt;span style="font-style: italic;"&gt;b&lt;/span&gt;+&lt;span style="font-style: italic;"&gt;c&lt;/span&gt;+&lt;span style="font-style: italic;"&gt;d&lt;/span&gt;.&lt;br /&gt;&lt;br /&gt;I wondered whether it is possible to create an infinitely long "inequality ordered set." Two possible ways to create such an infinite set: {1, (1/x), (1/x^2), ...} and {1, 1-(1/x), 1-(1/x)-(1/x^2), ...}. For the first kind, the smallest &lt;span style="font-style: italic;"&gt;x&lt;/span&gt; that still works is about 2. For the second kind, the smallest &lt;span style="font-style: italic;"&gt;x&lt;/span&gt; that still works is about 1.25. I'm working on writing a proof of these.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-4905152833748094581?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/4905152833748094581/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/12/pascals-triangle-modified.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/4905152833748094581'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/4905152833748094581'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/12/pascals-triangle-modified.html' title='Pascal&apos;s triangle (modified)'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_5RAO7k_azLU/Sygr8hfSEcI/AAAAAAAAAKY/xlZPxkZcWQ0/s72-c/pascal%27s+revised.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-3646644382725040232</id><published>2009-09-13T17:34:00.017-04:00</published><updated>2009-10-01T10:08:42.792-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='cross-examination debate'/><category scheme='http://www.blogger.com/atom/ns#' term='debate tournaments'/><category scheme='http://www.blogger.com/atom/ns#' term='matched pairs'/><category scheme='http://www.blogger.com/atom/ns#' term='high school debate'/><category scheme='http://www.blogger.com/atom/ns#' term='significance'/><category scheme='http://www.blogger.com/atom/ns#' term='side bias'/><title type='text'>Topic side bias</title><content type='html'>A Numbers Game did some interesting work on the side bias of various college topics, &lt;a href="http://code.google.com/p/anumbersgame/wiki/TopicSideBias"&gt;here&lt;/a&gt;, specifically, controlling for team strength. In that spirit, I decided to use a different method and see how the results compared.&lt;br /&gt;&lt;br /&gt;I used a matched pairs method: for each team, there is a matched pair of results: that team's win percentage on the affirmative, and that team's win percentage on the negative. If the two results show no difference, then the team did equally well (or equally poorly) on both sides of the topic. If the two results do show a difference, there are three possible explanations: (1) the team isn't equally strong on both sides of the topic, e.g., the 2A isn't as good as the 2N; (2) the team hit an unequal set of opponents on the two sides; or (3) there is side bias on the topic. When one looks at &lt;span style="font-style: italic;"&gt;all&lt;/span&gt; the teams on a topic, (1) is unlikely because the whole point is to control for team strength by assuming that the &lt;span style="font-style: italic;"&gt;average&lt;/span&gt; team is equally strong on either side, (2) cancels out when one looks at the entire pool, and (3) is left as the most plausible outcome. Although this method still relies on the assumption of invariant strength (that a team has a fixed strength, the same on both sides of the topic, unchanging throughout the year), so does any other method that attempts to control for team strength. With those disclaimers, here are the results:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_5RAO7k_azLU/SsAGb9rsGuI/AAAAAAAAAJk/KDlsgspnoVs/s1600-h/results+table.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 405px; height: 194px;" src="http://2.bp.blogspot.com/_5RAO7k_azLU/SsAGb9rsGuI/AAAAAAAAAJk/KDlsgspnoVs/s320/results+table.jpg" alt="" id="BLOGGER_PHOTO_ID_5386312231819156194" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;The third column shows the mean of the matched pairs computation: for each team, I subtracted its negative win percentage from its affirmative win percentage, and I averaged this score over all the teams that year. The fourth column shows a calculated (not the actual) affirmative win rate. They compare closely to the &lt;a href="http://code.google.com/p/anumbersgame/wiki/JudgeSideBias"&gt;actual rates&lt;/a&gt; A Numbers Game already found. The two that are highlighted differ slightly. The affirmative win rate for the China topic my analysis suggests is slightly lower than the actual rate. The affirmative win rate for the courts topic my analysis suggests that the negative had an advantage, while the actual rate showed an affirmative advantage.&lt;br /&gt;&lt;br /&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 389px; height: 395px;" src="http://2.bp.blogspot.com/_5RAO7k_azLU/SsANy4u0dcI/AAAAAAAAAJs/Cor0IqBbhaQ/s320/drilled+in+table.jpg" alt="" id="BLOGGER_PHOTO_ID_5386320322208495042" border="0" /&gt;&lt;br /&gt;Category 1 is roughly the 0-50th percentile (in terms of rounds of competition); category 2 is 50-75th; category 3 is 75-87th; category 4 is 87-94th; and category 5 is 94-100th. You can see the results clearly in both: the less experienced teams had greater success on the negative; the more experienced teams did better (relatively or absolutely) on the affirmative. The reason why the originally calculated affirmative win rate was too low was because there are so many more less experienced teams that bring down the average matched comparison -- but they debate few rounds, so they do not have a big effect on the total ballot count. (I looked at the same tables for other years, but there were no patterns as clear as '05-06 and '06-07.)&lt;br /&gt;&lt;br /&gt;One final note: All of the whole years' analyses are significant to at least the 95% level except for '06-07, which is only significant at about the 85% level. I used a 1-sample t-test, since the distributions are more or less normal:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_5RAO7k_azLU/SsOHMU71lDI/AAAAAAAAAJ8/FqBKZR4Pg3M/s1600-h/normal+graph.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 239px;" src="http://4.bp.blogspot.com/_5RAO7k_azLU/SsOHMU71lDI/AAAAAAAAAJ8/FqBKZR4Pg3M/s320/normal+graph.jpg" alt="" id="BLOGGER_PHOTO_ID_5387298225113109554" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;(This is '08-09, but all the distributions look like this.) In fact, the distribution looks a little tighter than the normal curve (given the population's mean and standard deviation), since so many teams have 0% aff-neg win spread. The cumulative frequency graph is even more persuasive:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_5RAO7k_azLU/SsOHL_8N5RI/AAAAAAAAAJ0/EotzMvQXft8/s1600-h/analysis.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 421px; height: 319px;" src="http://2.bp.blogspot.com/_5RAO7k_azLU/SsOHL_8N5RI/AAAAAAAAAJ0/EotzMvQXft8/s320/analysis.jpg" alt="" id="BLOGGER_PHOTO_ID_5387298219477558546" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;The blue line represents a normal CDF, given the population's ('08-09) mean and standard deviation. Anything below the line on the left or above the line on the right is tighter than normal. The reason is that the standard deviation is pulled way out by the teams that competed for few rounds (who had very high variability in the spread, from -1 to 1). For '08-09 for example, the standard deviation for the whole population is 0.31; excluding teams with fewer than 9 rounds experience, 0.22.&lt;br /&gt;&lt;br /&gt;Based on A Numbers Game's question, I created a Lorenz curve for '08-09:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/SsS3IqGUSVI/AAAAAAAAAKE/wY0reX_IolE/s1600-h/lorenz.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 388px; height: 314px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/SsS3IqGUSVI/AAAAAAAAAKE/wY0reX_IolE/s320/lorenz.jpg" alt="" id="BLOGGER_PHOTO_ID_5387632413609576786" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;A few data points in words:&lt;br /&gt;&lt;br /&gt;The top 5% of teams debated 19% of all rounds.&lt;br /&gt;The top 10% of teams debated 34% of all rounds.&lt;br /&gt;The top 20% of teams debated 54% of all rounds.&lt;br /&gt;The top half of teams debated 83% of all rounds.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-3646644382725040232?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/3646644382725040232/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/09/topic-side-bias.html#comment-form' title='5 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/3646644382725040232'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/3646644382725040232'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/09/topic-side-bias.html' title='Topic side bias'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_5RAO7k_azLU/SsAGb9rsGuI/AAAAAAAAAJk/KDlsgspnoVs/s72-c/results+table.jpg' height='72' width='72'/><thr:total>5</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-9176180892576917904</id><published>2009-08-25T22:16:00.013-04:00</published><updated>2009-08-27T22:59:27.099-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='debate tournaments'/><category scheme='http://www.blogger.com/atom/ns#' term='bias'/><category scheme='http://www.blogger.com/atom/ns#' term='judge'/><category scheme='http://www.blogger.com/atom/ns#' term='side bias'/><title type='text'>Judge side bias -- the whole field</title><content type='html'>I've been intrigued by A Numbers Game's information about &lt;a href="http://code.google.com/p/anumbersgame/wiki/JudgeSideBias"&gt;judge side bias&lt;/a&gt;. Rather than looking at particular judges, I wanted to look at the distribution of all the judges. I plotted the (prelim) judging records of all the college tournaments in '04-05 (data from Bruschke's &lt;a href="http://commweb.fullerton.edu/jbruschke/web/ResultsArchives/archiveindex.aspx"&gt;Debateresults.com&lt;/a&gt;)&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_5RAO7k_azLU/SpWM9m2IetI/AAAAAAAAAJc/hUzrp5opnvY/s1600-h/judge+side+bias+final.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 400px; height: 256px;" src="http://2.bp.blogspot.com/_5RAO7k_azLU/SpWM9m2IetI/AAAAAAAAAJc/hUzrp5opnvY/s400/judge+side+bias+final.jpg" alt="" id="BLOGGER_PHOTO_ID_5374356720364059346" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;(&lt;a href="http://www.mediafire.com/?mqg04myzne4"&gt;Excel workbook&lt;/a&gt;.) The vertical axis shows how many prelim rounds a judge judged; the horizontal axis shows the percentage of aff wins a judge gave. As you can see, the shape of the dot plot shows a clear pattern: as judges see more rounds, they cluster more tightly around the mean [.4840, according to A Numbers Game], and the plot narrows at the top. This is as it should be: the more rounds you judge, the less likely you get lots and lots of strong aff. teams (or weak aff. teams) by chance. But how to quantify this pattern and ask exactly how it compares to what we'd expect to see by chance?&lt;br /&gt;&lt;br /&gt;What makes this challenging is that the sample sizes differ for each judge. Some judges judged 80 rounds, some two. Normally, you'd expect to have a standard sample size. So I calculated the probabilities at various sample sizes, specifically, at a six-round increment to make the lines. The green lines mark the 68% confidence interval (roughly 1 standard deviation above and below the mean ); the yellow lines the 95% confidence interval (roughly 2 standard deviations); and the red lines mark the 99.8% confidence interval (roughly 3 s.d.s). This is an unusual method, so let me explain what I think it shows. If every judge saw 36 rounds, then we would expect 68% of those judges voted aff. between 40 and 60% of the time (you can trace to see that the green lines do indeed pass through these points). So far, so good. My somewhat original assumption is that you can add these slices up: since for &lt;span style="font-style: italic;"&gt;x&lt;/span&gt; rounds judged, 68% of those judges in that horizontal slice should be between the green lines, then for all the judges in the whole vertical column, 68% should be between the green lines.&lt;br /&gt;&lt;br /&gt;It turns out a little worse than expected, at 33.5%, but not by much. And, as A Numbers Game has shown, this is about the same for the other years, too.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-9176180892576917904?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/9176180892576917904/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/08/judge-side-bias-whole-field.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/9176180892576917904'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/9176180892576917904'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/08/judge-side-bias-whole-field.html' title='Judge side bias -- the whole field'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_5RAO7k_azLU/SpWM9m2IetI/AAAAAAAAAJc/hUzrp5opnvY/s72-c/judge+side+bias+final.jpg' height='72' width='72'/><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-2512047135875631184</id><published>2009-08-07T16:58:00.007-04:00</published><updated>2009-08-07T17:55:19.047-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='debate tournaments'/><category scheme='http://www.blogger.com/atom/ns#' term='power-matching'/><category scheme='http://www.blogger.com/atom/ns#' term='pairing methods'/><category scheme='http://www.blogger.com/atom/ns#' term='high school debate'/><category scheme='http://www.blogger.com/atom/ns#' term='schedule strength'/><category scheme='http://www.blogger.com/atom/ns#' term='strength of schedule'/><category scheme='http://www.blogger.com/atom/ns#' term='opponent wins'/><title type='text'>Another way to visualize strength-of-schedule pairings</title><content type='html'>I've written about a type of pairing I call a &lt;a href="http://art-of-logic.blogspot.com/2009/03/strength-of-schedule-pairings-work.html"&gt;strength-of-schedule&lt;/a&gt; pairing. The basic idea is that a team that has had a weak schedule so far (measured by opp. wins, opp. speaks, etc.) gets a strong opponent for the next round. (Of course, all of this is within a bracket, so weak and strong are relative to the average team strength and schedule strength in that bracket.) It sounds simple enough, but it has to work both ways -- both teams get the opponent they deserve in each other.&lt;br /&gt;&lt;br /&gt;It hit me how to help people visualize how this pairing method differs from the traditional. First, picture a Cartesian grid, depicting one bracket, like so:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_5RAO7k_azLU/SnyavIk3Y6I/AAAAAAAAAI0/OLF_fI8QhKw/s1600-h/blank+quads.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 398px; height: 400px;" src="http://2.bp.blogspot.com/_5RAO7k_azLU/SnyavIk3Y6I/AAAAAAAAAI0/OLF_fI8QhKw/s400/blank+quads.jpg" alt="" id="BLOGGER_PHOTO_ID_5367334990465426338" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;A position along the &lt;span style="font-style: italic;"&gt;x&lt;/span&gt;-axis shows a team's strength (say, speaker points) above or below the average, 0, of the bracket. (If it helps, you can think of these as standard deviations above or below the mean; or, you can think of these as speaker points above or below 28.) A position along the &lt;span style="font-style: italic;"&gt;y&lt;/span&gt;-axis shows a difficulty of a team's schedule above or below the average. Quadrant I contains the good teams in the bracket that have had tough schedules; quadrant IV contains the good teams that have had easy schedules.&lt;br /&gt;&lt;br /&gt;Ideally, you want debaters from quadrant I (strong teams, strong schedules) to face debaters from quadrant III (weak teams, weak schedules), debaters from quadrant II (weak teams, strong schedules) to face each other, and debaters from quadrant IV (strong teams, weak schedules) to face each other -- to even everything out. Let's look at how the two traditional methods fare. I generated 16 random points on the grid, and based on their scores, power-matched them using these two methods.&lt;br /&gt;&lt;br /&gt;First, high-high-pairings:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_5RAO7k_azLU/SnyavQh4e3I/AAAAAAAAAI8/ZiOGW1CNzT4/s1600-h/high-high+pairing.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 400px; height: 362px;" src="http://4.bp.blogspot.com/_5RAO7k_azLU/SnyavQh4e3I/AAAAAAAAAI8/ZiOGW1CNzT4/s400/high-high+pairing.jpg" alt="" id="BLOGGER_PHOTO_ID_5367334992600398706" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;The best team faces the second best; third, the fourth; on down to the second worst facing the worst. Two debates are matched between quadrants I and IV. These are unfair to quadrant I teams, who are good teams, with tough schedules, facing yet another good team. There are four debates between quadrant II and III. These are unfair to quadrant III teams, who are weak teams, with easy schedules, facing yet another weak team. I'd say there's really only one good match: the quadrant IV team to the other quadrant IV team. All in all, many of these debates are likely to exacerbate the range of schedule strength teams face. Score: 1/8.&lt;br /&gt;&lt;br /&gt;Second, let's look at the high-low pairing method, using the same 16 points:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_5RAO7k_azLU/SnyawErQazI/AAAAAAAAAJE/HD27i8_o36g/s1600-h/high-low+pairing.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 400px; height: 364px;" src="http://3.bp.blogspot.com/_5RAO7k_azLU/SnyawErQazI/AAAAAAAAAJE/HD27i8_o36g/s400/high-low+pairing.jpg" alt="" id="BLOGGER_PHOTO_ID_5367335006598359858" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;The best team debates the lowest, then the second best debates the second worst, and so on. This is not much of an improvement in terms of equalizing schedule strength. There are two debates between quadrant I to II -- unfair to quadrant II teams, weak teams, tough schedules, facing another good opponent. There are two debates between quadrant III and IV -- unfair to quadrant IV teams, good teams, easy schedules, facing another weak opponent. And there are two that are truly wretched: quadrant II (weak teams, tough schedules) to quadrant IV (strong teams, easy schedules) -- unfair to both quadrant II and IV teams!! There are really only two good matches, between quadrant I and III teams. Score: 2/8.&lt;br /&gt;&lt;br /&gt;Here's what a strength-of-schedule pairing looks like, for the same points:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_5RAO7k_azLU/Snyawb6vVvI/AAAAAAAAAJM/4sS8HtwUy5k/s1600-h/strength-of-schedule+pairing.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 400px; height: 396px;" src="http://3.bp.blogspot.com/_5RAO7k_azLU/Snyawb6vVvI/AAAAAAAAAJM/4sS8HtwUy5k/s400/strength-of-schedule+pairing.jpg" alt="" id="BLOGGER_PHOTO_ID_5367335012837316338" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;I didn't tweak it! This is what came out of my algorithm. All eight matches accord with the preferences I spelled out: &lt;span&gt;I&lt;/span&gt;s debate &lt;span&gt;III&lt;/span&gt;s, &lt;span&gt;II&lt;/span&gt;s debate &lt;span&gt;II&lt;/span&gt;s, and &lt;span&gt;IV&lt;/span&gt;s debate &lt;span&gt;IV&lt;/span&gt;s. I added in the dotted line to show that most of them have this rough symmetry, where the &lt;span style="font-style: italic;"&gt;x&lt;/span&gt; score of one is nearly as possible &lt;span style="font-style: italic;"&gt;-y&lt;/span&gt; of the other, and vice versa. Given the random distribution of the points, it's pretty darn good. All in all, this will equalize as much as possible the schedule strength faced by each team in this bracket. Tough schedule? Weak opponent. Easy schedule? Strong opponent. Score: 8/8.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-2512047135875631184?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/2512047135875631184/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/08/another-way-to-visualize-strength-of.html#comment-form' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/2512047135875631184'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/2512047135875631184'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/08/another-way-to-visualize-strength-of.html' title='Another way to visualize strength-of-schedule pairings'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_5RAO7k_azLU/SnyavIk3Y6I/AAAAAAAAAI0/OLF_fI8QhKw/s72-c/blank+quads.jpg' height='72' width='72'/><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-459213197559010019</id><published>2009-08-04T19:00:00.009-04:00</published><updated>2009-08-07T15:15:33.031-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='debate tournaments'/><category scheme='http://www.blogger.com/atom/ns#' term='rankings'/><category scheme='http://www.blogger.com/atom/ns#' term='high school debate'/><category scheme='http://www.blogger.com/atom/ns#' term='cyclical graphs'/><category scheme='http://www.blogger.com/atom/ns#' term='network graph theory'/><category scheme='http://www.blogger.com/atom/ns#' term='cycles'/><category scheme='http://www.blogger.com/atom/ns#' term='round robins'/><title type='text'>Network graph theory and debate tournaments</title><content type='html'>I recently saw A Numbers Game's &lt;a href="http://code.google.com/p/anumbersgame/wiki/TournamentCharts"&gt;charts of debate tournaments&lt;/a&gt;, which look like modified network graphs, and it inspired me to post about some thoughts I'd had a few years ago about graph theory and debate tournaments. (Network) graph theory is a fascinating branch of mathematics, and it is directly applicable to debate tournaments. Basically, a network graph is anything that maps all the pathways (edges) between some nodes (vertices). A network graph of a debate tournament shows the match-ups (edges) between the teams at the tournament (vertices). An edge without an arrow would just show a match-up between two teams; an edge with an arrow would indicate the winner of it. A network graph can show the results of all six (or eight or whatever) preliminary rounds simultaneously. You can see a lot of interesting patterns that would be hard to notice any other way; I've used &lt;a href="http://art-of-logic.blogspot.com/2009/03/debate-tournament-math.html"&gt;network graphs&lt;/a&gt; as a way to illustrate how a tournament played out.&lt;br /&gt;&lt;br /&gt;You might think, since graphs are a complete mapping of all the preliminary round results, that they could be used to rank all the teams at a tournament from first seed to worst. However, if you tried to use a graph this way, you'd run into three different problems. Graphs are best for illustrative purposes (and one alternative use I'll suggest at the end).&lt;br /&gt;&lt;br /&gt;The first problem with trying to use a graph to seed the teams is that you still need a lot of tiebreakers. Here's a simple example:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/Sni-tZSZyxI/AAAAAAAAAHU/mPU6uVcfDbc/s1600-h/network1.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 141px; height: 199px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/Sni-tZSZyxI/AAAAAAAAAHU/mPU6uVcfDbc/s400/network1.jpg" alt="" id="BLOGGER_PHOTO_ID_5366248643103410962" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;As indicated by the graph, team A beat B and C, and teams B and C both beat D. The problem is that B and C can't be ranked against each other from this information alone. Given the results, the final rankings must contain the sequences {A, B, D} and {A, C, D}, but both {A, B, C, D} and {A, C, B, D} satisfy this. The problem is that, except for round robins, there will always be teams that didn't meet at the tournament, and thus, pairs of vertices without edges.&lt;br /&gt;&lt;br /&gt;Ok, so, you still need tiebreakers, but a network graph as a ranking mechanism presents a second, bigger problem: "contradictions." Let's say we run a really small tournament, and we must force A and B to debate twice. Here's one possible outcome that creates a contradiction:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/Sni-t0yLjKI/AAAAAAAAAHc/AkcJCiL_Gfg/s1600-h/network2.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 200px; height: 121px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/Sni-t0yLjKI/AAAAAAAAAHc/AkcJCiL_Gfg/s400/network2.jpg" alt="" id="BLOGGER_PHOTO_ID_5366248650484452514" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;A (aff.) beat B, but B (aff.) beat A. If we try to use the network graph to rank these two teams, we'd be forced to give two contradictory statements. (It's worth remembering that a team's strength is not invariant: teams can be better on one side than the other, they can have off rounds or lucky rounds, and judges also play a factor.) This is simple enough to resolve: we can use speaker points to rank one team higher than the other. Here's a slightly more complex version of the same problem:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_5RAO7k_azLU/Sni-ucw0EFI/AAAAAAAAAHk/4KF5teVHrIU/s1600-h/network3.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 200px; height: 176px;" src="http://4.bp.blogspot.com/_5RAO7k_azLU/Sni-ucw0EFI/AAAAAAAAAHk/4KF5teVHrIU/s400/network3.jpg" alt="" id="BLOGGER_PHOTO_ID_5366248661216137298" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;A beat B (rd 1), B beat C (rd 2), and C beat A (rd 3). There's a contradiction here also. It will have to be resolved by "upsetting" one result, that is, a team must be ranked below an opponent whom they beat. For example, a final ranking might be {A, B, C}, which means that C's victory over A was "upset" or "overruled" because A had more overall wins, better speaker points, etc., than B or C. Bear in mind that doing a graph didn't create this problem; it merely exposed it. We're mostly oblivious to it because cume sheets show wins, points, etc., and don't provide a network graph. Look carefully through the results of nearly any tournament, and I'd be willing to beat you can find at least a few teams who are ranked below (based on overall record, speaks, etc.) an opponent they beat. Here's another example:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/Sni-uwjv0tI/AAAAAAAAAHs/I6VGNsXnxOU/s1600-h/network4.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 200px; height: 174px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/Sni-uwjv0tI/AAAAAAAAAHs/I6VGNsXnxOU/s400/network4.jpg" alt="" id="BLOGGER_PHOTO_ID_5366248666530042578" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Any such type of contradiction, no matter how many teams, is known as a simple cyclical graph, if there's only one cyclical pathway. The good news is that, however long a simple cyclical graph, only one result has to be upset: {A, B, C, D} only upsets D's victory over A. (A complex cyclical graph would contain multiple, intersecting cycles and be a much bigger headache, but my hunch is that they are extremely rare.)&lt;br /&gt;&lt;br /&gt;The third problem with using a network graph as a ranking mechanism is perhaps its biggest, if not mathematically, then for the debate community to stomach:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_5RAO7k_azLU/Sni-v-7wnzI/AAAAAAAAAH0/rv5PCr3ZJVQ/s1600-h/network5.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 146px; height: 201px;" src="http://2.bp.blogspot.com/_5RAO7k_azLU/Sni-v-7wnzI/AAAAAAAAAH0/rv5PCr3ZJVQ/s400/network5.jpg" alt="" id="BLOGGER_PHOTO_ID_5366248687568723762" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Notice the problem? There are no cycles; everything flows in only one direction. The rankings, according to the graph, are unambiguously {A, B, C, D, E, F}. Here it is again:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/Sni_kbaVyCI/AAAAAAAAAH8/GPDYcu-itqU/s1600-h/network6.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 135px; height: 200px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/Sni_kbaVyCI/AAAAAAAAAH8/GPDYcu-itqU/s400/network6.jpg" alt="" id="BLOGGER_PHOTO_ID_5366249588566378530" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;C beat D, but at any tournament, D would be ranked higher, because C is 1-2 and D is 2-1. In the situation I graphed, C is the better team but had a tougher schedule. (It's also possible to create an example in which D is the better team but just had an off-round or a crazy judge.) There's no cycle in the graph, so there's no need to have an upset, but I believe every debater and coach would say D should be ranked higher. Total wins as the first method of ranking is sacrosanct to the debate community, and with good reason. Total wins is clear and unambiguous; a network graph is abstract and complex. I know I would never want a tournament to start interpreting results with a network graph; it would create too much room for error when deciding breaks.&lt;br /&gt;&lt;br /&gt;This last problem is insurmountable. I think the lesson is that we need to take every effort to make schedule strength more equitable, but there's no mathematical way to jigger results to somehow weight or re-interpret an unfair set of pairings. The cat's out of the bag, and we just have to say, "Sorry, tournaments aren't always fair," at that point. The bottom line is that network graphs will never and ought not be used for tournament rankings. But there's is an alternative use for graph theory: as a tiebreaker at round robins.&lt;br /&gt;&lt;br /&gt;Let's say a six-team round robin has these final results:&lt;br /&gt;&lt;br /&gt; Team        Record&lt;br /&gt; A                4-1&lt;br /&gt; B                3-2&lt;br /&gt; C                3-2&lt;br /&gt; D                3-2&lt;br /&gt; E                2-3&lt;br /&gt; F                0-5&lt;br /&gt;&lt;br /&gt;There's a three-way tie for second place. My suggestion is that round robins can use an idea from graph theory as the first tiebreaker, before resorting to speaker points. I believe that direct results ought to be respected as much as possible, and in round robins, you have direct results for every head-to-head match up.  Who cares that team C spoke prettier than B or D if C lost both of those rounds? Here's the graph of this hypothetical round robin:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_5RAO7k_azLU/Sni_kwZlCjI/AAAAAAAAAIE/7LoSOSARBN8/s1600-h/network7.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 200px; height: 152px;" src="http://3.bp.blogspot.com/_5RAO7k_azLU/Sni_kwZlCjI/AAAAAAAAAIE/7LoSOSARBN8/s400/network7.jpg" alt="" id="BLOGGER_PHOTO_ID_5366249594200328754" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Now, you may notice that C beat A, which suggests that C is the best of the three, or you may focus on the fact that D beat both B and C, which suggests that D is the best. Both may catch your eye, but there's a way to quantify an exact result. But first, you need to turn the graph into an incidence matrix, like so:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/Sni_lmjUISI/AAAAAAAAAIM/AZQbwZ8kWsE/s1600-h/matrix1.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 183px; height: 134px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/Sni_lmjUISI/AAAAAAAAAIM/AZQbwZ8kWsE/s400/matrix1.jpg" alt="" id="BLOGGER_PHOTO_ID_5366249608736678178" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;A column represents a team's wins; a row, its losses. Hence, reading down column A, you see that team A beat B, D, E, and F; reading across column A, you see that team A lost to C. The incidence matrix contains all the information that the graph does; it's merely another representation of the same data. You might also notice that there's an easy way to double-check the matrix:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/Sni_mPMS_hI/AAAAAAAAAIU/NhMvVsHSjoE/s1600-h/matrix2.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 200px; height: 131px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/Sni_mPMS_hI/AAAAAAAAAIU/NhMvVsHSjoE/s400/matrix2.jpg" alt="" id="BLOGGER_PHOTO_ID_5366249619645988370" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;You can add to make sure you have the right number of wins in the column and losses in the row for each team. (The incidence matrix is easy to do for multi-ballot round robins; just put the ballots won into the correct spot for each team.)&lt;br /&gt;&lt;br /&gt;Now, we need to test possible rankings. There are six possibilities created by the three-way tie: {A, B, C, D, E, F}, {A, B, D, C, E, F}, {A, C, B, D, E, F}, {A, C, D, B, E, F}, {A, D, B, C, E, F}, and {A, D, C, B, E, F}. We create an incidence matrix for each possible ranking, a matrix of the hypothetical results that perfectly consistent the ranking order with no upsets, ties, or ambiguity. For example, for the possible ranking {A, B, C, D, E, F}, the matrix is:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_5RAO7k_azLU/Sni_mjzl27I/AAAAAAAAAIc/NOe6D9k39AA/s1600-h/matrix3.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 196px; height: 135px;" src="http://2.bp.blogspot.com/_5RAO7k_azLU/Sni_mjzl27I/AAAAAAAAAIc/NOe6D9k39AA/s400/matrix3.jpg" alt="" id="BLOGGER_PHOTO_ID_5366249625179511730" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The matrix shows results that would be perfectly consistent with the ranking. Now we can calculate a score for how well this ranking corresponds to the actual tournament results:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/SnjAZ6eTYtI/AAAAAAAAAIk/uwSUOAyaNFc/s1600-h/matrix4.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 200px; height: 115px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/SnjAZ6eTYtI/AAAAAAAAAIk/uwSUOAyaNFc/s400/matrix4.jpg" alt="" id="BLOGGER_PHOTO_ID_5366250507437564626" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Subtract the possible ranking matrix [&lt;span style="font-style: italic;"&gt;R&lt;/span&gt;] from the actual tournament results [&lt;span style="font-style: italic;"&gt;T&lt;/span&gt;] and count the -1s. (You can count the +1s also; they are symmetrical.) According to this ranking, there were four "upsets": that C actually beat A, that D actually beat B, that D actually beat C, and that E actually beat D. If a tournament accepts the ranking {A, B, C, D, E, F}, it "overturns" four direct results.&lt;br /&gt;&lt;br /&gt;How do the other rankings compare? Using the same method for each "prediction," the rankings can be compared:&lt;br /&gt;&lt;br /&gt; Rank order                "Upsets"&lt;br /&gt; {A, B, C, D, E, F} 4&lt;br /&gt; {A, B, D, C, E, F}        3&lt;br /&gt; {A, C, B, D, E, F}        5&lt;br /&gt; {A, C, D, B, E, F}        4&lt;br /&gt; {A, D, B, C, E, F}        2&lt;br /&gt; {A, D, C, B, E, F}        3&lt;br /&gt;&lt;br /&gt;The best ranking is obviously {A, D, B, C, E, F}. It upsets the fewest direct results. In fact, the two that are upset make perfect sense:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/SnjAaW-5QcI/AAAAAAAAAIs/BFcE_D1JBV0/s1600-h/matrix5.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 200px; height: 113px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/SnjAaW-5QcI/AAAAAAAAAIs/BFcE_D1JBV0/s400/matrix5.jpg" alt="" id="BLOGGER_PHOTO_ID_5366250515090457026" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;that C (3-2) actually beat A (4-1) and that E (2-3) actually beat D (3-2). In a sense, these were unavoidable (or you might even say real) upsets, not artifacts created by a poor ranking. Anyway, the point is, the three-way tie could be broken in this case without resorting to speaker points. This algorithm would be relatively easy to program into a tab program for round robins.&lt;br /&gt;&lt;br /&gt;Of course, some ties are cannot be resolved by this method, namely, if the ties are really contradictions created by cycles. There's still a place for speaker points and other tiebreakers.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-459213197559010019?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/459213197559010019/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/08/network-graph-theory-and-debate.html#comment-form' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/459213197559010019'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/459213197559010019'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/08/network-graph-theory-and-debate.html' title='Network graph theory and debate tournaments'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/_5RAO7k_azLU/Sni-tZSZyxI/AAAAAAAAAHU/mPU6uVcfDbc/s72-c/network1.jpg' height='72' width='72'/><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-4759369316660327300</id><published>2009-06-20T20:26:00.006-04:00</published><updated>2009-06-20T20:39:21.457-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Venn diagram'/><category scheme='http://www.blogger.com/atom/ns#' term='Aristotle'/><category scheme='http://www.blogger.com/atom/ns#' term='logic'/><category scheme='http://www.blogger.com/atom/ns#' term='syllogism'/><title type='text'>Have you ever heard of Plato, Aristotle, Socrates?</title><content type='html'>Aristotle wrote one of the earliest systemizations of logic, his syllogisms. Unfortunately, he made two tiny oversights. An easy and fun logic lesson with students is to use Venn diagrams to check each syllogism, like so:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_5RAO7k_azLU/Sj1_LxDxGNI/AAAAAAAAAHM/IkD3TuWr8Bk/s1600-h/Aristotle+logic+Venn+diagrams.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 309px; height: 400px;" src="http://4.bp.blogspot.com/_5RAO7k_azLU/Sj1_LxDxGNI/AAAAAAAAAHM/IkD3TuWr8Bk/s400/Aristotle+logic+Venn+diagrams.jpg" alt="" id="BLOGGER_PHOTO_ID_5349571772510443730" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;A full list of the syllogisms is in this &lt;a href="http://www.mediafire.com/?zyiyieunhhz"&gt;document&lt;/a&gt;. Thanks to Keith Devlin for the idea.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-4759369316660327300?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/4759369316660327300/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/06/have-you-ever-heard-of-plato-aristotle.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/4759369316660327300'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/4759369316660327300'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/06/have-you-ever-heard-of-plato-aristotle.html' title='Have you ever heard of Plato, Aristotle, Socrates?'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_5RAO7k_azLU/Sj1_LxDxGNI/AAAAAAAAAHM/IkD3TuWr8Bk/s72-c/Aristotle+logic+Venn+diagrams.jpg' height='72' width='72'/><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-7287062205193065184</id><published>2009-06-11T19:49:00.008-04:00</published><updated>2009-06-16T13:15:12.318-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='chain rule'/><category scheme='http://www.blogger.com/atom/ns#' term='derivatives'/><category scheme='http://www.blogger.com/atom/ns#' term='lower boundary'/><title type='text'>A neat application for derivatives</title><content type='html'>Whoa! May was crazy. But I survived. Here's a fun problem.&lt;br /&gt;&lt;br /&gt;The function &lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_5RAO7k_azLU/SjfMnZMr4nI/AAAAAAAAAGU/a9_UZ9e5vCQ/s1600-h/gx.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 127px; height: 51px;" src="http://2.bp.blogspot.com/_5RAO7k_azLU/SjfMnZMr4nI/AAAAAAAAAGU/a9_UZ9e5vCQ/s400/gx.jpg" alt="" id="BLOGGER_PHOTO_ID_5347968059676811890" border="0" /&gt;&lt;/a&gt;gives a Bell curve. The function&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/SjfMnEWLJmI/AAAAAAAAAGE/UtUa_jW0fZw/s1600-h/fx.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 125px; height: 45px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/SjfMnEWLJmI/AAAAAAAAAGE/UtUa_jW0fZw/s400/fx.jpg" alt="" id="BLOGGER_PHOTO_ID_5347968054079465058" border="0" /&gt;&lt;/a&gt;gives a downward-opening parabola that fits exactly under the Bell curve, like so:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_5RAO7k_azLU/SjGZ07qZQbI/AAAAAAAAAF0/OHvhpaR9krI/s1600-h/graphs.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 321px; height: 196px;" src="http://4.bp.blogspot.com/_5RAO7k_azLU/SjGZ07qZQbI/AAAAAAAAAF0/OHvhpaR9krI/s400/graphs.jpg" alt="" id="BLOGGER_PHOTO_ID_5346223367313244594" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;In other words, &lt;span style="font-style: italic;"&gt;f&lt;/span&gt;(&lt;span style="font-style: italic;"&gt;x&lt;/span&gt;) is a lower boundary to &lt;span style="font-style: italic;"&gt;g&lt;/span&gt;(&lt;span style="font-style: italic;"&gt;x&lt;/span&gt;):&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_5RAO7k_azLU/SjfMnCpdEOI/AAAAAAAAAGM/jYyt3w6B6LM/s1600-h/fxlessgx.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 158px; height: 88px;" src="http://3.bp.blogspot.com/_5RAO7k_azLU/SjfMnCpdEOI/AAAAAAAAAGM/jYyt3w6B6LM/s400/fxlessgx.jpg" alt="" id="BLOGGER_PHOTO_ID_5347968053623460066" border="0" /&gt;&lt;/a&gt;How to go about proving this? Algebraically, simplifying the above doesn't do much. It turns out, though, that looking at the derivatives does prove this.&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_5RAO7k_azLU/SjfMm3a_qXI/AAAAAAAAAF8/VTinCcHXD6M/s1600-h/derivaties.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 210px; height: 174px;" src="http://4.bp.blogspot.com/_5RAO7k_azLU/SjfMm3a_qXI/AAAAAAAAAF8/VTinCcHXD6M/s400/derivaties.jpg" alt="" id="BLOGGER_PHOTO_ID_5347968050610022770" border="0" /&gt;&lt;/a&gt;Using the Chain Rule for compounded functions on &lt;span style="font-style: italic;"&gt;g&lt;/span&gt;(x) reveals the similarity between the two functions. Here's a graph of the two derivatives:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_5RAO7k_azLU/SjfQC-QS3jI/AAAAAAAAAG0/BxhHkP8oHbg/s1600-h/slopes.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 400px; height: 243px;" src="http://3.bp.blogspot.com/_5RAO7k_azLU/SjfQC-QS3jI/AAAAAAAAAG0/BxhHkP8oHbg/s400/slopes.jpg" alt="" id="BLOGGER_PHOTO_ID_5347971832015412786" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;On the lower right-hand side, quadrant IV, &lt;span style="font-style: italic;"&gt;f&lt;/span&gt;(&lt;span style="font-style: italic;"&gt;x&lt;/span&gt;) has a more negative slope than &lt;span style="font-style: italic;"&gt;g&lt;/span&gt;(&lt;span style="font-style: italic;"&gt;x&lt;/span&gt;), which is easy enough to prove:&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/SjfMuepytJI/AAAAAAAAAGk/1PfuwI6AQME/s1600-h/slopesright.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 243px; height: 115px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/SjfMuepytJI/AAAAAAAAAGk/1PfuwI6AQME/s400/slopesright.jpg" alt="" id="BLOGGER_PHOTO_ID_5347968181400155282" border="0" /&gt;&lt;/a&gt;On the upper left-hand side, quadrant II, f(x) has a more positive slope than g(x), which has virtually the same proof:&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_5RAO7k_azLU/SjfMnmk_WLI/AAAAAAAAAGc/OG5PJU-c8us/s1600-h/slopesleft.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 239px; height: 103px;" src="http://3.bp.blogspot.com/_5RAO7k_azLU/SjfMnmk_WLI/AAAAAAAAAGc/OG5PJU-c8us/s400/slopesleft.jpg" alt="" id="BLOGGER_PHOTO_ID_5347968063268411570" border="0" /&gt;&lt;/a&gt;(Just remember that the &lt;span style="font-style: italic;"&gt;x&lt;/span&gt;s in these inequalities are negative, so the inequality signs are flipped twice, back to their original position.)&lt;br /&gt;&lt;br /&gt;What does this prove? One final fact: at &lt;span style="font-style: italic;"&gt;x&lt;/span&gt; = 0, &lt;span style="font-style: italic;"&gt;f&lt;/span&gt;(0) = &lt;span style="font-style: italic;"&gt;g&lt;/span&gt;(0).&lt;br /&gt;&lt;br /&gt;As &lt;span style="font-style: italic;"&gt;x&lt;/span&gt; increases, the slope of &lt;span style="font-style: italic;"&gt;f&lt;/span&gt;(&lt;span style="font-style: italic;"&gt;x&lt;/span&gt;) is always more negative than the slope of &lt;span style="font-style: italic;"&gt;g&lt;/span&gt;(&lt;span style="font-style: italic;"&gt;x&lt;/span&gt;) -- they start equal at &lt;span style="font-style: italic;"&gt;x&lt;/span&gt; = 0, but &lt;span style="font-style: italic;"&gt;f&lt;/span&gt;(&lt;span style="font-style: italic;"&gt;x&lt;/span&gt;) decreases more rapidly, so &lt;span style="font-style: italic;"&gt;f&lt;/span&gt;(&lt;span style="font-style: italic;"&gt;x&lt;/span&gt;) must always be less than &lt;span style="font-style: italic;"&gt;g&lt;/span&gt;(&lt;span style="font-style: italic;"&gt;x&lt;/span&gt;) as &lt;span style="font-style: italic;"&gt;x&lt;/span&gt; increases. On the other side, the logic is simply reversed.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-7287062205193065184?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/7287062205193065184/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/06/neat-application-for-derivatives.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/7287062205193065184'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/7287062205193065184'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/06/neat-application-for-derivatives.html' title='A neat application for derivatives'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_5RAO7k_azLU/SjfMnZMr4nI/AAAAAAAAAGU/a9_UZ9e5vCQ/s72-c/gx.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-2584531289967511380</id><published>2009-04-26T10:45:00.007-04:00</published><updated>2009-06-20T11:27:18.193-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='debate tournaments'/><category scheme='http://www.blogger.com/atom/ns#' term='combinatorics'/><category scheme='http://www.blogger.com/atom/ns#' term='high school debate'/><title type='text'>Standard debate tournament calculations</title><content type='html'>I thought it might be useful to post a list of standard probability/counting methods for debate tournaments. I list them in order of rapidity of growth -- the last listed expands most quickly, but they all increase without bound. For all of these, there a &lt;span style="font-style: italic;"&gt;n&lt;/span&gt; teams at the tournament, and &lt;span style="font-style: italic;"&gt;n&lt;/span&gt; is an even number.&lt;br /&gt;&lt;br /&gt;First: once the teams have been separated into aff and neg pools, how many possible matches are there to consider?&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_5RAO7k_azLU/SfR0_DmgLLI/AAAAAAAAAFk/kGbIoS3SC5Q/s1600-h/pooled_+possible+matches.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 43px; height: 31px;" src="http://3.bp.blogspot.com/_5RAO7k_azLU/SfR0_DmgLLI/AAAAAAAAAFk/kGbIoS3SC5Q/s400/pooled_+possible+matches.jpg" alt="" id="BLOGGER_PHOTO_ID_5329012885733518514" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;Second: how many possible matches are there at a tournament, period? If you don't consider sides, then there are&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/SfR0-_-vb5I/AAAAAAAAAFU/5G0lxMtDA2g/s1600-h/all+possible+matches.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 55px; height: 43px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/SfR0-_-vb5I/AAAAAAAAAFU/5G0lxMtDA2g/s400/all+possible+matches.jpg" alt="" id="BLOGGER_PHOTO_ID_5329012884761440146" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;possible matches. If you did consider sides (A aff vs. B is counted as different than B aff vs. A), then are twice as many possible matches.&lt;br /&gt;&lt;br /&gt;Third: how many ways are there to separate the teams into aff and neg pools?&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_5RAO7k_azLU/SfR0_Jmg-TI/AAAAAAAAAFs/BqUmb92sl2o/s1600-h/possible+poolings.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 42px; height: 31px;" src="http://3.bp.blogspot.com/_5RAO7k_azLU/SfR0_Jmg-TI/AAAAAAAAAFs/BqUmb92sl2o/s400/possible+poolings.jpg" alt="" id="BLOGGER_PHOTO_ID_5329012887344183602" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;Fourth: once the teams have been separated into aff and neg pools, how many complete (perfect) &lt;span style="font-weight: bold;"&gt;pairings&lt;/span&gt; are possible?&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_5RAO7k_azLU/SfR0-3hIy_I/AAAAAAAAAFc/fMd_hgelOVA/s1600-h/pooled_+perfect+pairings.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 47px; height: 36px;" src="http://2.bp.blogspot.com/_5RAO7k_azLU/SfR0-3hIy_I/AAAAAAAAAFc/fMd_hgelOVA/s400/pooled_+perfect+pairings.jpg" alt="" id="BLOGGER_PHOTO_ID_5329012882489789426" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;This is the fastest growing number of all.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-2584531289967511380?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/2584531289967511380/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/04/standard-debate-tournament-calculations.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/2584531289967511380'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/2584531289967511380'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/04/standard-debate-tournament-calculations.html' title='Standard debate tournament calculations'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_5RAO7k_azLU/SfR0_DmgLLI/AAAAAAAAAFk/kGbIoS3SC5Q/s72-c/pooled_+possible+matches.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-3507538392576008279</id><published>2009-04-24T08:25:00.013-04:00</published><updated>2011-03-05T21:06:01.323-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Pascal&apos;s triangle'/><category scheme='http://www.blogger.com/atom/ns#' term='infinite series'/><category scheme='http://www.blogger.com/atom/ns#' term='combinatorics'/><category scheme='http://www.blogger.com/atom/ns#' term='convergence'/><title type='text'>Pascal's triangle: a neat proof</title><content type='html'>There is an interesting question about how the terms in Pascal's triangle grow. All the terms in a row obviously grow (except the 1s at the extreme left- and right-hand sides of the triangle), but the rows' totals obviously grow, too. Do any of the terms in a row converge, as a percentage of the total of the row?&lt;br /&gt;&lt;br /&gt;The most interesting example is the middle term in a row, e.g.:&lt;br /&gt;&lt;br /&gt;&lt;div style="text-align: center;"&gt;&lt;span style="font-weight: bold; color: rgb(255, 0, 0);"&gt;1&lt;/span&gt;&lt;br /&gt;1    1&lt;br /&gt;1    &lt;span style="font-weight: bold; color: rgb(255, 0, 0);"&gt;2&lt;/span&gt;    1&lt;br /&gt;&lt;/div&gt;&lt;br /&gt;the 1 and 2 are middle terms for their respective rows. The middle term is always the largest term and grows quickly. So, which grows faster: the row total or its middle term, or is there a convergence? A few examples illustrate what happens:&lt;br /&gt;&lt;br /&gt;The 0th row -- 100%&lt;br /&gt;The 2nd row -- 50%&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_5RAO7k_azLU/SfGzoPwHvxI/AAAAAAAAAFE/WRPxRI0pElw/s1600-h/examples.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 141px; height: 216px;" src="http://3.bp.blogspot.com/_5RAO7k_azLU/SfGzoPwHvxI/AAAAAAAAAFE/WRPxRI0pElw/s400/examples.jpg" alt="" id="BLOGGER_PHOTO_ID_5328237338160512786" border="0" /&gt;&lt;/a&gt;The numerator is the formula for the middle term (see the &lt;a href="http://en.wikipedia.org/wiki/Binomial_distribution"&gt;binomial distribution&lt;/a&gt;); the denominator is the row's total. The largest row that my TI-84 calculator could handle before overflowing is the 332nd. As the examples show, the denominator is "winning" -- the middle term as a percentage of the total is steadily decreasing. Pretty amazing considering just how big the middle term is; for the 332nd row, the numerator is 3.8E98!&lt;br /&gt;&lt;br /&gt;Can we write a proof of this? Certainly. The first step is to re-write the numerator. Given that the combination is really a simplification of&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_5RAO7k_azLU/SfGyOw1XcvI/AAAAAAAAAEk/hL27lDaTRq4/s1600-h/algebra1.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 94px; height: 51px;" src="http://2.bp.blogspot.com/_5RAO7k_azLU/SfGyOw1XcvI/AAAAAAAAAEk/hL27lDaTRq4/s400/algebra1.jpg" alt="" id="BLOGGER_PHOTO_ID_5328235800852656882" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;so, our specific numerator can be re-written as:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_5RAO7k_azLU/SfGyOxwjYpI/AAAAAAAAAEs/OvdVHcpixbw/s1600-h/algebra2.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 116px; height: 50px;" src="http://2.bp.blogspot.com/_5RAO7k_azLU/SfGyOxwjYpI/AAAAAAAAAEs/OvdVHcpixbw/s400/algebra2.jpg" alt="" id="BLOGGER_PHOTO_ID_5328235801100903058" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;To re-write the limit for our whole expression, the middle term divided by the row total, would look like this:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_5RAO7k_azLU/SfGyPEpD57I/AAAAAAAAAE0/cXvTk2OouCQ/s1600-h/proof1.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 130px; height: 54px;" src="http://3.bp.blogspot.com/_5RAO7k_azLU/SfGyPEpD57I/AAAAAAAAAE0/cXvTk2OouCQ/s400/proof1.jpg" alt="" id="BLOGGER_PHOTO_ID_5328235806169753522" border="0" /&gt;&lt;/a&gt;Now the clever step. Let's re-organize that &lt;span style="font-style: italic;"&gt;n&lt;/span&gt; factorial in the numerator and expand the terms in the denominator:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/Sj0CIxDKfsI/AAAAAAAAAG8/MIwXWKO9p9Q/s1600-h/firstexpansion.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 253px; height: 60px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/Sj0CIxDKfsI/AAAAAAAAAG8/MIwXWKO9p9Q/s400/firstexpansion.jpg" alt="" id="BLOGGER_PHOTO_ID_5349434282014834370" border="0" /&gt;&lt;/a&gt;All the &lt;span style="font-style: italic;"&gt;n&lt;/span&gt; factorial terms are there; they just been re-organized, with the even terms on one side and the odd terms on the other. It should make sense that the terms in the numerator "sit" perfectly in the "seats" provided by the denominator: there are &lt;span style="font-style: italic;"&gt;n&lt;/span&gt; terms in the numerator, and there are two groups of &lt;span style="font-style: italic;"&gt;n&lt;/span&gt;/2 terms in the denominator.&lt;br /&gt;&lt;br /&gt;The proof is basically done. One simple re-write makes the final conclusion clear:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_5RAO7k_azLU/Sj0CJHnr3kI/AAAAAAAAAHE/YmQ1RnNLkDM/s1600-h/secondexpansion.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 222px; height: 78px;" src="http://3.bp.blogspot.com/_5RAO7k_azLU/Sj0CJHnr3kI/AAAAAAAAAHE/YmQ1RnNLkDM/s400/secondexpansion.jpg" alt="" id="BLOGGER_PHOTO_ID_5349434288073596482" border="0" /&gt;&lt;/a&gt;Each fraction is now on its own. The first set of fractions are all 1s. Every other fraction must be less than 1. An infinite multiplication of fractions less than or equal to 1 must converge to 0. So, in an infinite Pascal's triangle, the middle term, although it increases without bound, is 0% of the row's total.&lt;br /&gt;&lt;br /&gt;---&lt;br /&gt;&lt;br /&gt;The above paragraph is incorrect. A lot more work must be done to show that the product of the remaining fractions&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/-2gMwMQTY4XM/TXLk-EEFSVI/AAAAAAAAANA/EWzmH9UIzgQ/s1600/eq1.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 151px; height: 75px;" src="http://2.bp.blogspot.com/-2gMwMQTY4XM/TXLk-EEFSVI/AAAAAAAAANA/EWzmH9UIzgQ/s320/eq1.jpg" alt="" id="BLOGGER_PHOTO_ID_5580774643159353682" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;goes to zero. I like explanations that just make intuitive sense. So, the first term is 0.5. I noticed that the product of the next four terms (terms two to five) is slightly less than 0.5. A little cancelation helps make why clear:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/-ShRH5pAvzEQ/TXLlDUbItkI/AAAAAAAAANI/UjNB2oMfhHA/s1600/eq2.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 132px; height: 61px;" src="http://2.bp.blogspot.com/-ShRH5pAvzEQ/TXLlDUbItkI/AAAAAAAAANI/UjNB2oMfhHA/s320/eq2.jpg" alt="" id="BLOGGER_PHOTO_ID_5580774733450360386" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;Thus:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/-Ib74y76gePA/TXLlL-JZz_I/AAAAAAAAANQ/RDWthvJey0g/s1600/eq3.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 83px; height: 63px;" src="http://1.bp.blogspot.com/-Ib74y76gePA/TXLlL-JZz_I/AAAAAAAAANQ/RDWthvJey0g/s320/eq3.jpg" alt="" id="BLOGGER_PHOTO_ID_5580774882089226226" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;And this continues. The product of the next sixteen terms (terms six to twenty-one) is also less than 0.5. Here are the terms:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/-MsdxaSs83c4/TXLlgI-crBI/AAAAAAAAANo/_Jr8FhumMu4/s1600/eq6.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 368px; height: 48px;" src="http://1.bp.blogspot.com/-MsdxaSs83c4/TXLlgI-crBI/AAAAAAAAANo/_Jr8FhumMu4/s320/eq6.jpg" alt="" id="BLOGGER_PHOTO_ID_5580775228593450002" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;A litte cancelation starts the process:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/-IsE_a3Yn8MI/TXLln-jW19I/AAAAAAAAANw/zaaxR-EBU-Y/s1600/eq7.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 345px; height: 36px;" src="http://2.bp.blogspot.com/-IsE_a3Yn8MI/TXLln-jW19I/AAAAAAAAANw/zaaxR-EBU-Y/s320/eq7.jpg" alt="" id="BLOGGER_PHOTO_ID_5580775363234420690" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;and reorganizing the denominators makes the result clear:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/-CeLUpEHozZg/TXLlsBRZ92I/AAAAAAAAAN4/62etP6uV1Vk/s1600/eq8.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 46px;" src="http://2.bp.blogspot.com/-CeLUpEHozZg/TXLlsBRZ92I/AAAAAAAAAN4/62etP6uV1Vk/s320/eq8.jpg" alt="" id="BLOGGER_PHOTO_ID_5580775432683911010" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;Each pair of terms is slightly less than one. Each pair of terms can be written in the form:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/-sNHdn0SpEfo/TXLlRSxeK9I/AAAAAAAAANY/UcOYWX5yBDc/s1600/eq4.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 120px; height: 60px;" src="http://4.bp.blogspot.com/-sNHdn0SpEfo/TXLlRSxeK9I/AAAAAAAAANY/UcOYWX5yBDc/s320/eq4.jpg" alt="" id="BLOGGER_PHOTO_ID_5580774973525339090" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;or&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/-l4qGJ03Xb68/TXLlXe3PuKI/AAAAAAAAANg/la59DoPh3JI/s1600/eq5.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 58px; height: 45px;" src="http://1.bp.blogspot.com/-l4qGJ03Xb68/TXLlXe3PuKI/AAAAAAAAANg/la59DoPh3JI/s320/eq5.jpg" alt="" id="BLOGGER_PHOTO_ID_5580775079849998498" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;The product of the next 64 terms is also less than 0.5. (The number of terms is based on powers of 4.) So, the whole product can be rewritten as 0.5^infinity... that definitely goes to zero.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-3507538392576008279?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/3507538392576008279/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/04/pascals-triangle-neat-proof.html#comment-form' title='17 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/3507538392576008279'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/3507538392576008279'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/04/pascals-triangle-neat-proof.html' title='Pascal&apos;s triangle: a neat proof'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_5RAO7k_azLU/SfGzoPwHvxI/AAAAAAAAAFE/WRPxRI0pElw/s72-c/examples.jpg' height='72' width='72'/><thr:total>17</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-2817632174130580323</id><published>2009-04-21T17:09:00.006-04:00</published><updated>2009-05-05T09:47:36.412-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='breaks'/><category scheme='http://www.blogger.com/atom/ns#' term='debate tournaments'/><category scheme='http://www.blogger.com/atom/ns#' term='Pascal&apos;s triangle'/><category scheme='http://www.blogger.com/atom/ns#' term='high school debate'/><category scheme='http://www.blogger.com/atom/ns#' term='brackets'/><title type='text'>Pascal's triangle and brackets</title><content type='html'>As many debate coaches and competitors already know, because teams are always power-matching within brackets against opponents with the same record, it is possible to construct a simple branching diagram to predict how many teams are in each bracket, like so:&lt;br /&gt;&lt;br /&gt;&lt;div style="text-align: center;"&gt;100&lt;br /&gt;50    50&lt;br /&gt;25    50    25&lt;br /&gt;&lt;/div&gt;&lt;br /&gt;and so on. What they may not realize is the connection to &lt;a href="http://en.wikipedia.org/wiki/Pascal%27s_triangle"&gt;Pascal's triangle&lt;/a&gt;, a famous problem in mathematics:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_5RAO7k_azLU/Se426XWp-YI/AAAAAAAAAEE/BAMION8Yl2g/s1600-h/pascal_tri.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 325px; height: 191px;" src="http://3.bp.blogspot.com/_5RAO7k_azLU/Se426XWp-YI/AAAAAAAAAEE/BAMION8Yl2g/s400/pascal_tri.jpg" alt="" id="BLOGGER_PHOTO_ID_5327255785555229058" border="0" /&gt;&lt;/a&gt;Here are the first nine rows. Each number in a row is created by adding the two numbers in the row above, the number diagonally left and the number diagonally right. The numbers in each row can easily be turned into percentages by dividing a number by the total of the row. For example, in row one, 1/1 is 100%; in row two, 1/2 is 50%; in row three, 1/4 is 25%. As you might have noticed, the total for each row is always 2^(&lt;span style="font-style: italic;"&gt;n&lt;/span&gt;-1), where &lt;span style="font-style: italic;"&gt;n&lt;/span&gt; is the row number. (There's also a &lt;a href="http://en.wikipedia.org/wiki/Binomial_expansion"&gt;shortcut&lt;/a&gt; for finding the numbers in the rows.)&lt;br /&gt;&lt;br /&gt;Once everything has been converted into a percentage, it can be organized in a more easy-to-read chart:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/Se426diPE8I/AAAAAAAAAEM/3Apb7ejcF_g/s1600-h/percent_brackets.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 326px; height: 78px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/Se426diPE8I/AAAAAAAAAEM/3Apb7ejcF_g/s400/percent_brackets.jpg" alt="" id="BLOGGER_PHOTO_ID_5327255787214410690" border="0" /&gt;&lt;/a&gt;Of course, some of these percentages are overly precise for a debate tournament. The percentages never quite work out exactly because of pull ups caused by uneven numbered brackets, side constraints, team constraints, etc. I always use the exact percentage to multiply by the number of teams at the tournament -- but I am never surprised by +/- 1 or even 2 teams off the prediction. Still, it can be a simple way to estimate the number of teams in each bracket, especially at a very large tournament where the constraints will have less effect. I've looked at the data from large tournaments before and found that the bracket size predictions were within a percentage point. That estimation is useful to estimate the number of teams that could break:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/Se426jMu6tI/AAAAAAAAAEU/gveVdthMZV8/s1600-h/percent_breaking.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 400px; height: 74px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/Se426jMu6tI/AAAAAAAAAEU/gveVdthMZV8/s400/percent_breaking.jpg" alt="" id="BLOGGER_PHOTO_ID_5327255788734835410" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;The left two columns show the percentages of teams with a winning record (excluding those with a 50-50% win-loss record) after various even numbers of rounds. The middle columns show the percentage of teams with winning records after various odd numbers of rounds -- always 50%. The right-most column shows the percentages of teams with winning records excluding the worst winning bracket (i.e., excluding 2-1s after three rounds, 3-2s after five rounds, and 4-3s after seven rounds).&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-2817632174130580323?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/2817632174130580323/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/04/pascals-triangle-and-brackets.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/2817632174130580323'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/2817632174130580323'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/04/pascals-triangle-and-brackets.html' title='Pascal&apos;s triangle and brackets'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_5RAO7k_azLU/Se426XWp-YI/AAAAAAAAAEE/BAMION8Yl2g/s72-c/pascal_tri.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-1806686179980922900</id><published>2009-04-18T10:57:00.003-04:00</published><updated>2009-04-18T11:35:07.104-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='debate tournaments'/><category scheme='http://www.blogger.com/atom/ns#' term='high school debate'/><category scheme='http://www.blogger.com/atom/ns#' term='partial elimination round'/><title type='text'>Partial elimination round calculator</title><content type='html'>I'm a big believer that every team at a debate tournament with a winning record should make it to elimination rounds. (Or, if this is simply impossible, break every team with a certain record, e.g. all 5-2s and no 4-3s. That only seems fair; breaking some 5-2s on speaker points, but not other 5-2s, places too much trust in the objectivity of speaker points.)&lt;br /&gt;&lt;br /&gt;Of course, the problem is that breaking every team in a certain bracket creates the need to run a partial elimination round (because how often will a tournament need to break exactly 2^&lt;span style="font-style: italic;"&gt;n&lt;/span&gt; teams?). The logistics of a partial elimination round can seem a bit unpredictable at first -- how many teams will need to be in the partial? how many judges will be needed? -- so I created a "partials calculator" to help &lt;span style="font-weight: bold;"&gt;estimate&lt;/span&gt; answers to these questions: &lt;a href="http://www.mediafire.com/?tmtrnmqtnzu"&gt;http://www.mediafire.com/?tmtrnmqtnzu&lt;/a&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;&lt;br /&gt;&lt;/span&gt;A few notes about the calculator. I set it up with a default of 34% of teams breaking, a good assumption for the percentage of 4-2s or better, but this value can be changed in the green box. I also set up a default of one judge per two teams in the single-flighted event and one judge per three teams in the double-flighted event, although these values can also be changed in their green boxes.&lt;br /&gt;&lt;br /&gt;The yellow highlighted boxes show when a tournament will need extra elim judges. For example, in the single-flighted event, there are very few situations where the tournament would need extra elim judges -- the most significant troubles are in the 100s-110s, where the tournament might be short 10 judges. Otherwise, there are few problems.&lt;br /&gt;&lt;br /&gt;The double-flighted event shows two options: (a) single-flight the partial and double-flight the first elim round, or (b) double-flight the partial and single-flight the first full elim. Requiring one judge for three teams is a crucial value; there will enough judges in almost every case to single-flight one (or both) of these two rounds.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-1806686179980922900?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/1806686179980922900/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/04/im-big-believer-that-every-team-at.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/1806686179980922900'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/1806686179980922900'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/04/im-big-believer-that-every-team-at.html' title='Partial elimination round calculator'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-4216763639674394306</id><published>2009-04-15T10:10:00.002-04:00</published><updated>2009-04-15T10:12:19.534-04:00</updated><title type='text'>Side assignment algorithm</title><content type='html'>The PDF contains a description the &lt;a href="http://www.mediafire.com/?tyyzq3d1jjt"&gt;side assignment algorithm&lt;/a&gt; that I found.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-4216763639674394306?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/4216763639674394306/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/04/side-assignment-algorithm.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/4216763639674394306'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/4216763639674394306'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/04/side-assignment-algorithm.html' title='Side assignment algorithm'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-6543930019759617314</id><published>2009-04-08T11:47:00.008-04:00</published><updated>2009-04-08T12:41:09.650-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='debate tournaments'/><category scheme='http://www.blogger.com/atom/ns#' term='side constraints'/><category scheme='http://www.blogger.com/atom/ns#' term='algorithm'/><category scheme='http://www.blogger.com/atom/ns#' term='tabulation program'/><title type='text'>Side assignment algorithm found!</title><content type='html'>One of the most vexing problems in running a small tournament is assigning sides in odd rounds. If you assign the sides incorrectly in an odd round, there may be nothing but bad options left for the subsequent even round: break side constraints (a team is aff. rounds 3 and 4), break school constraints (force two teams from the same school to debate), or re-match two teams (two teams that have already met have to debate again).&lt;br /&gt;&lt;br /&gt;For a round robin, there are very few possible solution in the third to last round. Say you have 8 teams, so before round 5 is paired, team A has three opponents remaining: B, C, and D. If A is assigned to the aff, then 2/3 of {B, C, and D} must be assigned to the neg side -- otherwise, it will be impossible to honor side constraints for rounds 5 and 6. This sounds easy until you realize that B, C, and D all have three opponents each remaining, 2/3 of whom must be assigned to the opposite side... There ends up being just a few ways to pair round 5 that are consistent with all side constraints and re-match constraints for round 6 too.&lt;br /&gt;&lt;br /&gt;The complexity of this problem has lead tab programs to include a "schedule round robin" option that executes before any rounds have happened at all. Although round robins are the epitome of this problem, many small tournaments with heavy school constraints (many teams from the same school) also experience it, leading to late round pairings that violate many constraints -- and there's no option yet programmed that solves that. Even big tournaments suffer from a similar problem. Although there's no risk of a big tournament violating any constraints, there is always the question of how well mixed a tournament is. If the same group of teams always is aff in odd rounds {A, B, C, D, E...}, then there's no chance that A can debate B, B debate C, etc. The tournament is better mixed if round 1 affs are {A, B, C, D, E...} and round 3 affs are {A, C, E...} and so on. The current assumption is that randomness is sufficient to mix a tournament well, which might be true, but it's nice to have an algorithm in hand that guarantees that.&lt;br /&gt;&lt;br /&gt;Now, you may be tempted to think that a computer program can solve this sequentially: pair round 3, then have it look ahead to round 4 and see if there are any problems. This may just work at a tiny tournament, but the number of possibilities becomes daunting quickly, before becoming downright impossible, even for a supercomputer (and I don't believe many tab rooms would want to book time on the Roadrunner supercomputer). If you set a pairing for round 3, then look at all the possible round 4 options that follow, there are (&lt;span style="font-style: italic;"&gt;n&lt;/span&gt;/2)! options, where &lt;span style="font-style: italic;"&gt;n&lt;/span&gt; = number of teams. For 40 teams, there are 2.43 E 18 options. The world's fastest computer, by my rough estimation, would take 37 minutes to verify that all the options for round 4 were bad. To put it in perspective, 2.43 E 18 is about how many stars we can see in the sky. There is a better way, and it's to do a clever simultaneous approach.&lt;br /&gt;&lt;br /&gt;Here's the gist of what I found. The mixing issue and the constraints issue are actually two sides of the same coin. If in round 1 team A aff. defeats team B neg., and in round 2 team B aff. defeats C neg., then the computer should be able to reject several possible side assignments out of hand. The best mixed, least conflicted option is actually to put {A, B, C} on the aff. for round 3. A and B can't debate again, so they might as well be on the same side; ditto for B and C. The only possible round that's lost is A vs. C, but any other way to assign the sides rules out more possible rounds. A smart use of this fact enables the algorithm to quickly toss out many possible options and reduce it to a manageable number.&lt;br /&gt;&lt;br /&gt;Does the algorithm actually work? Yes. I tested it on a regular laptop, and it will pair a round robin on the fly. Without giving the program any prior knowledge that a tournament will be a round robin, it just picks the best round each time in a few seconds -- and pairs the round robin correctly and completely. The algorithm itself is not complex, but I'll go into it in a later post.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-6543930019759617314?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/6543930019759617314/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/04/side-assignment-algorithm-found.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/6543930019759617314'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/6543930019759617314'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/04/side-assignment-algorithm-found.html' title='Side assignment algorithm found!'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-6400764188955500914</id><published>2009-04-02T15:42:00.006-04:00</published><updated>2009-12-08T13:44:40.545-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='co-functions'/><category scheme='http://www.blogger.com/atom/ns#' term='tangents'/><category scheme='http://www.blogger.com/atom/ns#' term='trigonometric identities'/><category scheme='http://www.blogger.com/atom/ns#' term='trigonometry'/><category scheme='http://www.blogger.com/atom/ns#' term='slope'/><title type='text'>Neat proofs with tangents and slopes</title><content type='html'>Spring break is over, and it's time to do some math again!&lt;br /&gt;&lt;br /&gt;Let's say you have two lines, &lt;span style="font-style: italic;"&gt;y&lt;/span&gt;1 and &lt;span style="font-style: italic;"&gt;y&lt;/span&gt;2, with unknown slopes. However, you do know that &lt;span style="font-style: italic;"&gt;y&lt;/span&gt;1 is perpendicular to &lt;span style="font-style: italic;"&gt;y&lt;/span&gt;2, like so:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_5RAO7k_azLU/SdUZQeRjNDI/AAAAAAAAAD0/HvhdxdXBbfo/s1600-h/image.png"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 277px; height: 189px;" src="http://4.bp.blogspot.com/_5RAO7k_azLU/SdUZQeRjNDI/AAAAAAAAAD0/HvhdxdXBbfo/s400/image.png" alt="" id="BLOGGER_PHOTO_ID_5320186305603384370" border="0" /&gt;&lt;/a&gt;Without invoking the triangle sum, how can you prove two marked angles are complementary? With a simple use of the co-function.&lt;br /&gt;&lt;br /&gt;If angles &lt;span style="font-style: italic;"&gt;a&lt;/span&gt; and &lt;span style="font-style: italic;"&gt;b&lt;/span&gt; are complementary, then &lt;span style="font-style: italic;"&gt;a&lt;/span&gt; + &lt;span style="font-style: italic;"&gt;b&lt;/span&gt; = 90, and 90 - &lt;span style="font-style: italic;"&gt;a&lt;/span&gt; = &lt;span style="font-style: italic;"&gt;b&lt;/span&gt;.&lt;br /&gt;&lt;br /&gt;The co-function of tangent is co-tangent: cot (90 - &lt;span style="font-style: italic;"&gt;a&lt;/span&gt;) = tan (&lt;span style="font-style: italic;"&gt;a&lt;/span&gt;)*, so cot (&lt;span style="font-style: italic;"&gt;b&lt;/span&gt;) = tan (&lt;span style="font-style: italic;"&gt;a&lt;/span&gt;) if &lt;span style="font-style: italic;"&gt;a&lt;/span&gt; and &lt;span style="font-style: italic;"&gt;b&lt;/span&gt; are complementary. Is that true? To see, a few more labels help.&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_5RAO7k_azLU/SdUZRDzvywI/AAAAAAAAAD8/R5HNnKG6pgc/s1600-h/image2.png"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 281px; height: 196px;" src="http://3.bp.blogspot.com/_5RAO7k_azLU/SdUZRDzvywI/AAAAAAAAAD8/R5HNnKG6pgc/s400/image2.png" alt="" id="BLOGGER_PHOTO_ID_5320186315678927618" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Cot (&lt;span style="font-style: italic;"&gt;b&lt;/span&gt;) is just &lt;span style="font-style: italic;"&gt;x&lt;/span&gt;2/&lt;span style="font-style: italic;"&gt;h&lt;/span&gt;, and tan (&lt;span style="font-style: italic;"&gt;a&lt;/span&gt;) is just &lt;span style="font-style: italic;"&gt;h&lt;/span&gt;/&lt;span style="font-style: italic;"&gt;x&lt;/span&gt;1. So, is &lt;span style="font-style: italic;"&gt;x&lt;/span&gt;2/&lt;span style="font-style: italic;"&gt;h&lt;/span&gt; = &lt;span style="font-style: italic;"&gt;h&lt;/span&gt;/&lt;span style="font-style: italic;"&gt;x&lt;/span&gt;1? You bet -- the slope of lines are (negative) reciprocals of each other.&lt;br /&gt;&lt;br /&gt;* Proving co-functions is simple. Starting with the unit circle:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_5RAO7k_azLU/Sx6cnhrNMeI/AAAAAAAAAKM/ddOncewEDug/s1600-h/unit+circle.png"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 267px;" src="http://4.bp.blogspot.com/_5RAO7k_azLU/Sx6cnhrNMeI/AAAAAAAAAKM/ddOncewEDug/s320/unit+circle.png" alt="" id="BLOGGER_PHOTO_ID_5412936005014335970" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;The coordinates of (&lt;span style="font-style: italic;"&gt;x&lt;/span&gt;, &lt;span style="font-style: italic;"&gt;y&lt;/span&gt;) = (cos (&lt;span style="font-style: italic;"&gt;a&lt;/span&gt;), sin (&lt;span style="font-style: italic;"&gt;a&lt;/span&gt;)). However, if you begin at (1, 0) and move clockwise (therefore, an angle of 90 - &lt;span style="font-style: italic;"&gt;a&lt;/span&gt;), the points are a mirror image reflected over the &lt;span style="font-style: italic;"&gt;y&lt;/span&gt; = &lt;span style="font-style: italic;"&gt;x&lt;/span&gt; line of those before, and therefore (&lt;span style="font-style: italic;"&gt;y&lt;/span&gt;, &lt;span style="font-style: italic;"&gt;x&lt;/span&gt;) = (cos(90 - &lt;span style="font-style: italic;"&gt;a&lt;/span&gt;), sin(90 - &lt;span style="font-style: italic;"&gt;a&lt;/span&gt;). This defines the basic co-functions: &lt;span style="font-style: italic;"&gt;x&lt;/span&gt; = cos(&lt;span style="font-style: italic;"&gt;a&lt;/span&gt;) = sin(90 - &lt;span style="font-style: italic;"&gt;a&lt;/span&gt;), &lt;span style="font-style: italic;"&gt;y&lt;/span&gt; = sin(&lt;span style="font-style: italic;"&gt;a&lt;/span&gt;) = cos(90 - &lt;span style="font-style: italic;"&gt;a&lt;/span&gt;). And it follows that cot(90 - &lt;span style="font-style: italic;"&gt;a&lt;/span&gt;) = cos(90 - &lt;span style="font-style: italic;"&gt;a&lt;/span&gt;)/sin(90 - &lt;span style="font-style: italic;"&gt;a&lt;/span&gt;) = sin(&lt;span style="font-style: italic;"&gt;a&lt;/span&gt;)/cos(&lt;span style="font-style: italic;"&gt;a&lt;/span&gt;) = tan(&lt;span style="font-style: italic;"&gt;a&lt;/span&gt;).&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-6400764188955500914?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/6400764188955500914/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/04/neat-proofs-with-tangents-and-slopes.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/6400764188955500914'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/6400764188955500914'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/04/neat-proofs-with-tangents-and-slopes.html' title='Neat proofs with tangents and slopes'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_5RAO7k_azLU/SdUZQeRjNDI/AAAAAAAAAD0/HvhdxdXBbfo/s72-c/image.png' height='72' width='72'/><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-1077943923975023712</id><published>2009-03-22T19:14:00.012-04:00</published><updated>2009-03-24T13:57:12.986-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='debate tournaments'/><category scheme='http://www.blogger.com/atom/ns#' term='high school debate'/><category scheme='http://www.blogger.com/atom/ns#' term='schedule strength'/><category scheme='http://www.blogger.com/atom/ns#' term='opponent wins'/><title type='text'>Strength of schedule pairings work!</title><content type='html'>I created a new power matching method, a "strength-of-schedule" (S-o-S) power matching method. This method was used to run a hypothetical tournament, to compare the results to an actual tournament. (Thanks to Orion and Joe for the idea of running a hypothetical tournament.)&lt;br /&gt;&lt;br /&gt;A major (180+ teams) 2008 national debate tournament was the point of comparison. The actual results of the seven preliminary rounds were available online. For the hypothetical tournament, round 1 used the same pre-set matches and results as the actual tournament. Round 2 and every subsequent even round used the strength-of-schedule power matching method: teams who had had good opponents so far faced the weaker ones in their bracket; teams who had had weak opponents so far faced the stronger ones in their bracket. Round 3 and every subsequent odd round used the traditional, high/low power matching method in TRPC. Once the pairing for a round was set, a "ballot" was entered for every debate. If the teams had met at the actual tournament, the real results were entered. If the teams had not met, each side received the speaker points they had earned in their respective debates for that round (against different opponents) at the actual tournament, and the winner was determined using the final rankings from the actual tournament (the higher ranking team won). Then, I power-matched then next round. Thus, the hypothetical tournament results were meant to replicate the actual tournament results as closely as possible, without bringing in any info that wouldn't have been available to a tab director during the tournament.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;And the results are...&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;First, the strength-of-schedule power matching method generated only the correct, minimum number of pull-ups. Teams pulled up were always those with the weakest opposition record in their bracket. Otherwise, all teams were correctly paired within their brackets.&lt;br /&gt;&lt;br /&gt;Second, the results from the hypothetical tournament closely matched those of the actual tournament. Of the 32 teams that made it into elimination rounds at the actual tournament, 30 of them would have made it into elimination rounds at the hypothetical tournament. (At the actual tournament, there was a four-way speaker point tie for 31st place, broken on opponent wins. The 30th and 32nd place teams at the actual tournament had different opponents — and lower opponent wins — at the hypothetical tournament and dropped below the threshold.)&lt;br /&gt;&lt;br /&gt;Third, and most important, in every bracket except the 7-0s, the hypothetical tournament using the strength-of-schedule power matching method had &lt;span style="font-style: italic;"&gt;narrower&lt;/span&gt; ranges for opponent wins and &lt;span style="font-style: italic;"&gt;smaller&lt;/span&gt; standard deviations for opponent wins:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/ScbHyWCfv6I/AAAAAAAAADc/pwHNZu1H3DM/s1600-h/results.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 390px; height: 104px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/ScbHyWCfv6I/AAAAAAAAADc/pwHNZu1H3DM/s400/results.jpg" alt="" id="BLOGGER_PHOTO_ID_5316156077880885154" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;(With so few 7-0s, the addition of one outlier made a large impact. This is not the most revealing statistic.) The range for opponent wins for 6-1s at the actual tournament was nine, but four for the hypothetical tournament. That standard deviation was nearly halved. The range for 5-2s decreased from 15 to seven. The range for 4-3s decreased from 15 to ten.&lt;br /&gt;&lt;br /&gt;Another telling statistic is the comparison for the top 32 teams at the actual and the top 32 teams at the hypothetical tournament:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_5RAO7k_azLU/ScbHy7gPbKI/AAAAAAAAADk/OhAtRu58U-4/s1600-h/results2.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 273px; height: 120px;" src="http://3.bp.blogspot.com/_5RAO7k_azLU/ScbHy7gPbKI/AAAAAAAAADk/OhAtRu58U-4/s400/results2.jpg" alt="" id="BLOGGER_PHOTO_ID_5316156087937756322" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;The ranges were the same, but the standard deviation was far lower at the hypothetical tournament, meaning that more of the data points were closer to the mean opponent wins. The middle 94% of the top 32 teams, eliminating the highest and lowest outlier, is even more telling. The range for the actual tournament, even eliminating the outliers, was still 12; the range for the hypothetical tournament dropped to eight. You can see that the standard deviation is nearly one opponent win lower.&lt;br /&gt;&lt;br /&gt;The bottom line is, it worked. There was nothing in the process that required human judgment or that would be difficult to do in a computer program:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;Retrieve the relevant statistics from the tabulation program.&lt;/li&gt;&lt;li&gt;Assign byes.&lt;/li&gt;&lt;li&gt;Calculate the z-scores of a team's strength and its opponents' strength.&lt;/li&gt;&lt;li&gt;Populate an optimization matrix.&lt;/li&gt;&lt;li&gt;Solve the optimization matrix using the Hungarian algorithm.&lt;/li&gt;&lt;li&gt;Feed the solution back into the tabulation program as the next round’s pairings.&lt;/li&gt;&lt;/ol&gt;Alternatively, the new power-matching algorithm could be written into an existing tabulation program, eliminating steps 1 and 6.&lt;br /&gt;&lt;br /&gt;Read the full paper for a description of the method I used: &lt;a href="http://www.mediafire.com/?0wymlzdzwoz"&gt;http://www.mediafire.com/?0wymlzdzwoz&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;And here's the Java code for the Hungarian algorithm I used: &lt;a href="http://www.mediafire.com/?y3nqjtmnim2"&gt;http://www.mediafire.com/?y3nqjtmnim2&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-1077943923975023712?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/1077943923975023712/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/03/strength-of-schedule-pairings-work.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/1077943923975023712'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/1077943923975023712'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/03/strength-of-schedule-pairings-work.html' title='Strength of schedule pairings work!'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/_5RAO7k_azLU/ScbHyWCfv6I/AAAAAAAAADc/pwHNZu1H3DM/s72-c/results.jpg' height='72' width='72'/><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-7533855679338316704</id><published>2009-03-15T15:28:00.012-04:00</published><updated>2009-03-23T17:39:40.333-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='debate tournaments'/><category scheme='http://www.blogger.com/atom/ns#' term='high school debate'/><category scheme='http://www.blogger.com/atom/ns#' term='schedule strength'/><category scheme='http://www.blogger.com/atom/ns#' term='opponent wins'/><title type='text'>Strength of schedule pairings</title><content type='html'>This is a comparison of running a debate tournament in two different ways. In the left column are the results are from a tournament I helped to run, using the traditional high-low power-matching methods. In the right column are the results from re-running the exact same tournament using my strength of schedule power-matching method. (Specifically, round 1 is the same random pre-set as the original tournament; round 3 uses a traditional high-low power-match; but for rounds 2 and 4 I used my strength of schedule pairing. For each hypothetical round, i.e., every round after round 1, I referred to the actual rankings to determine the winner). Here's the comparison:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_5RAO7k_azLU/Sb1b_PgYBnI/AAAAAAAAADU/lIHMcCcYT7o/s1600-h/comparison.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 158px; height: 416px;" src="http://4.bp.blogspot.com/_5RAO7k_azLU/Sb1b_PgYBnI/AAAAAAAAADU/lIHMcCcYT7o/s400/comparison.jpg" alt="" id="BLOGGER_PHOTO_ID_5313504277419263602" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;Download the Excel workbook: &lt;a href="http://www.mediafire.com/?lanmmnnmlmn"&gt;http://www.mediafire.com/?lanmmnnmlmn&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;As you can see, the groupings are tighter for 3-1s (now a range from 9 to 6) and 2-2s (now from 9 to 6). What is tougher to see is that for the 3-1s, the standard deviation of opponent wins was cut by 33%, from 1.55 to 1.00, and for the 2-2s, the standard deviation of opponent wins was cut by nearly 50%, from 1.86 to 1.05. In other words, for teams in the middle of the tournament, the schedule strengths were much more evened out.&lt;br /&gt;&lt;br /&gt;Now, it's true that the range increased slightly for 4-0s and 1-3s. But for the 4-0s, it didn't increase terribly, and for 1-3s, it would have decreased but for one outlier (the team who had only 6 opponent wins). Furthermore, this was a small tournament with team constraints that created a lot of pull-ups; that the results show this level of improvement given those constraints is impressive.&lt;br /&gt;&lt;br /&gt;I'm going to test this out on a much larger scale so that the constraints don't impede the algorithm nearly as much.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-7533855679338316704?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/7533855679338316704/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/03/strength-of-schedule-pairings.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/7533855679338316704'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/7533855679338316704'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/03/strength-of-schedule-pairings.html' title='Strength of schedule pairings'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_5RAO7k_azLU/Sb1b_PgYBnI/AAAAAAAAADU/lIHMcCcYT7o/s72-c/comparison.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-1234514714508281051</id><published>2009-03-12T08:26:00.008-04:00</published><updated>2009-03-12T12:13:25.620-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='pre-calculus'/><category scheme='http://www.blogger.com/atom/ns#' term='circles'/><category scheme='http://www.blogger.com/atom/ns#' term='ellipses'/><category scheme='http://www.blogger.com/atom/ns#' term='trigonometry'/><category scheme='http://www.blogger.com/atom/ns#' term='parametric equations'/><category scheme='http://www.blogger.com/atom/ns#' term='Cartesian coordinates'/><title type='text'>Circles, ellipses, and Cartesian and parametric equations</title><content type='html'>Here is a great problem to introduce students to the utility of different forms of representation. Imagine two miniature train tracks that overlap: one, a circle of radius 4 inches centered at (1, 3) and the other, an ellipse with a long horizontal axis of 8 inches and a vertical axis of 4 inches centered at (0, 4).&lt;br /&gt;&lt;br /&gt;1) At what (&lt;span style="font-style: italic;"&gt;x&lt;/span&gt;, &lt;span style="font-style: italic;"&gt;y&lt;/span&gt;) coordinates do the tracks cross?&lt;br /&gt;2) If trains are placed at an arbitrary point on each track but travel at the same speed, will they &lt;span style="font-style: italic;"&gt;ever&lt;/span&gt; collide?&lt;br /&gt;&lt;br /&gt;To answer question 1, the Cartesian equations turn out to be the easiest way to go. The circle can be written as:&lt;br /&gt;&lt;div style="text-align: center;"&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/SbkE3y6u3II/AAAAAAAAAB0/-g74bMt_bx8/s1600-h/circle.jpg"&gt;&lt;img style="cursor: pointer; width: 138px; height: 41px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/SbkE3y6u3II/AAAAAAAAAB0/-g74bMt_bx8/s400/circle.jpg" alt="" id="BLOGGER_PHOTO_ID_5312282592067640450" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;/div&gt;The ellipse as:&lt;br /&gt;&lt;br /&gt;&lt;div style="text-align: center;"&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/SbkE4BfdmLI/AAAAAAAAAB8/5nSQ2SgXgXQ/s1600-h/ellipse1.jpg"&gt;&lt;img style="cursor: pointer; width: 108px; height: 52px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/SbkE4BfdmLI/AAAAAAAAAB8/5nSQ2SgXgXQ/s400/ellipse1.jpg" alt="" id="BLOGGER_PHOTO_ID_5312282595979794610" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;/div&gt;Or, alternatively, the ellipse could be:&lt;br /&gt;&lt;div style="text-align: center;"&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/SbkE4uQb4PI/AAAAAAAAACE/RFa6SkaIjwU/s1600-h/elllipse2.jpg"&gt;&lt;img style="cursor: pointer; width: 119px; height: 45px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/SbkE4uQb4PI/AAAAAAAAACE/RFa6SkaIjwU/s400/elllipse2.jpg" alt="" id="BLOGGER_PHOTO_ID_5312282607996362994" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;/div&gt;At this point, most students recognize that the circle and ellipse equations can be set equal to each other, and they can solve for &lt;span style="font-style: italic;"&gt;x&lt;/span&gt; or &lt;span style="font-style: italic;"&gt;y&lt;/span&gt; (whichever is easier) in terms of the other variable, and substitute back in. And that strategy works remarkably well for these equations because the &lt;span style="font-style: italic;"&gt;x&lt;/span&gt; squared terms cancel out.&lt;br /&gt;&lt;br /&gt;To answer question 2, parametric equations are the only way to go. Indeed, a good representation can make the answer to the question obvious and lets one make an even bolder statement. The circle is easy enough to write:&lt;br /&gt;&lt;br /&gt;&lt;div style="text-align: center;"&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/Sbkr1QxI3MI/AAAAAAAAACM/VtIMRxKtf-4/s1600-h/circle.jpg"&gt;&lt;img style="cursor: pointer; width: 117px; height: 59px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/Sbkr1QxI3MI/AAAAAAAAACM/VtIMRxKtf-4/s400/circle.jpg" alt="" id="BLOGGER_PHOTO_ID_5312325429494340802" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;/div&gt;&lt;br /&gt;The ellipse requires a little more effort. The problem says the trains are going at the same speed, but they're running on different length tracks. Specifically, the circle track length is 8 * pi, and the ellipse is approximately (square root 40) * pi in length. That means that the period of the elliptical-track train must be adjusted; that train will complete nearly 1.3 revolutions for every 1 the circular-track train completes.&lt;br /&gt;&lt;br /&gt;&lt;div style="text-align: center;"&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_5RAO7k_azLU/SbkvXtGlryI/AAAAAAAAACs/H3ytc5MB1Q8/s1600-h/ellipse.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 150px; height: 112px;" src="http://3.bp.blogspot.com/_5RAO7k_azLU/SbkvXtGlryI/AAAAAAAAACs/H3ytc5MB1Q8/s400/ellipse.jpg" alt="" id="BLOGGER_PHOTO_ID_5312329319750938402" border="0" /&gt;&lt;/a&gt;&lt;/div&gt;Now, you have something to graph and see what the paths of the trains look like. Comparison of the &lt;span style="font-style: italic;"&gt;x&lt;/span&gt;-coordinates --&lt;br /&gt;&lt;br /&gt;&lt;div style="text-align: center;"&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_5RAO7k_azLU/SbkvYA-jVcI/AAAAAAAAAC0/lTzPw2f2_G4/s1600-h/parametric+xs.png"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 400px; height: 334px;" src="http://3.bp.blogspot.com/_5RAO7k_azLU/SbkvYA-jVcI/AAAAAAAAAC0/lTzPw2f2_G4/s400/parametric+xs.png" alt="" id="BLOGGER_PHOTO_ID_5312329325085939138" border="0" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;br /&gt;and the &lt;span style="font-style: italic;"&gt;y&lt;/span&gt;-coordinates --&lt;br /&gt;&lt;br /&gt;&lt;div style="text-align: center;"&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_5RAO7k_azLU/SbkvYJP2auI/AAAAAAAAAC8/VujzlZurVlo/s1600-h/parametric+ys.png"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 400px; height: 334px;" src="http://2.bp.blogspot.com/_5RAO7k_azLU/SbkvYJP2auI/AAAAAAAAAC8/VujzlZurVlo/s400/parametric+ys.png" alt="" id="BLOGGER_PHOTO_ID_5312329327305976546" border="0" /&gt;&lt;/a&gt;&lt;/div&gt;shows that the trains will indeed cross paths (where the equations cross at the same time &lt;span style="font-style: italic;"&gt;t&lt;/span&gt; on each graph; equations crossing on the &lt;span style="font-style: italic;"&gt;x&lt;/span&gt; graph only or &lt;span style="font-style: italic;"&gt;y&lt;/span&gt; graph only would show where they were on roughly opposite sides of their respective tracks). It becomes obvious with this representation that of course they cross paths because they have different periods (travel time for one circuit around the track). In fact, this representation should make it obvious that "ever" is too weak a question -- they &lt;span style="font-style: italic;"&gt;must&lt;/span&gt; cross paths, no matter where their starting places. It is especially neat for students to see that there's no least common multiple of the periods possible; that is, the combination of the two functions is non-repeating. Take &lt;span style="font-style: italic;"&gt;t&lt;/span&gt; to infinity and you'll never see the two trains at the same time in the same places they were at &lt;span style="font-style: italic;"&gt;t&lt;/span&gt; = 0. Neat.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-1234514714508281051?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/1234514714508281051/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/03/circles-ellipses-and-cartesian-and.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/1234514714508281051'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/1234514714508281051'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/03/circles-ellipses-and-cartesian-and.html' title='Circles, ellipses, and Cartesian and parametric equations'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/_5RAO7k_azLU/SbkE3y6u3II/AAAAAAAAAB0/-g74bMt_bx8/s72-c/circle.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-538153946535953452</id><published>2009-03-09T09:54:00.005-04:00</published><updated>2009-03-23T17:36:56.487-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='debate tournaments'/><category scheme='http://www.blogger.com/atom/ns#' term='seed'/><category scheme='http://www.blogger.com/atom/ns#' term='round robin'/><category scheme='http://www.blogger.com/atom/ns#' term='high school debate'/><title type='text'>Half-round robin</title><content type='html'>This idea grew out of a conversation with a Michigan coach. What if you had only 12 teams and 6 prelims? Obviously, it's going to be hard to power-match the tournament; the brackets are going to be too small too quickly (basically, nothing but pull-ups after round 3). So why not do a half-round robin? The Excel workbook shows one way to make this happen, and, as it shows, if you can seed the teams before the tournament starts, then you can make a pretty fair pairing: &lt;a href="http://www.mediafire.com/?qzediimilke"&gt;http://www.mediafire.com/?qzediimilke&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-538153946535953452?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/538153946535953452/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/03/half-round-robin.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/538153946535953452'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/538153946535953452'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/03/half-round-robin.html' title='Half-round robin'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-3611948421034275034</id><published>2009-03-06T14:08:00.006-05:00</published><updated>2009-03-10T07:54:52.528-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='debate tournaments'/><category scheme='http://www.blogger.com/atom/ns#' term='power-matching'/><category scheme='http://www.blogger.com/atom/ns#' term='high school debate'/><category scheme='http://www.blogger.com/atom/ns#' term='schedule strength'/><category scheme='http://www.blogger.com/atom/ns#' term='opponent wins'/><title type='text'>What are normal opponents wins in a given bracket?</title><content type='html'>I decided to look at several big, well-run tournaments from this year and last year. I chose big tournaments because there's less of a chance that odd results were created by restrictions given small brackets with too many teams from the same schools. I'm not going to include the tournaments' names -- this is just data. Here are the results for teams that broke:&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_5RAO7k_azLU/SbF0wIDo5kI/AAAAAAAAABk/YcYs2ga8O3k/s1600-h/6+rd+OW+spreads.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 155px; height: 106px;" src="http://4.bp.blogspot.com/_5RAO7k_azLU/SbF0wIDo5kI/AAAAAAAAABk/YcYs2ga8O3k/s200/6+rd+OW+spreads.jpg" alt="" id="BLOGGER_PHOTO_ID_5310153805791815234" border="0" /&gt;&lt;/a&gt;That means at one tournament, the 6-0 with the hardest schedule faced opponents accumulating 25 wins, while at the same tournament, the 6-0 with the easiest schedule faced opponents accumulating only 22 wins. For the most part, the 6-0s at all these tournaments had reasonably narrow ranges (meaning that all the 6-0s had roughly similar strengths of schedule) except at two tournaments: the 16-25 and 19-24 are unusually broad ranges. A result of 25 opponent wins averages out to a little better than a 4-2 record/opponent; 16 OW averages out to worse than a 3-3 record! The spread for 5-1s, however, looks consistently larger, from better than a 4-2 record/opponent average down to a worse than a 3-3 record/opponent average.&lt;br /&gt;&lt;br /&gt;The results are even more surprising when looking at seven round divisions:&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/SbF006eup5I/AAAAAAAAABs/OaJah-ztPLM/s1600-h/7+rd+OW+spreads.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 223px; height: 55px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/SbF006eup5I/AAAAAAAAABs/OaJah-ztPLM/s200/7+rd+OW+spreads.jpg" alt="" id="BLOGGER_PHOTO_ID_5310153888046688146" border="0" /&gt;&lt;/a&gt;The 7-0s' ranges look reasonably small, but the 6-1s and 5-2s faced very different schedules of opponents! At one tournament, the luckiest 5-2 faced opponents racking up only 21 wins (an average of a 3-4 record), while another 5-2 faced opponents racking up a whopping 36 wins (an average of better than 5-2) -- a harder schedule than the best 7-0 faced!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-3611948421034275034?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/3611948421034275034/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/03/what-are-normal-opponents-wins-in-given.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/3611948421034275034'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/3611948421034275034'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/03/what-are-normal-opponents-wins-in-given.html' title='What are normal opponents wins in a given bracket?'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_5RAO7k_azLU/SbF0wIDo5kI/AAAAAAAAABk/YcYs2ga8O3k/s72-c/6+rd+OW+spreads.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-7964056123671797398</id><published>2009-03-04T20:59:00.005-05:00</published><updated>2009-03-09T10:00:44.262-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='debate tournaments'/><category scheme='http://www.blogger.com/atom/ns#' term='power-matching'/><category scheme='http://www.blogger.com/atom/ns#' term='schedule strength'/><category scheme='http://www.blogger.com/atom/ns#' term='opponent wins'/><title type='text'>A hypothetical worst case debate math scenario...</title><content type='html'>One other little bit of tournament math... Imagine this hypothetical team, call it team uno, the best team at a tournament, in a tournament using the traditional high-low power-matching system. First and second round are random, so it's possible team uno might hit the worst and second worst teams at the tournament in rounds 1 and 2. These two awful teams go on to a 0-6 win-loss record. Then, team uno, being 2-0 with the best speaker points, will hit the worst 2-0 with the lowest speaker points, which could conceivably lose all its remaining rounds and finish 2-4. The same for the next round, hitting the worst 3-0, which could finish 3-3, and all the way through. It is possible in this way for the top team to face six opponents with a combined record of only 14 wins in six rounds. This averages to just slightly better than a 2-4 record/opponent. (Of course, it will likely be better, but it &lt;span style="font-style: italic;"&gt;could&lt;/span&gt; even be worse if there are an uneven number of teams in each bracket and the top team receives a "pull-up" and debates an opponent with a one-loss worse record in one or more "power-matched" round.) Now, I think the ideal is for the best team at the tournament to face excellent opponents (this is what power-matching systems, like the Swiss system, are supposed to do!) perhaps averaging 4-2 or 5-1 records, for combined opponent wins in the range of 24-30. A far cry from 14 -- which could easily results from pairings that the current algorithm does create and is powerless to flag or rectify.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-7964056123671797398?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/7964056123671797398/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/03/hypothetical-worst-case-debate-math.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/7964056123671797398'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/7964056123671797398'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/03/hypothetical-worst-case-debate-math.html' title='A hypothetical worst case debate math scenario...'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-2798384366685163756</id><published>2009-03-03T11:34:00.012-05:00</published><updated>2009-03-23T17:51:11.346-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='recursive functions'/><category scheme='http://www.blogger.com/atom/ns#' term='mautam'/><category scheme='http://www.blogger.com/atom/ns#' term='exponential growth'/><category scheme='http://www.blogger.com/atom/ns#' term='mautaam'/><category scheme='http://www.blogger.com/atom/ns#' term='black rats'/><title type='text'>Rat Attack</title><content type='html'>On Feb. 24, 2009, &lt;span style="font-style: italic;"&gt;NOVA&lt;/span&gt; ran a special on the mautaam event in India: &lt;a href="http://www.pbs.org/wgbh/nova/rats"&gt;http://www.pbs.org/wgbh/nova/rats&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Apparently, once every 48 years, the bamboo flowers and produces an enormous quantity of fruit, which in turn causes a population explosion among the black rats in the forest. Once the fruit is gone, this plague of rats devours the rice fields, causing a lot of human suffering.&lt;br /&gt;&lt;br /&gt;The math is simple: exponential population growth. What is staggering is the sheer rapidity of rat reproduction when there's no limit to the environmental carrying capacity. This is a great, real example to use with your students of exponential growth.&lt;br /&gt;&lt;br /&gt;Here are the details I looked up: black rats have a gestation period of 21 days and can have a litter of about 10 pups at a time; female rats can nurse a litter while also pregnant; and rats reach sexual maturity in 6 weeks and therefore can have their first litter at 9 weeks of age. These facts produce explosive -- yes, explosive -- population growth. You can model the growth by tracking the size of each age cohort (newborns, adolescents, mature adults) in an Excel spreadsheet, like I did in this one: &lt;a href="http://www.mediafire.com/?linigzqgmmk"&gt;http://www.mediafire.com/?linigzqgmmk&lt;br /&gt;&lt;/a&gt;&lt;br /&gt;Or, you can model the growth with a recursive formula:&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_5RAO7k_azLU/Sa3B5wFnK-I/AAAAAAAAABU/7GdtdOKdx6U/s1600-h/equation.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 154px; height: 44px;" src="http://2.bp.blogspot.com/_5RAO7k_azLU/Sa3B5wFnK-I/AAAAAAAAABU/7GdtdOKdx6U/s320/equation.jpg" alt="" id="BLOGGER_PHOTO_ID_5309112733644827618" border="0" /&gt;&lt;/a&gt;where &lt;span style="font-style: italic;"&gt;a&lt;/span&gt; is the time in weeks. You can also come close with an explicit formula,&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/Sa3DRsgH8-I/AAAAAAAAABc/--9L5O_97aQ/s1600-h/equation2.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 143px; height: 37px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/Sa3DRsgH8-I/AAAAAAAAABc/--9L5O_97aQ/s200/equation2.jpg" alt="" id="BLOGGER_PHOTO_ID_5309114244510774242" border="0" /&gt;&lt;/a&gt;where &lt;span style="font-style: italic;"&gt;t&lt;/span&gt; is the time in weeks. I graphed this explicit formula into the Excel spreadsheet as well. The upshot is that the rat population comes close to doubling every three weeks; in the four month season of mautaam, the population grows nearly &lt;span style="font-weight: bold; font-style: italic;"&gt;120-fold&lt;/span&gt;. That's a real plague of rats.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-2798384366685163756?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/2798384366685163756/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/03/rat-attack.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/2798384366685163756'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/2798384366685163756'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/03/rat-attack.html' title='Rat Attack'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_5RAO7k_azLU/Sa3B5wFnK-I/AAAAAAAAABU/7GdtdOKdx6U/s72-c/equation.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8734744291040505450.post-8547276020954435304</id><published>2009-03-02T17:00:00.012-05:00</published><updated>2009-03-23T17:44:58.391-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='cross-examination debate'/><category scheme='http://www.blogger.com/atom/ns#' term='breaks'/><category scheme='http://www.blogger.com/atom/ns#' term='high school debate'/><category scheme='http://www.blogger.com/atom/ns#' term='swiss system'/><category scheme='http://www.blogger.com/atom/ns#' term='tournament'/><category scheme='http://www.blogger.com/atom/ns#' term='network graph'/><title type='text'>Debate tournament math</title><content type='html'>Here's how a high school or college debate tournament works: for the first two rounds of debating, each team is randomly assigned an opponent; for the third round, the winners of the first two rounds are assigned other winners as opponents, while losers debate losers. This system continues for several preliminary rounds, "power matching" teams against opponents with the same record of wins and losses, until the top "brackets" with winning records (7-0s and 6-1s, for example) move on to elimination rounds. Thus, the preliminary rounds are a type of Swiss system tournament, a format that is used in chess competition, too. The number of teams in each final bracket follows a perfect binomial distribution (plus or minus one team or two for odd numbers that require a team to be "pulled up" from a lower bracket).&lt;br /&gt;&lt;br /&gt;This approach is generally felt to be fair, although it is a recognized problem that a good team could lose the first or second round and would have easier opponents all the way through. How often does this happen? A visualization helps:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_5RAO7k_azLU/SaxcxqKXBmI/AAAAAAAAABE/2jipwDKHM5s/s1600-h/topbreaks.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 308px; height: 163px;" src="http://4.bp.blogspot.com/_5RAO7k_azLU/SaxcxqKXBmI/AAAAAAAAABE/2jipwDKHM5s/s400/topbreaks.jpg" alt="" id="BLOGGER_PHOTO_ID_5308720068964058722" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;Click on image for more detail or download from &lt;a href="http://www.mediafire.com/imageview.php?quickkey=mumjuwznyiv&amp;amp;thumb=5"&gt;mediafire&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;These are the preliminary varsity policy debate results at the 2009 Harvard invitational high school tournament. (I took out names because I don't want to seem like I'm ragging on any school; I'm really just interested in the math.) Each row represents a different bracket -- the 7-0 at the top, 6-1s one row down, etc., and the 0-7 at the bottom -- and each row is sorted best speaker points (left) to worst speaker points (right) in that bracket. Each arrow represents one actual debate between two teams, pointing to the winner but in the loser's row color. Every single round is there, but I bolded the rounds that the top nine teams won. You can see how differently the top teams (the 7-0 and 6-1s) got that record. Some 6-1s, circled, defeated at least three 5-2 or better teams. Other 6-1s, in squares, defeated only one or no 5-2s. The 6-1 on the far left defeated &lt;span style="font-weight: bold;"&gt;not one&lt;/span&gt; team in the top 20%. Perhaps they could have, but they never even faced off against one. They made it into elimination rounds on the basis of an easier schedule than any other 6-1.&lt;br /&gt;&lt;br /&gt;Let me make it absolutely clear, I'm not criticizing the folks who run the Harvard tournament. They do a fine job. The problem is not with their execution. I'm sure that at every point, the 6-1s were given proper opponents for their records; the problem is that some of those opponents went on to lose many of their remaining rounds and revealed their weakness. The problem is the method, which is only as good as the current record of each team accurately reflects its true strength. Since this information can't be known in advance, the only solution so far has been to repeat the process many, many times to thoroughly test and properly rank each team in preliminary rounds. Potentially, what you're looking at above is a raw sort that still contains some errors, like ABCEDLFGJIMNP... it's getting better, but there's still a need for further sorting. Consider it this way: the first round is supposed to determine whether a letter is in the first half of the alphabet or not, by picking up two letters at the same and determining which comes first. Generally speaking, this works, and A, B, C, etc., are likely to end up in the first-half pile. But what happens if the letters you pick up to compare are T and W? T will be misleadingly placed in the first-half pile, and you hope that this doesn't happen two, or three, or &lt;span style="font-style: italic;"&gt;seven&lt;/span&gt; times in a row, but clearly, it can and did happen, and a team made into the top 6% without ever facing an opponent in the top 20%.&lt;br /&gt;&lt;br /&gt;Randomness isn't enough. There needs to be an element added to power-matching that controls for strength of schedule. If you need further convincing, here are the 5-2s highlighted:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_5RAO7k_azLU/Saxpk55zIFI/AAAAAAAAABM/NZaJXaIgu0Y/s1600-h/lower+breaks.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 306px; height: 158px;" src="http://1.bp.blogspot.com/_5RAO7k_azLU/Saxpk55zIFI/AAAAAAAAABM/NZaJXaIgu0Y/s400/lower+breaks.jpg" alt="" id="BLOGGER_PHOTO_ID_5308734143502426194" border="0" /&gt;&lt;/a&gt;Click on image for more detail or download from &lt;a href="http://www.mediafire.com/imageview.php?quickkey=2mfq5dzwaqh&amp;amp;thumb=5"&gt;mediafire&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;The circled 5-2s defeated at least one other 5-2. (It's hard to see those blue arrows, so click on the image for expansion first.) The 5-2s in squares defeated only one or two 4-3s or better -- that is, they made it into the top 20% and elimination rounds on the basis of defeating only one or two teams in the top 40%. That's quite a disparate schedule: debating other 5-2s and several 4-3s, or debating a few 4-3s and then several teams that are weaker.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8734744291040505450-8547276020954435304?l=art-of-logic.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://art-of-logic.blogspot.com/feeds/8547276020954435304/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://art-of-logic.blogspot.com/2009/03/debate-tournament-math.html#comment-form' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/8547276020954435304'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8734744291040505450/posts/default/8547276020954435304'/><link rel='alternate' type='text/html' href='http://art-of-logic.blogspot.com/2009/03/debate-tournament-math.html' title='Debate tournament math'/><author><name>Russell Hanes</name><uri>http://www.blogger.com/profile/13594411930757264086</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://bp0.blogger.com/_5RAO7k_azLU/R4qgAShXSZI/AAAAAAAAAAM/L0k2H0bTG5s/S220/russell1.png'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_5RAO7k_azLU/SaxcxqKXBmI/AAAAAAAAABE/2jipwDKHM5s/s72-c/topbreaks.jpg' height='72' width='72'/><thr:total>4</thr:total></entry></feed>
