Inconsistent Analysis Engine

Sort:
CraigIreland

What is going on with the analysis tool?

It's taken me a long time to work out why I can't always find the best move from a position but I've finally figured it out. Sometimes, you'll move say F6 and it'll say the best move is F4. So you take the move back and play F4 and it'll say the best move is F6. As you can imagine this situation leads to cases where the engine won't credit any move as best. Worse still there are situations where the best move, by its own analysis can be rated as not even excellent or good.

This can't be by design right? It's got to be a bug.

 

justbefair
CraigIreland wrote:

What is going on with the analysis tool?

It's taken me a long time to work out why I can't always find the best move from a position but I've finally figured it out. Sometimes, you'll move say F6 and it'll say the best move is F4. So you take the move back and play F4 and it'll say the best move is F6. As you can imagine this situation leads to cases where the engine won't credit any move as best. Worse still there are situations where the best move, by its own analysis can be rated as not even excellent or good.

This can't be by design right? It's got to be a bug.

 

Hmm, an actual example with screenshots might help.

GMegasDoux

I have seen that. My assumption is that the engine does not give itself enough time for a reasonable evaluation to form. Even engines have a horrizon where it is not apparant fast enough what the best move is. The app seems to only give a fraction of a second for the analysis. Best you can do is evaluate why a move does or does not work. Sometimes you have to live with the incorrect mark when your move was better.

CraigIreland

Now I know how it works. I'm cool with it. I just wish I hadn't wasted so much time looking for moves which the engine could apparently detect but were never actually there!