<?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-25964010</id><updated>2012-02-15T04:36:46.150-08:00</updated><title type='text'>TECH-MUSINGS</title><subtitle type='html'>Thoughts On Algorithms, Geometry etc...</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>24</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-25964010.post-8931246844295208423</id><published>2012-02-07T03:27:00.001-08:00</published><updated>2012-02-15T04:36:46.169-08:00</updated><title type='text'>Packing Rectangles</title><content type='html'>Here is a puzzle to which I dunno the answer yet.&lt;br /&gt;&lt;br /&gt;Claim: Given N (N&gt;1) rectangles all of the same area but all with different perimeters.&lt;br /&gt;We cannot pack them without gaps to form a large rectangle.&lt;br /&gt;&lt;br /&gt;IOW, if a rectangle is broken into N smaller rectangles all of same area, at least two of the pieces are identical.&lt;br /&gt;&lt;br /&gt;Remark: it is not too hard to show rectangles which can be divided into N equal area rectangles with just 2 pieces identical, and all others having different perimeter.&lt;br /&gt;&lt;br /&gt;Perhaps the claim may be easier to prove under the constraint: the sides of the rectangle and the pieces ought to be integers/rationals. &lt;br /&gt;&lt;br /&gt;The following pages may be of interest.&lt;br /&gt;http://mathdl.maa.org/images/upload_library/22/Ford/Wagon601-617.pdf &lt;br /&gt;http://www.math.uwaterloo.ca/navigation/ideas/articles/honsberger2/index.shtml&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-8931246844295208423?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/8931246844295208423/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=8931246844295208423' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/8931246844295208423'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/8931246844295208423'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2012/02/packing-rectangles.html' title='Packing Rectangles'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-1396582181417705701</id><published>2010-01-01T14:16:00.000-08:00</published><updated>2010-01-14T07:22:24.746-08:00</updated><title type='text'>Congruent Partitions - A Special Case</title><content type='html'>Question: Let us say, we cut from a convex polygon P 2 mutually congruent pieces such that the pieces have as great an area as possible. Find that polygon P which causes the maximum wastage - the fraction of the area wasted to the total area of P.&lt;br /&gt;&lt;br /&gt;P is constrained to be convex with the pieces allowed to be non-convex. Which shape of P gives highest 'wastage fraction'? Basically, we need to upper-bound the wastage fraction when a convex P is 'maximally congruent bisected'.&lt;br /&gt;&lt;br /&gt;A simple fact: The two maximum area pieces have to touch each other; indeed, otherwise both pieces could be moved in the interior of P (which is convex) to a config where neither piece touches the walls of P or each other - and from that stage, both pieces can be expanded identically =&gt; the area of the pieces were not max to begin with.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-1396582181417705701?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/1396582181417705701/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=1396582181417705701' title='38 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/1396582181417705701'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/1396582181417705701'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2010/01/congruent-partitions-special-case.html' title='Congruent Partitions - A Special Case'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>38</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-8934028492847454895</id><published>2009-10-24T21:18:00.000-07:00</published><updated>2010-01-01T14:26:32.868-08:00</updated><title type='text'>Another Congruent Partition Problem</title><content type='html'>A bit of news: The basic Congruent partition problem has been listed at:&lt;br /&gt;http://maven.smith.edu/~orourke/TOPP/P73.html&lt;br /&gt;&lt;br /&gt;Question: Given a convex polygon P and a number N so that P can somehow be cut into N mutually congruent *non-convex* pieces with no wastage - ie. a 'perfect congruent partition' exists for P for that N. Then is it true that P necessarily also allows a partition into N mutually congruent convex pieces?&lt;br /&gt;&lt;br /&gt;In other words, can we say: "there is no P and N such that P can be perfectly congruent-partitioned into N pieces only when the pieces are necessarily non-convex"?&lt;br /&gt;&lt;br /&gt;For N = 2, the above question seems to have an affirmative answer - no convex polygon appears to have only a congruent 2-partition such that pieces are non-convex. Beyond N=2, nothing much seems to be known.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-8934028492847454895?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/8934028492847454895/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=8934028492847454895' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/8934028492847454895'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/8934028492847454895'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2009/10/another-congruent-partition-problem.html' title='Another Congruent Partition Problem'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-8181832419261728058</id><published>2009-05-04T05:36:00.000-07:00</published><updated>2010-01-06T04:50:20.324-08:00</updated><title type='text'>'Congruent' Partitions of Polygons</title><content type='html'>Here is another polygon partitioning problem, a work-in-progress thought:&lt;br /&gt;&lt;br /&gt;Problem: Given a polygon P and an number N. We need to cut from&lt;br /&gt;P, N mutually congruent (*) pieces (or 'tiles')of a suitable shape such that the area inside P is as fully covered by the pieces as possible.&lt;br /&gt;&lt;br /&gt;(*) - two polygons are congruent if one can be made to&lt;br /&gt;coincide totally with the other by translation, rotation or 'flipping&lt;br /&gt;over'.&lt;br /&gt;&lt;br /&gt;Note 1: It is known that a convex polygon *need not* admit a partitioning into N congruent pieces which together cover the whole of its interior. eg:&lt;br /&gt;http://domino.research.ibm.com/Comm/wwwr_ponder.nsf/challenges/December2003.html&lt;br /&gt;(Part 2 of the 'challenge').&lt;br /&gt;&lt;br /&gt;Guess: It seems this inevitability of there being a left-over (in some cases)is a 2D phenomenon. Any 3D input region appears cuttable into, say, 2 (or any N) identical and non-convex pieces which fill the whole of the input region in a very fractally way with dense and interpenetrating branches (somewhat like the two worms which eat up an anpple in Gamow's '1,2,3,infinity'). &lt;br /&gt;&lt;br /&gt;So, the problem requires us to choose the shape the identical pieces should have so&lt;br /&gt;that as little area of the input polygon is left uncovered - or the&lt;br /&gt;input sheet is as fully 'utilized' as possible.&lt;br /&gt;&lt;br /&gt;-----------------&lt;br /&gt;Further thoughts: &lt;br /&gt;-----------------&lt;br /&gt;&lt;br /&gt;1. Consider the following claim: for any N and for any input *convex* polygon, if we do the 'congruent partitioning' with the further condition that the identical pieces are also convex and find the best solution, it will also be the global optimum - ie. allowing the pieces to be concave leads to no better utilization of the input convex polygon. &lt;br /&gt;&lt;br /&gt;This claim - that the best congruent partition of a convex polygon can be done with convex pieces - is *not true* it appears (thanks to Prof. Erich Friedman).&lt;br /&gt;&lt;br /&gt;eg: Consider a 3X7 rectangle and remove a unit square from a corner; then form the *convex hull* of the resulting object, getting a pentagon or area 20.5. Out of this, an area of 20 can be filled by five L-tetrominoes - non convex objects. No convex congruent partition of this pentagon appears to leave such a small remainder.&lt;br /&gt;&lt;br /&gt;Now, we float a new guess: the complexity of the piece (measured in the number of edges in it) in the best congruent partition is not more than linear in the complexity of the input polygon (here, Circular arcs are treated as no more complex than straight lines). There *probably* is no dependence of the complexity of the piece on N, the number of pieces. Basically, the guess is that if the input polygon has a 'simple' shape, the pieces in the best congruent partition cannot be highly branched and complex but comparable in complexity to the input polygon itself, for any N.&lt;br /&gt;&lt;br /&gt;-----&lt;br /&gt;&lt;br /&gt;2.If we relax the original requirement - to give N mutually congruent tiles - and seek N mutually identical *sets of tiles* (every tile of any set i is congruent to a tile in any other set j as i and j run from 1 to N), with each tile-set allowed to have finitely many pieces, we can do better in terms of reducing leftover: &lt;br /&gt;&lt;br /&gt;Fact: Any triangle can be cut into 4 mutually congruent triangles; and any polygon can be divided into triangles. Any m-gon will give m-2 triangles.&lt;br /&gt;&lt;br /&gt;So, If N is 4, we can triangulate the (m-vertex) input polygon and further divide each triangle into 4 so as to achieve a partition into 4 tile-sets each with m-2 triangles. This is easily generalizable to N = any power of 2. No bit of the input polygon is wasted.&lt;br /&gt;&lt;br /&gt;Definition: A polygon is n-sectible if it can be cut into n mutually congruent pieces.&lt;br /&gt;&lt;br /&gt;If N=3, we could try this: Somehow partition the input polygon into *some* number of pieces (each of which may be quite different from each other) such that each of them is 3-sectible; that will in turn enable a partition into 3 mutually identical sets of pieces with no leftover. &lt;br /&gt;&lt;br /&gt;Note 1: 3-sectibility is a very loose property and is shown by a wide range of shapes. And it is not clear if any given polygon *always* allows partitioning into 3-sectable pieces (or in general, partitioning into m-sectable pieces) with no leftover.&lt;br /&gt;&lt;br /&gt;Note 2: Even the apparently simpler (to state) problem: "given a polygon, determine if it is 3-sectible" appears unexplored - although there is work on partitioning a polygon into 3 pieces all of same area and same perimeter (eg: in the 'fair partitioning' context).&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-8181832419261728058?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/8181832419261728058/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=8181832419261728058' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/8181832419261728058'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/8181832419261728058'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2009/05/identical-partitions-of-polygons.html' title='&apos;Congruent&apos; Partitions of Polygons'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-2243369660859910685</id><published>2009-04-25T11:20:00.000-07:00</published><updated>2009-05-04T05:40:16.226-07:00</updated><title type='text'>A Doubt On Circle Packing</title><content type='html'>We understand that for packing identical circles (indeed packing copies of any centrally symmetric convex shape) in an infinite plane, the best arrangment is a always a lattice arrangement (hexagonal lattice for packing circles).&lt;br /&gt;&lt;br /&gt;Does the above lead naturally to the following?&lt;br /&gt;&lt;br /&gt;Consider any specified 2d shape as a container for identical circles. &lt;br /&gt;&lt;br /&gt;Claim: Some finite critical magnification(scaling) of this shape exists such that &lt;br /&gt;1.the best packing in it of circles is a hexagonal lattice of circles arranged inside and &lt;br /&gt;2.for any further scaling up of this shape the best pack is the hexagonal pack.&lt;br /&gt;&lt;br /&gt;This implies: If the container is a square, there is some critical size of the square beyond which the best circle packing of unit circles is ALWAYS the hexagonal lattice. &lt;br /&gt;&lt;br /&gt;Some more thoughts on 'automatable' arrangments to follow...&lt;br /&gt;&lt;br /&gt;Update (3rd May 2009): The main guess above is invalid. For the square the hex lattice is tbe best packing only in the asymptotic limit, as the square goes to infinity and is the same as the plane itself. No finite threshold and stuff. This is a bit surprising to me but that is how things probably are!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-2243369660859910685?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/2243369660859910685/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=2243369660859910685' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/2243369660859910685'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/2243369660859910685'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2009/04/doubt-on-circle-packing.html' title='A Doubt On Circle Packing'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-3001480381808042718</id><published>2009-02-13T23:30:00.000-08:00</published><updated>2009-02-13T23:35:13.877-08:00</updated><title type='text'>Fair Partitions - Article</title><content type='html'>After all those 'work in progress' posts on the polygon partitionig problem we posed (a series which went on for well over a year), we collected whatever we thought up into a proper article. It can be read at:&lt;br /&gt;&lt;br /&gt;http://arxiv.org/abs/0812.2241&lt;br /&gt;&lt;br /&gt;Note: The article is on the longer side since we try to develop the themes at a leisurely pace and try to give several illustrative examples. Hope it reads well, and even more importantly, that our arguments are logically tight. Right now, the jury is out...&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-3001480381808042718?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/3001480381808042718/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=3001480381808042718' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/3001480381808042718'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/3001480381808042718'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2009/02/fair-partitions-article.html' title='Fair Partitions - Article'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-5075609108463287580</id><published>2008-09-07T00:43:00.000-07:00</published><updated>2008-10-23T11:50:05.991-07:00</updated><title type='text'>Fair Partitions - 2^N?</title><content type='html'>We (Ramana Rao and self) consider here a recursive scheme for extending our polygon partitioning conjecture to 2^N. This approach is a variant of a naive recursion on N=2, which does not work - as argued in the post 'Fair Partitions -V':&lt;br /&gt;&lt;br /&gt;------------&lt;br /&gt;The conjecture: Given any positive integer N, any convex polygonal region allows partitioning into N convex pieces such that every piece has the same area and perimeter.&lt;br /&gt;------------&lt;br /&gt;&lt;br /&gt;Definitions:&lt;br /&gt;-----------&lt;br /&gt;We define a 'diagonal', as a line that divides a convex polygon into two pieces of equal area; their perimeters could be different (the diagonal could be between any two points on the boundary, not necessarily vertices). &lt;br /&gt;&lt;br /&gt;Let us further call a line which divides a convex polygon into 2 pieces of equal area and equal perimeter a 'fair bisector'. Of course, a polygon can have just one fair bisector ( eg: for an isosceles triangle with very narrow base), a few or even infinitely many (a square for example) depending on its symmetry. &lt;br /&gt;&lt;br /&gt;The Scheme:&lt;br /&gt;----------&lt;br /&gt;Divide input polygon into two equal area pieces by a diagonal; call these pieces A and B. Consider a *fair bisector* of piece A, dividing A into {A1, A2} - where A1 and A2 have equal area and equal perimeter. Likewise consider a fair bisector of B which gives pieces {B1,B2}. Initially, let us say the pair of pieces A1-A2 have higher perimeter than the pair B1-B2.&lt;br /&gt;&lt;br /&gt;Rotate the *diagonal* continously; then, the pieces A and B change continuously maintaining equal areas; the two fair bisector lines also keep changing. Finally the diagonal reaches a position that is perfectly reverse of its initial position. Now, pieces A1-A2 have less perimeter than pair B1-B2 - they have merely exchanged their initial positions. By a continuity argument, we have somewhere along the rotation of the diagonal, a state where the two pairs had the same perimeter.&lt;br /&gt;&lt;br /&gt;This could settle the conjecture for N= 4. Repeating the recursion, we could even prove the claim for N= 2^n. And if the conjecture could be proved for any number m, this could give a ready extension to N= m * 2^n&lt;br /&gt; &lt;br /&gt;Possible Catch:&lt;br /&gt;--------------&lt;br /&gt;It needs to be shown that if a polygon is *continuously changed*, its fair bisector(s) change continuously - by a line segment moving continuously, we mean both its end points move continuously (of course, the length, orientation,etc of the segment as a whole could change).&lt;br /&gt;&lt;br /&gt;Take a square and slightly and continously make it asymmetric, keeping its area constant; the new polygon might have only a few or just one fair bisector. this means most fair bisectors have simply *disappeared* by a continous transformation. &lt;br /&gt; &lt;br /&gt;A more general case:&lt;br /&gt;&lt;br /&gt;Consider a case where the fair bisector of piece A is such that sub-piece A2 covers the bisector entirely, ie. the fair bisector of A connects two edges of the input polygon and does not touch the diagonal which demarkates A and B.&lt;br /&gt;&lt;br /&gt;Now let diagonal rotate a little, continuously, keeping the areas of pieces A and B same.Then, perimeter of piece A2 changes while A1 is *unaffected*. Of course, the areas of A1 and A2 remain equal. The net result: a difference just begins to develop between perimeters of A1 and A2. &lt;br /&gt;&lt;br /&gt;Now, we need to change the fair bisector between A1 and A2 continuously to cancel out the perimeter difference that has emerged (due to the rotation of the diagonal) between A1 and A2. And we need a guarantee that such a continous change is possible for the entire rotation of the diagonal. What we need to prove is: at least one fair bisector of piece A - call this b(A) - and a fair bisector of piece B - call this b(B) - are such that as diagonal moves by a total of 180 degrees, b(A) continuously moves to b(B); a further movement of 180 of diagonal will cause b(B) to return to b(A).&lt;br /&gt;&lt;br /&gt;Note : The new recursive scheme puts a constraint on the fair partitioning, a constraint we were not keen to put: &lt;br /&gt; &lt;br /&gt;A general convex partitioning need not have two pieces meet in the interior of the polygon at 180 degrees - they only need to be convex. &lt;br /&gt; &lt;br /&gt;In the recursive scheme A1 and A2, if they meet in the interior of polygon, are forced to together form an angle of 180 degrees. In the final partitioning, two pieces A1 and A2 together are forced meet the other two pieces along a straight line.&lt;br /&gt;&lt;br /&gt;Update (12-9-08): &lt;br /&gt;----------------&lt;br /&gt;Let us call fair bisectors which are the result of symmetry and which cannot change continuously (and which merely vanish) when a polygon is slightly changed, 'bad bisectors'; those fair bisectors which do change continuously are good ones.&lt;br /&gt;&lt;br /&gt;Our scheme seems to need the following to hold: Given two equal area convex polygons which share an edge (and together form a convex polygon). The number of  'good fair bisectors' of both these polygons are necessarily equal. &lt;br /&gt;&lt;br /&gt;Indeed, if at a given position of a *diagonal*, the two equal area pieces A and B have different numbers of good fair bisectors, we would begin to doubt if one of A can actually continuously change all the way to one of B (as the diagonal does a 180 degree sweep) and vice versa.&lt;br /&gt;&lt;br /&gt;Example:&lt;br /&gt;We could check that the pentagon formed by points:&lt;br /&gt;{(0,0),(6,20),(12,0),(12,-7.947),(12-.92, -19.39075)} has 3 good fair bisectors.&lt;br /&gt;Consider the triangle:&lt;br /&gt;{(0,0),(12-.92, -19.39075),(7,-55.53)}.&lt;br /&gt;This triangle shares an edge with the pentagon, has the same area and together with the pentagon forms a convex polygon.  &lt;br /&gt;=&gt; the common edge is a 'diagonal' of the big polygon formed by the pentagon and triangle. &lt;br /&gt;&lt;br /&gt;Now, the triangle has only one fair bisector =&gt; &lt;br /&gt;some evidence that when the diagonal moves thru 180 degrees, the fair bisectors *need not* evolve continuously throughout the evolution of the diagonal.&lt;br /&gt;&lt;br /&gt;Update (October 22, 2008): &lt;br /&gt;-------------------------&lt;br /&gt;Further experiments have confirmed that the fair bisector(s) of a polygon *may not* evolve continuously as the polygon is continuously deformed (keeping its area constant). But, (crucially!) for this new recursive scheme to work, we do not really need the fair bisectors to keep changing continuously - only the *perimeters of the pieces resulting from the fair bisectors need to change continuously*. In all examples tested so far, the perimeters do change continuously. &lt;br /&gt;&lt;br /&gt;No logical proof yet either that the perimeters of pieces resulting from fair bisection of a polygon necessarily change continuously when the polygon itself is changed continuously. Work in progress...&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-5075609108463287580?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/5075609108463287580/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=5075609108463287580' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/5075609108463287580'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/5075609108463287580'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2008/09/fair-partitions-2n.html' title='Fair Partitions - 2^N?'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-8492388442523837276</id><published>2008-08-28T03:40:00.001-07:00</published><updated>2008-10-21T21:34:00.245-07:00</updated><title type='text'>Fair Partitions: N=3?</title><content type='html'>The conjecture: For any positive integer N, any convex polygon allows partitioning into N convex pieces so that every piece has the same area and same perimeter.&lt;br /&gt;&lt;br /&gt;Our attempt on N=3 case of the conjecture (3 pieces):&lt;br /&gt;----------------------------------------------------&lt;br /&gt;0. Basic Observations:&lt;br /&gt;--------------------------------&lt;br /&gt;Every point P on the plane of *any* convex polygon has the property: For any P on or outside the polygon, we have *2 rays* starting from P which together cut the polygon into 3 pieces of equal area. If P is inside, we can find infinitely many sets of *3 rays* diverging from P which cut the polygon into 3 pieces of equal area. &lt;br /&gt; &lt;br /&gt;Further, if P is in a 2-d region in the interior of the polygon, we can have at least 2 distinct ray triplets diverging from P which divide the polygon into 3 equal area pieces *with two of the pieces also having equal perimeter*.&lt;br /&gt; &lt;br /&gt;1. 'Reflexive polygons'&lt;br /&gt;-------------------------------&lt;br /&gt;- We first look at 'reflexive polygons' ie. convex polygons with at least one reflection symmetry axis (isosceles triangles are the simplest examples of reflexive polygons). &lt;br /&gt; &lt;br /&gt;(Property 1): It is obvious that *every* point on the infinite line containing the reflection axis of  a reflexive polygon is the origin of 2 or 3 rays which divide the polygon into 3 pieces of equal area so that 2 of the 3 pieces also have equal perimeter.&lt;br /&gt; &lt;br /&gt;Experimentally, we note a further property for this axis:&lt;br /&gt;(Property 2): *Some* point(s) on the infinite line containing the reflection axis is the starting point of 2 or 3 infinite rays which divide the reflexive polygon into 3 pieces of equal area and *all three pieces* also having equal perimeter. &lt;br /&gt; &lt;br /&gt;2. General convex polygons:&lt;br /&gt;---------------------------------------&lt;br /&gt;Our approach: We observed above that reflexive polygons allow the type of 3-partitioning we need; next we try to establish a specific structural property holds with no qualitative difference between reflexive and general convex polygons - this property could lead to the required 3-partitioning being possible for general polygons as well.&lt;br /&gt; &lt;br /&gt;For a general convex polygon, we experimentally find that an *infinite continuous polyline* exists, passing thru the polygon, and sharing the Property 1 with the axis of reflexive polygons: *every* point on this polyline is the start of 2 or 3 rays which divide the convex polygon into 3 pieces of equal area so that 2 of the pieces also have equal perimeter.&lt;br /&gt; &lt;br /&gt;Since for the general convex polygon there (experimentally) exists an infinite polyline which shares a crucial property with the axis of refelexive polygons (except that this is a polyline with bends, there appear no qualitative differences), we are led to believe that this infinite curve also has the Property 2, ie some point(s) on this infinite polyline also has 2 or 3 rays diverging which give 3 equal area pieces from the polygon with *all pieces* also having same perimeter. And that is what we need to prove.&lt;br /&gt; &lt;br /&gt;3. Remarks on the 'polyline' for general convex polygons:&lt;br /&gt;---------------------------------------------------------------------------&lt;br /&gt; &lt;br /&gt;The infinite polyline mentioned above for general polygons is not unique. As noted in (0) above, there is a *2-dimensional region* in the interior of the polygon where every point gives at least 2 ray triplets which divide the polygon into 3 equal area pieces with 2 pieces also having same perimeter. So, within this 'core' region, the polyline is not unique. &lt;br /&gt; &lt;br /&gt;We could prove: there exist at least 2 points (say A and B) on the boundary of the general polygon, from where 2 rays diverge dividing the polygon into 3 pieces of equal area with 2 of the pieces also having equal perimeter. And starting at A and B,  we have 'semi-infinite polylines' going *outwards* and tending to diametrically opposite directions at infinity - with all points on these two half-polylines being start points of 2 rays with the same property as points A and B. &lt;br /&gt; &lt;br /&gt;Experiments indicate that *between A and B* we have a continuous, 2-dimensional  'bridge region' thru the interior of the polygon with this property: every point in this bridge has 3 rays diverging from it and dividing the polygon into 3 pieces of equal area and with 2 of the pieces also having same perimeter. Such a bridge will guarantee the continuity of the infinte polyline.&lt;br /&gt;&lt;br /&gt;Note: Such a 2-d bridge region in the interior exists for reflexive polygons as well and the axis passes thru this region.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-8492388442523837276?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/8492388442523837276/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=8492388442523837276' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/8492388442523837276'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/8492388442523837276'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2008/08/fair-partitions-n3.html' title='Fair Partitions: N=3?'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-1987114167471072899</id><published>2007-11-24T01:36:00.000-08:00</published><updated>2007-11-29T00:19:55.362-08:00</updated><title type='text'>Fair Partitions - VII</title><content type='html'>This is a status report on the fair partitioning business.&lt;br /&gt;&lt;br /&gt;First, a bit of speculation. We have been trying to prove the convex fair partitioning conjecture ("given any integer N, any convex polygon allows paritioning into N convex pieces all of equal area and perimeter") for N=3 - ie. fair partitioning into 3 convex pieces.&lt;br /&gt;&lt;br /&gt;In an earlier post, some continuity-based speculations had been floated. Now we think the following could work:&lt;br /&gt;&lt;br /&gt;- There is a *large region* in the plane of the convex polygon (this large region includes a portion of the interior of the plane and also *most* of its exterior), the points P of which satisfy: (1) the polygon can be cut into 3 convex pieces of equal area by 3 rays diverging from P with (2) the extra requirement that one of these rays goes in the +X direction.&lt;br /&gt;&lt;br /&gt;- Call the three resulting equal area convex pieces 1, 2 and 3, measured counterclockwise from the +X direction and their perimeters, P1, P2 and P3.&lt;br /&gt;&lt;br /&gt;- There will be a continuous region in the plane so that for points there (as the sources of the rays) P1 is the greatest (ie. piece 1 has most perimeter), a region where P2 is greatest and likewise for P3. We could label these regions by P1, P2 and P3. &lt;br /&gt;&lt;br /&gt;- We *guess* that from the P1 region we could go continuously either to the P2 region or to the P3 region; likewise from the P2 region we could cross over continously to  P1 or P3 region and likewise for P3 region. This guess implies, there are dividing curves between the regions where P1=P2, P2=P3 and P3=P1 *and also* that these curves are bound to intersect. An intersection point between two of the curves is a meeting point from where 3 diverging rays, with one ray in +X do a convex fair partitioning of the given polygon.&lt;br /&gt;&lt;br /&gt;Note 1: The angles between the rays need not all be less than 180 degrees. The pieces of the convex polygon that result should all be convex. That is all. Moreover, the ray in +X direction from the meeting point need not touch the polygon. &lt;br /&gt;&lt;br /&gt;Note 2: Three such regions where each of P1, P2 and P3 are maximum, are expected to be present at least for one orientation of the polygon with respect to the X axis. That is sufficient for at least one meeting point for the rays and a partitioning of the type we need.&lt;br /&gt;&lt;br /&gt;------------------&lt;br /&gt;Now, we try to explicitly do some special cases of convex fair partitioning.&lt;br /&gt;&lt;br /&gt;A. A regular hexagon into 7 pieces all of equal area and perimeter.&lt;br /&gt;&lt;br /&gt;Consider the 'extreme configurations':&lt;br /&gt;&lt;br /&gt;1. config 1: Hexagon of side 1, kept with a vertex, call this vertex 1 at the bottom and another - this is vertex 4 - at the top. A square (the area of this square has to be 3/7 of the hexagons) kept as a diamond inside the hexagon so that the centers of both coincide and a diagonal coinciding with diagonal 1-4 of the hexagon. The square can be divided into 3 identical rectangles and the rest of the hexagon into 4 identical pentagons. &lt;br /&gt;&lt;br /&gt;In above state, the perimeter of each of the 3 rectangles constituting the central square is 2.81388. The perimeter of the 4 pentagons is 2.92894.&lt;br /&gt; &lt;br /&gt;(the calculation uses the formula area of full hexagon = 6*sqrt(3)/4. and area of square is 3/7 of this and some basic trigonometry).&lt;br /&gt; &lt;br /&gt;2. The other extreme config (config 2)is: Big regular hexagon unchanged.  The square in the middle (appearing as a diamond) is gradually stretched vertically into a rhombus (of course, keeping its area constant)with the longer diagonal eventually coinciding with diagonal 1-4 of the regular hexagon. &lt;br /&gt;&lt;br /&gt;The rhombus has the same area as the square of config 1 from which it is deformed. and the rhombus can be cut into 3 mutually identical parallelograms. the rest of the hexagon outside the rhombus can be obviously cut into 4 mutually identical quadrilaterals. &lt;br /&gt;&lt;br /&gt;In this state, the perimeter of each of the 3 parallelograms which form the inner rhombus is 3.05208. the perimeter of each of the 4 outer pieces is now 2.95382.&lt;br /&gt; &lt;br /&gt;Conclusion: config 2 can be reached by continuously deforming config 1. Throughout the deformation, the inner rhombus gives 3 identical parallelograms and the rest of the hexagon is formed of 4 identical pieces. In config 1, the 3 inner pieces have *lower* perimeter than the 4 outer pieces. In config 2, the 3 inner pieces have *greater* perimeter than the outer pieces. So, by continuity, there is a intermediate state where the perimeters of the two sets of pieces are equal. That settles the regular hexagon into 7 pieces case. If N = 5, the above continuity argument will still work with the square deformed into a rhombus as before but with area 1/5 of the big regular hexagon.&lt;br /&gt;&lt;br /&gt;B. An equilateral triangle into 5 convex pieces:&lt;br /&gt;&lt;br /&gt;Consider an equilateral triangle of side 5 units.We begin by dividing a side of the base AB of the triangle (any side can be the base) into 5 equal parts and connecting the dividing points to the opposite vertex, the apex C. Now, if we number the 5 pieces left to right as 1,2,3,4,5, extreme pieces 1 and 5 have max perimeter and the central piece 3 has least. All pieces have the same area. &lt;br /&gt; &lt;br /&gt;Consider pieces 1 and 2 together as a single large triangular piece. We find that we can divide this piece into two pieces 1' and 2' of equal area and also equal perimeter by a line from a point on its side (segment AC) at a distance 0.4098 from the apex C to a point on the base at a distance 1.0892 from vertex A (basically, original piece 1 has had its base increased from 1 unit and height reduced keeping area constant but so that its perimeter reduces a bit). &lt;br /&gt; &lt;br /&gt;Now, surprisingly, the perimeters of 1' and 2' are found to be exactly equal to that of central piece 3 which has not been touched. The areas of all pieces 1',2' and 3 are anyway equal. The same strategy employed to pieces 4 and 5 together finishes the partitioning.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-1987114167471072899?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/1987114167471072899/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=1987114167471072899' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/1987114167471072899'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/1987114167471072899'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2007/11/fair-partitions-vii.html' title='Fair Partitions - VII'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-4762380564655863662</id><published>2007-08-24T03:00:00.000-07:00</published><updated>2007-08-24T03:21:02.932-07:00</updated><title type='text'>Fair Partitions - VI</title><content type='html'>We countinue on the conjecture: &lt;br /&gt;&lt;br /&gt;"For every positive integer N, any convex polygon allows breaking into N convex pieces so that all pieces have the same area and same perimeter."&lt;br /&gt;&lt;br /&gt;------&lt;br /&gt;We recall the Definitions: Fair partition is a partition of a polygon which leaves all pieces with equal area and perimeter. A convex fair partition is a fair partition where all pieces are also convex.&lt;br /&gt;&lt;br /&gt;We wondered if among all fair partitions possible for a convex polygon, the one with the least total perimeter of pieces - or least length of cuts - is a convex fair partition. But this appears to be *NOT* the case, at least for small N. &lt;br /&gt;&lt;br /&gt;eg: Consider an isoscles triangle with base 1 and altitude 2 (the equal sides are then sqrt 5 each). Join a square of side 1 to the base to form  pentagon. The area of this pentagon is 2 units. Take N = 2. ie we need to break the pentagon into 2 pieces of equal area and perimeter. &lt;br /&gt;&lt;br /&gt;By inspection, the *only* convex fair partition is by the bisector of the apex of the isosceles triangle. And the length of the cut is 3 units. Now, it is possible to have another fair partitioning of the pentagon into one convex and one non convex pieces with cut length just around 1.7 units - considerably less than 3. So, the convex fair partitioning is not the 'best'.&lt;br /&gt;&lt;br /&gt;The reason for considering the above line of thought was this: if somehow one can prove that for any non convex fair partitioning, there is always a better fair partitioning (better means one with less total of cut lengths) that can be achieved by tweaking one of the non convex pieces (and the remaining portion of the input polygon), we could have argued: "There definitely has to be *some* fair partitioning that has the least total of cut lengths. If any non convex fair partitioning can be improved, the fair partitioning with least cut lengths has to be one with no non convex pieces. This establishes the existence a convex fair partition thus proving the original conjecture". &lt;br /&gt;&lt;br /&gt;But things do not appear to be so simple!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-4762380564655863662?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/4762380564655863662/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=4762380564655863662' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/4762380564655863662'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/4762380564655863662'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2007/08/fair-partitions-vi.html' title='Fair Partitions - VI'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-7602861309313472147</id><published>2007-07-27T03:35:00.000-07:00</published><updated>2008-09-07T01:15:16.463-07:00</updated><title type='text'>Fair Partitions - V</title><content type='html'>Here is a bit more on the conjecture we had formulated a while ago:&lt;br /&gt;"For every positive integer N, any convex polygon allows breaking into N convex pieces so that all pieces have the same area and same perimeter."&lt;br /&gt;&lt;br /&gt;The news is that it has been listed as an open problem (with rather different wording) at &lt;a href="http://maven.smith.edu/~orourke/TOPP/P67.html#Problem.67"&gt;http://maven.smith.edu/~orourke/TOPP/P67.html#Problem.67&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;We have two more small findings (tentative) to report:&lt;br /&gt;1. For any N, any convex polygon can be divided into N convex pieces all of equal perimeter (not looking at their areas) by a family of suitably spaced parallel lines of any orientation =&gt; there are infinitely many ways of cutting the convex polygon into N convex pieces of equal perimeter - just like there are infinitely many ways to cut it into N convex pieces of equal area. This appears to add strength to the conjecture.&lt;br /&gt;&lt;br /&gt;2. We made the following proposition: Given two convex polygons P and Q of equal area and perimeter *which together form another convex polygon*. Let P be cut into P1 and P2 where the two pieces have equal area and perimeter and Q, similarly into Q1 and Q2. We can have some pair of partitionings which make P1, P2, Q1 and Q2 all of same area and perimeter.&lt;br /&gt;&lt;br /&gt;If this proposition can be proved, the main conjecture can be proved for N = any power of 2.&lt;br /&gt;However, it appears that the above proposition is not necessarily true, at least as far as we can make out. So, the conjecture retains its mystery.&lt;br /&gt;&lt;br /&gt;------------------------------------------------------------------------------------&lt;br /&gt;Apparent Failure of N=2 to *recursively* generalize to N = 2^N in a straightforward manner&lt;br /&gt;------------------------------------------------------------------------------------&lt;br /&gt;Example: &lt;br /&gt;------------&lt;br /&gt;- Polygon P1 is an isosceles triangle with a narrow base. &lt;br /&gt;- Polygon P2 is a *trapezium* with same base length and one base angle equal to 90 degrees. P2 also has slightly less 'height' than the triangle P1; we can now adjust its other sides so that both P1 and P2 have same area and perimeter. &lt;br /&gt; &lt;br /&gt;- Now, consider the large convex polygon P formed by joining P1 and P2 along their bases. &lt;br /&gt; &lt;br /&gt;We find that P has exactly *3 bisections* so that the 2 resulting pieces have both equal area and perimeter (the obvious parition into P1 and P2 themselves plus 2 other partitions). In the specific numerical example we tried, *none of these 3 bisections* seems to give two pieces, which when  bisected further gave 4 resultant convex pieces all with same area and perimeter - the final 4 pieces all have same area but their perimeters always come in 2 mutually different pairs.&lt;br /&gt; &lt;br /&gt;A specific numerical case: &lt;br /&gt; &lt;br /&gt;P1, the triangle has vertices: (0,0), (6, 20), ( 12, 0);&lt;br /&gt;P2, the trapezium has vertices: (0,0), ( 12, 0), ( 12, &lt;br /&gt;-18.992), ( 11.3631,-18.992);&lt;br /&gt; &lt;br /&gt;For large polygon P, formed by joining P1 and P2 along (0,0) - (12,0), we find P can be cut into 2 convex pieces of equal area and perimeter in 3 different ways.&lt;br /&gt; &lt;br /&gt;- by the the obvious line joining (0,0) and (12,0)&lt;br /&gt;- the line joining (0.50602,1.68673) and (12, -1.76073).&lt;br /&gt;- the line joining (2.50594,-4.18836) and (10.5974,4.67521).&lt;br /&gt; &lt;br /&gt;We considered each of these 3 bisections of P and looked at further bisections of the 2 resulting pieces. Numerically, in none of these cases could we find 4 resultant pieces all of same area and perimeter.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-7602861309313472147?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/7602861309313472147/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=7602861309313472147' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/7602861309313472147'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/7602861309313472147'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2007/07/cutting-shapes-v.html' title='Fair Partitions - V'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-8503417883304354343</id><published>2007-06-09T02:18:00.000-07:00</published><updated>2008-11-05T20:57:30.092-08:00</updated><title type='text'>Fair Partitions - IV</title><content type='html'>After a longish gap, we continue on the conjecture:&lt;br /&gt;"For every positive integer N, any convex polygon allows breaking into N convex pieces so that all pieces have the same area and same perimeter."&lt;br /&gt;&lt;br /&gt;1. Proof for N=2 (easy, although full of English)&lt;br /&gt;------------------------&lt;br /&gt;*Any* point on the perimeter of the convex polygon P, there is another point Q (call this the 'opposite point to P1') so that the line P-Q (direction important) divides the polygon into two equal area convex pieces. the two pieces will in general have different perimeter.&lt;br /&gt;&lt;br /&gt;Let us begin with a specific point P1 on the boundary - its opposite point is P2. say, the equal area piece to left of cut line P1-P2 has greater perimeter.&lt;br /&gt;&lt;br /&gt;Now, we move P1 along the perimeter (clockwise, say, does not matter which way). the opposite point P2 also moves in the same direction around the perimeter. Obviously when P1 reaches the initial position of P2, P2 will be at the initial position of P1. and now, the half area piece to the *right* of P1-P2 has greater perimeter, the opposite to what we started with. In other words, the difference between the perimeters of the two equal area pieces has changed sign.&lt;br /&gt;&lt;br /&gt;So, assuming the perimeters of the two pieces change continuously (obvious), we have some position in between when the two equal area pieces of the polygon also will have equal perimeter - when the difference between perimeters is zero.  QED.&lt;br /&gt;-----------&lt;br /&gt;2. The following 'restrictive sequential' approach  will not work in general for general N:&lt;br /&gt;&lt;br /&gt;First cut a convex piece off *leaving behind a convex piece*. Then break a convex piece of same perimeter and area off the remaining piece, again leaving behind a convex piece. Repeat the process N-1 times.&lt;br /&gt;&lt;br /&gt;eg: If a circular disc is to be broken into 3 pieces of equal area and perimeter (N=3), *if the first cut should leave behind a convex piece*, the first cut is necessarily a chord which breaks off 1/3 area of the disc. Now, it appears the remainder can be broken into two pieces with mutually equal area and perimeter *only* by making them congruent (identical) to each other. There is only one way of doing so and the resulting two pieces won't have the same perimeter as the piece broken first.&lt;br /&gt;-------------&lt;br /&gt;3a: A special case. N=3, the input polygon is a square.  Here we arrive at a solution different from the obvious one of "two parallel cut lines". This approach led us to the claims set out in case 3b below.&lt;br /&gt;&lt;br /&gt;We look at two extreme cases. (1) Consider two cut lines parallel to a *diagonal* of a square and equally spaced with respect to that diagonal (call this diagonal AB) and which cut the square into 3 equal area pieces. The middle piece is now a flat hexagon and the two *congruent* outer pieces are triangles. We note that the middle piece has more perimeter than the outer ones.&lt;br /&gt;&lt;br /&gt;(2) Now choose an end point of the above diagonal, say A. Slide the end points of both cut lines which lie nearer to A,  towards A. We simultaneously adjust the cut lines so that the two outer pieces and the middle piece continue to have equal area (and also keeping the outer pieces mutually identical so these two pieces continue to have equal perimeter). The ends of the cuts eventually meet at point A. Now, the merge the end points which have met and continue move them together along diagonal AB towards B. The middle piece now is a quadrilateral and the side pieces also have become quadrilaterals. Finally a configuration is reached when the middle piece is a *square* of side a/sqrt(3) and the side pieces are two mutually identical trapeziums. At this point, the middle piece has *less* perimeter.&lt;br /&gt;&lt;br /&gt;Since we have changed the cuts continuously, the perimeters of the pieces must have changed continuously. And the perimeter of the middle piece, initially greater than the other two has changed to be less. So, in between, there is some position where the perimeter of the middle piece equalled that of the two side pieces.&lt;br /&gt;----------------&lt;br /&gt;&lt;br /&gt;3b. Thoughts on the N=3 case (this is tentative and might be knocked out by a counter; still am documenting our thoughts, for completeness). We present a chain of claims:&lt;br /&gt;&lt;br /&gt;- From any point on the boundary of a convex polygon, we can draw two diverging lines which divide the polygon into 3 equal *area* pieces (obvious).&lt;br /&gt;&lt;br /&gt;Consider a point P on the boundary of a convex polygon and the three equal area pieces generated by diverging lines starting at that point. We number the three pieces 1,2,3 in say, clockwise order as viewed from P.&lt;br /&gt;Claim 1:  we can always find at least one P on the boundary of the input polygon so that the 'outer' equal area pieces *1 and 3* will also have equal perimeter.&lt;br /&gt;&lt;br /&gt;Note: there are convex polygons for which the middle piece 2 never has same perimeter as the others - for example a circle. And we *do not* look at diverging lines which yield same perimeter for pieces 1 and 2 and a different value for piece 3.&lt;br /&gt;&lt;br /&gt;Claim1 is provable from continuity.&lt;br /&gt;&lt;br /&gt;- Now, we stand at a point P so that two lines diverging into the polygon divide the polygon into three equal area pieces and pieces 1 and 3 have same perimeter. now, consider the two fan shaped regions formed by the two cuts (the interior of piece 2 and its opposite region in the exterior of the polygon).&lt;br /&gt;&lt;br /&gt;Claim 2: we always have a curve (maybe even a line) passing thru P and extending into the two fan shaped regions meeting at P so that from every point on this curve, we can have a Y formed by three cut lines meeting inside the polygon (if the point is inside polygon) or a V (if outside) so that all pieces are convex and the pieces 1 and 3 continue to have equal perimeter - ie. a curve along which the perimeter of peces 1 and 3 vary equally from their value at P (and all continue to be convex and also have same area). We are not sure about claim 2 although it looks correct due to the convexity of the input polygon and the way we have chosen P.&lt;br /&gt;&lt;br /&gt;Claim 3: The two values of the perimeters ({p(1) and p(3)} and {p(2)} vary continuously }on the curve described in claim 3, and there will always a point so that all the 3 perimeters are the same. That is all.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-8503417883304354343?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/8503417883304354343/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=8503417883304354343' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/8503417883304354343'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/8503417883304354343'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2007/06/cutting-shapes-iv.html' title='Fair Partitions - IV'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-7299956729710048093</id><published>2007-04-19T04:42:00.000-07:00</published><updated>2007-12-13T23:37:37.075-08:00</updated><title type='text'>A Different 'Center' To A Polygon</title><content type='html'>In the last post here, we pondered (without nailing to the wall), the problem of finding the point inside a convex polygon which maximizes the minimum angle subtended there by the edges of the polygon. Now, we have something else on similar lines.&lt;br /&gt;&lt;br /&gt;Problem: Given a convex polygon, find the point in its interior for which the sum of distances to the vertices of the polygon is least.&lt;br /&gt;&lt;br /&gt;Thoughts: The required point need not be the centroid of the polygon.&lt;br /&gt;---------&lt;br /&gt;Example. consider a convex polygon formed by (1) 100 points extremely close to each other - so close that they are separate only at near infinite zoom - near the point x=-1 on the X axis, (2) another 100 points similarly close to each other but near the point x = +1 on the X axis and (3) a single point on the Y axis at Y = 201. Of course, the close by points lie so that the total set of 21 points form a convex polygon - from a distance this polygon looks like a triangle though.&lt;br /&gt;&lt;br /&gt;Now, the centroid of this polygon is very close to a point on Y axis: y = +1. this centroid is at a distance 200 from the lone apex point and nearly sqrt(2) distant from the other 200 points. Now, consider the mid point of the base of the polygon, lying between the two point bunches at x = +/-1. This mid point is at distance 201 from the lone apex point but only at distance equal to nearly 1 from the other 200 points. Its distance sum is clearly less than that of the centroid.&lt;br /&gt;&lt;br /&gt;------------&lt;br /&gt;&lt;br /&gt;It might be interesting to see how this distance sum function varies across the region of the polygon in various cases. If I understand right, Earnshaw's theorem probably implies Sum (reciprocals of distances from vertices) has no proper minimum in the interior (only saddle points). Maybe something similar could be said about the distance sum as well.&lt;br /&gt;&lt;br /&gt;Note added on May 23rd: Earnshaw's theorem is, as far as I know, a consequence of the electrostatic potential satisfying Laplace equation. The present problem has a potential that increases linearly with distance from the 'charge' and this *does not* satisfy Laplace equation. Hence there can very well be local maxima and minima for the distance sum function in the interior of the polygon. I know of no case where the *maximum* of the (sum of distances from vertices) is somewhere in the interior of the convex polygon - here we look at only the interior of the polygon and its boundary, not exterior.&lt;br /&gt;&lt;br /&gt;Note added on July 5th 2007: Experiments indicate that the point which minimizes the sum of distances from the vertices has a unique position (there are no local minima etc for this distance sum function) . This appears true not only when the vertices are those of a convex polygon - any distribution of points (call them vertices)appears to have this property: a unique point minimizes the sum of the distances from these vertices.&lt;br /&gt;&lt;br /&gt;And here is some further perspective from 'Mathworld':&lt;br /&gt;"A convex function is a &lt;a class="Hyperlink" href="http://mathworld.wolfram.com/ContinuousFunction.html"&gt;continuous function&lt;/a&gt; whose value at the &lt;a class="Hyperlink" href="http://mathworld.wolfram.com/Midpoint.html"&gt;midpoint&lt;/a&gt; of every &lt;a class="Hyperlink" href="http://mathworld.wolfram.com/Interval.html"&gt;interval&lt;/a&gt; in its &lt;a class="Hyperlink" href="http://mathworld.wolfram.com/Domain.html"&gt;domain&lt;/a&gt; does not exceed the &lt;a class="Hyperlink" href="http://mathworld.wolfram.com/ArithmeticMean.html"&gt;arithmetic mean&lt;/a&gt; of its values at the ends of the &lt;a class="Hyperlink" href="http://mathworld.wolfram.com/Interval.html"&gt;interval&lt;/a&gt;."&lt;br /&gt;This implies a convex function has to have at most one local minimum in its domain. I remember hearing that distance is a convex funtion (not sure about the proof) and probably, so is the sum of distances. Thus, we could say:&lt;br /&gt;"Given a distribution of vertices on a plane and a point P which varies along any straight line. The sum of the distances from P to the vertices has a unique minimum on its straight line path.  And since for P running along *any* straight line path in that plane, the distance sum function has a unique minimum, the function has to have a unique minimum *for the plane as a whole*.&lt;br /&gt;&lt;br /&gt;Note added on December 12th: If the input polygon is a triangle, this problem is called the Fermat's problem. In this special case, the solution also solves the Steiner tree problem. Coxeter has described this special case in his 'Intro to Geometry' and proved the point is such that all the 3 sides of the triangle subtend 120 degrees there. And this wikipedia article has more details: http://en.wikipedia.org/wiki/Geometric_median&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-7299956729710048093?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/7299956729710048093/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=7299956729710048093' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/7299956729710048093'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/7299956729710048093'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2007/04/different-center-to-polygon.html' title='A Different &apos;Center&apos; To A Polygon'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-2602860411373390521</id><published>2007-04-05T03:14:00.000-07:00</published><updated>2007-07-06T00:35:32.795-07:00</updated><title type='text'>A Triangulation Problem</title><content type='html'>The following problem was posed by Anurag. Thanks to Ramana Rao for his inputs.&lt;br /&gt;&lt;br /&gt;--------&lt;br /&gt;Given a convex polygon, how does one choose a point in its interior so that the least angle subtended at this point by the edges of the polygon is a maximum?&lt;br /&gt;--------&lt;br /&gt;Our present line of thought is:&lt;br /&gt;1. Choose a variable point, say P at any location in the interior of the polygon and note the smallest angle subtended by the sides there. Note this side as S.&lt;br /&gt;2. Move P towards this side S - so that the angle subtended by S at P keeps increasing, until the angle subtended by another side S' at the current point equals that subtended by S. Note the present position of P.&lt;br /&gt;3. Now we need to further search in the intersection region of two circles - C passing thru the end points of S and P and circle C', that passes thru the end points of S' and P. Of course during this further search, we also need to see if any other edge of the polygon S'' subtends a smaller angle than S and S'.&lt;br /&gt;&lt;br /&gt;The two circles intersect at another point apart from P, say P'. It appears that the best position of the point we need is not necessarily on the line joining P and P' (if we understand right, the reason is related to the locus of points at which two line segments subtend equal angles not being a straight line and being apparently governed by a higher degree polynomial) . So, we might need to search exhaustively the intersection region of the two circles.&lt;br /&gt;&lt;br /&gt;To sum up, we do not know the best possible answer and the above method may be seriously flawed!&lt;br /&gt;&lt;br /&gt;Note added on July 5th 2007: Experiments indicate that maximizing the minimum angle subtended by the edges of the polygon leads to a unique optimal point. In other words, the function: "minimum among the angles subtended by the edges of the polygon" has a very regular behavior in the interior of the polygon and a single maximum.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-2602860411373390521?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/2602860411373390521/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=2602860411373390521' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/2602860411373390521'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/2602860411373390521'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2007/04/triangulation-problem.html' title='A Triangulation Problem'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-117024358188773472</id><published>2007-01-31T03:19:00.000-08:00</published><updated>2007-04-18T22:25:46.788-07:00</updated><title type='text'>An Optimized Road Network</title><content type='html'>Problem:&lt;br /&gt;Consider a 2D region - it could be as simple as a square.&lt;br /&gt;&lt;br /&gt;We are interested in laying out a network of roads (idealized as lines and polylines) in this region, satisfying the following requirements:&lt;br /&gt;&lt;br /&gt;---------&lt;br /&gt;0. The road network should be fully connected; there is one single network for the domain, no separate webs.&lt;br /&gt;&lt;br /&gt;1. No point in the territory should be farther from the nearest point on *some* road by a given number 'a'. This is to ensure good penetration of the domain by the road network - no remote areas. Let us call 'a' the 'penetration constant'.&lt;br /&gt;&lt;br /&gt;2. If A and B are two points which lie ON some roads in the network, and if we use the road network to travel from A to B, the total distance we move along the roads should not be more than the straight line distance from A to B by some given factor, say 'f' (*). This condition tries to ensure a minimum of 'intra-connectivity' in the network - it should be sufficiently cross-wired. Let us call 'f', the 'intra-connectivity factor'.&lt;br /&gt;&lt;br /&gt;3. Yes; the road network should have the least possible total length.&lt;br /&gt;---------&lt;br /&gt;(*)Note: If A and B in the given region but not necessarily on the roads, we could follow the following protocol to reach B from A.&lt;br /&gt;a) Find a road near to A and reach a suitable point on that road from A&lt;br /&gt;b) Traverse the network of roads available optimally so that we reach B or very near B.&lt;br /&gt;c) Leave the network and move to B.&lt;br /&gt;A condition similar to #2 could perhaps be formulated in this case.&lt;br /&gt;---------&lt;br /&gt;The problem was inspired by the following question which opened the Landmark Pune Quiz 2007:&lt;br /&gt;"Which Indian state has the largest length of surfaced roads?"&lt;br /&gt;&lt;br /&gt;Update on April 5th 2007:&lt;br /&gt;--------------------------&lt;br /&gt;This is following some further thinking aided by a comment from Anurag.&lt;br /&gt;&lt;br /&gt;1. It now appears that condition #3, the intra-connectivity requirement, should apply only for points on the network which are sufficiently far apart (their straight line separation should be greater than the penetration constant 'a' or 2*a). For points much less than 'a' apart, there can always be network distances 2* their straight line distance, (or sqrt(2)* straight distance) however dense the network is.&lt;br /&gt;&lt;br /&gt;2. The road network can have open ends - especially near corners of the territory. This does not anyway spoil the connectivity.&lt;br /&gt;&lt;br /&gt;3. It now appears that the penetration requirement can be achieved by forming *successive insets* of the boundary of the region - each successive inset is by twice the penetration distance 'a'. (Note: From the first inset of the boundary, we need to have open end roads running towards the vertices of the region until they reach a point distant a from the vertex) .  Intuitively, it appears that these successive insets, suitably interconnected to ensure the intra-network connectivity would actually achieve the least lengthy network. The *suitable* interconnections might involve tricky details - but that these have to be between progressively and predictably shrinking polygons should simplify things.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-117024358188773472?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/117024358188773472/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=117024358188773472' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/117024358188773472'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/117024358188773472'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2007/01/optimized-road-network.html' title='An Optimized Road Network'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-116132551195457783</id><published>2006-10-19T23:11:00.000-07:00</published><updated>2008-10-21T21:48:08.510-07:00</updated><title type='text'>Fair Partitions - III</title><content type='html'>This is the third part of the present trip of partitioning *convex* polygons into equal area pieces with additional constraints.&lt;br /&gt;&lt;br /&gt;We (Ramana Rao and self) make an attempt to solve a specific case of the larger problem - to split a triangle into 3 convex pieces with equal area and perimeter.&lt;br /&gt;&lt;br /&gt;After this attempt, I tend to believe: if we are to partition a convex polygon into convex pieces with equal area using the *least total length of cuts*, the resulting pieces need not all be of the same perimeter (just a guess). It is well-known that if all we need are equal area pieces with least total length of cuts, the pieces need not even be convex. So, one could also wonder if insisting on the pieces having same perimeter *and* same area and also that the total length of cuts is to be minimized, we are guaranteed convex pieces.&lt;br /&gt;&lt;br /&gt;------------------&lt;br /&gt;Cutting a triangle into 3 pieces of equal area and perimeter:&lt;br /&gt;------------------&lt;br /&gt;&lt;br /&gt;Here we try to deal mainly with long and thin triangles. For reasonably 'fat' ones - those with all three angles comparable, things could be easier - for an equilateral triangle, it is trivial.&lt;br /&gt;Note: Of course, my feeling is that what follows works for ALL triangles! But, even for thin triangles, I am not sure if the approach is *not an overkill*!&lt;br /&gt;&lt;br /&gt;--------&lt;br /&gt;A simple specific example or the argument:&lt;br /&gt;Dividing an equilateral triangle into 3 pieces with same area and perimeter.&lt;br /&gt;&lt;br /&gt;Let one side of the input equilateral triangle T be the base and its opposite vertex, the apex.&lt;br /&gt;&lt;br /&gt;1. The input equilateral triangle T is initially divided into three equal area pieces with apexes meeting at the apex of T and each having base = 1/3 of the input T. Obviously the two side pieces have greater perimeter than the middle piece.&lt;br /&gt;&lt;br /&gt;2. Slide down the apexes of the side triangles until they both reach a height 2/3 of the altitude of T. Simultaneously, increase the base of both side pieces at the expense of the middle piece until the middle piece just has one point on the base of T. ie. the bases of both the two side pieces have increased by a factor of 3/2 from their initial value. Now, it is easy to see that the areas of the three pieces (the two side pieces which are now  triangles and the middle piece which is a quadrilateral) are all equal. Crucially, the middle piece now has greater perimeter than the two side pieces.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;3. Note that at the initial point in the sliding, the middle piece had less perimeter and at the end, the middle piece has more perimeter. So somewhere in the middle, the perimeters all have to necessarily equal since intuitively, at every intermediate stage of the sliding process, we can have equal areas for all the three pieces - a pentagon (the middle piece) and two triangles.&lt;br /&gt;&lt;br /&gt;This approach has not given us the obvious way to divide an equilateral triangle into three congruent isosceles triangles (which meet at the centroid of the equilateral triangle) but gives an intro to the general argument below&lt;br /&gt;&lt;br /&gt;-------&lt;br /&gt;&lt;br /&gt;For a general triangle.&lt;br /&gt;&lt;br /&gt;1.  Identify the shortest side of the given triangle and make it the 'base' of the triangle. The angles at the end of the base will be called base angles; the vertex opposite to the base will be called 'apex'. Note: the base perhaps need not be the shortest side, but things appear clearer with such an assignment.&lt;br /&gt;&lt;br /&gt;Divide the base into three equal portions. Connect the ends of the three portions to the opposite vertex with lines. Now, the triangle has been divided into three equal area triangular pieces - with different perimeters (in general).&lt;br /&gt;&lt;br /&gt;2. Now among the three pieces, identify the piece with least perimeter. This will either be (case i) the middle piece (if the two base angles are both less than 90) or (case ii)one of the end pieces (if one base angle is obtuse).&lt;br /&gt;&lt;br /&gt;We now try to reduce the perimeters of the other two pieces while keeping the areas of all 3 pieces constant. The above two cases are treated separately. Note: In both cases, the apexes of all the three equal area pieces *initially* coincide with the apex of the input triangle.&lt;br /&gt;&lt;br /&gt;Case (i): We increase slightly the bases of the two side pieces (these have more perimeter). This base increase is at the expense of the middle piece.  Now, to keep the areas of the side pieces constant, their altitudes would have to be reduced by a greater extent. This we do by sliding the apexes of these two side pieces down along the two sides (other than the base) of the input triangle - thus converting the middle piece into a pentagon. It is clear that the perimeters of the two side pieces reduce considerably whereas the middle piece which originally had least perimeter would slightly increase its perimeter - at any rate the perimeter of the middle piece does not decrease as fast as that of the side pieces. It looks,  by this process, the perimeters of all three pieces can be equalized - the result will be a two triangles and a pentagon in the middle.&lt;br /&gt;&lt;br /&gt;Case (ii): In this case, one end piece has the largest perimeter, the middle piece will have the second largest perimeter and the other end piece will have least perimeter. We could convert the end piece with the largest perimeter into a triangle with slightly larger base and a much reduced altittude and hence perimeter - the altitude reduction will be by sliding the apex of this piece down the longest side of the input triangle. The middle piece has now become a quadrilateral. We now increase the base of the middle piece (both base increases we have done are at the expense of the base of the end piece which originally had least perimeter) and slide its highest vertex down the longest side of the input triangle. Thus the middle piece, originally an obtuse triangle, turns into a shorter and fatter quadrilateral with same area - and less perimeter. The end piece with originally least perimeter now turns into a quadrilateral with slightly narrower base but with perimeter slightly increased. The resulting pieces in this case are two quadrilaterals and a triangle.&lt;br /&gt;&lt;br /&gt;Thus, it appears that in both cases, we can reduce the perimeter of the pieces which have more perimeter,  and get the perimeters of all three pieces to equalize. I hope this exhausts all possibilities.&lt;br /&gt;&lt;br /&gt;Generalization(?)&lt;br /&gt;-----------------&lt;br /&gt;And assuming the above argument is correct and complete, it also indicates how to cut a triangle into *N* pieces all with equal area and perimeter. We put N-1 equally spaced points on the base and form N equal area triangular pieces by connecting these points with the apex. Now, the perimeters of the triangles, in a left to right order either&lt;br /&gt;(1) begins with a high value, steadily decreases and again increases to another maximum - this is for both base angles are less than 90 or&lt;br /&gt;(2)begins with the highest (or lowest) value and steadily reduces (or increases) to a minimum (or maximum) value - when one base angle is obtuse.&lt;br /&gt;&lt;br /&gt;Both cases, which are essentially analogous to the case (i) and (ii) treated above, appear to admit similar solutions by similar sliding of vertices. Case (i) will lead to two triangles at the ends, a pentagon in the middle containing the apex, and the rest of the pieces are quadrilaterals. Case (ii) yields a triangle at an end and all other pieces will be quadrilaterals.&lt;br /&gt;&lt;br /&gt;The above are only plausibility arguments, not conclusive proofs. More to understand; and of course, this whole line of thinking can be demolised by a single well-aimed 'counter-punch'!&lt;br /&gt;&lt;br /&gt;Update (October 22, 2008):&lt;br /&gt;--------------------------&lt;br /&gt;Some experimental work was done on the above 'sliding vertices' proposal. We tried to fair partition *right triangles* into N pieces for various N. The output is not conclusive.&lt;br /&gt;&lt;br /&gt;For example, an isosceles right triangle with base - 10 units and along +X axis and altitude  - 10 units along +Y, we could find fair partitions for up to N=10. If the base and altitude are not equal, the larger of the two could be taken as the base and we could go on for larger values of N - upto 20 and even more depending on the ratio between the sides. But evidence points to: for arbitrarily large N, merely sliding the vertices along the hypotenuse and base (with no cutlines meeting in the interior of the input triangle) might not suffice. Further work is in progress.&lt;br /&gt;&lt;br /&gt;A specific example: base 10, altitude 10. 8 pieces required.&lt;br /&gt;&lt;br /&gt;X coordinates of the cutline ends on the hypotenuse: 0.000000 0.095000 0.284853 0.553162 0.898463 1.335723 1.884090 2.708066 &lt;br /&gt;&lt;br /&gt;X coordinates of the cutline ends on the base: 0.000000 1.166078 2.280096 3.384029 4.506422 5.671883 6.919630 8.285777 &lt;br /&gt;&lt;br /&gt;Details of the 8 resulting pieces:&lt;br /&gt;&lt;br /&gt;perimeter: 21.263170 area: 6.250000&lt;br /&gt;perimeter: 21.263170 area: 6.250000&lt;br /&gt;perimeter: 21.263170 area: 6.250000&lt;br /&gt;perimeter: 21.263170 area: 6.250000&lt;br /&gt;perimeter: 21.263170 area: 6.250000&lt;br /&gt;perimeter: 21.263170 area: 6.250000&lt;br /&gt;perimeter: 21.263170 area: 6.250000&lt;br /&gt;perimeter: 21.207162 area: 6.250001&lt;br /&gt;&lt;br /&gt;(the 8th piece has a slightly different perimeter. fine-tuning the position of the cutlines can achieve arbitrarily closer equality.)&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-116132551195457783?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/116132551195457783/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=116132551195457783' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/116132551195457783'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/116132551195457783'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2006/10/cutting-shapes-iii.html' title='Fair Partitions - III'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-116098044538623299</id><published>2006-10-15T23:26:00.000-07:00</published><updated>2007-08-19T23:00:32.278-07:00</updated><title type='text'>'Fair Partitions' - II</title><content type='html'>Here we propose a proof for a weaker version of the claim floated in the last post here: Any convex polygon, for any N, can be partitioned into N equal area and equal perimeter pieces, *if the pieces need not be convex*.&lt;br /&gt;&lt;br /&gt;-----------------&lt;br /&gt;Proof for possibility of partitioning a convex polygon into N equal area and perimeter pieces which need not themselves be convex:&lt;br /&gt;-----------------&lt;br /&gt;1. We first divide the input polygon into N equal area pieces so that exactly 1 'inner' piece *does not* touch the boundary and each of the remaining N -1 pieces share some *finite* boundary with this inner piece (and also divide up the outer boundary of the input polygon among them). We argue how this can always be done a little later.&lt;br /&gt;&lt;br /&gt;2. Now, we could deform the common boundary of the inner piece with each of its N-1 neighbors to make all N-1 neighbors have the same perimeter.&lt;br /&gt;&lt;br /&gt;If two pieces share an edge, if we introduce some zigzags (with concavities) on that edge, the perimeter of both pieces increase by the same amount - and we can do this without changing their areas. So we note among the  N-1 outer pieces, which has the highest perimeter and increase the perimeters of each of the other N-2 outer pieces to this value - by tweaking the  common boundary of each of them with the inner piece.&lt;br /&gt;&lt;br /&gt;3. Now, all outer pieces have same area and same perimeter. The inner piece also has the same area but a possibly very large perimeter since its boundaries with all outer pieces (except one) have been deformed. We now try to increase the perimeter of all outer pieces to equal this large value.&lt;br /&gt;&lt;br /&gt;We note the difference between the perimeter of the inner piece and that of an outer piece  - call this quantity d. Then we deform *all* the boundaries between the outer pieces - ie the dividing boundary between outer piece 1 and 2, then the boundary between 2 and 3 and so on - so that the increase in perimeter to both the pieces separated by a given boundary is d/2. So, when all boundaries have been deformed, every outer piece increases its perimeter by d - their areas should be kept constant - which is as desired.&lt;br /&gt;&lt;br /&gt;Exception: If after step 2, the inner piece still has *less perimeter* than the common value of the perimeters of the outer pieces, we could tweak the boundary of the input piece with each of the outer ones equally so that every outer piece gains a little perimeter and the innter piece gains N-1 times that much so we could again equalize the perimeters.&lt;br /&gt;&lt;br /&gt;A bit remains: how to divide the input convex polygon into N equal area pieces so that one piece is in the middle and the remaining N-1 surround it? For this, we could scale the input polygon by a factor of N and the resulting small polygon can be put somewhere inside the input polygon (this scaling will work if the input polygon is convex). This is the central piece. Then we can walk around the central piece and sweep out N-1 equal area pieces from the remaining 'annular' portion of the input polygon. These N-1 outer pieces are free to be be concave so we could force each of these to share a finite boundary with the inner piece.&lt;br /&gt;&lt;br /&gt;Remarks:&lt;br /&gt;-------&lt;br /&gt;&lt;br /&gt;Obviously, this approach can cause all the pieces to have  very large perimeters and they will also have jagged boundaries.  No attempt has been made to minimize the sum of the perimeters of the pieces, which remains to be understood.&lt;br /&gt;&lt;br /&gt;We can't see how this argument can be modified to handle the case where the pieces have also to be convex. But this argument does appear to allow us to prove this: "for any N, any (non-convex) polygon can be broken into (non-convex) N pieces all of equal area and perimeter" - the only new idea is to put an thinned down - almost insetted - polygon of area 1/N of the target polygon in the interior of the target (the thinned polygon will be of the same basic skeletal shape as the target and much thinner and will run along the entire length of the target; intuitively, such a polygon can always be found with the required area) - This skeletal polygon will serve as the central polygon in the above proof. The rest of the proof should go thru unchanged. Of course, now we have the question: how to partition a general polygon into general pieces of equal area and equal perimeter *minimizing the perimeter of each*?&lt;br /&gt;&lt;br /&gt;---------&lt;br /&gt;For the case when the pieces also have to be convex (the full version of the claim), we tried to find counter-examples like 'dividing a triangle into 5 convex pieces with equal area and perimeter' - no progress yet on that front.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-116098044538623299?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/116098044538623299/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=116098044538623299' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/116098044538623299'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/116098044538623299'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2006/10/cutting-shapes-ii.html' title='&apos;Fair Partitions&apos; - II'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-115945249634089917</id><published>2006-09-28T06:57:00.000-07:00</published><updated>2007-08-25T01:30:59.031-07:00</updated><title type='text'>'Fair' Partitions</title><content type='html'>Let us (N. Ramana Rao and self) float yet another geometric conjecture&lt;br /&gt;&lt;br /&gt;****&lt;br /&gt;Given any convex shape and any positive integer N. There exist some way(s) of partitioning this shape into N convex pieces so that all pieces have equal area and equal perimeter.&lt;br /&gt;****&lt;br /&gt;&lt;br /&gt;Note: We could define the 'fair partition' of a polygon as a partition into pieces of equal area and perimeter and further, a 'convex fair partition' as a fair partition in which the pieces are also convex. The claim above could be restated as: "for any N, any convex shape allows convex fair partitioning into N pieces".&lt;br /&gt;&lt;br /&gt;If the claim is indeed true, how could one try to minimize the perimeter of each resulting piece?.&lt;br /&gt;&lt;br /&gt;To be honest I don't know for sure if it is possible to divide, say, an equilateral triangle into, say, 5 convex pieces all with same area and same perimeter. Even this simple example appears somewhat tricky although the convexity requirement on the pieces is a strong constraint which makes the claim shaky.&lt;br /&gt;&lt;br /&gt;Of course, if the claim gets successfully countered, then, one could relax the claim in various ways and say, say&lt;br /&gt;&lt;br /&gt;(1) any convex shape, for any N, can be cut into N pieces, not necessarily convex so that all pieces have same area and same perimeter (this claim looks very plausible as of now).&lt;br /&gt;&lt;br /&gt;or else&lt;br /&gt;&lt;br /&gt;(2) For any convex shape, there exists some N, so that the shape can be cut into N convex pieces of same area and same perimeter. Perhaps one could say: "some N greater than 2". Well, things seem murky!&lt;br /&gt;&lt;br /&gt;I could not find any known result on this - although there has been work on dividing into pieces so that every piece has same area and the same fraction of the outer boundary of the target. The requirement that all pieces should have same perimeter is not very easy to ensure - at least not as easy as ensuring equal areas for them. One does not know ab initio what precise perimeter each piece should have!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-115945249634089917?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/115945249634089917/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=115945249634089917' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/115945249634089917'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/115945249634089917'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2006/09/cutting-shapes.html' title='&apos;Fair&apos; Partitions'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-115097180510624232</id><published>2006-06-22T03:16:00.000-07:00</published><updated>2006-06-22T03:23:25.116-07:00</updated><title type='text'>Traversing A Tree</title><content type='html'>Problem:&lt;br /&gt;&lt;br /&gt;Given a Binary Tree. You have to print the data in inorder traversal.&lt;br /&gt;Restrictions: No recursion, no queue, no stack, no extra memory...&lt;br /&gt;&lt;br /&gt;Suggested Solution:&lt;br /&gt;&lt;br /&gt;One could use a single additional integer N to hold the path to nodes in the input tree - the number's binary equivalent will signify a path from root to some element: the first bit in the binary string stands of root; then for each successive bit, if bit is 0, move to the left child of the current element and if the bit is 1 move to the right child. For instance the value of N=9 with binary string 1001 signifies the path to the node reached from root  (the first 1 in the binary) by a left-left-right (0-0-1)path from root. The mapping from the value of this number N and elements in the input tree is one-one.&lt;br /&gt;&lt;br /&gt;For in-order traversal, one could find the next element at each step as follows. We maintain throughout a single integer whose binary representation gives the path from root to the current element in the traversal. This binary string keeps getting bits added or removed from it as we progress. Appending a 1 to the binary string implies multiplying the integer by 2 and adding 1; deleting a 0 at the end, corresponds to dividing the integer by 2 and so on.&lt;br /&gt;&lt;br /&gt;The traversal begins at the left most element of the input tree (need not be a leaf) - got by starting with a binary string with a single 1 and adding as many 0's to it as allowed by the input tree.&lt;br /&gt;&lt;br /&gt;Cases:&lt;br /&gt;1: If you are currently at a leaf at the end of a leftward going branch, the next element in traversal is its parent. this parent is reached by dropping a 0 from the end of the binary string (path) to the current element.&lt;br /&gt;&lt;br /&gt;2. If you are at a leaf at the end of a right going branch, the next inorder element is got by backtracking up to its nearest ancestor A which is the left child of some other node, say P and return P. This can be done by dropping 1's from the end of the binary string corresponding to current element till a 0 is reached and then dropping one 0.&lt;br /&gt;&lt;br /&gt;3. If you are at any other element, the next element in the traversal is the left most leaf element of the right subtree starting at the current element. This next element can be reached by the following process:&lt;br /&gt;If possible append a 1 to the binary string.  Append as many 0's as possible - if corresponding nodes exist in the input tree. Wherever no more 0 can be appended, stop and return that element. If no 1 can be appended at the beginning, the current element, though not a leaf ought to be treated as a leaf. If the present last bit of the binary number is 1, execute case 2. if the last bit is 0, execute case 1.&lt;br /&gt;&lt;br /&gt;The traversal ends when one finds oneself at the root on dropping a 1 from the binary string.&lt;br /&gt;&lt;br /&gt;Thus we seem to have carried out the in-order traversal using only a single extra integer.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-115097180510624232?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/115097180510624232/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=115097180510624232' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/115097180510624232'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/115097180510624232'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2006/06/traversing-tree.html' title='Traversing A Tree'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-114786769851619520</id><published>2006-05-17T05:01:00.000-07:00</published><updated>2006-05-17T07:53:19.796-07:00</updated><title type='text'>A Sequence Puzzle</title><content type='html'>The following problem was contributed by B. Sairam.&lt;br /&gt;&lt;br /&gt;There is a series which goes like this&lt;br /&gt;&lt;br /&gt;T(1) = 1&lt;br /&gt;T(2) = 2&lt;br /&gt;T(k) = T(k-1) + SumOfDigitsOf ( T(k-1) ). For instance, if T(p) = 129 then&lt;br /&gt;T(p+1) = 129+1+2+9&lt;br /&gt;&lt;br /&gt;Question: Then does the number 123456789 occur in this series?&lt;br /&gt;&lt;br /&gt;Spoiler Warning: Solution below!&lt;br /&gt;&lt;br /&gt;[Additional questions: How fast does the function digitsum(N) grow as a function of N? How fast does the therm T(N) in the above series grow with N?]&lt;br /&gt;&lt;br /&gt;-----------&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;-----------&lt;br /&gt;Of course, it is easy to check programmatically that 123456789 does not occur in the series. A non-brute-force argument follows....&lt;br /&gt;-----------&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Every number N and digitsum(N) both have the same value modulo 3.&lt;br /&gt;&lt;br /&gt;When a number that equals 1 (modulo 3) is added to its own digitsum, the value of the sum (modulo 3) will be 2.&lt;br /&gt;&lt;br /&gt;When a number that equals 2 (modulo 3) is added to its own digitsum, the value of the sum (modulo 3) will be 1.&lt;br /&gt;&lt;br /&gt;The series begins with 1, which equals 1 (modulo 3). the next will be 2, which equals 2 (modulo 3). The next number is 4 which equals 1 (modulo 3) the next number will equal 2 (modulo 3) and so on...&lt;br /&gt;&lt;br /&gt;Thus,the series consists alternately of numbers equaling 1 and 2 modulo 3. But the given number equals 0 modulo 3 (since it can be easily checked it is divisible by 3). so, it cannot be in the series. QED.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-114786769851619520?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/114786769851619520/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=114786769851619520' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/114786769851619520'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/114786769851619520'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2006/05/sequence-puzzle.html' title='A Sequence Puzzle'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-114494867095542274</id><published>2006-04-13T10:12:00.000-07:00</published><updated>2006-04-15T05:56:47.496-07:00</updated><title type='text'>A 'Road Coloring' Problem</title><content type='html'>This is on the July 2003 challenge at the Ponder This column at IBM Research. &lt;a href ="http://domino.research.ibm.com/Comm/wwwr_ponder.nsf/challenges/July2003.html"&gt; See here &lt;/a&gt; for the statement of the problem.&lt;br /&gt;&lt;br /&gt;This problem is stated to be still open. Here we (N. Ramana Rao and self)look at a special case thereof.&lt;br /&gt;&lt;br /&gt;1. We look at the special case of Road Coloring where at least one of the cities has an outgoing road ending in the same city. Suppose there are N cities, and Cx be any of the cities which have road to itself. We do the following visualization:&lt;br /&gt;&lt;br /&gt;Keep Cx at the center and arrange the other cities in layers around it. First keep those cities which have roads directly leading to Cx to Cx in the first layer around Cx. Call this layer L1. Now keep the cities which have roads directly leading to cities of L1 in the next layer L2. Thus we keep all the cities in layers around Cx.&lt;br /&gt;&lt;br /&gt;The coloring:&lt;br /&gt;For every other city C, there is at least one outgoing road leading into the layer just inside of the layer on which C lies.  Color this road from C to its next inner layer red. The other outgoing road from C is colored green. If both roads from C lead to the next inner layer, either may be colored red or green. For the central city Cx, the self-reaching loop road should be red.&lt;br /&gt;&lt;br /&gt;With this coloring, one has a constant and finite path leading from ANY city to the central city Cx. This sequence of roads to the central city is always of the form of one Green followed by as many Reds as there are layers (an example is given below).&lt;br /&gt;&lt;br /&gt;For any specified city C', there exists a fixed path from central city Cx to it (guaranteed in problem statement). So given any destination C', starting at any unknown source C, we can by first taking the constant path to the center and the path from center to C'. The path will be the same for any starting city C and will depend only on destination C'. &lt;br /&gt;&lt;br /&gt;Example:&lt;br /&gt;&lt;br /&gt;There are 5 cities numbered 1 to 5. arranged in a pentagon and connected clockwise. 1, 2, 4 and 5 have one road each that loops back on itself. 3-5 is another road.&lt;br /&gt;&lt;br /&gt;ie, the roads are 1-2, 2-3, 3-4, 4-5, 5-1, 1-1, 2-2, 3-5, 4-4, 5-5&lt;br /&gt;&lt;br /&gt;there are two cycles 1-2-3-5 (length 4) and 1-2-3-4-5 (length 5) - the lengths are relatively prime. As far as we can make out, this property is not used in what follows...&lt;br /&gt;&lt;br /&gt;We choose 1 as the central city. The next layer has only 5 (since only from 5 is there a direct path to 1) In the next layer there are two cities, 3 and 4 In the outermost layer there is only 2.&lt;br /&gt;&lt;br /&gt;By above coloring scheme,  2-3, 3-5, 4-5, 5-1, and 1-1 should be red and the others roads are green.&lt;br /&gt;&lt;br /&gt;The seqeunce  GRRR takes you to city 1 from any starting city. Once we have a samepath to the central city from anywhere we also have a same path to any required destination from anywhere.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-114494867095542274?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/114494867095542274/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=114494867095542274' title='5 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/114494867095542274'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/114494867095542274'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2006/04/road-coloring-problem.html' title='A &apos;Road Coloring&apos; Problem'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>5</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-114494664604386351</id><published>2006-04-13T09:34:00.000-07:00</published><updated>2006-04-13T23:07:31.986-07:00</updated><title type='text'>A 'Line Fitting' Problem</title><content type='html'>This post came out of a discussion with N. Ramana Rao.&lt;br /&gt;&lt;br /&gt;Statement of the Problem:&lt;br /&gt;------------------------&lt;br /&gt;Given a distribution of N points in 2D Euclidean plane. Describe the line which minimizes the Sum of the Orthogonal Distances of the given points from itself.&lt;br /&gt;&lt;br /&gt;Please note that we consider abs values of the perpendicular distances themselves, NOT their squares. We could call such a line a "min-SOD line" o r perhaps the "spine" of the point distribution. The line need not be unique.&lt;br /&gt;&lt;br /&gt;An Extension: If we are to minimize (the SOD plus the minimum length of the line so that it contains the feet of the perpendiculars from all the input points to the min-SOD line) what could be said about a line that achieves it?&lt;br /&gt;&lt;br /&gt;Proposed answer to the main part:&lt;br /&gt;--------------------------------&lt;br /&gt;&lt;br /&gt;(This is a 'lemma' which we have tried to use to find an efficient algorithm to compute the min-SOD line).&lt;br /&gt;&lt;br /&gt;A min-SOD line (spine) has to pass thru at least two of the input points and should be such that on neither half plane it divides the plane into, there should be more than Floor (N/2) points.&lt;br /&gt;&lt;br /&gt;Attempted proof of our  lemma:&lt;br /&gt;------------------------------&lt;br /&gt;&lt;br /&gt;Consider a line which claims to be the spine and which pass thru none of the N input points. First we note that candidate line has to have equal number of the input points on either side ( else we could shift in parallel to itself in one of the two possible directions and achieve a reduction in SOD).&lt;br /&gt;&lt;br /&gt;Let this candidate spine be infinitesimally rotated in the plane about ANY point on itself, say P. Now, for any input point Pi the perpendicular&lt;br /&gt;distance from the candidate spine thru P is given by r* sin t where t is the angle made by the line from P to Pi and the candidate spine . When the line rotates infinitesimally by angle dt, the differential change in the perpendicular distance is r* cos t dt.&lt;br /&gt;&lt;br /&gt;We note that if the line were to rotate in the opposite direction from what considered above, the differential change in the perpendicular distance of the point Pi from the candidate spine would simply change sign (because then dt -&gt; -dt ). &lt;br /&gt;&lt;br /&gt;So for the entire set of input points, the overall change in the Sum of Orthogonal Distances will also have opposite signs when the candidate spine is rotated in the two possible directions.&lt;br /&gt;&lt;br /&gt;This proves that if SOD increases in one direction overall, it necessarily decreases in the other direction - it cannot increase in both directions =&gt; the position of the candidate spine is not a minimum for the SOD. However if the candidate line passes thru one of the input points, for that point  the perpendicular distance increases in both directions of rotation and then the line COULD BE be one for which the SOD is a minimum.&lt;br /&gt;&lt;br /&gt;Special case:&lt;br /&gt;------------&lt;br /&gt;The SOD could be unchanged for both infinitesimal rotations (for example if the input points are arranged along two parallel lines in equal numbers and the candidate spine is parallel to both these lines and equidistant from both). Then we note that this property of unchanging SOD holds only locally and gets lost the moment the we disturb the symmetry of the distribution of the input points about the candidate spine by an infinitesimal rotation of the candidate spine. This always seems to be the case as long as the input points are a discrete set.&lt;br /&gt;&lt;br /&gt;Thus we see that the candidate spine has to pass thru at least one input point. We now repeat the above argument with this input point as the center of rotation for the candidate spine; we see that the candidate line has to pass thru one more input point.&lt;br /&gt;&lt;br /&gt;We thus conclude that the spine passes thru at least two input points and neither side it has more than floor (N/2) points.&lt;br /&gt;&lt;br /&gt;Remarks on computing the spine:&lt;br /&gt;------------------------------&lt;br /&gt;For input points in general position, the spine is one of the Halving lines. So in order to computationally determine the spine for a given point set, we could try to find all the halving lines and compare the Sum of Orthogonal Distances (SOD) of the input points from each halving line.&lt;br /&gt;&lt;br /&gt;From the work of Tamal Dey and others on the 'k-set problem', the number of halving lines for N points could be as high as N^4/3. Finding them all could take O(log N) time per halving line using dynamic convex hull data structures. Finding the SOD for one halving line and to recalculate it for each successive halving line could take only constant time per iteration. Thus we could have approximately an O(N^4/3 * log N) algorithm to find the spine. We are grateful to Prof. David Eppstein (UC -Irvine) for pointing out these details to us.&lt;br /&gt;&lt;br /&gt;We are not aware of better complexity results for this problem. We also do not know if this problem has been explored before.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;The extension:&lt;br /&gt;---------&lt;br /&gt;If we are to minimize {the SOD plus the minimum length of the spine so that it just contains the feet of the perpendiculars from all the input points to the min-SOD line} , the spine again appears to satisfy the above property - it passes thru at least two input points and has &lt;= floor(N/2) points on either side. the same arguments appear to hold.&lt;br /&gt;&lt;br /&gt;However, the line that minizes only the SOD and the line minimizing {SOD + 'spine length'} need not be the same. For example, if there are 3 input points at the vertices of an isosceles right triangle, the min-SOD line is the hypotenuse but if we are to minimize the SOD + spine length, we choose either of the two equal sides of the triangle as the spine.&lt;br /&gt;&lt;br /&gt;Additional Remark: &lt;br /&gt;------------------&lt;br /&gt;&lt;br /&gt;It would seem that the lemma could be improved to at most Floor( (N-1)/2)    points on each side of the line. This makes a difference when N is even. &lt;br /&gt;&lt;br /&gt;Suppose  N is even and we have a line L passing through at least 2 points, with exactly N/2 points on one side. Shift L parallel to itself towards the N/2 points (which does not change the SOD), so it is not touching any points. Suppose L is now the x-axis. Rotate it through theta around the origin. &lt;br /&gt;&lt;br /&gt;(Remark: because there are exactly N/2 points on each side, it doesn't matter which point we choose as pivot.)&lt;br /&gt;&lt;br /&gt;If there were N/2 points (x_i,y_i) above the axis and N/2 points (z_j, - w_j) below the axis (notice y_i and w_j are all positive), then the SOD (as a function of theta) is   ( sum y_i + sum w_j) (cos theta) + ( - sum x_i + sum z_j) (sin theta). The second derivative at theta=0 is  ( - sum y_i - sum w_j ) which is negative, so a small rotation in one direction or the other will decrease SOD. So we did not have the minimum.  Conclusion: at most Floor((N-1)/2) points on each side of the line.&lt;br /&gt;&lt;br /&gt;Note: &lt;br /&gt;-----&lt;br /&gt;For a distribution of points in Euclidean 3D, the min-SOD line NEED NOT pass thru any of the points.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-114494664604386351?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/114494664604386351/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=114494664604386351' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/114494664604386351'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/114494664604386351'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2006/04/line-fitting-problem.html' title='A &apos;Line Fitting&apos; Problem'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-114494590652928995</id><published>2006-04-13T09:13:00.000-07:00</published><updated>2006-04-14T09:57:59.606-07:00</updated><title type='text'>Packing Circles - Questions Galore!</title><content type='html'>The prime inspiration for this post is &lt;a href ="http://www.stetson.edu/~efriedma/packing.html"&gt; 'Erich's Packing Center'&lt;/a&gt;. What I have here is a long list of doubts based on the interesting facts given there on the specific problem of packing circles in squares - for a given number N, finding the smallest square which will hold exactly N unit circles. For several examples please see &lt;a href ="http://www.stetson.edu/~efriedma/cirinsqu/"&gt; here &lt;/a&gt;.&lt;br /&gt;&lt;br /&gt; 1. It appears that one needs to solve each instance of the problem (each instance given by a certain specified number of circles to be packed in a least square) separately. Are there general rules for characterizing packings like: (i)  For what numbers could we always manage with a simple parallelogram lattice of circles (as in the case of 16, 18 and 20 circles for instance) ?  (ii) For what numbers will there be one or more 'loose circles' in the packing (circles which can move a finite distance about its position in the packing without violating the square) (7, 11, 17, 21 etc..)  ?&lt;br /&gt;&lt;br /&gt;Remark: It appears that there are no such rules. Obviously some numbers work well for this 18=4+3+4+3+4 and 20=4+4+4+4+4.  But you don't know ahead of time that this translates into an optimal packing.&lt;br /&gt;&lt;br /&gt;2. If we allow only simple parallelogram lattices of circles  (with one circle per 'unit cell') to be used while packing circles in squares, could we have a general method to find the minimal square given the number of circles to be packed? This becomes relevant if we are automating the packing and can only handle simple lattice arrangements of the circles.&lt;br /&gt;&lt;br /&gt;Remark: The hex packing is a lot better than the diamond packing, so for large N this won't be as good - it would be better to place the square over a hex lattice and trap as many circles as possible.&lt;br /&gt;&lt;br /&gt;3. If we allow only simple parallelogram lattices but allow the container to be a rectangle with (i) minimum area or (ii) minimum perimeter, do we have a single general algorithm for any number of circles to be packed?&lt;br /&gt;&lt;br /&gt;Remark: It appears this is unexplored territory.&lt;br /&gt;&lt;br /&gt;4. And if we allow the container to be other than a square, can the 'loose circles' /non-lattice arrangements be always avoided for some specific type of container? Even in the 'Circles in Circles' page at the 'Packing Center', loose circles are seen for some numbers.&lt;br /&gt;&lt;br /&gt;Remark: "thin" enough containers won't have this problem, But it is hard to see any shape that won't have this problem when scaled up large enough.&lt;br /&gt;&lt;br /&gt;5. It is possible that there is a connection between selections of N circles from a fixed lattice to polyominoes with N squares - the number of different N-ominoes is exponential. The number of candidate circle arrangements perhaps is probably exponential as well.&lt;br /&gt;&lt;br /&gt;Maybe we could have ways to filter down the number of candidate selections of circles to a polynomial in N - perhaps by eliminating circle selections corresponding to long 'polyominoes' if one is looking for the smallest square. &lt;br /&gt;&lt;br /&gt;Remark: One needs to find a good way to prune the tree of polyominoes to only consider ones that are fat instead of skinny.  Perhaps a more general idea of convexity, while making sure the width and height don't differ by 2 or more..&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;6. I would also like to know if there are any problems in this area which are known to be NP-complete. Finding the minimal square for a given number of circles seems to be far more complex than NP-complete since one cannot choose from a discrete set of options.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;8. Here is an apparently simpler problem: Given a known and fixed parallelogram lattice of circles and a number N. Find the minimal area/ perimeter rectangle (or square) that can be placed on the lattice so that it 'traps' N circles fully within it. Does this or some other variant of the main packing problem enable a reduction of the problem to choosing from a discrete set of candidates?&lt;br /&gt;&lt;br /&gt;Remark: One needs to see how to reduce the problem to finitely many cases.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-114494590652928995?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/114494590652928995/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=114494590652928995' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/114494590652928995'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/114494590652928995'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2006/04/packing-circles-questions-galore.html' title='Packing Circles - Questions Galore!'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-25964010.post-114486094441961105</id><published>2006-04-12T09:33:00.000-07:00</published><updated>2006-04-12T10:15:36.583-07:00</updated><title type='text'>Starting Up...</title><content type='html'>Hello World!&lt;br /&gt;&lt;br /&gt;This blog is a spinoff from my 'catch all' collection of personal stuff, &lt;a href ="http://nandakumarr.blogspot.com"&gt; 'Anamika' &lt;/a&gt;. Here I will try to  post as regularly as possible on matters geometric, computational etc.. &lt;br /&gt;&lt;br /&gt;This initial post is a 'recap'. Let me form here, a 'bucket' of pointers to some selected posts made at Anamika over the last year. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;1. &lt;a href ="http://nandakumarr.blogspot.com/2005/04/good-bad-and-ugly-some-issues-with.html"&gt;  On the 'Change Making' problem &lt;/a&gt;&lt;br /&gt;&lt;br /&gt;2. &lt;a href ="http://nandakumarr.blogspot.com/2005/04/glass-bulbs-puzzle.html"&gt; A problem on Calibrating Glass Bulbs &lt;/a&gt;&lt;br /&gt;&lt;br /&gt;3. &lt;a href ="http://nandakumarr.blogspot.com/2005/04/bulbs-glow.html"&gt; Solution to the Glass Bulb Problem &lt;/a&gt;&lt;br /&gt;&lt;br /&gt;4. &lt;a href ="http://nandakumarr.blogspot.com/2005/05/cutting-polygonal-cake.html"&gt; On Partitioning Polygons &lt;/a&gt;&lt;br /&gt;&lt;br /&gt;5. &lt;a href ="http://nandakumarr.blogspot.com/2005/05/of-prisoners-and-switches-puzzle.html"&gt;   A Puzzle on Prisoners and Switches &lt;/a&gt;&lt;br /&gt;&lt;br /&gt;6. &lt;a href ="http://nandakumarr.blogspot.com/2005/05/more-on-prisoners-and-switches.html"&gt; More on the Prisoners and Switches Puzzle &lt;/a&gt;&lt;br /&gt;&lt;br /&gt;7. &lt;a href ="http://nandakumarr.blogspot.com/2005/05/sudoku-yet-another-puzzle.html"&gt; An encounter with Sudoku &lt;/a&gt;&lt;br /&gt;&lt;br /&gt;8. &lt;a href ="http://nandakumarr.blogspot.com/2005/08/pigeon-hole-puzzle.html"&gt; A Pigeon Hole Puzzle &lt;/a&gt;&lt;br /&gt;&lt;br /&gt;9. &lt;a href ="http://nandakumarr.blogspot.com/2005/10/reflections-on-angel-problem.html"&gt; Speculations on the Angel Problem &lt;/a&gt;&lt;br /&gt;&lt;br /&gt;10. &lt;a href ="http://nandakumarr.blogspot.com/2005/11/atomic-polygons.html"&gt; 'Atomic' Polygons &lt;/a&gt;&lt;br /&gt;&lt;br /&gt;11. &lt;a href ="http://nandakumarr.blogspot.com/2006/02/conjecture-and-quote-from-arnold.html"&gt;  A 'Conjecture'&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;12. &lt;a href ="http://nandakumarr.blogspot.com/2006/02/conjecture-debunked-and-some-more.html"&gt; A Conjecture Debunked &lt;/a&gt;&lt;br /&gt;&lt;br /&gt;13. &lt;a href ="http://nandakumarr.blogspot.com/2006/03/more-on-cutting-polygons-and-stuff.html"&gt; Cutting Polygons - contd. &lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/25964010-114486094441961105?l=nandacumar.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://nandacumar.blogspot.com/feeds/114486094441961105/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=25964010&amp;postID=114486094441961105' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/114486094441961105'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/25964010/posts/default/114486094441961105'/><link rel='alternate' type='text/html' href='http://nandacumar.blogspot.com/2006/04/starting-up.html' title='Starting Up...'/><author><name>R.Nandakumar</name><uri>http://www.blogger.com/profile/06879162776342731034</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://4.bp.blogspot.com/_o2euH9F9QP0/TOTe3Si4tOI/AAAAAAAAAC0/dJWNLBVoJ58/S220/nk_online.jpg'/></author><thr:total>0</thr:total></entry></feed>
