Author: Renze Steenhuisen
Date: 09:35:21 03/31/04
Go up one level in this thread
>(1) >I recognized that a different move ordering delivers very alternating >results in my alpha beta search. (I implemented null move, pv search, >mvv/lva, some history moves, transposition table, quiescence search ...) >Is this a bug or is this a normal behaviour? >For example, with 3 history moves (on initial position) i get: >[...] > 8. 0:01.12 993512 0.00 Nc3 Nf6 d4 d5 Nf3 Bf5 Ne5 Ne4 >... and with just one more history move (4): >[...] > 8. 0:01.28 1088694 0.00 e4 Nc6 Nf3 e5 d4 Nxd4 Nxd4 h6 Seems reasonable. >(2) >Another move ordering issue: my move ordering is as follows: > - hash move (if there's any) (hash table 1 mio. entries) > - captures (mmv/lva) > - some history moves (experementing with 3..5) > - rest unsorted >I get a first cut rate of 60 - 80 % percent. Is this too low or just >normal for this (still somewhat poor) move ordering? I am doing almost the same (SEE instead of MVV/LVA, and using 2 Killers) and I am getting the same numbers typically. I am ordering all remaining moves according to their History value. >(3) >I searched the net forth to back and back to forth and cannot find any >good doc about SEE in move ordering. Does someone have a description and/or >links to descriptions, where I can read about this method? Me too, can't find it... I am using sources :-) But what I really would like to have is a good description of which techniques together cause a FH-% of 90-95% And I can't find it... soo... Cheers! Renze
This page took 0.01 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.