TalkChess.com

It looks to me like this is due to over-aggressive null move pruning, which makes sense, because some of the key lines (for example after the position I posted with "e3" bm) require one or more "quiet" moves to gain an advantage, and that is the sort of thing null move prunes away. I do use verifica...

> However, it seems that it doesn't simulate 'thinking' by wasting it's time; in other words, if set to a lower strength, the engine moves immediately. Is this correct?

It does add idle time to the search. But maybe not enough to be noticeable.

--Jon

You can give them this feeback via info@cheessbase.com.

They do fix things in their programs via updates. I really wish they'd fix the resource leaks in ChessBaxe that make you have to shut it down and restart every once in a while.

Just another note: I said this is a sac, but it isn't really because the pawn is pinned. However, Black was already down material (2 pawns) and is still down one after Nxh4.

--Jon

I have recently been spending quite a bit of time looking at this position, from a game ArasanX-WaspX on FICS recently; 8/6p1/p4p1k/8/4pNqP/PP2PnP1/3r1PK1/2R2Q2 b - - 0 1 Here Wasp played the sac Nxh4+ and won. Arasan saw the move, but not that it is winning for Black. The difficulty is that once Bl...

I also go no improvement with the 12.52 training set over my default set. In fact it was a regression. YMMV.

--Jon

I have a bunch of opening books. Hiarcs book recommends 5. Nf3. A line from that book, also found in the Chessbase French Powerbook 2018, goes:

1. e4 e6 2. d4 d5 3. Nc3 Nf6 4. e5 Ng8 5. Nf3 Ne7 6. Bd3 Nbc6 7. O-O Nb4 8. Be2
Nbc6 9. Qd3

with very good stats for White.

make clang: error: no input files expr: syntax error awk: syntax error at source line 1 context is BEGIN{print CCVER >>> >= <<< awk: illegal statement at source line 1 awk: illegal statement at source line 1 Makefile:186: *** GCC version is : versions < not supported. Stop. You need to follow the b...

maksimKorzh wrote: ↑

Mon Oct 12, 2020 10:51 pm

It would be great, Oliver, I'd appreciate that (pull request would be just awesome). Could you also post what the errors are? I have no idea what compilers are used on MacOS.

The MacOS standard compiler nowadays is clang.

Lc0 is interesting because it finds lines other engines miss, but it still seems like it also steps into blunders that other engines will not fall for.