The Territory of Go
This is the second mission about the
Go game
. The first one is the
Eaten Go Stones
.
In this mission you'll learn how to count territory in the Go. Pay attention that this mission is simplified compared to the real game and its rules (the tests won't have cases where stones of one color are on the territory of the other player).
So what is the territory in the Go game? It’s all unoccupied points which are surrounded by the complete and solid stone border consisting of stones of the same color. It can be a form in the center of the board which creates the border by using just the stones, or it can also be the form positioned near the edge of the board which uses...
Look at the picture below. It displays the input data and the conception of the 'territory':
CheckiO Extensions allow you to use local files to solve missions. More info in a blog post.
In order to install CheckiO client you'll need installed Python (version at least 3.8)
Install CheckiO Client first:
pip3 install checkio_client
Configure your tool
checkio --domain=py config --key=
Sync solutions into your local folder
checkio sync
(in beta testing) Launch local server so your browser can use it and sync solution between local file end extension on the fly. (doesn't work for safari)
checkio serv -d
Alternatevly, you can install Chrome extension or FF addon
checkio install-plugin
checkio install-plugin --ff
checkio install-plugin --chromium
Read more here about other functionality that the checkio client provides. Feel free to submit an issue in case of any difficulties.
Welcome to Pair Programming! Engage in real-time collaboration on coding projects by starting a session and sharing the provided unique URL with friends or colleagues. This feature is perfect for joint project development, debugging, or learning new skills together. Simply click 'Start Session' to begin your collaborative coding journey!
You are trying to join a pair programming session that has not started yet.
Please wait for the session creator to join.
It looks like the creator of the pair programming session closed the editor window.
It might happen accidentally, so that you can wait for reconnection.
