m (Grammatical and typographic corrections)
(Also this page refers to combinatory logic term modules. That was why I made a separate page for it (two references are enough for that))
Revision as of 14:40, 4 August 2006
See Wikipedia article on Chaitin's construction, referring to e.g.
- Computing a Glimpse of Randomness (written by Cristian S. Calude, Michael J. Dinneen, and Chi-Kou Shu)
- Omega and why math has no TOEs (Gregory Chaitin).
2 Basing it on combinatory logic
See the prefix coding system described in Binary Lambda Calculus and Combinatory Logic (page 20) written by John Tromp:
of course, c, d are meta-variables, and also some other notations are changed slightly.
Having seen this, decoding is rather straightforward. Here is a parser for illustration, but it serves only didactical purposes: it will not be used in the final implementation, because a good term generator makes parsing superfluous at this task.
2.3 Chaitin's construction
Now, Chaitin's construction will be here
- should denote an unary predicate “has normal form” (“terminates”)
- should mean an operator “decode” (a function from finite bit sequences to combinatory logic terms)
- should denote the set of all finite bit sequences
- should denote the set of syntactically correct bit sequences (semantically, they may either terminate or diverge), i.e. the domain of the decoding function, i.e. the range of the coding function. Thus,
- “Absolute value”
- should mean the length of a bit sequence (not combinatory logic term evaluation!)
3 Eliminating any concept of code by handling combinatory logic terms directly
We can avoid referring to any code notion, if we transfer (lift) the notion of “length” from bit sequences to combinatory logic terms in an appropriate way. Let us call it the “norm” of the term:
Thus, we have no notions of “bit sequence”,“code”, “coding”, “decoding” at all. But their ghosts still haunt us: the definition of norm function looks rather strange without thinking on the fact that is was transferred from a concept of coding.
Question: If we already move away from the approaches referring to any code concept, then could we define norm in other ways? E.g.
And is it worth doing it at all? The former one, at leat, had a good theoretical foundation (based on analysis, arithmetic and probability theory). This latter one is not so cleaner, that we should prefer it, so, lacking theoretical grounds.
What I really want is to exclude the (IMHO) underestimation of this “probability of termination” number -- an underestimation coming from taking into account the syntactically non-correct codes (IMHO). Thus taking only termination vs nontermination into account, when calculating this number (which can be interpreted as a probability).
3.1 Term generator
module CLGen where import Generator (gen0) import CL (k, s, apply) direct :: [CL] direct = gen0 apply [s, k]
module Generator (gen0) where import PreludeExt (cross) gen0 :: (a -> a -> a) -> [a] -> [a] gen0 f c = gen f c 0 gen :: (a -> a -> a) -> [a] -> Integer -> [a] gen f c n = sizedGen f c n ++ gen f c (succ n) sizedGen :: (a -> a -> a) -> [a] -> Integer -> [a] sizedGen f c 0 = c sizedGen f c (n + 1) = map (uncurry f) $ concat [sizedGen f c i `cross` sizedGen f c (n - i) | i <- [0..n]]
module PreludeExt (cross) where cross :: [a] -> [a] -> [(a, a)] cross xs ys = [(x, y) | x <- xs, y <- ys]
4 Related concepts
5 To do
Writing a program in Haskell -- or in combinatory logic:-) -- which could help in making conjectures on combinatory logic-based Chaitin's constructions. It would make only approximations, in a similar way that most Mandelbrot plotting softwares work: it would ask for a maximum limit of iterations.
chaitin --computation=cl --coding=tromp --limit-of-iterations=5000 --digits=10 --decimal