Ticket #29: arend_7_7.3a-avoid_large_scale_side_effect.diff

File arend_7_7.3a-avoid_large_scale_side_effect.diff, 1.3 kB (added by arend, 3 years ago)

avoid side effects between large scale and find_more_owl... by reordering them

  • engine/value_moves.c 

    
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.

RCS file: /cvsroot/gnugo/gnugo/engine/value_moves.c,v
retrieving revision 1.152
diff -u -p -r1.152 value_moves.c
     
    37563756  find_more_attack_and_defense_moves(color); 
    37573757  time_report(2, "  find_more_attack_and_defense_moves", NO_MOVE, 1.0); 
    37583758 
    3759   if (large_scale && level >= 6) { 
    3760     find_large_scale_owl_attack_moves(color); 
    3761     time_report(2, "  find_large_scale_owl_attack_moves", NO_MOVE, 1.0); 
    3762   } 
    3763  
    37643759  if (level >= 6) { 
    37653760    find_more_owl_attack_and_defense_moves(color); 
    37663761    time_report(2, "  find_more_owl_attack_and_defense_moves", NO_MOVE, 1.0); 
     3762  } 
     3763 
     3764  if (large_scale && level >= 6) { 
     3765    find_large_scale_owl_attack_moves(color); 
     3766    time_report(2, "  find_large_scale_owl_attack_moves", NO_MOVE, 1.0); 
    37673767  } 
    37683768 
    37693769  find_more_semeai_moves(color);