Re: [gnugo-devel] Tests inside SGF files

[Dave Denholm]

Trevor Morris <address@hidden> writes:

> Here's an SGF file with three problems encoded in it.
> 
> (
> ;
> FF[4]
> GM[1]
> SZ[19]
> AP[Jago:Version 4.18]
> AW[os][or][oq][op][pp][qp][sp][rp]
> AB[ps][pr][pq][qq][rq][sq]
> C[owl_attack Q1
> 1 S2]
> GN[6c01a]
> ;
> AE[os]
> C[owl_attack Q1
> (2|3) S1]
> ;
> AE[sp]
> C[owl_attack Q1
> 0]
> )
> 
> 
> Similarly, it would be handy when reviewing a game to be able to
> annotate the file directly, with correct moves or tests.
> 
> I find it very slow going to flip between my SGF viewer and the
> *.tst file.  Annotating the SGF file directly seems to make
> a great deal of sense.
> 
> I'm considering enhancing regress.pl to take a marked up SGF test 
> file, and generate the results in much the same way that the *.tst
> files work now.  I'm not quite sure the best way to uniquely
> identify the problems, however - something that's very simple with
> the *.tst files.
> 
> Thoughts?


Not sure if it's relevant, but a while ago I made some changes locally
to take the sgf files from uligo and generate test cases. I can
try to dig that out if you like.

Uligo's datafiles are annotated variations in sgf files.

See section 7 in

  http://www.g0ertz.de/uligo/doc.html



Also, ISTR that some of the early autotest stuff was in the form
of annotated sgf files. It was implemented as a --mode I think.
But I think all that must have been removed now, in favour of the
current scheme.


dd
-- 
address@hidden          http://www.insignia.com