Re: [Computer-go] Paper “Complexity of Go” by Robson

2018-06-18 Thread Andries E. Brouwer
On Mon, Jun 18, 2018 at 11:54:51AM -0500, Mario Xerxes Castelán Castro wrote: > Hello. I am asking for help finding the following paper: > > J. M. Robson (1983) “The Complexity of Go”. Proceedings of the IFIP > Congress 1983 p. 413-417. > > I could not find it online. There is no DOI anywhere

Re: [Computer-go] SGF

2017-01-05 Thread Andries E. Brouwer
On Fri, Dec 30, 2016 at 01:28:34PM -0700, Anders Kierulf wrote: >> It would be good if your document would clearly state which properties >> are part of the FF[4] standard and which ones you’re adding. >> For example, JD (Japanese Date) is not in FF[4], yet is listed as >> “standardized in this

Re: [Computer-go] SGF

2017-01-02 Thread Andries E. Brouwer
On Mon, Jan 02, 2017 at 11:42:30AM -0800, David Fotland wrote: > I think the character set property just refers to the contents > of comments and similar fields. The sgf format itself is entirely > in the common characters in UTF-8 and US-ASCII. > There is no need to assume a character set before

Re: [Computer-go] SGF

2017-01-01 Thread Andries E. Brouwer
On Fri, Dec 30, 2016 at 01:28:34PM -0700, Anders Kierulf wrote: > It would be good if your document would clearly state which properties > are part of the FF[4] standard and which ones you’re adding. > For example, JD (Japanese Date) is not in FF[4], yet is listed as > “standardized in this

[Computer-go] SGF

2016-12-30 Thread Andries E. Brouwer
The SGF format is wildly successful. It is virtually the unique format in the West, and one of the major formats in the East. However, there is no precise definition of the format. In particular, FF[4] is not precise and where it is precise it is too strict to follow. One troublesome area is that

[Computer-go] recognizing games

2015-01-27 Thread Andries E. Brouwer
Erik van der Werf write on 2014-12-15: Also, if you're not careful, it is quite easy to get duplicate games in your dataset (I've had cases where one game was annotated in chinese, and the other (duplicate) in English, or where the board was simply rotated). My solution around this was to