Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Horizon effect
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Examples == In [[chess]], assume a situation where the computer only searches the game tree to six [[Ply (game theory)|plies]] and from the current position determines that the queen is lost in the sixth ply; and suppose there is a move in the search depth where it may [[sacrifice (chess)|sacrifice]] a rook, and the loss of the queen is pushed to the eighth ply. This is, of course, a worse move than sacrificing the queen because it leads to losing both a queen and a rook. However, because the loss of the queen was pushed over the horizon of search, it is not discovered and evaluated by the search. Losing the rook seems to be better than losing the queen, so the sacrifice is returned as the best option whereas delaying the sacrifice of the queen has in fact additionally weakened the computer's position. As another example, while some [[perpetual check]]s quickly trigger a threefold-repetition draw, others can involve a queen chasing a king around across the board, varying the position each time, meaning the actual forced draw could be many moves into the future. If a quiescence search playing out the checks isn't done, then the AI might not detect the possibility, and can let the engine blunder a winning position into a drawn one. In [[Go (board game)|Go]], the horizon effect is a major concern for writing an AI capable of even beginner-level play, and part of why alpha-beta search was a weak approach to [[Computer Go]] compared to later machine learning and pattern recognition approaches. It is a very common situation for certain stones to be "dead" yet require many moves to actually capture them if fought over. The horizon effect may cause a naive algorithm to incorrectly assess the situation and believe that the stones are savable by calculating a play that seems to keep the doomed stones alive as of the move the search tree stops at. While the death of the group can indeed be delayed, it cannot be stopped, and contesting this will only allow more stones to be captured. A classic example that beginners learn are [[Ladder (Go)|Go ladders]], but the same general idea occurs even in situations that aren't strictly ladders.<ref>{{cite web |url=https://staff.itee.uq.edu.au/janetw/Computer%20Go/go-vs-chess.pdf |title=The Challenge of Go as a Domain for AI Research: A Comparison Between Go and Chess |first=Jay |last=Burmeister |first2=Janet |last2=Wiles |date=1995 |pages=181-186 |doi=10.1109/ANZIIS.1995.705737 }}</ref> {| style="display:inline; display:inline-table;" |- | style="border: solid thin; padding: 3px;" | {{Goban 13x13 <!--A B C D E F G H J K L M N--> | | | | | | | | | | c| b| b| b<!--13--> | | | | | | | | | | | w| w| w<!--12--> | | | | | | | | | | | | | <!--11--> | | | | x| | | | | | x| | | <!--10--> | | | | | | | | | | | | | <!--9--> | | | | | | | | | | | | | <!--8--> | | | | | | | | | | | | | <!--7--> | | | | | | | | | | | | | <!--6--> | | | | | | | | | | | | | <!--5--> | | | | x| | | | | | x| | | <!--4--> | | | | | | | | | | | | | <!--3--> | | | | | | | | | | | | | <!--2--> | | | | | | | | | | | | | <!--1--> <!--A B C D E F G H J K L M N-->|14}} |- | style="text-align:center" | Black to play. Playing on the X spot<br/>gets the stones briefly out of [[Atari (go)|atari]],<br/>and thus appears a useful move<br/>to shallow searches... |} {| style="display:inline; display:inline-table;" |- | style="border: solid thin; padding: 3px;" | {{Goban 13x13 <!--A B C D E F G H J K L M N--> | | b| b| b| b| b| b| b| b| b| b| b| b<!--13--> | | w| w| w| w| w| w| w| w| w| w| w| w<!--12--> | | | | | | | | | | | | | <!--11--> | | | | x| | | | | | x| | | <!--10--> | | | | | | | | | | | | | <!--9--> | | | | | | | | | | | | | <!--8--> | | | | | | | | | | | | | <!--7--> | | | | | | | | | | | | | <!--6--> | | | | | | | | | | | | | <!--5--> | | | | x| | | | | | x| | | <!--4--> | | | | | | | | | | | | | <!--3--> | | | | | | | | | | | | | <!--2--> | | | | | | | | | | | | | <!--1--> <!--A B C D E F G H J K L M N-->|14}} |- | style="text-align:center" | ...but Black loses far more than<br/>three stones if the [[Ladder (Go)|ladder]] is<br/>foolishly played to completion. |}
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)