Stockfish Testing Queue

Finished - 1408 tests

18-12-02 31m queen_attacks2 diff
LLR: -2.95 (-2.94,2.94) [0.00,5.00]
Total: 2053 W: 435 L: 559 D: 1059
sprt @ 10+0.1 th 1 Fixed version. Remove "& b" (it performs terribly) and solve the pinning problem by reordering the code so that the "pos.blockers_for_king(Us) & s" condition comes after the expansion of b.
18-12-02 31m queen_attacks2 diff
LLR: -2.96 (-2.94,2.94) [0.00,5.00]
Total: 1423 W: 264 L: 390 D: 769
sprt @ 10+0.1 th 1 I'm finally ready to try the originally-intended all-sliders case discussed with Bryan and @protonspring. Add in bishops.
18-12-02 31m queen_attacks diff
LLR: -2.95 (-2.94,2.94) [0.00,5.00]
Total: 333 W: 35 L: 172 D: 126
sprt @ 10+0.1 th 1 Merge new master and try a small change (possible bugfix?): I hadn't included "& b" because I thought it would be functionally equivalent, but I now realize it is needed when the queen is pinned. Since I'm not 100% sure this will be an improvement, even if more technically correct, I will leave the other test running for now.
18-12-02 31m queen_attacks diff
LLR: -2.96 (-2.94,2.94) [0.00,5.00]
Total: 26660 W: 5765 L: 5766 D: 15129
sprt @ 10+0.1 th 1 Same rank or same file.
18-12-02 31m queen_attacks diff
LLR: -2.95 (-2.94,2.94) [0.00,5.00]
Total: 317 W: 35 L: 176 D: 106
sprt @ 10+0.1 th 1 Realizing that some later uses of attackedBy[][QUEEN] seem to assume direct attacks, try reordering the code to only apply this expansion to attackedBy2.
18-12-02 31m overload_redux diff
LLR: -2.96 (-2.94,2.94) [0.00,5.00]
Total: 13893 W: 3030 L: 3093 D: 7770
sprt @ 10+0.1 th 1 It occurs to me that some Overload cases are now covered by RestrictedPiece. Retry S(10, 5) but exclude RestrictedPiece to avoid inadvertently giving too much bonus.
18-12-02 31m SliderOnQueen_support diff
LLR: -2.96 (-2.94,2.94) [0.00,5.00]
Total: 27637 W: 5997 L: 5993 D: 15647
sprt @ 10+0.1 th 1 Just the bishop case.
18-12-02 31m SliderOnQueen_support diff
LLR: -3.66 (-2.94,2.94) [0.00,5.00]
Total: 33402 W: 7256 L: 7255 D: 18891
sprt @ 10+0.1 th 1 Just the rook case mentioned by Bryan (not the bishop one), fixed.
18-12-02 31m DoubleProtectedKR1 diff
LLR: 2.96 (-2.94,2.94) [0.00,5.00]
Total: 16530 W: 2795 L: 2607 D: 11128
sprt @ 60+0.6 th 1 LTC for @Vizvezdenec.
18-12-01 31m tweak_pruningNPM3 diff
LLR: -2.95 (-2.94,2.94) [0.00,4.00]
Total: 32066 W: 5226 L: 5278 D: 21562
sprt @ 60+0.6 th 1 Rebase onto newest master and attempt a speculative LTC of this 141K yellow. Low throughput (166). I will attempt combo patches if this fails.
18-12-02 31m SliderOnQueen_support diff
LLR: -2.95 (-2.94,2.94) [0.00,5.00]
Total: 32421 W: 7176 L: 7147 D: 18098
sprt @ 10+0.1 th 1 Bugfix: I forgot that SliderOnQueen also applies to bishops, not just rooks, and that case must be handled separately.
18-12-02 31m SliderOnQueen_support diff
LLR: -0.16 (-2.94,2.94) [0.00,5.00]
Total: 2870 W: 624 L: 617 D: 1629
sprt @ 10+0.1 th 1 On the forum, Bryan points out a case where SliderOnQueen is surprisingly blind, perhaps even bugged, with a queen supporting a rook along a file. (See FEN below.) The rook is not given a SliderOnQueen bonus because its landing square further down the file is not attackedBy2[Us]--a condition intended to make sure the landing square is defended--but it will be defended anyway, because the queen will support the rook. Try to fix this case, though it may be too narrow to pass. 7k/1np1br1q/1p1p3r/p2Pp1n1/P1P2pQ1/1NB2P1P/1P2N1PK/4R1R1 w - - 5 56
18-12-01 31m overload_redux diff
LLR: -2.95 (-2.94,2.94) [0.00,5.00]
Total: 21502 W: 4620 L: 4646 D: 12236
sprt @ 10+0.1 th 1 Another of Overload's previous values (and to my knowledge, the last): S(13, 6).
18-12-01 31m overload_redux diff
LLR: -2.95 (-2.94,2.94) [0.00,5.00]
Total: 38085 W: 8266 L: 8211 D: 21608
sprt @ 10+0.1 th 1 I am surprised by the trajectory of the Overload bonus over the course of its three simplifications. The first two (July 18; July 21) expanded its definition to include new positions, and the most recent (today) replaced it with only the newer positions. In other words, the original positions that once gave Elo gains have disappeared. Try a redux Overload patch--the original, narrow version from April--atop the new master.
18-12-01 31m overload_redux diff
LLR: -2.95 (-2.94,2.94) [0.00,5.00]
Total: 24026 W: 5263 L: 5276 D: 13487
sprt @ 10+0.1 th 1 Try a different value this bonus has previously taken, S(16, 7).
18-12-01 31m tweak_pruningNPM diff
LLR: -2.96 (-2.94,2.94) [0.00,4.00]
Total: 141852 W: 31156 L: 30763 D: 79933
sprt @ 10+0.1 th 1 Value 6000.
18-12-01 31m tweak_pruningNPM2 diff
LLR: -2.95 (-2.94,2.94) [0.00,4.00]
Total: 122305 W: 26813 L: 26497 D: 68995
sprt @ 10+0.1 th 1 Value 7000.
18-12-01 31m tweak_pruningNPM2^ diff
LLR: -2.96 (-2.94,2.94) [0.00,4.00]
Total: 67836 W: 14838 L: 14736 D: 38262
sprt @ 10+0.1 th 1 Both directions seem to be performing reasonably well, so try further change in each. Here, value 3000.
18-12-01 31m tweak_pruningNPM^ diff
LLR: -2.94 (-2.94,2.94) [0.00,4.00]
Total: 33740 W: 7356 L: 7387 D: 18997
sprt @ 10+0.1 th 1 Before simplifying away this condition, quickly check to make sure Elo can't be gained with an alternative value. Value 4000.
18-12-01 31m weakKD_attackedBy2^^ diff
LLR: -2.96 (-2.94,2.94) [0.00,5.00]
Total: 30978 W: 6795 L: 6774 D: 17409
sprt @ 10+0.1 th 1 Half effect (coefficient 25).
18-12-01 31m weakKD_attackedBy2^^^ diff
LLR: -2.96 (-2.94,2.94) [0.00,5.00]
Total: 19390 W: 4281 L: 4317 D: 10792
sprt @ 10+0.1 th 1 Give extra king danger for weak kingRing squares that are attacked twice by the enemy. Coefficient 50 (a random guess).
18-12-01 31m weakKD_attackedBy2^ diff
LLR: -2.95 (-2.94,2.94) [0.00,5.00]
Total: 8195 W: 1787 L: 1878 D: 4530
sprt @ 10+0.1 th 1 A shot-in-the-dark attempt at compensation: reduce the singly-attacked case's coefficient.
18-12-01 31m weakKD_attackedBy2 diff
LLR: -2.96 (-2.94,2.94) [0.00,5.00]
Total: 7266 W: 1526 L: 1622 D: 4118
sprt @ 10+0.1 th 1 A shot-in-the-dark attempt at compensation: reduce the constant term.
18-12-01 31m QueenRepulsion diff
LLR: -2.96 (-2.94,2.94) [0.00,5.00]
Total: 8518 W: 1875 L: 1965 D: 4678
sprt @ 10+0.1 th 1 The opposite: endgame only. S(0, 15).
18-12-01 31m QueenRepulsion diff
LLR: -2.97 (-2.94,2.94) [0.00,5.00]
Total: 23038 W: 5094 L: 5112 D: 12832
sprt @ 10+0.1 th 1 A different take on the threat_strongqueen idea. Rather than scaling ThreatByRook[QUEEN], introduce a separate bonus and try middlegame-only. S(25, 0).
18-11-30 31m threat_strongqueen diff
LLR: -2.96 (-2.94,2.94) [0.00,5.00]
Total: 31213 W: 6770 L: 6749 D: 17694
sprt @ 10+0.1 th 1 Return to the simpler (and best so far) version and continue modulating effect size. Divisor 4.
18-11-30 31m threat_strongqueen diff
LLR: -2.97 (-2.94,2.94) [0.00,5.00]
Total: 15873 W: 3421 L: 3475 D: 8977
sprt @ 10+0.1 th 1 See if this 70K STC yellow/108K LTC yellow can be made green. Require that the rook be defended.
18-11-30 31m threat_strongqueen diff
LLR: -2.96 (-2.94,2.94) [0.00,5.00]
Total: 7804 W: 1638 L: 1731 D: 4435
sprt @ 10+0.1 th 1 Require further that the rook not be attacked by two enemies.
18-11-29 31m QueenOverload3 diff
LLR: -2.96 (-2.94,2.94) [0.00,5.00]
Total: 22263 W: 3649 L: 3684 D: 14930
sprt @ 60+0.6 th 1 LTC for @Vizvezdenec.
18-11-29 31m threat_strongqueen^ diff
LLR: -2.96 (-2.94,2.94) [0.00,5.00]
Total: 108414 W: 18179 L: 17870 D: 72365
sprt @ 60+0.6 th 1 This appears to be almost enough to pass STC (LLR < -2.5 after nearly 70K games). Speculative LTC, low throughput (166).
18-11-29 31m threat_strongqueen diff
LLR: -2.96 (-2.94,2.94) [0.00,5.00]
Total: 70851 W: 15699 L: 15481 D: 39671
sprt @ 10+0.1 th 1 Half effect.
18-11-29 31m threat_strongqueen diff
LLR: -2.95 (-2.94,2.94) [0.00,5.00]
Total: 36413 W: 8005 L: 7957 D: 20451
sprt @ 10+0.1 th 1 It seems plausible that this adjustment to ThreatByRook should also be applied to ThreatByMinor. (Half effect for both)
18-11-29 31m threat_strongqueen diff
LLR: -2.96 (-2.94,2.94) [0.00,5.00]
Total: 16232 W: 3490 L: 3542 D: 9200
sprt @ 10+0.1 th 1 I suspect similar ideas have been tried before, but in response to recent forum posts (and on an empty framework), give ThreatByRook[QUEEN] bonus even if the queen is not weak.
18-11-27 31m tweak_overload diff
LLR: -2.95 (-2.94,2.94) [0.00,4.00]
Total: 39157 W: 8560 L: 8570 D: 22027
sprt @ 10+0.1 th 1 +100% (double).
18-11-27 31m tweak_overload diff
LLR: -2.96 (-2.94,2.94) [0.00,4.00]
Total: 9805 W: 2082 L: 2208 D: 5515
sprt @ 10+0.1 th 1 Surprisingly, +100% (double) is performing better than +50%--one of these is lucky or unlucky. As an experiment, keep increasing. Triple Overload.
18-11-27 31m tweak_overload^ diff
LLR: -2.95 (-2.94,2.94) [0.00,4.00]
Total: 9600 W: 1997 L: 2123 D: 5480
sprt @ 10+0.1 th 1 A currently-running [-3, 1] simplifies away Overload, merging some cases of it with Hanging. Notably, both bonuses have a 2:1 mg:eg ratio, though Hanging is much larger. Make sure we can't gain Elo by just scaling up Overload. +50%
18-11-25 31m extend_enpassant diff
LLR: -2.95 (-2.94,2.94) [0.00,5.00]
Total: 26042 W: 5712 L: 5715 D: 14615
sprt @ 10+0.1 th 1 Simple extension for en passant moves.
18-11-24 31m simplify_castleext diff
LLR: 2.95 (-2.94,2.94) [-3.00,1.00]
Total: 88283 W: 14681 L: 14668 D: 58934
sprt @ 60+0.6 th 1 LTC: Extend castling only.
18-11-24 31m simplify_castleext diff
LLR: 2.95 (-2.94,2.94) [-3.00,1.00]
Total: 110948 W: 24209 L: 24263 D: 62476
sprt @ 10+0.1 th 1 On the 16th, before the removal of the depth condition, I tried replacing all castling-rights-changing moves with just castling. It appeared to be a slight Elo gain at STC but insufficient to pass [0, 4] (+0.5 Elo), but what I overlooked was that it made pos.can_castle(us) irrelevant and should have been a simplification. See if this result still holds.
18-11-24 31m tropism_cubic diff
LLR: -2.95 (-2.94,2.94) [0.00,5.00]
Total: 658 W: 116 L: 252 D: 290
sprt @ 10+0.1 th 1 As a small experiment, try an even greater degree for the tropism term in king danger: cubic. tropism^3 / 8
18-11-23 31m passerAttackBy2_2 diff
LLR: -2.95 (-2.94,2.94) [0.00,5.00]
Total: 13605 W: 3045 L: 3109 D: 7451
sprt @ 10+0.1 th 1 S(20, 20) was better than S(10, 10), so try S(30, 30).
18-11-22 31m stochastic8 diff
LLR: -2.95 (-2.94,2.94) [0.00,5.00]
Total: 37153 W: 6295 L: 6268 D: 24590
sprt @ 60+0.6 th 1 LTC for @snicolet
18-11-22 31m passerAttackBy2_2^ diff
LLR: -2.97 (-2.94,2.94) [0.00,5.00]
Total: 52161 W: 11495 L: 11370 D: 29296
sprt @ 10+0.1 th 1 Try removing the rank dependence (of increasing k for a bonus): use a simple S(20, 20) bonus instead.
18-11-22 31m passerAttackBy2_2 diff
LLR: -2.96 (-2.94,2.94) [0.00,5.00]
Total: 7645 W: 1622 L: 1716 D: 4307
sprt @ 10+0.1 th 1 Half effect, S(10, 10).
18-11-22 31m extend_enablecastle diff
LLR: -2.95 (-2.94,2.94) [0.00,5.00]
Total: 5774 W: 1236 L: 1339 D: 3199
sprt @ 10+0.1 th 1 Derived from an idea provided by @GuardianRM. Extend moves that immediately enable castling.
18-11-21 31m passerAttackBy2_2 diff
LLR: -2.95 (-2.94,2.94) [0.00,5.00]
Total: 65972 W: 14666 L: 14471 D: 36835
sprt @ 10+0.1 th 1 Rather than k += 2 if other conditions apply, k++ independent of other conditions.
18-11-21 31m passerAttackBy2_2 diff
LLR: -2.96 (-2.94,2.94) [0.00,5.00]
Total: 59309 W: 13041 L: 12881 D: 33387
sprt @ 10+0.1 th 1 Requiring rook defense was absolutely terrible: red in 5.2K games. Try requiring that the passer is doubly defended but not by a rook at all.
18-11-21 31m ThreatByKing_hanging diff
LLR: -2.96 (-2.94,2.94) [0.00,5.00]
Total: 35407 W: 7791 L: 7748 D: 19868
sprt @ 10+0.1 th 1 On the forum's suggestions thread, Bryan pointed out that ThreatByKing covers some cases where the enemy target is defended, and thus the threats are at the very least not immediate. Try requiring that the targets of ThreatByKing be completely undefended.
18-11-21 31m passerAttackBy2_2 diff
LLR: -2.95 (-2.94,2.94) [0.00,5.00]
Total: 23957 W: 4011 L: 4038 D: 15908
sprt @ 60+0.6 th 1 LTC. k += 2 for a doubly protected passer where at least one defender is a rook, bugfixed version.
18-11-21 31m ThreatByKing_hanging diff
LLR: -2.95 (-2.94,2.94) [0.00,5.00]
Total: 19414 W: 4305 L: 4340 D: 10769
sprt @ 10+0.1 th 1 This change seems to reduce the number of ThreatByKing positions by about a quarter. Increase ThreatByKing by a quarter to compensate.