Slashdot Mirror


Are Computers Ready to Create Mathematical Proofs?

DoraLives writes "Interesting article in the New York Times regarding the quandary mathematicians are now finding themselves in. In a lovely irony reminiscent of the torture, in days of yore, that students were put through when it came to using, or not using, newfangled calculators in class, the Big Guys are now wrestling with a very similar issue regarding computers: 'Can we trust the darned things?' 'Can we know what we know?' Fascinating stuff."

39 of 441 comments (clear)

  1. Rumsfeld, anyone? by dolo666 · · Score: 5, Funny

    > 'Can we know what we know?' Fascinating stuff.

    Reminds me of Rumsfeld... "Reports that say that something hasn't happened are always interesting to me, because as we know, there are known knowns; there are things we know we know. We also know there are known unknowns; that is to say we know there are some things we do not know. But there are also unknown unknowns -- the ones we don't know we don't know."

    1. Re:Rumsfeld, anyone? by Tower · · Score: 5, Informative

      Actually, this is three of the four quadrants of knowledge...

      KK | KD
      ___|____
      |
      DK | DD

      So, you can:
      Know that you Know something
      Know that you Don't Know something (the second most common)
      Don't Know that you Don't Know something (most things fall in this category for most people)
      Don't Know that you Know something (the most interesting of the categories)

      Big, huge, red tape operations can easily fall into the latter category (DK)... since it is rather easy for a group to obtain knowledge, yet be unaware of it [political commentary omitted].

      --
      "It's tough to be bilingual when you get hit in the head."
    2. Re:Rumsfeld, anyone? by Deraj+DeZine · · Score: 4, Funny

      Well, I had been in the don't care that I don't know category; now I'm in the don't care that I know. Great.

      --
      True story.
    3. Re:Rumsfeld, anyone? by cs · · Score: 5, Interesting

      Can't remember where I came across this, but for entertainment:

      Men are four:
      He who knows and knows that he knows; he is wise, follow him.
      He who knows and knows not that he knows; he is asleep, wake him.
      He who knows not and knows that he knows not; he is ignorant, teach him.
      He who knows not and knows not that he knows not; he is a fool, spurn him!

      I'm sure it's coloured my attitude to supporting users:-)

      --
      Cameron Simpson, DoD#743 cs@cskk.id.au http://www.cskk.ezoshosting.com/cs/
    4. Re:Rumsfeld, anyone? by jgabby · · Score: 5, Funny

      Then there's:

      My boss, who knows that he knows not;
      But pretends that he knows that he knows;
      And he's so convincing at it, that;
      People who know that he doesn't know;
      Beleive that he knows that he knows anyway.

    5. Re:Rumsfeld, anyone? by sbaker · · Score: 4, Interesting

      I'm not sure that there are only those four catagories.

      Godels theorem pretty much says that there are things that you can NEVER know are true or false...and that in some cases you can PROVE that you can never know them.

      This leads to some other states that your knowledge can be in:

      CERTAINTY OF UNCERTAINTY: In some cases you can know (by solid mathematical proof) that you can never know some particular thing. For example. we know with absolute certainty - that you can't solve the 'Halting Problem' (to prove whether an arbitary computer program will eventually halt or whether it'll run forever). That's something we KNOW we'll never be able to do no matter how smart we get. That's not the same as KK/KD/DK or DD. It's tempting to lump this in with KD - but in the case of simply being aware that we are ignorant of something, we might take steps to resolve that ignorance. In this case, we know that this is something we cannot EVER know.

      CERTAINTY OF POTENTIAL CERTAINTY: If you know the current "largest prime number" - then by definition, you don't know of a larger prime - but you DO know that you could definitely find a larger prime if you really wanted to.

      UNCERTAINTY OF POTENTIAL CERTAINTY: Then there are other things that you might not know whether they are knowable or not - such as the proof of some of the classic mathematical problems. Before Fermat's last theorem was proved, nobody was sure whether it could be proved or not.

      --
      www.sjbaker.org
  2. Create vs. Verify by Squeamish+Ossifrage · · Score: 5, Informative

    The headline does a slight disservice in describing the article that way: Whether or not computers can create proofs isn't an issue. The problem comes when the resulting proof is too involved to be verified by a human, and so the computer's work has to be trusted.

    1. Re:Create vs. Verify by Vancorps · · Score: 4, Insightful
      If humans created the computer to do the task should they not trust that it would do the task and do it well? Perhaps, perhaps not.

      A computer could quite easier come up with a very complex answer simply because it can do more calculations in a given second than a human can. Of course humans take in a lot more variables at a given time so the numbers are actually very opposite but I'm sure you get my point.

      I think you test it with progressively more different problems, if the answers come out precise and accurate then you can build your level of trust in the system. Kind of like the process of getting users to trust saving to the server after a bad crash wiped everything because the previous admin was a moron.
    2. Re:Create vs. Verify by Xilo · · Score: 4, Insightful

      involved, not complicated - like the Four Color [Conjecture]. Noone could figure out a way to actually prove it, so some one (or group of someones) wrote a program to systematically determine all the possible arrangements of regions in a simplified series of maps, and then figure out how to color each of those maps. The involved part was .. well, all of it. It wasn't necessarily very complicated, just labor-intensive. Computers are perfectly suited for tedium.

      --
      Read; Write; Execute
    3. Re:Create vs. Verify by Llywelyn · · Score: 4, Insightful

      Sometimes it is enough to know that something is *true* or *false* without having to know the details of the in-between steps.

      I'll give some trivial examples to illustrate:

      For a famous example, it would provide a great deal of peace of mind if we could prove that P != NP. It wouldn't matter that we understand that proof so much as that it is *provably true*. If, on the other hand, it is proven false that is just as important (if not more so) and while an understanding of the proof might lead more easily to examples of such, we would know (for certain) that trusting public key encryption over the long run would be a Bad Idea(TM) (for example) and that it is just a matter of time before a polynomial time algorithm is developed.

      (Not that such will necessarily be fast, mind you, but we would know it would exist).

      For another example--there are certain things that can be inferred if Poincare Conjecture is true for N=3. If we can prove the Poincare Conjecture is true (and it is now thought that it might be) it means things to physicists, even if we don't know why it is true.

      The bigger question here is "can we trust it if we can't verify it by hand."

      --
      Integrate Keynote and LaTeX
    4. Re:Create vs. Verify by panaceaa · · Score: 5, Funny

      Fortunately for you software researchers haven't programmed computers to create their own long sentences with so many prepositions that human readers of the created sentences are unable to remember the subject or figure out which verb, or possibly adjective, the trailing adverb applies to by the time they have read the entire sentence yet!

    5. Re:Create vs. Verify by eightheadsofdoom · · Score: 5, Insightful

      That's exactly the case. I had Ken Appel as a professor, and he mentioned the 4-color theorem a couple of times. As he put it, the math wasn't intensive, but actually doing the work the computer was able to do would have taken an army of grad. students years to finish. The way he saw it, the proof was understandable, just extraordinarily, arduously long. That's when they decided to use a computer to solve the problem. Unfortunately, there are still many pure mathematicians who shun computer-based proofs because they (or their grad. students) are not working things out with their own pencils. Unfortunately, I don't think that's a problem that's going away, but I do think it opens up some interesting doors such as writing program A to prove a theorem, and then haveing to prove program A's correctness, for which you write program B and so forth.

    6. Re:Create vs. Verify by eliza_effect · · Score: 5, Funny

      Can you please tell us The Question?

      The Ultimate Question?

      Yes!

      Of Life, The Universe..

      And everything?

      And Everything.

      Yes.

      Tricky..

      But can you do it?

      ...No. But I'll tell you who can.

      Who? Tell us!

      I speak of none, but the computer that is to come after me.

      What computer?

      A computer whose merest operational parameters I am not worthy to calculate and yet I will design it for you. A computer which can calculate The Question to the Ultimate Answer. A computer of such infinite and subtle complexity that organic life itself will form part of it's operational matrix. And it will be called.. The Earth.

      What a dull name.

    7. Re:Create vs. Verify by njj · · Score: 4, Interesting

      If we can prove the Poincare Conjecture is true
      OK, yes, that would definitely be worth doing. Various chunks of 3-dimensional geometric topology currently include the caveat ``... if the 3-dimensional Poincare Conjecture is true.''

      (and it is now thought that it might be)
      Depends who you talk to, of course. Perelman reckons he's got an outline proof of Thurston's Geometrisation Conjecture, which implies the Poincare Conjecture as a corollary. But as I understand it he's not actually proved it, just described how one would go about proving it - essentially saying ``It's over the other side of that hill''. Now Perelman is a very bright lad (cleverer than I am) but the Poincare Conjecture has a long history of almost being proved (my research supervisor (I've just finished a PhD in algebraic and geometric topology) almost did it about twenty years ago, for example, but there was a very subtle and unresolvable flaw in his argument) so I'm going to reserve judgement until the paper turns up in the Annals of Mathematics.

      I wouldn't be surprised if the Conjecture turned out to be true, as the corresponding result is known to be true in dimensions 1,2,4,5,... (well, to be picky, the smooth 4-dimensional case hasn't been proved yet, but the topological and piecewise-linear ones have). But equally, I wouldn't be shocked if it weren't - 3-dimensional topology is a weird subject, as there's enough room to start discussing interesting things, but there's not so much room that everything trivialises.

      Quick precis of the Conjecture:
      ``If it looks like a sphere, it is''.

      Slightly less quick precis of the Conjecture:
      Given any topological space X, we can assign a sequence of groups (`homotopy groups') pi_n(X) to it, so that pi_n(X) in some sense describes the n-dimensional structure of X. An n-manifold (a topological space which locally `looks like' ordinary, flat n-dimensional space) which has the same sequence of homotopy groups as the 3-dimensional sphere, is called a `homotopy 3-sphere'. The Poincare Conjecture is that the 3-sphere itself is the only homotopy 3-sphere.

      So, to prove it, we have to show that every homotopy 3-sphere is topologically equivalent (`homeomorphic') to the 3-sphere. And to disprove it, we just have to find one counterexample - a homotopy 3-sphere which isn't equivalent to the 3-sphere itself.

      Now to use a computer to prove the Conjecture, we need to find some way of verifying that every possible homotopy 3-sphere is equivalent to the 3-sphere. This is theoretically doable - there's an algorithm (the Rego-Rourke algorithm) which lists (with redundancy), all possible homotopy 3-spheres. There's another algorithm (the Rubenstein-Thompson algorithm) which, given a homotopy 3-sphere, can tell if it is equivalent to the 3-sphere. So in theory we just feed the output of the RRA into the RTA.

      Except that there are an infinite number of possible homotopy 3-spheres to check, so if the Conjecture is true, this program will never terminate.

      Now if you can find some way of reducing the cases under consideration to some finite subset (by, for example, showing that all but a finite number of homotopy 3-spheres obviously satisfy the conjecture) then using a computer suddenly becomes a worthwhile endeavour. This is basically what Appel and Haken did with the Four-Colour Map Theorem.

      The computer approach is also useful for searching for counterexamples, and for verifying that all cases up to some level of complexity satisfy the Conjecture.

      But where computers aren't currently going to help, is in the actual creative side of things - a lot of important modern mathematics (and the related theorems and proofs) has come from very clever humans saying ``OK, what happens if we try this (utterly weird and counterintuitive) thing here'' and having the aesthetic sense to tell when something's actually interesting or just irrelevant. Until computers are capable of this kind of creative/intuitive/aesthetic/etc behaviour, I doubt they're going to be replacing human research mathematicians any time soon.

      nicholas

  3. 'Can we trust the darned things?' by FFFish · · Score: 4, Funny

    Depends whether it's a Pentium with an FDIV bug, I imagine...

    --

    --
    Don't like it? Respond with words, not karma.
  4. It was a big help with the 4-color map proof... by The+Beezer · · Score: 5, Informative

    and there are already programs out that help with this. Here's one for example...

  5. I see no good reason why not.... by kommakazi · · Score: 4, Interesting

    Computers are a human creation...it's not a matter of whether we can trust the computer, but rather a matter of can we trust that the people who built the computer and coded the software it runs knew what they were doing and didn't make any errors. Computers can only do what we tell them to...so really it was humans who indirectly made the proofs by producing a system capable of doing so. All it really boils down to is whether the folks who made the system and it's software knew what they were doing or not and whether they made any errors or not.

  6. Re:Can someone elaborate on... by stephentyrone · · Score: 5, Informative

    It's not hard to *see*. It's hard to *prove*. Very little of mathematics is consumed with proving deep, mystical statements that no one would ever anticipate to be true. Much (maybe most) of mathematics is built around proving (relatively) obvious things. Why bother? because sometimes, relatively obvious things turn out to be false, and there's no way to know that they won't until you've prooved them true. In general, showing that discrete (or semi-discrete) phenomena are optimal is fairly tricky; you can't just appeal to calculus to optimize some function. You often have to somehow break the search space up into a bunch of disjunct cases that span all the possibilities, and be able to prove that they span all possibilities. Then, if you're lucky, you can use some kind of calculus-type argument on the continuous spaces you're left with.

  7. Theorem Provers by bsd4me · · Score: 4, Informative

    Theorem provers have been around for a long time. A net search should turn up a ton of hits. The key is to implement a system that can be verified by hand, and then build on it.

    --

    (S(SKK)(SKK))(S(SKK)(SKK))

  8. new facet of an old issue by colmore · · Score: 5, Insightful

    20th century mathematics has seen some pretty amazing things, but at the same time, there are very real questions as to what constitutes "proof" any more.

    consider this: the hypothesis of the famous Riemann Zeta problem has been tested for trillions of different solutions, and it has held true in every case. (If you want an explanation of the Zeta problem, look elsewhere, I don't have the time)

    Now that means that it's *probably* true, but nobody accepts that as mathematical proof.

    On the other hand, the classification problem for finite simple groups has been rigorously solved, but the collected proof (done in bits by hundreds of mathematicians working over 30 years) is tens of thousands of pages in many different journals. given the standards of review, it is a virtual certainty that there is an error somewhere in there that hasn't been found. So, again, the solution to this problem is *probably* right, but it has been accepted as solved.

    What's the difference between these two cases really? What's the difference between these and relying on computer proofs that are, again, *probably* right?

    In this light, the math of the late 19th century and early 20th century was something of a golden age, modern standards of logical rigor were in place, but the big breakthroughs were still using elementary enough techniques that the proofs could be written in only a few pages, and the majority of mathematically literate readers could be expected to follow along. These days proofs run in the hundreds of pages and only a handful of hyper-specialized readers can be expected to understand, much less review them.

    --
    In Capitalist America, bank robs you!
    1. Re:new facet of an old issue by I+Be+Hatin' · · Score: 5, Insightful
      consider this: the hypothesis of the famous Riemann Zeta problem has been tested for trillions of different solutions, and it has held true in every case. (If you want an explanation of the Zeta problem, look elsewhere, I don't have the time) Now that means that it's *probably* true, but nobody accepts that as mathematical proof.
      On the other hand, the classification problem for finite simple groups has been rigorously solved, but the collected proof (done in bits by hundreds of mathematicians working over 30 years) is tens of thousands of pages in many different journals. given the standards of review, it is a virtual certainty that there is an error somewhere in there that hasn't been found. So, again, the solution to this problem is *probably* right, but it has been accepted as solved.
      What's the difference between these two cases really?

      That one claims to be a proof and the other doesn't? You simply can't prove the Riemann Hypothesis by testing trillions of numbers (though if you find one case where it fails, you have disproved it). As a simple example, I can find trillions of numbers whose base-10 expansion is less than a googolplex digits long. Does this mean that all integers have this property? Of course not... So even if all of the calculations are right, you still don't have a proof.

      On the other hand, the classification of finite simple groups does claim to be a proof, and if there are no errors, it is a proof. You're right that there are probably errors, but these may be only minor errors that can be fixed. At least no one seems to have found evidence that the proof is completely flawed yet. But it's certainly possible that someone will find an insurmountable error in one of the proofs. There have been cases of propositions that were "proved" true for more than 80 years before a counterexample was found.

      What's the difference between these and relying on computer proofs that are, again, *probably* right?

      Again, it depends upon what the computer is trying to show. The computer proofs I'm familiar with are ones where the methods are documented, it's just that the computations are too tedious to do by hand. So you can read the proof and say "modulo software bugs, it's a proof". And then it works the same as science: anyone who wants to can repeat the proof for themselves, and see that they get the same answer. As more people validate these results, the likelihood of bugs goes down exponentially, and the likelihood of the proof being accepted increases.

      --
      I know god exists. I read it on the internet, so it must be true.
  9. Re:I think so, yes. by Quill345 · · Score: 5, Insightful

    Automated theorem provers have been around for a long time, if you can express your thoughts using first order logic. Here's a program from 1986... lisp code

  10. I don't see what the big deal is by ameoba · · Score: 4, Interesting

    I don't see what the big deal is; not only is the general problem of proving mathematical statements undecidable (even without considering Godel's theorem) but even solvable problems require a lot of human intervention to get solved. Most problems (ie - examples out of math textbooks) aren't going to come up with a proof in any reasonable amount of time by simply dropping it into a theorem prover and pushing "go".

    "Automated theorem proving" is less an automatic process (like you'd get with an automated production line) and more of a mechanical assistance to the job (like using a fork-lift to move heavy things faster than you could by hand).

    It not only takes work to convert a problem into a good representation, but then you have to structure the problem statement in such a way that a theorem prover can make optimal use of it. Often times, you're forced to, upon following the output, prove lemmas (sub-proofs).

    Then, when you finally get a proof, you get the joy of trying to simplify it to something that -can- be understood by a person; again, this is part of the process that can't really be automated well.

    --
    my sig's at the bottom of the page.
  11. change the title by NotAnotherReboot · · Score: 4, Insightful

    Change the title to: "Are Computers Able to Verify Mathematical Proofs Beyond All Doubt?"

  12. Wait, I know this one... by bomb_number_20 · · Score: 4, Funny

    The answer is left as an exercise for the reader.

    --
    That's ok, Jesus likes me anyway.
  13. indeed by rebelcool · · Score: 4, Insightful
    On a similar topic, today I attended a lecture by Tony Hoare on compilers that can generate verified code and tools that guide the human programmer into designing programs that can be easily validated (from the compiler's stance). One very good question raised afterwards was, well how do you know you can trust the compiler generating the verified program?

    Though Dr. Hoare danced around that question a little, presumably that aspect of the project would have to be done by hand, a monumental task to say the least.

    --

    -

    1. Re:indeed by Squeamish+Ossifrage · · Score: 4, Informative

      At least some provable properties can be "pushed" through the compilation process all the way to the resulting object code. If you're interested, you can look into proof-carrying code and typed assembly language (papers by Necula, Appel, Walker, Zdanzewic, Crary and a cast of thousands.)

      The resulting proofs are still hairy enough that they have to be checked by machine, but the size and complexity of the proof-checker is much less than that of the compilation toolchain. That means that while there's still some code that has to be trusted, it's much less. Here's my informal scariness hierarchy:

      Normal model (you have to trust everything) > type safe languages (you have to trust the compilers / interpreters) > proof-carrying code (you have to trust the proof-checker*).

      If you haven't already, you should definitely read Ken Thompson's Turing Award lecture, "Reflections on Trusting Trust" here.

      * - Pedantry point: If you're talking about Necula's original PCC work, you also have to trust the verification condition generator, which is some fairly deep voodoo. Appel's Foundational PCC addresses this to a signficant extent.

    2. Re:indeed by Squeamish+Ossifrage · · Score: 5, Interesting

      No! Definitely not! Really! :-)

      Most faults are software problems, not hardware, so having different machines won't help. Further, interestingly, most major software faults (at least, of the sort that make it through serious testing) tend to be conceptual problems, not coding ones, and different people tend to make the same mistakes. This means in practice that even when you have completely independent software implementations (called n-version programming), they're frequently all wrong in the same way at the same times. See the famous Knight & Leveson paper.

    3. Re:indeed by maxwell+demon · · Score: 4, Interesting

      While the article spaks about intentional errors, I could imagine the same to be true for bugs (while introducing a self-replicating bug by accident is unlikely, I'm not sure if it's unlikely enough to never occur).

      Say, an optimizer is buggy. Say, in a certain line of code in the compiler, there's a '>' instead of a '<' sign. Unfortunately, this causes, under certain, rare conditions, the optimizer to miscompile '<' into '>'. Now, since triggering that bug is rare, it goes unnoticed for a while, and the buggy compiler is installed as default compiler for further development.

      Now, at some later time, the bug is found, a developer looks at the code and finally finds the error. He replaces the '>' by '<' in the hope of fixing the bug. Unfortunately, he doesn't recognise that this very comndition now triggers the bug, having the compiler internally replacing '<' to '>' again, replicating the bug again.

      Now, the test case will show that the bug is still there, but the developer will simply not find the bug in the code. After all, the bug isn't in the source any more. It's only there in the compiled program. At some later time, though, it might magically disappear by some unrelated change nearby, which causes the bug not to be triggered any more.

      --
      The Tao of math: The numbers you can count are not the real numbers.
  14. The stack might get a bit deep, but... by Odin's+Raven · · Score: 4, Funny
    'Can we trust the darned things?' 'Can we know what we know?'

    The obvious solution is to have the computer create a new proof that shows that the algorithm it used to create the original proof is, in fact correct.

    And to prove that the proof of the proof can be trusted, have the computer create a proof of the proof of the proof.

    And to prove that the proof of the proof of the proof can be trusted, ...
    --
    A marriage is always made up of two people who are prepared to swear that only the other one snores.
  15. a mathematician's perspective by jockeys · · Score: 5, Interesting

    as a graduate in the fields of mathematics, i spent a large portion of my five undergraduate years doing proofs. there are a great many ways to prove things, sometimes applicable sometimes not. (e.g. using inductive proofs for numeric theorems is all well and good but completely useless for any sort of ring-theory or spatial proofs)

    there are also several levels of depth for proofs, ranging from "i've found a counter example so i can write the whole thing off as garbage" to "i have exhaustively and rigorously proved this starting with the basic axioms of number theory and worked my way on up"

    the latter is really the only acceptable way to prove anything seriously. sometimes when you are reworking an already- done proof to illustrate a point, other mathematicians will allow a bit of latitude when it comes to cutting corners, but for a proof as far-reaching as the one in the article, i would only be interested in a "rigorous" proof, that is, one that started with the foundational tenets of mathematics and combined those to form and prove other postulates, etc. very much a form of abstraction, not unlike large development projects.

    the problem arises when one (or several) humans have to be able to objectively check the whole thing. to use my prior example of a large development project, no one developer at microsoft understand the whole of windows. it's too big for a single human to understand. each developer knows what he needs to do to complete his part, and so on and so forth.

    traditionally, for proofs, a single mathematician (or a small group) would hammer out the whole proof, so the level of complexity remained at a human-understandable level. (even if tedious) my concern, as a mathematician, with using an automated solution would be the rapidly growing order of complexity needed to properly back up increasingly complex proofs. as stated in the article, it's like trying to proofread a phonebook. (only, you must also consider that for every element of the proof (a particular listing) there are several branching layers of complexity (fundamental, underlying proofs many layers deep) underneath. this gets more complicated in an exponential fashion) obviously this approach will only remain human-checkable for relatively small problems. (programmers: think of some horrible nondeterministic- polynomial problem like the "traveling salesman" problem. systems, like humans, are a finite resource, but if you increase the size of the problem, the complexity will quickly grow far beyond your ability to compute. large proofs suffer from the same difficulties, if not quite as concrete and pronounced as NP algorithms)

    in closing, i would have to agree that proofs, no matter the effort and computing time put into them, really should not be viewed as being as rigorous as those provable "by hand" and human- understandable, even if the computer has arrived at a satisfactory conclusion, because we have no way of KNOWING if the computer has built up the proof correctly, except that it says it has.

    --

    In Soviet Russia jokes are formulaic and decidedly non-humorous.
    1. Re:a mathematician's perspective by Tom7 · · Score: 4, Insightful

      because we have no way of KNOWING if the computer has built up the proof correctly, except that it says it has

      Sure we do -- typical theorem provers spit out a proof that can be checked by hand (god forbid), or else checked by a simple procedure. Understanding that a theorem prover is implemented correctly is tough, but understanding that a checker is implemented correctly isn't. I trust such proofs more than I trust hand-checked proofs, because humans are more susceptible to mistakes than computers are.

  16. Re: . . . As we know it. by Bastian · · Score: 4, Interesting

    I think the "as we know it" is the key word here. It creates a new juggling act that teachers have to deal with. On one hand, calculators are extremely useful for the things at which humans are error prone. If students can use calculators or Mathematica or something, they can check their arithmetic much more reliably, which is great for isolating problems with learning concepts from basic mathematical errors. Granted, some people don't see this as a bonus since it's good to be able to do arithmetic reliably without aid. For smaller numbers I agree, but in the real world people use calculators for arithmetic with numbers that have a lot of sig figs. Making students do this arithmetic by hand is just distracting them from learning the concepts they are supposed to be learning.
    On the other hand, many students are prone to using these devices and applications as crutches and try to get away with doing things like using their calculator's implementation of Newton's Method instead of solving the problem themselves.

    Some professors have found solutions to this problem, others havent. When I was at college, I think our math department had achieved a pretty good level of harmony with Mathematica - we were expected to do a lot of stuff by hand or in our heads - Gaussian elimination, for example - but in order to make the math seem useful, we were also exptected to be able to solve real-world problems with the stuff we learned. Not contrived "real-world" problems from your high-school textbook, but stuff like interpreting large and dirty scientific datasets where the specific technique we would have to use to solve the problem was something we could figure out, but not something that had been explicitly laid out by the textbook or in lecture. We had to apply the concepts we had learned to figure out the problem, but there was no way we were going to chug out that arithmetic by hand - when was the last time you tried to work on a 16x16 matrix using a pencil and paper? How about a 100x100 one?

  17. You beat me to it by UberQwerty · · Score: 4, Informative

    I professor showed me the Robbins Algebra proof a while ago. I was going to link here, but first I searched the page for (Score:5, Informative), and there you were :)

    Here's an excerpt:

    In 1933, E. V. Huntington presented [1,2] the following basis for Boolean algebra:
    x + y = y + x. [commutativity]
    (x + y) + z = x + (y + z). [associativity]
    n(n(x) + y) + n(n(x) + n(y)) = x. [Huntington equation]

    Shortly thereafter, Herbert Robbins conjectured that the Huntington equation can be replaced with a simpler one [5]:
    n(n(x + y) + n(x + n(y))) = x. [Robbins equation]


    Robbins and Huntington could not find a proof. The theorem was proved automatically by EQP, a theorem proving program developed at Argonne National Laboratory.

    --


    PUBLIC SPLIT ON WHETHER BUSH IS A DIVIDER -CNN scrolling banner, 10/15/2004
  18. Re:The dawn of a new age of Math... and Science! by ParadoxicalPostulate · · Score: 5, Insightful


    once upon a time, only advanced mathematicians knew calculus, but now we learn it in high school. Just wait until warp theory is an entry level college engineering course

    Once upon a time, the majority of adult males knew how to trap a rabbit (or similar creature), gut it, skin it, start up a fire, cook it, and eat it.

    I don't.

    Heck, I couldn't even look up at the sky at night and tell you which way was north.

    Once upon a time, most people could.

    All I'm saying is that the amount of knowledge and skills the average human being can possess will not increase expontentially over time (barring artificial manipulation). We gain new skills as a population and lose old ones.

  19. Flyspeck Project by harlows_monkeys · · Score: 4, Informative

    Here's a link to the Flyspeck Project, briefly mentioned at the end of the article, which aims to give a formal proof of the theorem.

  20. Re:identity by sbaker · · Score: 4, Informative

    Some things have to be taken as Axioms. A=A is one of them. All the things you prove that rely on A always being equal to A can be taken as true PROVIDING you accept that axiom. We like to pick axioms that we have a gut feel 'must' be true - but you can do interesting mathematics by denying some of those axioms and see where they take you. The classic geometric case of denying that parallel lines never meet produced a whole range of interesting geometries that don't exactly represent the real world but none-the-less have interesting and useful consequences.

    So - when you come across a theorem that you can't prove but are pretty damned certain is true - you COULD choose to simply make it be an axiom. The problem is that the theorems you are subsequently able to come up with are only as reliable as your initial assumption of that axiom.

    If your axioms eventually turn out not to match the real world - then all you have is a pile of more or less useless theorems that don't mean anything for the real world.

    It's therefore pretty important to stick with a really basic set of axioms to reduce the risk that an axiom might turn out not to be 'true' for the real world and bring down the entire edifice of mathematics along with it.

    If we ever found some sense in which A!=A then every single thing we thought we knew about math would be in doubt.

    --
    www.sjbaker.org
  21. Re:Ok I am always confused about the difference. by Forgotten · · Score: 4, Insightful

    Most people probably knew the "four quadrants of knowledge" thing, but didn't know they knew (DK). That is, they have enough to put it together, but have probably never put it into words before. Intuitive knowledge is one way of putting it. The bulk of most people's knowledge probably falls into this category, which is fine - language is often overrated as a conduit of knowledge (not that it's not incredibly useful and important, but other means exist and are constantly used).

    I don't actually believe particularly firmly in that model, though, because I don't agree with the D-K dichotomy that underlies it. It's your usual classical Greek quadrant, which means it springs from a dual dichotomy, or in this case a dual-aspect single one. Dichotomy (or even one-dimensional spectra) is not the only way to look at things, but it is a dangerously compelling model - that is, when people have been presented with a dichotomy, they typically become unable to consider without it. And the defence of a dichotomy is usually a tautology - I mean it's obvious, isn't it, you either know something or you don't? ;)

    Still useful and interesting if you can get it out of your head when needed, though.

  22. Re:Ok I am always confused about the difference. by Photar · · Score: 4, Informative

    I believe its called the fallacy of the false delemma.

    --
    He who knows not and knows he knows not is a wise man. He who knows not and knows not he knows not is a fool.