131–140 of 189 posts
Earlier quoted context omitted.
Trouble is, from the existing title it's not clear who had the handicap. So the poster is right to try and fix it.
It's not clear from the revised title either though. In fact I found it even more confusing. The issue is the ambiguity of the wording "with a two-stone handicap", not where it's located in the sentence.
Earlier quoted context omitted.
I would probably phrase it as 'Go grandmaster Shin defeats two-stone-handicapped AI KataGo'
Are there ads on the page? If so, let’s A/B test that along with “Grandmaster Shin Savagely Beats Handicapped Opponent”.
Edit: 10 years since i made the HN account and I only now notice you can't see the scores of other people's comments. Here's hoping the brilliance of the above comment is appreciated.
KataGo isn't very good at exploiting weaker opponents. In chess people were convinced a grandmaster can never be beaten with a knight odds. It's just too easy to simplify the position and win. It was very easy (for a grandmaster) vs already super human Stockfish. It was still kinda easy (for a strong GM) vs 200+ ELO stronger NNUE Stockfish. And then someone made a net optimized for exploiting humans. Its games are am…
Earlier quoted context omitted.
At double-digit kyu level, you should just play every day until you feel you are stuck. After you get stuck, you should pick one thing at a time to focus on improving. But the one thing should probably be related to tesuji or life and death.
Thanks! One follow-up: Any recommended go servers to play on? OGS, Fox, Pandanet?
It can take a few minutes to get a match on OGS. When that happens, I take the opportunity to warm up with a few tsumego drills on goproblems.com
Earlier quoted context omitted.
> Katago (almost certainly significantly stronger than AlphaGo) Interesting KataGo is an open sourced Go program written primarily by David Wu in C++ and recently heavily vibe coded by Claude. It's running on four Nvidia RTX-3090 GPUs with 96GB VRAM. [1] [1] https://github.com/lightvector/KataGo
I had to read your comment five times thinking "how it is written in C++ if it's a go program?" Do'h!
This is the bed all you AI hypers made. Now all manner of disparate tools fall under the banner of AI, with something like this that are not LLMs or transformer type tool, they happen to get lumped with all the rest of them.
Earlier quoted context omitted.
In odds chess bots, the bots would willingly take more disadvantageous positions which are more complicated--probably the bots in GO which are trained for odds do similar? Why does it not avoid such a joseki & play a worse response which it believes the human cannot read?
Go AIs tend to naturally be quite bad at playing handicap games, due to the horizon effect. To massively simplify, when the AI sees that there's a large score gap, it realizes that every move it plays has a very low/high win rate, so it basically picks one at random. The early AIs played lots of slack moves when they were ahead, often making small endgame mistakes but winning by half a point in the end. To account fo…
Earlier quoted context omitted.
>Go grandmaster Shin defeats AI KataGo with a two-stone handicap English is not my first language but for clarity perhaps the title should be: Go grandmaster Shin with a two-stone handicap defeats AI KataGo
fwiw, as a native speaker, your revised version sounds wrong. I'm terrible at grammer, but i think it's because when you put the "with" early in the sentence, it acts as a preposition modifying the noun, where later in the sentence it acts as an adverbial phrase modifying the verb defeat. The handicap is describing the manner of the defeat and not a trait of the grandmaster, so the with has to go at the end of the se…
Also pretty bad at spelling.
Earlier quoted context omitted.
Go AIs tend to naturally be quite bad at playing handicap games, due to the horizon effect. To massively simplify, when the AI sees that there's a large score gap, it realizes that every move it plays has a very low/high win rate, so it basically picks one at random. The early AIs played lots of slack moves when they were ahead, often making small endgame mistakes but winning by half a point in the end. To account fo…
Oh wow, this is one of the best explanations on the thread. I guess the horizon problem is not such an issue for chess bots because reaching endgame is much shorter? And whole-piece handicaps probably snowball way faster than a potential go equivalent