<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Math on the Mississippi</title>
	<link>http://bit-player.org/2007/math-on-the-mississippi</link>
	<description>An amateur's outlook on computation and mathematics.</description>
	<pubDate>Fri, 29 Aug 2008 05:35:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.2</generator>

	<item>
 		<title>Comment on Math on the Mississippi by: Jasper Crowne</title>
		<link>http://bit-player.org/2007/math-on-the-mississippi#comment-1440</link>
		<pubDate>Fri, 09 Mar 2007 22:15:32 +0000</pubDate>
		<guid>http://bit-player.org/2007/math-on-the-mississippi#comment-1440</guid>
					<description>I just realized that my comment was cut off (most likely due to use of the less than sign), and that I misspelled my name... 

It follows from the triangle inequality that

&amp;#166;(b’-Y’)/y’/&amp;#166;+&amp;#166;(b-Y)/y/&amp;#166;+&amp;#166;V&amp;#166; is less than or equal to &amp;#166;U&amp;#166;; since /y/ and /y'/ are arbitrary in the general case, we have equality only when b=Y, b'=Y', and hence V=U.  QED</description>
		<content:encoded><![CDATA[	<p>I just realized that my comment was cut off (most likely due to use of the less than sign), and that I misspelled my name&#8230; </p>
	<p>It follows from the triangle inequality that</p>
	<p>|(b’-Y’)/y’/|+|(b-Y)/y/|+|V| is less than or equal to |U|; since /y/ and /y&#8217;/ are arbitrary in the general case, we have equality only when b=Y, b&#8217;=Y&#8217;, and hence V=U.  QED
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Math on the Mississippi by: Jasper Crowe</title>
		<link>http://bit-player.org/2007/math-on-the-mississippi#comment-1409</link>
		<pubDate>Sat, 13 Jan 2007 08:29:27 +0000</pubDate>
		<guid>http://bit-player.org/2007/math-on-the-mississippi#comment-1409</guid>
					<description>I think the following proves Merten's algorithm is the best possible: 
Let the point in the (x',y') lattice be at (X',Y')  and let the point in the (x,y) lattice be (X,Y).  Any path from (X',Y') to (X,Y) has three segments: 
1) we travel from (X',Y') through the (x',y') lattice until we reach x'=0.  Call this point (0,b').
2) we walk through the park to the line x=0.  Call this point (0,b).
3) we travel through the (x,y) lattice from (0,b) to (X,Y).

In 1), note that any direct path you take from (X',Y') to (0,b') (by this I mean any path such that the Manhattan distance to (0,b') is strictly decreasing) has the same distance as just walking from (X',Y') to (0,Y') and then walking from (0,Y') to (0,b').  And similarly for 2).  This reduces the problem to finding b, b' so that the sum of the following distances is minimized:  
1) from (0,Y') to (0,b') (along the y' axis)
2) from (0,b') to (0,b) (through the park)
3) from (0,b) to (0,Y) (along the y axis)

The distance we are trying to minimize is (b'-Y')+(b-Y)+&amp;#166;V&amp;#166; where V is the vector in 2).  We'd like to show that this is less than &amp;#166;U&amp;#166; where U is the vector from (0,Y') to (0,Y) (i.e. where b'=Y' and b=Y).  Let /y'/ be the unit vector in the +y' direction and /y/ be the unit vector in the +y direction.  Then we have the following vector sum:

(b'-Y')/y'/+(b-Y)/y/+V=U
It follows from the triangle inequality that 

&amp;#166;(b'-Y')/y'/&amp;#166;+&amp;#166;(b-Y)/y/&amp;#166;+&amp;#166;V&amp;#166; </description>
		<content:encoded><![CDATA[	<p>I think the following proves Merten&#8217;s algorithm is the best possible:<br />
Let the point in the (x&#8217;,y&#8217;) lattice be at (X&#8217;,Y&#8217;)  and let the point in the (x,y) lattice be (X,Y).  Any path from (X&#8217;,Y&#8217;) to (X,Y) has three segments:<br />
1) we travel from (X&#8217;,Y&#8217;) through the (x&#8217;,y&#8217;) lattice until we reach x&#8217;=0.  Call this point (0,b&#8217;).<br />
2) we walk through the park to the line x=0.  Call this point (0,b).<br />
3) we travel through the (x,y) lattice from (0,b) to (X,Y).</p>
	<p>In 1), note that any direct path you take from (X&#8217;,Y&#8217;) to (0,b&#8217;) (by this I mean any path such that the Manhattan distance to (0,b&#8217;) is strictly decreasing) has the same distance as just walking from (X&#8217;,Y&#8217;) to (0,Y&#8217;) and then walking from (0,Y&#8217;) to (0,b&#8217;).  And similarly for 2).  This reduces the problem to finding b, b&#8217; so that the sum of the following distances is minimized:<br />
1) from (0,Y&#8217;) to (0,b&#8217;) (along the y&#8217; axis)<br />
2) from (0,b&#8217;) to (0,b) (through the park)<br />
3) from (0,b) to (0,Y) (along the y axis)</p>
	<p>The distance we are trying to minimize is (b&#8217;-Y&#8217;)+(b-Y)+|V| where V is the vector in 2).  We&#8217;d like to show that this is less than |U| where U is the vector from (0,Y&#8217;) to (0,Y) (i.e. where b&#8217;=Y&#8217; and b=Y).  Let /y&#8217;/ be the unit vector in the +y&#8217; direction and /y/ be the unit vector in the +y direction.  Then we have the following vector sum:</p>
	<p>(b&#8217;-Y&#8217;)/y&#8217;/+(b-Y)/y/+V=U<br />
It follows from the triangle inequality that </p>
	<p>|(b&#8217;-Y&#8217;)/y&#8217;/|+|(b-Y)/y/|+|V|
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Math on the Mississippi by: brian</title>
		<link>http://bit-player.org/2007/math-on-the-mississippi#comment-1408</link>
		<pubDate>Thu, 11 Jan 2007 15:50:00 +0000</pubDate>
		<guid>http://bit-player.org/2007/math-on-the-mississippi#comment-1408</guid>
					<description>&quot;Incommensurable&quot; was sloppy wording on my part. I simply meant that you cannot make *all* the intersections line up neatly (unless the angle is a multiple of 90 degrees).

Incidentally, although the blocks in New Orleans are roughly square, other cities favor elongated rectangles; Manhattan, for example, has short blocks along the avenues and longer blocks along the cross streets. If you build a city by knitting together adjacent patches of grid rotated by 45 degrees, there's a very nice solution with blocks whose aspect ratio is 1:&amp;#8730;2.</description>
		<content:encoded><![CDATA[	<p>&#8220;Incommensurable&#8221; was sloppy wording on my part. I simply meant that you cannot make *all* the intersections line up neatly (unless the angle is a multiple of 90 degrees).</p>
	<p>Incidentally, although the blocks in New Orleans are roughly square, other cities favor elongated rectangles; Manhattan, for example, has short blocks along the avenues and longer blocks along the cross streets. If you build a city by knitting together adjacent patches of grid rotated by 45 degrees, there&#8217;s a very nice solution with blocks whose aspect ratio is 1:&radic;2.
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Math on the Mississippi by: Barry Cipra</title>
		<link>http://bit-player.org/2007/math-on-the-mississippi#comment-1407</link>
		<pubDate>Wed, 10 Jan 2007 18:08:43 +0000</pubDate>
		<guid>http://bit-player.org/2007/math-on-the-mississippi#comment-1407</guid>
					<description>&quot;If the two lattices have the same spacing but different orientations, then they are incommensurable...&quot;  This isn't quite correct.  Integer solutions of the Pythagorean formula a^2 + b^2 = c^2 allow for commensurable orientations -- e.g., a slope of 3/4 permits a 5-way intersection at every fifth corner for the tilted grid.  (One would presumably extend each untilted street till it meets the boundary of the tilted grid.  Otherwise there could be some fairly long detours.)</description>
		<content:encoded><![CDATA[	<p>&#8220;If the two lattices have the same spacing but different orientations, then they are incommensurable&#8230;&#8221;  This isn&#8217;t quite correct.  Integer solutions of the Pythagorean formula a^2 + b^2 = c^2 allow for commensurable orientations &#8212; e.g., a slope of 3/4 permits a 5-way intersection at every fifth corner for the tilted grid.  (One would presumably extend each untilted street till it meets the boundary of the tilted grid.  Otherwise there could be some fairly long detours.)
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Math on the Mississippi by: Stephan Mertens</title>
		<link>http://bit-player.org/2007/math-on-the-mississippi#comment-1406</link>
		<pubDate>Tue, 09 Jan 2007 15:29:26 +0000</pubDate>
		<guid>http://bit-player.org/2007/math-on-the-mississippi#comment-1406</guid>
					<description>Let us assume equal lattice spacings in both parts of the grid (like in your counter example).
Can you think of an example where the straight line heuristics is off by *more* than one block?</description>
		<content:encoded><![CDATA[	<p>Let us assume equal lattice spacings in both parts of the grid (like in your counter example).<br />
Can you think of an example where the straight line heuristics is off by *more* than one block?
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Math on the Mississippi by: Stephan Mertens</title>
		<link>http://bit-player.org/2007/math-on-the-mississippi#comment-1405</link>
		<pubDate>Tue, 09 Jan 2007 11:14:29 +0000</pubDate>
		<guid>http://bit-player.org/2007/math-on-the-mississippi#comment-1405</guid>
					<description>Draw a straight line on the map between your hotel and the destination in the tilted grid. Take the transition point that is closest to the point where this line intersects the discontinuity. This should give the shortest distance, and apparently Google knows that.

Stephan</description>
		<content:encoded><![CDATA[	<p>Draw a straight line on the map between your hotel and the destination in the tilted grid. Take the transition point that is closest to the point where this line intersects the discontinuity. This should give the shortest distance, and apparently Google knows that.</p>
	<p>Stephan
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
