[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gnugo-devel] 3.5.3 vs 3.5.4

From: SP lee
Subject: Re: [gnugo-devel] 3.5.3 vs 3.5.4
Date: Sat, 21 Feb 2004 11:50:54 -0800

> > Seems that something was broken in gnugo_3_5_4
> List of patches that can be theoritically responsible for something
> bad between 3.5.3 and 3.5.4:
> paul_5_4.2a. A simple followup to paul_5_4.2 below.
> arend_5_4.3. Break-in code now uses new cache. (very unlikely)
> splee_5_4.1b. Revision of estimate_lunch_eye_value(). Supercedes
> splee_5_4.1a. Revision of splee_5_4.1. Semeai tweak.
> paul_5_4.2. Semeai patch.
> paul_5_4.1. Seki code improvements. (very unlikely)
> gunnar_5_4.7. Tuning. (large patch)
> martin_5_4.1b. Revision of martin_5_4.1a. Revision of martin_5_4.1.
> Owl tuning. (might waste node, don't know counters)
> evan_5_4.2a. Revision of evan_5_4.2. Tuning. (hardly)
> gunnar_5_4.1. Tuning. (very good breakage -- unlikely)
> arend_5_4.1. Breakin fix. (very unlikely)
> Not too many candidates.  Anyone wants to check?  The main problem
> is to determine on what to check.
> Paul

I would think it's hard to say any patch is wrong. Without any doubt gnugo
3.5.4 knows more than 3.5.3 and 3.4. From one case of the last examples I
studied it appears that gnugo 3.4 "happened to kill" a group of gnugo 3.5.4
without knowing it. The other case is that gnugo 3.5.4 knows a seki case and
revised the status of a group from critical to alive, so that the
happened-to-be-good owl move is ignored, while gnugo 3.4 didn't know this

SP Lee

reply via email to

[Prev in Thread] Current Thread [Next in Thread]