peter wrote:Hi!
Sorry, there I don't get your point. If you know, which move to exclude, what do you need the engine for?
The basic idea goes like this (example):
You let the engine analyze for some time the position you're interested in. It comes out with move A, as white, with a score of 0.20.
Since my time is limited, I get better results by forcing this move and see what the engine thinks about it, basically pruning all the other moves to get deeper.
It comes with move Aa, as black with a score of 0.10.
Extending the line a bit, the engine thinks this move is not as good as it seemed, and I repeat step 1. Now move AaA has a score of 0.00.
The best move the engine has found leads to 0.00 when I go deeper, so what I do, is going back to the original position, and
exclude move A, so the engine searches for an alternative.
Now, the engine will come with move B, and I may choose to look it further (if its score is > 0.00) or go back to move A (if B's is score < 0.00)
This is usually faster than sitting at the original position 2 extra plies (or more) to wait for the engine to realize A is 0.00, faster than using Multi-PV 2 on each position (because in the example, we don't need to search for alternatives for black) and it's impossible to do with engines that don't support Multi-PV or exclude moves (because once the hash is full it'll start running in circles.)