Ticket #75 (closed defect: fixed)
Generate cut move reasons for cutting moves found during find_connections()
| Reported by: | arend | Owned by: | arend |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.7.11 |
| Component: | source | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | patch: | yes |
Description (last modified by arend) (diff)
When the dragons are built via find_connections(), this is mostly done via patterns such as the following:
Pattern CC503 O . O :+,C c a b ;!xcut(a) && !oplay_disconnect(b,c)
However, so far we throw away the information in case a cutting move is found. This patch changes that by introducing a disconnect_helper(): a wrapper around disconnect() that reports back in case a cutting move is found. The cutting moves are stored in a list in dragon.c, and later CUT_MOVE reasons are generated where appropriate.
The breakage is as follows:
trevorb:220 FAIL G1 [J3] Cut move reasons misevalued global:16 FAIL Q11 [O10] This is ok. 13x13:35 PASS D2 [D2] This is good though lucky. nngs3:330 FAIL F5 [P12|Q11] Very good, F5 most urgent. nngs4:260 FAIL G9 [A4] G9 is ok, increases aji in sente. nngs4:630 FAIL C5 [B6] Bad, Connection misread. nngs4:870 FAIL H9 [C3|C4|D3] Very bad, H9 doesn't do anything. olympiad2004:3 PASS P5 [!Q10] Good. Total nodes: 1690527606 3283875 12582021 Total time: 7647.19 (14078.61)
Attachments
Regression Results
| Attachment | Rev. | PASS | FAIL | Nodes | Status | |
| arend_7_9.4.diff | 2381 | 4 | 6 | +0.71% +0.11% +0.96% | details | |
| arend_7_9.4a.diff | 2381 | 4 | 6 | +0.71% +0.11% +0.96% | details |
Change History
Note: See
TracTickets for help on using
tickets.
