“I think move A is a 12 point swing, and move B is a 10 point swing, but move B narrows the search tree for future moves in a way that I think will net me at least 2 more points.”
No. 2 points is a lot at that level. If the commentator would think a move cost 2 points he wouldn’t call it conversative but he would call it an error.
Not playing out every move is more about keeping aji open and not wasting possible ko threads. Unfortunately I don’t know how to translate aji into English.
No. 2 points is a lot at that level. If the commentator would think a move cost 2 points he wouldn’t call it conversative but he would call it an error.
I think B actually results in more points overall, which is why it would play it; my curiosity is what fraction is due to direct effects vs. indirect effects.
For example, one could imagine the board position evaluation function being different for different timing schemes. If you’re playing a blitz game where both players have 10 seconds to play each turn, some positions might move from mildly favoring black to strongly favoring black because white needs to do a bunch of thinking to navigate the game tree successfully.
It goes in that direction but moves don’t have to be used directly to constrain movements elsewhere on the board.
When playing around with Fold.it there was a similar scenario. It’s often possible to run a script to get a higher local maxima. However that made the fold more “rigid”. The experienced folders did only run the script to search the local maximas at the end when they manually did everything that could be done. With my usage of Go vocabulary running the script to optimize locally beforehand would also be a case of aji-keshi.
Aji is for me a phenomological primitive that I learned while playing Go and that I can use outside of Go but which doesn’t have an existing English or German word.
No. 2 points is a lot at that level. If the commentator would think a move cost 2 points he wouldn’t call it conversative but he would call it an error.
Not playing out every move is more about keeping aji open and not wasting possible ko threads. Unfortunately I don’t know how to translate aji into English.
I think B actually results in more points overall, which is why it would play it; my curiosity is what fraction is due to direct effects vs. indirect effects.
For example, one could imagine the board position evaluation function being different for different timing schemes. If you’re playing a blitz game where both players have 10 seconds to play each turn, some positions might move from mildly favoring black to strongly favoring black because white needs to do a bunch of thinking to navigate the game tree successfully.
It’s no blitz game and there plenty of time to think through moves.
Just for the record at my prime I used to play Go at around 2 kyu.
I understand aji as potential for future moves that is currently not too usable but may be after the board configuration has evolved.
It goes in that direction but moves don’t have to be used directly to constrain movements elsewhere on the board.
When playing around with Fold.it there was a similar scenario. It’s often possible to run a script to get a higher local maxima. However that made the fold more “rigid”. The experienced folders did only run the script to search the local maximas at the end when they manually did everything that could be done. With my usage of Go vocabulary running the script to optimize locally beforehand would also be a case of aji-keshi.
Aji is for me a phenomological primitive that I learned while playing Go and that I can use outside of Go but which doesn’t have an existing English or German word.
The way I think about aji is something fragile on a ledge—sure, it’s safe now, but as things shift around, it may suddenly become unsafe.