I seriously doubt there will be repeat games with FatMan or Mogo. Maybe with Gnugo but their only opponent will be Monte Carlo type programs.
Nevertheless, as a sanity check we can look for repeat games. I've always want to make a program to test for repeat games - taking symmetries into account - so I will make one for this later unless such a thing already exists. - Don terry mcintyre wrote: > Don, > > All sounds good. Yes, I forgot to mention that I am using linux. > > If possible, I'd suggest that the process be as automatic as possible - > rather than the user emailing results, periodically ssh or scp outbound to > your computer. > > The copies of gnugo/mogo/fatman and any other programs would need to be local > copies, in order to prevent conflict with existing versions. I'd suggest a > current version of Gnugo - they are at 3.7.11 now, I think. Gunnar, any > interesting updates in the pipeline? > > An automatic status page on the central www server would provide excellent > feedback. > > I'd also love to see the games themselves, the better to capture blunders and > convert them to test cases which can be used to test subsequent go programs. > A few good test cases might encourage fixes for the current weaknesses with > respect to nakade plays, for instance. > > Will there be a method at the top level to weed out duplicate games? > > How confident are we that resignation works properly? There were some odd > results in the latest KGS tournament, if I recall correctly; programs were > resigning won games. > > > Terry McIntyre <[EMAIL PROTECTED]> > From: Don Dailey <[EMAIL PROTECTED]> > > > I assume you are on a unix based system since you are talking aboing > nicing a job. Good. I can easily deal with Mac's or Linux for this. > > What I would do is bundle up everything into a tarball and have it all > set up and ready to go, so that it would not be much work on your part. > The tarball would consist of: > > 1. FatMan binary modifed to support LONG levels. > 2. autotest binary (or if you have a tclkit just the kit.) > 3. copy of mogo. > 4. a sqlite database that already has the registry set up for you. > 5. A script that starts the tester for you. > 6. A script that extracts the results so they can be mailed. > > You could mail the results periodically, whenever it was convenient > for > you. > > I would probably also include a copy of mogo and gnugo just so that > every test is running the exact same binaries. > > I increased the memory usage of FatMan so that these tests could run > and > the main pool of nodes required for the in memory tree takes only 134 > megs of memory. However, each copy of FatMan would require this much > memory. It's not clear to me how much this was effect your system or > step on your cache. > > I have no idea of the memory requirements of Mogo. We would want to > set a copy of Mogo (or perhaps someone already has) on CGOS to get a > reference point and we would want to run it exactly the same. > > On a fast machine, such as my core 2 duo, at the highest level we > would test it would take about 20 minutes per move in the opening > position. If we turn ON the resign feature of all the programs and > considering that it speeds up as the game progresses, we might get > in > 3 or 4 games per day per machine on the highest 2 levels - of course > other game will go faster. In fact, with resign turned on we may get > in a lot more games than that, even if the highest level was one of > the > players because many games are resignable fairly early. > > I'm still looking at the memory usage, we might get away with cutting > the memory usage in half from the values I previously gave you. > > If you could set up a script to periodically scp the result files to > me, I would set up a web page that continuously updates a web page > with a graph and crosstable similar to CGOS all-time list. > > This would be fun - should I start setting this up? > > - Don > > > > > > > > terry mcintyre wrote: > >> I have two linux desktops, a dual AMD with 1 or 2 gigs and a quad >> > Intel 6600 with 3 gigs RAM; both sit idle much of the time. Can you sketch > the requirements for this test? Will it be using time controls or > fixed numbers of playouts? In the latter case, I can nice the process(es) > when need be. > >> I've also been considering Amazon's EC2 -- one server-month costs >> > about $72. > >> >> Terry McIntyre <[EMAIL PROTECTED]> >> “Wherever is found what is called a paternal government, there is >> > found state education. It has been discovered that the best way to > insure implicit obedience is to commence tyranny in the nursery.” > >> >> Benjamin Disraeli, Speech in the House of Commons [June 15, 1874] >> >> ----- Original Message ---- >> From: Don Dailey <[EMAIL PROTECTED]> >> To: computer-go <computer-go@computer-go.org> >> Sent: Thursday, January 17, 2008 10:11:14 AM >> Subject: Re: [computer-go] Suicide question >> >> >> >> >> Michael Williams wrote: >> >> >>> It is a very nice graph. I wish we could see the next 11 doublings. >>> >>> >> With some help, I could redo this experiment and add: >> >> 1 or 2 more levels. >> A version of gnugo with known strength. >> and/or some fixed version of mogo - which we could simultaneously >> test on CGOS. >> >> I would need an enormous amount of power to complete this with a good >> sample in less than a few months. >> >> Anybody have any linux machines lying around? They need to be >> relatively powerful and probably need at least 1 gig of memory due to >> the large tree size I would have to set up. >> >> - Don >> >> >> >> >> _______________________________________________ >> computer-go mailing list >> computer-go@computer-go.org >> http://www.computer-go.org/mailman/listinfo/computer-go/ >> >> >> >> >> >> >> >> >> > > ____________________________________________________________________________________ > >> Looking for last minute shopping deals? >> Find them fast with Yahoo! Search. >> > http://tools.search.yahoo.com/newsearch/category.php?category=shopping > >> >> >> > ------------------------------------------------------------------------ > >> _______________________________________________ >> computer-go mailing list >> computer-go@computer-go.org >> http://www.computer-go.org/mailman/listinfo/computer-go/ >> > _______________________________________________ > computer-go mailing list > computer-go@computer-go.org > http://www.computer-go.org/mailman/listinfo/computer-go/ > > > > > > > > > ____________________________________________________________________________________ > Never miss a thing. Make Yahoo your home page. > http://www.yahoo.com/r/hs > > ------------------------------------------------------------------------ > > _______________________________________________ > computer-go mailing list > computer-go@computer-go.org > http://www.computer-go.org/mailman/listinfo/computer-go/ _______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
