GUI = Graphical User Interface, UCI = Universal Chess Interface. A GUI is just the stuff you see that lets you interact with a program. For instance, the GUI in your web-browser is mostly the home, forward and back buttons, and the address bar.
Chess engines are like the engines in a car, while the steering wheel and gas pedals, etc. are like the GUI. They are both pretty useless by themselves. You put an engine inside a GUI and control the engine with the GUI. Arena is an exampl of a GUI for chess engines. There are many good ones (and some that are a little easier to use than Arena that I might recommend, but that's really up to you). UCI is the protocol that most engines use to communicate with the GUI.
As far as analysis scores, the standard way to do it is white is + and black is -, but there are programs out there that display it as the side to move is + and the other side is -. So if your evaluation is alternating from + to - every single half-move, that is probably what's up.
Depth = how many half-moves ahead the computer has calculated
kN/sec = kilonodes per second, basically (I think) how many thousand positions per second the computer is evaluating.
tablebases = a set of completely solved positions. You will see references to 6-man tablebases. This means that every single possible position with up to 6 chess pieces on the board is 100% solved and doesn't require calculation to see how it evaluates--you just look up the answer in a big database.
Opening books = starting from the opening position, an opening book is just a set of preferred moves in each possible position. An opening book can be as simple as just one move. Say, e4. Or it could be e4 then if c5, you play Nf3. All the way up to extremely deep and wide trees of moves, all starting from the opening position. It saves a lot of calculation in very well known positions and also helps shore up a weakness of a lot of engines (opening play).
thnx v much
easier GUIs plz .....
GUI = Graphical User Interface, UCI = Universal Chess Interface. A GUI is just the stuff you see that lets you interact with a program. For instance, the GUI in your web-browser is mostly the home, forward and back buttons, and the address bar.
Chess engines are like the engines in a car, while the steering wheel and gas pedals, etc. are like the GUI. They are both pretty useless by themselves. You put an engine inside a GUI and control the engine with the GUI. Arena is an exampl of a GUI for chess engines. There are many good ones (and some that are a little easier to use than Arena that I might recommend, but that's really up to you). UCI is the protocol that most engines use to communicate with the GUI.
As far as analysis scores, the standard way to do it is white is + and black is -, but there are programs out there that display it as the side to move is + and the other side is -. So if your evaluation is alternating from + to - every single half-move, that is probably what's up.
Depth = how many half-moves ahead the computer has calculated
kN/sec = kilonodes per second, basically (I think) how many thousand positions per second the computer is evaluating.
tablebases = a set of completely solved positions. You will see references to 6-man tablebases. This means that every single possible position with up to 6 chess pieces on the board is 100% solved and doesn't require calculation to see how it evaluates--you just look up the answer in a big database.
Opening books = starting from the opening position, an opening book is just a set of preferred moves in each possible position. An opening book can be as simple as just one move. Say, e4. Or it could be e4 then if c5, you play Nf3. All the way up to extremely deep and wide trees of moves, all starting from the opening position. It saves a lot of calculation in very well known positions and also helps shore up a weakness of a lot of engines (opening play).