Re: [gnugo-devel] arend_3_7.5: blunder more carefully

[Gunnar Farneback]

Arend wrote:
> Instead of confirm_safety() only reporting whether there is an
> unexpected attack, it instead reports its size (and hence, it is renamed
> to blunder_size). Instead of using the somewhat crude
> allowed_blunder_size heuristic, the move valuation tries to do the right
> thing: Subtract the "blunder size" from the move value.
> 
> If it is still the highest valued move, we play it nevertheless.
> Otherwise, we check the next best move for safety.  (This part,
> together with the triggering of reevaluate_ko_threats(), is
> moved out of review_move_reasons into a separate function
> find_best_move() for clarity.)

Good. I have also come to the conclusion that this should be a better
way to handle blunders, but never tried to implement it.

/Gunnar