[Top][All Lists]

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

Re: [gnugo-devel] Evan's tests

From: Evan Berggren Daniel
Subject: Re: [gnugo-devel] Evan's tests
Date: Tue, 10 Sep 2002 12:42:35 -0400 (EDT)

On Tue, 10 Sep 2002, Gunnar Farneback wrote:

> Evan wrote:
> > Thanks for the comments.  I'll make changes tomorrow.  By way of
> > explanation, I've put up the matchercheck results on the web, which should
> > point out what's going wrong.  In some cases I can't tell exactly what's
> > going on, so I put something in that I thought was close.  I don't have
> > the nngs matcher_check results, so I'll rerun those tomorrow.
> Where on the web?


> > Also, I noticed the | used... but sometimes, I get GTP output back with
> > multiple answers, in which case [1 A|B] wouldn't match "2 A B".  What is
> > the policy for this?  use | and not worry about it?
> This is starting to sound somewhat confused but it may help to know
> that all this is regular expression matching (except an initial "!"
> which is interpreted as a negation of the match result). Thus this
> example from ld_owl.tst
> loadsgf games/life_and_death/ld2.sgf
> 5 dragon_status B18
> #? [critical (B19|E19) (B19|E19|F18|F19)]
> means that either of the following 8 results of the dragon_status
> command count as passed:
> critical B19 B19
> critical B19 E19
> critical B19 F18
> critical B19 F19
> critical E19 B19
> critical E19 E19
> critical E19 F18
> critical E19 F19

Yeah, I got that part.  What I'm wondering about is the fact that

#? [1 B19|E19]

won't match

= 2 B19 E19

because there's no 1 to match.  Should I just drop the 1, as in

#? [B19|E19]

because I think I remember that not working.


Evan Daniel

reply via email to

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