There were a lot of side effects by the interaction between large scale moves
and the standard find_more_owl_attack_and_defense_moves(): Since 
large scale moves are tried with lower node limit, and the results get stored
in the caches, find_more_owl_attack_and_defense_moves() should go first
so it is unaffected by these cache results.

Index: engine/value_moves.c
===================================================================
RCS file: /cvsroot/gnugo/gnugo/engine/value_moves.c,v
retrieving revision 1.152
diff -u -p -r1.152 value_moves.c
--- engine/value_moves.c	25 Sep 2005 20:30:02 -0000	1.152
+++ engine/value_moves.c	25 Sep 2005 22:01:26 -0000
@@ -3756,14 +3756,14 @@ review_move_reasons(int *the_move, float
   find_more_attack_and_defense_moves(color);
   time_report(2, "  find_more_attack_and_defense_moves", NO_MOVE, 1.0);
 
-  if (large_scale && level >= 6) {
-    find_large_scale_owl_attack_moves(color);
-    time_report(2, "  find_large_scale_owl_attack_moves", NO_MOVE, 1.0);
-  }
-
   if (level >= 6) {
     find_more_owl_attack_and_defense_moves(color);
     time_report(2, "  find_more_owl_attack_and_defense_moves", NO_MOVE, 1.0);
+  }
+
+  if (large_scale && level >= 6) {
+    find_large_scale_owl_attack_moves(color);
+    time_report(2, "  find_large_scale_owl_attack_moves", NO_MOVE, 1.0);
   }
 
   find_more_semeai_moves(color);