In the comments to one of my earlier [Demsbki][demsbki-info-theory] posts, I was responding to a comment by a poster, and realized that what we were discussing was probably interesting enough to promote up to a front-page post.
A poster named [Garote][garote] said:
>I think PaulC said exactly what needs to be said, that grants us all
>hearty permission to ignore Dembski's work. I think it bears repeating:
>"If I am betting on coin flips and notice any kind of algorithmic pattern then
>there are legitimate reasons to conclude that the person flipping coins is not
>playing fair. However, this method does not allow one to discriminate between
>the product of evolution and the product of "intelligent design" since neither
>of these processes in any way resemble random coin flips."
>Dembski's feverishly comparing apples to oranges, to prove that one is an
Now, my contempt for Dembski is pretty clear. But this argument against him struck me as making a mistake - and it's a mistake that strikes at something near-and-dear to my interests: mathematical modeling. Modeling can be sorely abused, [as I've discussed before][modeling]; but I don't want to throw out the baby with the bathwater.
My whole viewpoint on mathematics is that much of its value comes from **abstraction**: the ability to look at something complex; to identify a set of relevant properties for understanding some feature of it; and to use that to create a simpler mathematical model of the complex system based on its fundamental principles. That kind of abstraction isn't just useful for diddling around in the world of pure math, but for much of how math is used in science. There are a lot of interesting things that we can't grasp in their entirety; but that we can understand by breaking them down through abstraction into a set of simpler facets that we can study.
I don't want to throw away the validity of the concept of abstraction and mathematical modeling; but one way of reading that comment is as an argument against the concept of working with a simplified abstract model to understand something complex. (Note that I'm not saying that that's what Garote meant; but I thought that focusing on this could produce an interesting discussion.)
In Dembski's favor, I can see the "coin-flip" thing is an abstraction of a complex process to something simple that contains a relevant feature. The thing is, there are things in nature that produce highly random results; and there are other things that produce interesting patterns. Recognizing that there's something different about processes that produce patterns could be an interesting thing; and recognizing the distinction between randomness and pattern is an interesting subject which probability theorists have spent time studying; it's right at the intersection between probability theory and information theory, and it's produced some interesting insights about what information is and what it means.
The problem WRT to Demsbki isn't that he's reducing a problem to a mathematical model through abstraction and then analyzing the model. The problem is that when you build a mathematical model, you *need to make sure that your abstraction captures all of the relevant features of what you're modeling*. And when you draw conclusions based on the analysis of the mathematical model, *you need to make sure that your abstraction isn't the source of the conclusion*. Both of those are different ways of stating the fundamental rule of mathematical modeling:
**Mathematical models must be validated against the thing that they model.**
Demsbki's reduction of the process of analyzing certain features of the universe to the a metaphor involving recognition of patterns in coin flips is fine with me. The problem is that he creates a model that *omits important elements* of the real world, and then insists that the *conclusions drawn from his abstract model are applicable to the real world*. But in fact, his conclusions are the result of properties of his model, *not* of the real world. The validation of his model fails: the specific conclusions are the result of eliminating things from his model that might permit a different conclusion.
To continue with the example of the coin flip metaphor: if you're studying patterns, you could abstract the problem of observing patterns to one of observing flipping coins in an idealized universe, where the coin is perfectly even, and nothing about the surface that it lands on can affect the outcome of a flip. That might be a useful model for trying to understand the difference between random sequences of flips, and patterns in sequences.
If you then try to use that model to determine the *cause* of a pattern, you'll conclude that the only possible cause of a pattern *is the actions of the coin flipper*. If you've abstracted away everything that could influence the outcome of the coin-flip except the influence of the coin-flipper, then *in your model*, concluding that the flipper is the only possible source of a pattern could be a reasonable conclusion.
That doesn't mean that you can then say that in the real world, the *only possible cause* of a pattern in a sequence of coin-flips is some action taken by the coin-flipper. You can't apply that simplified abstraction of your model to the real world without showing that it's a valid model with respect to the the properties that affected your conclusion.
The ultra-simple coin flip model isn't valid for the real world, because it deliberately omits factors of the real world that could influence the conclusion. In the real world, there are unfair coins (both deliberately unfair coins, and coins that have become unfair either through minting flaws or through wear and tear). There are magnetic fields. There are irregular surfaces.
The problem with many of the conclusions that bad mathematicians draw from mathematical models is that *the models don't represent what they claim to represent*. They abstract away relevant features of reality, and then demand that reality doesn't possess those features, because they aren't in the model.