<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: The Math Problem That 1,000 Math Teachers Couldn&#8217;t Solve	</title>
	<atom:link href="/2015/the-math-problem-that-1000-math-teachers-couldnt-solve/feed/" rel="self" type="application/rss+xml" />
	<link>/2015/the-math-problem-that-1000-math-teachers-couldnt-solve/</link>
	<description>less helpful</description>
	<lastBuildDate>Fri, 11 Mar 2016 19:09:41 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.2</generator>
	<item>
		<title>
		By: JoeBod		</title>
		<link>/2015/the-math-problem-that-1000-math-teachers-couldnt-solve/#comment-2418698</link>

		<dc:creator><![CDATA[JoeBod]]></dc:creator>
		<pubDate>Fri, 11 Mar 2016 19:09:41 +0000</pubDate>
		<guid isPermaLink="false">/?p=22681#comment-2418698</guid>

					<description><![CDATA[1.  Take your number.
    2.  Write down all of its prime factors from least to greatest.
    3.  If there are three or fewer prime factors, your dimensions are pretty easy to figure out.
    4.  If there are four or more factors, divide by the rounded down and rounded up value of the cube root of the number.
    5.  If a perfect cube, this is the three dimensions.
    6.  If neither divisions produce an integer quotient, subtract one from the rounded down value and add one to the rounded up value and divide again.
    7.  Repeat this step 6 until you find at least one division that produces an integer quotient.
    8.  If both divisions produce an integer quotient, then these are the first two dimensions.
    9.  Divide by their product for the third dimension.
    10.  If only one division produces an integer quotient, then this is the first dimension.
    11.  Divide by the first dimension and find the square root of the quotient.
    12.  Divide the quotient by the rounded down and rounded up value of the square root of the number.
    13.  If a perfect square, this is the second and third dimension.
    14.  If both divisions produce an integer quotient, then these are the last two dimensions.
    15.  If one division produces an integer quotient, this is the second dimension.
    16.  Divide the quotient by the second dimension to find the third dimension.
    17.  If neither divisions produce an integer quotient, subtract one from the rounded down value and add one to the rounded up value and divide again.
    18.  Repeat this step 17 until you find at least one division that produces an integer quotient.]]></description>
			<content:encoded><![CDATA[<p>1.  Take your number.<br />
    2.  Write down all of its prime factors from least to greatest.<br />
    3.  If there are three or fewer prime factors, your dimensions are pretty easy to figure out.<br />
    4.  If there are four or more factors, divide by the rounded down and rounded up value of the cube root of the number.<br />
    5.  If a perfect cube, this is the three dimensions.<br />
    6.  If neither divisions produce an integer quotient, subtract one from the rounded down value and add one to the rounded up value and divide again.<br />
    7.  Repeat this step 6 until you find at least one division that produces an integer quotient.<br />
    8.  If both divisions produce an integer quotient, then these are the first two dimensions.<br />
    9.  Divide by their product for the third dimension.<br />
    10.  If only one division produces an integer quotient, then this is the first dimension.<br />
    11.  Divide by the first dimension and find the square root of the quotient.<br />
    12.  Divide the quotient by the rounded down and rounded up value of the square root of the number.<br />
    13.  If a perfect square, this is the second and third dimension.<br />
    14.  If both divisions produce an integer quotient, then these are the last two dimensions.<br />
    15.  If one division produces an integer quotient, this is the second dimension.<br />
    16.  Divide the quotient by the second dimension to find the third dimension.<br />
    17.  If neither divisions produce an integer quotient, subtract one from the rounded down value and add one to the rounded up value and divide again.<br />
    18.  Repeat this step 17 until you find at least one division that produces an integer quotient.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Neeraj		</title>
		<link>/2015/the-math-problem-that-1000-math-teachers-couldnt-solve/#comment-2417054</link>

		<dc:creator><![CDATA[Neeraj]]></dc:creator>
		<pubDate>Thu, 28 Jan 2016 00:11:24 +0000</pubDate>
		<guid isPermaLink="false">/?p=22681#comment-2417054</guid>

					<description><![CDATA[For all the above cases my solution is working perfectly fine.

Steps

1) Find all the factors possible for the number

2) Take cuberoot of the given number

3) If it&#039;s not an integer then ceil it to next value.

4) Find all the numbers starting from that number which can perfectly divide that number, if you get a prime number then that&#039;s your first number else the minimum number from all the possible divisors is the first number.

5) Next for remaining 2 numbers divide and find the remaining amount for which we need to solve.

6) Then take the square root, and if it&#039;s not an integer then ceil it to next value.

7) Repeat step 4 and you will get your second number

8) Now you can easily find the third number.]]></description>
			<content:encoded><![CDATA[<p>For all the above cases my solution is working perfectly fine.</p>
<p>Steps</p>
<p>1) Find all the factors possible for the number</p>
<p>2) Take cuberoot of the given number</p>
<p>3) If it&#8217;s not an integer then ceil it to next value.</p>
<p>4) Find all the numbers starting from that number which can perfectly divide that number, if you get a prime number then that&#8217;s your first number else the minimum number from all the possible divisors is the first number.</p>
<p>5) Next for remaining 2 numbers divide and find the remaining amount for which we need to solve.</p>
<p>6) Then take the square root, and if it&#8217;s not an integer then ceil it to next value.</p>
<p>7) Repeat step 4 and you will get your second number</p>
<p>8) Now you can easily find the third number.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jonah		</title>
		<link>/2015/the-math-problem-that-1000-math-teachers-couldnt-solve/#comment-2416470</link>

		<dc:creator><![CDATA[Jonah]]></dc:creator>
		<pubDate>Sun, 10 Jan 2016 17:45:32 +0000</pubDate>
		<guid isPermaLink="false">/?p=22681#comment-2416470</guid>

					<description><![CDATA[(Man, I love that I still get emails about this thread.)

George, we&#039;re using different definitions of &quot;easy&quot; and &quot;hard&quot;. I&#039;m happy with an algorithm that&#039;s polynomial in V, the volume of the box, and brute force does that well enough: just try all the triples of numbers less than V (there are only V^3 of them) and see which is best. Cryptographers want (or, perhaps, don&#039;t want) an algorithm that&#039;s polynomial in the *number of digits* of V. I think that&#039;s the source of confusion here.]]></description>
			<content:encoded><![CDATA[<p>(Man, I love that I still get emails about this thread.)</p>
<p>George, we&#8217;re using different definitions of &#8220;easy&#8221; and &#8220;hard&#8221;. I&#8217;m happy with an algorithm that&#8217;s polynomial in V, the volume of the box, and brute force does that well enough: just try all the triples of numbers less than V (there are only V^3 of them) and see which is best. Cryptographers want (or, perhaps, don&#8217;t want) an algorithm that&#8217;s polynomial in the *number of digits* of V. I think that&#8217;s the source of confusion here.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: George Padolsey		</title>
		<link>/2015/the-math-problem-that-1000-math-teachers-couldnt-solve/#comment-2416465</link>

		<dc:creator><![CDATA[George Padolsey]]></dc:creator>
		<pubDate>Sun, 10 Jan 2016 15:35:05 +0000</pubDate>
		<guid isPermaLink="false">/?p=22681#comment-2416465</guid>

					<description><![CDATA[Hi,

I was looking at the problem and, as many already have, realise it&#039;s based on integer factorisation. In effect what you are doing is finding all integer factorizations of the number and finding the one with the most similar numbers (most cube), as in closest to cbrt(k^3) sides. You want to find an algorithm which can do this quickly (scaling nicely) and works with all integers with no error. In affect what you were trying to find is a Polynomial [P] algorithm for integer factorization.

If the 1000 teachers had been able to solve this problem outright with a Polynomial [P] algorithmn (not brute force - NP) that works for all numbers then they might have earned $1 million dollars, saved millions of lives and changed our society irrevocably. They would have definitely in the process have made most of the encryption methods used on the internet irrelevant. It is an open problem in the field of computer science by itself (Wikipedia [1] - &quot;Can integer factorization be done in polynomial time on a classical computer?”.)  Granted with this problem it would not have to find all factors of the number just 3 that work but let’s say we had a semiprime number (made by multiplying two primes — Wikipedia [2] — as is used in Public Key Cryptography - Wikipedia [3]) the algorithm;
Let’s say 3 * 5 as both primes produce 15 a semiprime.
If we use this supposed algorithm on it would produce 3 * 5 * 1 as that is the only way you can factor 15. 
We can generalise this to any semiprime.
Let a and b be the number multiplied to get the semiprime
When passed through the algorithm we would expect some permutation of (a, b, 1)

In effect we can find the prime factorization of any semiprime. If this algorithm worked fast, it means that public key cryptography which relies on one-way feature of multiplication + factorisation of semiprimes would be broken. This would contribute to another open problem in computer science which is whether one way functions exist: Wikipedia [4] — One-way function.

The reason this might earn $1-million-dollars and save millions of lives is because: depending on the solution some believe it would also solve P vs. NP which a $1-million-dollar solution prize is awarded if they find a solution by the clay maths institute as part of their 7 millennium maths problems (Clay-Math [5].)  If it did prove P = NP it would mean things like protein folding would be possible instantly (or at least very fast) undoubtedly saving millions of lives. It would mean that hypothetically a computer would be able create a masterpiece in any art form (as currently creating a masterpiece is in effect a brute force for computers which is an NP problem.) 

Looking at the responses to this problem currently it seems most of the responses algorithms work with numbers up to a certain value then start faltering. If they want to be able to do this with all numbers with no faults and with an improved brute force - the best algorithm that we have for integer factorization at the moment is the general number field sieve (Wikipedia [6] - GNFS.) If you wanted to solve the problem for this, then you would find all factors for this number with this algorithm and then compare them and choose ones which are closest to together to create the number (closest to cbrt(k^3) sides.) 

In effect what I am saying is there is currently no way to create a non-brute force solution that works with all sizes of cuboid without solving the semiprime factorization problem in computer science, something that has been baffling computer scientists and mathematicians alike for centuries. 
So in short if the collection of 1000 teachers / various people viewing this on the web had found a fast algorithm to do this then they would have:
-	Broken most cryptography used on the web (PKC)
        -    Contributed to solving whether one-way functions really exist
-	Save millions of lives
-	Contributed to solving P vs. NP and possibly depending on the algorithm found may have won $1 million dollars from solving it
        -    In the process saving society irrevocably — all artistic pieces would be able to be remade using a computer hypothetically
-	Made a huge discovery in the field of computer science, computational complexity and mathematics as a whole!
So, if anyone actually finds a fast algorithm for this then seriously tell someone… now!

For those unfamiliar with P vs. NP I recommend this video:
https://youtu.be/YX40hbAHx3s

If you are interested in looking at current challenges related to semiprime factorization: 
https://en.wikipedia.org/wiki/RSA_Factoring_Challenge 

Please do check this for yourself I am only a secondary school student so may be wrong!

[1]: https://en.wikipedia.org/wiki/List_of_unsolved_problems_in_computer_science
[2]: https://en.wikipedia.org/wiki/Semiprime 
[3]: https://en.wikipedia.org/wiki/Public-key_cryptography 
[4]: https://en.wikipedia.org/wiki/One-way_function 
[5]: http://www.claymath.org/millennium-problems/p-vs-np-problem
[6]: https://en.wikipedia.org/wiki/General_number_field_sieve]]></description>
			<content:encoded><![CDATA[<p>Hi,</p>
<p>I was looking at the problem and, as many already have, realise it&#8217;s based on integer factorisation. In effect what you are doing is finding all integer factorizations of the number and finding the one with the most similar numbers (most cube), as in closest to cbrt(k^3) sides. You want to find an algorithm which can do this quickly (scaling nicely) and works with all integers with no error. In affect what you were trying to find is a Polynomial [P] algorithm for integer factorization.</p>
<p>If the 1000 teachers had been able to solve this problem outright with a Polynomial [P] algorithmn (not brute force &#8211; NP) that works for all numbers then they might have earned $1 million dollars, saved millions of lives and changed our society irrevocably. They would have definitely in the process have made most of the encryption methods used on the internet irrelevant. It is an open problem in the field of computer science by itself (Wikipedia [1] &#8211; &#8220;Can integer factorization be done in polynomial time on a classical computer?”.)  Granted with this problem it would not have to find all factors of the number just 3 that work but let’s say we had a semiprime number (made by multiplying two primes — Wikipedia [2] — as is used in Public Key Cryptography &#8211; Wikipedia [3]) the algorithm;<br />
Let’s say 3 * 5 as both primes produce 15 a semiprime.<br />
If we use this supposed algorithm on it would produce 3 * 5 * 1 as that is the only way you can factor 15.<br />
We can generalise this to any semiprime.<br />
Let a and b be the number multiplied to get the semiprime<br />
When passed through the algorithm we would expect some permutation of (a, b, 1)</p>
<p>In effect we can find the prime factorization of any semiprime. If this algorithm worked fast, it means that public key cryptography which relies on one-way feature of multiplication + factorisation of semiprimes would be broken. This would contribute to another open problem in computer science which is whether one way functions exist: Wikipedia [4] — One-way function.</p>
<p>The reason this might earn $1-million-dollars and save millions of lives is because: depending on the solution some believe it would also solve P vs. NP which a $1-million-dollar solution prize is awarded if they find a solution by the clay maths institute as part of their 7 millennium maths problems (Clay-Math [5].)  If it did prove P = NP it would mean things like protein folding would be possible instantly (or at least very fast) undoubtedly saving millions of lives. It would mean that hypothetically a computer would be able create a masterpiece in any art form (as currently creating a masterpiece is in effect a brute force for computers which is an NP problem.) </p>
<p>Looking at the responses to this problem currently it seems most of the responses algorithms work with numbers up to a certain value then start faltering. If they want to be able to do this with all numbers with no faults and with an improved brute force &#8211; the best algorithm that we have for integer factorization at the moment is the general number field sieve (Wikipedia [6] &#8211; GNFS.) If you wanted to solve the problem for this, then you would find all factors for this number with this algorithm and then compare them and choose ones which are closest to together to create the number (closest to cbrt(k^3) sides.) </p>
<p>In effect what I am saying is there is currently no way to create a non-brute force solution that works with all sizes of cuboid without solving the semiprime factorization problem in computer science, something that has been baffling computer scientists and mathematicians alike for centuries.<br />
So in short if the collection of 1000 teachers / various people viewing this on the web had found a fast algorithm to do this then they would have:<br />
&#8211;	Broken most cryptography used on the web (PKC)<br />
        &#8211;    Contributed to solving whether one-way functions really exist<br />
&#8211;	Save millions of lives<br />
&#8211;	Contributed to solving P vs. NP and possibly depending on the algorithm found may have won $1 million dollars from solving it<br />
        &#8211;    In the process saving society irrevocably — all artistic pieces would be able to be remade using a computer hypothetically<br />
&#8211;	Made a huge discovery in the field of computer science, computational complexity and mathematics as a whole!<br />
So, if anyone actually finds a fast algorithm for this then seriously tell someone… now!</p>
<p>For those unfamiliar with P vs. NP I recommend this video:<br />
<a href="https://youtu.be/YX40hbAHx3s" rel="nofollow ugc">https://youtu.be/YX40hbAHx3s</a></p>
<p>If you are interested in looking at current challenges related to semiprime factorization:<br />
<a href="https://en.wikipedia.org/wiki/RSA_Factoring_Challenge" rel="nofollow ugc">https://en.wikipedia.org/wiki/RSA_Factoring_Challenge</a> </p>
<p>Please do check this for yourself I am only a secondary school student so may be wrong!</p>
<p>[1]: <a href="https://en.wikipedia.org/wiki/List_of_unsolved_problems_in_computer_science" rel="nofollow ugc">https://en.wikipedia.org/wiki/List_of_unsolved_problems_in_computer_science</a><br />
[2]: <a href="https://en.wikipedia.org/wiki/Semiprime" rel="nofollow ugc">https://en.wikipedia.org/wiki/Semiprime</a><br />
[3]: <a href="https://en.wikipedia.org/wiki/Public-key_cryptography" rel="nofollow ugc">https://en.wikipedia.org/wiki/Public-key_cryptography</a><br />
[4]: <a href="https://en.wikipedia.org/wiki/One-way_function" rel="nofollow ugc">https://en.wikipedia.org/wiki/One-way_function</a><br />
[5]: <a href="http://www.claymath.org/millennium-problems/p-vs-np-problem" rel="nofollow ugc">http://www.claymath.org/millennium-problems/p-vs-np-problem</a><br />
[6]: <a href="https://en.wikipedia.org/wiki/General_number_field_sieve" rel="nofollow ugc">https://en.wikipedia.org/wiki/General_number_field_sieve</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: dy/dan &#187; Blog Archive &#187; 2015 Remainders		</title>
		<link>/2015/the-math-problem-that-1000-math-teachers-couldnt-solve/#comment-2416246</link>

		<dc:creator><![CDATA[dy/dan &#187; Blog Archive &#187; 2015 Remainders]]></dc:creator>
		<pubDate>Tue, 05 Jan 2016 15:49:50 +0000</pubDate>
		<guid isPermaLink="false">/?p=22681#comment-2416246</guid>

					<description><![CDATA[[&#8230;] The Math Problem That 1,000 Math Teachers Couldn’t Solve [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] The Math Problem That 1,000 Math Teachers Couldn’t Solve [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Bob		</title>
		<link>/2015/the-math-problem-that-1000-math-teachers-couldnt-solve/#comment-2413851</link>

		<dc:creator><![CDATA[Bob]]></dc:creator>
		<pubDate>Tue, 03 Nov 2015 00:25:24 +0000</pubDate>
		<guid isPermaLink="false">/?p=22681#comment-2413851</guid>

					<description><![CDATA[Okay, forget previous post…..  doesn&#039;t work with several examples.

-Bob]]></description>
			<content:encoded><![CDATA[<p>Okay, forget previous post…..  doesn&#8217;t work with several examples.</p>
<p>-Bob</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Bob		</title>
		<link>/2015/the-math-problem-that-1000-math-teachers-couldnt-solve/#comment-2413847</link>

		<dc:creator><![CDATA[Bob]]></dc:creator>
		<pubDate>Mon, 02 Nov 2015 22:54:51 +0000</pubDate>
		<guid isPermaLink="false">/?p=22681#comment-2413847</guid>

					<description><![CDATA[Didn&#039;t read every post so may have missed this one…..

- Obtain the prime factorization and put in descending order.

- Begin filling three bins, A, B, and C by placing the largest prime factor in A, the next largest in B, and third largest in C.

- The next prime factor in descending order will be placed in the bin whose product of prime factors already contained in that bin is the smallest.

- Continue in descending order until all prime factors are binned.

(To handle the cases where there are fewer than three prime factors, start with a 1 in each bin.)

Example:  1260 = 2 x 2 x 3 x 3 x 5 x 7

Bin A:  7 x 2 = 14
Bin B:  5 x 2 = 10
Bin C:  3 x 3 = 9

7, 5 and 3 would go in first.  Then the second 3 would go into Bin C with the first 3, then a 2 would go in Bin B with the 5 and the last 2 would go in Bin A with the 7.

If there are two bins with the same product of primes, you could select the &quot;lower&quot; letter (A over B, etc.).

-Bob]]></description>
			<content:encoded><![CDATA[<p>Didn&#8217;t read every post so may have missed this one…..</p>
<p>&#8211; Obtain the prime factorization and put in descending order.</p>
<p>&#8211; Begin filling three bins, A, B, and C by placing the largest prime factor in A, the next largest in B, and third largest in C.</p>
<p>&#8211; The next prime factor in descending order will be placed in the bin whose product of prime factors already contained in that bin is the smallest.</p>
<p>&#8211; Continue in descending order until all prime factors are binned.</p>
<p>(To handle the cases where there are fewer than three prime factors, start with a 1 in each bin.)</p>
<p>Example:  1260 = 2 x 2 x 3 x 3 x 5 x 7</p>
<p>Bin A:  7 x 2 = 14<br />
Bin B:  5 x 2 = 10<br />
Bin C:  3 x 3 = 9</p>
<p>7, 5 and 3 would go in first.  Then the second 3 would go into Bin C with the first 3, then a 2 would go in Bin B with the 5 and the last 2 would go in Bin A with the 7.</p>
<p>If there are two bins with the same product of primes, you could select the &#8220;lower&#8221; letter (A over B, etc.).</p>
<p>-Bob</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Dave Marain		</title>
		<link>/2015/the-math-problem-that-1000-math-teachers-couldnt-solve/#comment-2412659</link>

		<dc:creator><![CDATA[Dave Marain]]></dc:creator>
		<pubDate>Tue, 06 Oct 2015 17:10:21 +0000</pubDate>
		<guid isPermaLink="false">/?p=22681#comment-2412659</guid>

					<description><![CDATA[Until there&#039;s a valid proof of any algorithm we can&#039;t be sure it&#039;ll work in all cases. Some truly ingenious offerings thus far which shows how we can provoke some of our students with math conundrums!
OK, here&#039;s mine and of course it needs rigorous verification. It does pass all the counterexamples but check that!
Let C=V^(1/3). Most suggestions work around this cube root but I think there are 2 cases.  Case 1 is critical to the general solution!
Case1: The largest prime factor, P_max, of V IS GREATER THAN C. In this case,  P_max MUST be one of the dimensions. From this point, process as in Case 2, Step 2 to find the other dimensions.
Case 2: All prime factors of V are â‰¤ C
Step 1. Choose the factor, F_1, closest to C. If there&#039;s a choice, choose one arbitrarily.
Step 2. Divide V by F_1 (or P_max from Case 1). Call the quotient Q 
Step 3. Find the factors of Q. This refactoring is key.
Step 4. Choose a factor, F_2, of Q &quot;closest&quot; to âˆšQ. 
Step 5. Divide Q by F_2 to obtain the final dimension, F_3.
Note that F_2 and F_3 will also be close to C, the cube root of V since Q is approx VÃ·V(^1/3)=V^(2/3), so âˆšQâ‰ˆV^(1/3)!!
A la Fermat, not enough room in this box to prove or demo it! I may post in my blog, MathNotations. However, I did verify it for (2^2)(3^5)(7)(11^4)]]></description>
			<content:encoded><![CDATA[<p>Until there&#8217;s a valid proof of any algorithm we can&#8217;t be sure it&#8217;ll work in all cases. Some truly ingenious offerings thus far which shows how we can provoke some of our students with math conundrums!<br />
OK, here&#8217;s mine and of course it needs rigorous verification. It does pass all the counterexamples but check that!<br />
Let C=V^(1/3). Most suggestions work around this cube root but I think there are 2 cases.  Case 1 is critical to the general solution!<br />
Case1: The largest prime factor, P_max, of V IS GREATER THAN C. In this case,  P_max MUST be one of the dimensions. From this point, process as in Case 2, Step 2 to find the other dimensions.<br />
Case 2: All prime factors of V are â‰¤ C<br />
Step 1. Choose the factor, F_1, closest to C. If there&#8217;s a choice, choose one arbitrarily.<br />
Step 2. Divide V by F_1 (or P_max from Case 1). Call the quotient Q<br />
Step 3. Find the factors of Q. This refactoring is key.<br />
Step 4. Choose a factor, F_2, of Q &#8220;closest&#8221; to âˆšQ.<br />
Step 5. Divide Q by F_2 to obtain the final dimension, F_3.<br />
Note that F_2 and F_3 will also be close to C, the cube root of V since Q is approx VÃ·V(^1/3)=V^(2/3), so âˆšQâ‰ˆV^(1/3)!!<br />
A la Fermat, not enough room in this box to prove or demo it! I may post in my blog, MathNotations. However, I did verify it for (2^2)(3^5)(7)(11^4)</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Emmanuel Goldstein		</title>
		<link>/2015/the-math-problem-that-1000-math-teachers-couldnt-solve/#comment-2412562</link>

		<dc:creator><![CDATA[Emmanuel Goldstein]]></dc:creator>
		<pubDate>Fri, 02 Oct 2015 16:28:53 +0000</pubDate>
		<guid isPermaLink="false">/?p=22681#comment-2412562</guid>

					<description><![CDATA[I see, everything between a less than sign and a greater than sign, is getting interpreted as an html tag. Apologies, and here we go, then:

-Example run-

p(594720);

144 divisors: [84, 80, 90, 96, 72, 70, 105, 63, 60, 59, 112, 56, 118, 120, 48, 45, 126, 42, 40, 36, 35, 32, 30, 140, 28, 144, 24, 21, 20, 18, 16, 15, 14, 12, 10, 9, 160, 8, 7, 6, 5, 4, 3, 2, 1, 168, 177, 180, 210, 224, 236, 240, 252, 280, 288, 295, 315, 336, 354, 360, 413, 420, 472, 480, 504, 531, 560, 590, 630, 672, 708, 720, 826, 840, 885, 944, 1008, 1062, 1120, 1180, 1239, 1260, 1416, 1440, 1652, 1680, 1770, 1888, 2016, 2065, 2124, 2360, 2478, 2520, 2655, 2832, 3304, 3360, 3540, 3717, 4130, 4248, 4720, 4956, 5040, 5310, 5664, 6195, 6608, 7080, 7434, 8260, 8496, 9440, 9912, 10080, 10620, 12390, 13216, 14160, 14868, 16520, 16992, 18585, 19824, 21240, 24780, 28320, 29736, 33040, 37170, 39648, 42480, 49560, 59472, 66080, 74340, 84960, 99120, 118944, 148680, 198240, 297360, 594720]

cube root: 84.09513032

z: 84
value: 22032
removed: [60, 84, 118]

z: 80
value: 21914
removed: [63, 80, 118]

z: 90
removed: [59, 90, 112]

z: 96
removed: [59, 96, 105]

z: 72
value: 21796
removed: [70, 72, 118]

z: 56
removed all z less than or equal to 56, bounded by: 22161.97904

z: 120
removed all z greater than or equal to 120, bounded by: 21851.72727


divisors examined: 7
[70, 72, 118]]]></description>
			<content:encoded><![CDATA[<p>I see, everything between a less than sign and a greater than sign, is getting interpreted as an html tag. Apologies, and here we go, then:</p>
<p>-Example run-</p>
<p>p(594720);</p>
<p>144 divisors: [84, 80, 90, 96, 72, 70, 105, 63, 60, 59, 112, 56, 118, 120, 48, 45, 126, 42, 40, 36, 35, 32, 30, 140, 28, 144, 24, 21, 20, 18, 16, 15, 14, 12, 10, 9, 160, 8, 7, 6, 5, 4, 3, 2, 1, 168, 177, 180, 210, 224, 236, 240, 252, 280, 288, 295, 315, 336, 354, 360, 413, 420, 472, 480, 504, 531, 560, 590, 630, 672, 708, 720, 826, 840, 885, 944, 1008, 1062, 1120, 1180, 1239, 1260, 1416, 1440, 1652, 1680, 1770, 1888, 2016, 2065, 2124, 2360, 2478, 2520, 2655, 2832, 3304, 3360, 3540, 3717, 4130, 4248, 4720, 4956, 5040, 5310, 5664, 6195, 6608, 7080, 7434, 8260, 8496, 9440, 9912, 10080, 10620, 12390, 13216, 14160, 14868, 16520, 16992, 18585, 19824, 21240, 24780, 28320, 29736, 33040, 37170, 39648, 42480, 49560, 59472, 66080, 74340, 84960, 99120, 118944, 148680, 198240, 297360, 594720]</p>
<p>cube root: 84.09513032</p>
<p>z: 84<br />
value: 22032<br />
removed: [60, 84, 118]</p>
<p>z: 80<br />
value: 21914<br />
removed: [63, 80, 118]</p>
<p>z: 90<br />
removed: [59, 90, 112]</p>
<p>z: 96<br />
removed: [59, 96, 105]</p>
<p>z: 72<br />
value: 21796<br />
removed: [70, 72, 118]</p>
<p>z: 56<br />
removed all z less than or equal to 56, bounded by: 22161.97904</p>
<p>z: 120<br />
removed all z greater than or equal to 120, bounded by: 21851.72727</p>
<p>divisors examined: 7<br />
[70, 72, 118]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Emmanuel Goldstein		</title>
		<link>/2015/the-math-problem-that-1000-math-teachers-couldnt-solve/#comment-2412561</link>

		<dc:creator><![CDATA[Emmanuel Goldstein]]></dc:creator>
		<pubDate>Fri, 02 Oct 2015 16:26:41 +0000</pubDate>
		<guid isPermaLink="false">/?p=22681#comment-2412561</guid>

					<description><![CDATA[A bit frustrating: we&#039;re supposed to see that at z=56, all divisors = 120 get eliminated. I&#039;ll try one last time:

z: 84
value: 22032
removed: [60, 84, 118]

z: 80
value: 21914
removed: [63, 80, 118]

z: 90
removed: [59, 90, 112]

z: 96
removed: [59, 96, 105]

z: 72
value: 21796
removed: [70, 72, 118]

z: 56
removed all z = 120, bounded by: 21851.72727


divisors examined: 7
[70, 72, 118]]]></description>
			<content:encoded><![CDATA[<p>A bit frustrating: we&#8217;re supposed to see that at z=56, all divisors = 120 get eliminated. I&#8217;ll try one last time:</p>
<p>z: 84<br />
value: 22032<br />
removed: [60, 84, 118]</p>
<p>z: 80<br />
value: 21914<br />
removed: [63, 80, 118]</p>
<p>z: 90<br />
removed: [59, 90, 112]</p>
<p>z: 96<br />
removed: [59, 96, 105]</p>
<p>z: 72<br />
value: 21796<br />
removed: [70, 72, 118]</p>
<p>z: 56<br />
removed all z = 120, bounded by: 21851.72727</p>
<p>divisors examined: 7<br />
[70, 72, 118]</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
