Re: [Computer-go] Lines of code
I see the idea. Gather stats for the best go playing programs, put the figures into CLOP. Hey presto! You now know exactly how many lines of code the perfect Go playing program needs. Seriously, when comparing source code sizes for different implementations of the same thing, it's often helps if you strip out comments and then compress the code. This removes size differences caused by style issues such as comments, indentation and identifier length etc. Of course comparing size of binaries also gets round these problems, but you can run into difficulties with libraries. Raffles On 09/01/2012 02:51, terry mcintyre wrote: Go programs can have databases too. They can be a compact representation of information which might otherwise be a large amount of case-specific code. Terry McIntyre terrymcint...@yahoo.com Unix/Linux Systems Administration Taking time to do it right saves having to do it twice. *From:* Michael Williams michaelwilliam...@gmail.com *To:* computer-go@dvandva.org *Sent:* Sunday, January 8, 2012 3:13 PM *Subject:* [Computer-go] Lines of code Has there been any studies into the number of lines of code in the top chess/go programs over time? Another measure would be bytes of executable or bytes of executable+data. Obviously the latter grows in chess with endgame databases, so maybe that's less interesting. ___ Computer-go mailing list Computer-go@dvandva.org mailto:Computer-go@dvandva.org http://dvandva.org/cgi-bin/mailman/listinfo/computer-go ___ Computer-go mailing list Computer-go@dvandva.org http://dvandva.org/cgi-bin/mailman/listinfo/computer-go ___ Computer-go mailing list Computer-go@dvandva.org http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
[Computer-go] Lines of code
Has there been any studies into the number of lines of code in the top chess/go programs over time? Another measure would be bytes of executable or bytes of executable+data. Obviously the latter grows in chess with endgame databases, so maybe that's less interesting. ___ Computer-go mailing list Computer-go@dvandva.org http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
Re: [Computer-go] Lines of code
Go programs can have databases too. They can be a compact representation of information which might otherwise be a large amount of case-specific code. Terry McIntyre terrymcint...@yahoo.com Unix/Linux Systems Administration Taking time to do it right saves having to do it twice. From: Michael Williams michaelwilliam...@gmail.com To: computer-go@dvandva.org Sent: Sunday, January 8, 2012 3:13 PM Subject: [Computer-go] Lines of code Has there been any studies into the number of lines of code in the top chess/go programs over time? Another measure would be bytes of executable or bytes of executable+data. Obviously the latter grows in chess with endgame databases, so maybe that's less interesting. ___ Computer-go mailing list Computer-go@dvandva.org http://dvandva.org/cgi-bin/mailman/listinfo/computer-go ___ Computer-go mailing list Computer-go@dvandva.org http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
Re: [Computer-go] Lines of code
For Many Faces, all engine code is c, and line counts are from wc (includes blank lines and comments for .c and .h files) today: The uct/playout code is 10K lines. The old go engine is 55K lines. Some of the is code is not used by the strongest level, but the weaker levels still use the old alpha-beta searcher. There are about 2500 playout pattern gamma constants, about 62K joseki patterns, and about 2K old program patterns (with 51K move-value pairs). version 10, in 1997, had 42K lines of code in 2001 the old engine had 53K lines of code version 11, in 2002, had 52K lines of code The original version 12, 10/2008, had 5.2K lines in the uct/playout code. This was the first release that used MCTS. I don't have any on-line source older than version 10, and the older backups are on floppies, so I can't read them any more J I don't think I even have backups any more for any code before 1990. Everything from version 10 forward is in Git, so I could in theory see how many lines are unchanged since 1997. David From: computer-go-boun...@dvandva.org [mailto:computer-go-boun...@dvandva.org] On Behalf Of Michael Williams Sent: Sunday, January 08, 2012 12:14 PM To: computer-go@dvandva.org Subject: [Computer-go] Lines of code Has there been any studies into the number of lines of code in the top chess/go programs over time? Another measure would be bytes of executable or bytes of executable+data. Obviously the latter grows in chess with endgame databases, so maybe that's less interesting. ___ Computer-go mailing list Computer-go@dvandva.org http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
Re: [Computer-go] Lines of code
awesome. :) s. On Sun, Jan 8, 2012 at 8:12 PM, David Fotland fotl...@smart-games.com wrote: For Many Faces, all engine code is c, and line counts are from wc (includes blank lines and comments for .c and .h files) today: The uct/playout code is 10K lines. The old go engine is 55K lines. Some of the is code is not used by the strongest level, but the weaker levels still use the old alpha-beta searcher. There are about 2500 playout pattern gamma constants, about 62K joseki patterns, and about 2K old program patterns (with 51K move-value pairs). version 10, in 1997, had 42K lines of code in 2001 the old engine had 53K lines of code version 11, in 2002, had 52K lines of code The original version 12, 10/2008, had 5.2K lines in the uct/playout code. This was the first release that used MCTS. I don’t have any on-line source older than version 10, and the older backups are on floppies, so I can’t read them any more J I don’t think I even have backups any more for any code before 1990. Everything from version 10 forward is in Git, so I could in theory see how many lines are unchanged since 1997. David From: computer-go-boun...@dvandva.org [mailto:computer-go-boun...@dvandva.org] On Behalf Of Michael Williams Sent: Sunday, January 08, 2012 12:14 PM To: computer-go@dvandva.org Subject: [Computer-go] Lines of code Has there been any studies into the number of lines of code in the top chess/go programs over time? Another measure would be bytes of executable or bytes of executable+data. Obviously the latter grows in chess with endgame databases, so maybe that's less interesting. ___ Computer-go mailing list Computer-go@dvandva.org http://dvandva.org/cgi-bin/mailman/listinfo/computer-go ___ Computer-go mailing list Computer-go@dvandva.org http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
