About two weeks to go! Deadlines and submission guidelines are available at the tournament website.
I also took some time to spin up an Amazon EC2 instance of c3.large size, on which all the AIs will be running. Here are OpenTafl’s benchmark mode results for v0.4.4.7b:
./OpenTafl.sh --benchmark
OpenTafl v0.4.4.7b log from Sat Dec 03 02:20:31 UTC 2016 on ip-172-31-5-180
Java version: 1.8.0_111
Brandub 7: finished in 27.429 sec, searching 1133609 nodes to depth 6
Tablut 9: finished in 36.718 sec, searching 1127203 nodes to depth 5
Copenhagen 11: finished in 6.562 sec, searching 23562 nodes to depth 4
Tablut 15: finished in 11.343 sec, searching 113556 nodes to depth 4
These results are directly comparable to the results of any other benchmark run using OpenTafl v0.4.4.7b, and are a good indicator of both single-core performance and memory performance. (For comparison, my laptop, with a recent Core i7m, is about twice as fast on Brandub through Copenhagen, and about 33% faster for Tablut.) Plan accordingly!
I’ll be running the OpenTafl server on another EC2 instance in the same datacenter, to reduce the influence of latency on AI time usage planning. When tournament games are ongoing, I’ll post the server address here so people can spectate.