judicata wrote:
I'm not entirely sure what you mean, but I'll speculate on anything I think may be useful for people reading a review. Are you referring to my speculation that Crazy Stone is designed to seek center influence to capitalize on its fighting ability? If so, I respectfully disagree--a layperson is in a position to offer such speculation. I try to make it clear that I'm speculating, and comments are always offered simply for what they're worth.
Of course people shouldn't pretend to be an expert on something they're not, but anyone from novices to hobbyists to professionals can comment on what they observe and speculate. Also, I have a propensity for anti-elitism, so your comment may have hit a nerve

.
Nope. We should report on how we see the programs behave at the user level. You gave an example of that. I was referring to speculation about what details of implementation might be responsible the behavior. As to the degree professionalism required to comment on that, well there are program design/coding issues that novices and hobbyists can understand and some that would challenge even most folks making their living in the cypher mines. This is one of the latter, a tough one even for the pros. Why do I say that? A little unfair advantage on my part. See, all the players in this game (those trying to write implementations) have access to the academic papers behind the algorithm. Nevertheless, even one of the people who was a leader in the race before the MCTS algorithm came along has failed to get his implementation of a MCTS version strong enough, fast enough. I know because I did volunteer beta testing for him and had to tell him "you are at least 2-3 stones behind". Part of that might be at the algorithm tweaking level (where to prune, etc.) but part is probably elegance in choice of data structures and method.
My "line of country" (though not with game playing software). Many were the times I ended up having to rewrite a program (designed and written by another pro) and sometimes managed almost two magnitudes improvement in performance (same language, just different design and coding). It is very hard to teach this (given
this problem, how to recognize what are the data structures and algorithms that make an elegant/efficient solution possible). BTW, this does affect my attitudes about what is reasonable or unreasonable in terms of the price of software. In other words, I know what I expected to get paid per hour of this level of work.