Author: Christophe Theron
Date: 00:15:51 04/15/00
Go up one level in this thread
On April 15, 2000 at 01:25:24, KarinsDad wrote:
>On April 14, 2000 at 19:52:48, Christophe Theron wrote:
>
>>On April 14, 2000 at 14:41:08, KarinsDad wrote:
>>
>>>On April 13, 2000 at 20:32:01, Robert Hyatt wrote:
>>>
>>>[snip]
>>>>
>>>>You are talking about "forward pruning" which is full of danger. Your
>>>>eval likely doesn't understand deep tactics, yet you will be letting it
>>>>dictate which moves you search looking for tactics and which you don't.
>>>>
>>>>It is _very_ difficult to do this and not cause huge search problems...
>>>
>>>
>>>That is why Fathom will be so dangerous ("yeah, right" says all of the old
>>>programmers). It does a type of forward pruning. Whether it will be successful
>>>with this, only time will tell.
>>>
>>>KarinsDad :)
>>
>>
>>I hope you'll succeed. If you were going to create just another Crafty-nullmove
>>clone, it would not be interesting.
>>
>>Don't go for the easy way, try to find yours. It will be VERY difficult, but
>>much more interesting.
>
>Difficult?!? That's an understatement. However, it is fun (I just got back from
>my Friday night coding session with my partner and we had a blast debugging).
>It's weird to read stuff here and try to sort out what may work and what
>definitely will not. It's almost a crap shoot due to our basic algorithms being
>so drastically different. The interesting thing is that once in a while, an idea
>pops out of these web pages, but it is often unrelated directly to the topic in
>the message.
>
>>
>>In the early days of computer chess, programmers were much more creative. Many
>>gave up, and it's too bad.
>
>In the early days, programmers had more limitations as to what they could search
>due to drastically reduced hardware. Therefore, they were almost forced into
>some form(s) of selective search. However, they did not have the horsepower to
>effectively come up with a "human-like" selective search. I'm hoping that
>today's hardware will enable us to minimize tactical errors within a selective
>search by spending a little more time trying to figure out where the tactical
>pitfalls should lie (and thus avoiding them).
Working on slow hardware was very good. We had to take the best out of every
bit.
By trying to improve the performance of Tiger 11.9 on my 386sx 20MHz notebook, I
came up with a significant improvement that became Tiger 12.0. I have been able
to do that because I was studying manually a shallow search tree.
The field is still open. Forward pruning will get back, I hope.
Christophe
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.