Mixed up engine

@asdf5656 Both the arrow and the evaluation are server analyses, no? Why are they different?

@sheckley666 You mean Ne5 is 3rd best?

@StingerPuzzles If the arrow recommends an inaccuracy that's not exactly harmless.

@StingerPuzzles said in #7:
> It's an often reported harmless bug. In fact it actually provides useful information.
Harmless bug?
I thought it would bite

@Zubbubu Yes, Ne5 is 3rd best move.

@saurabhsangeeth

The little arrows are next best moves. The big arrow is saying: Mate the mf.

@Zubbubu said in #15:
> @saurabhsangeeth
>
> The little arrows are next best moves. The big arrow is saying: Mate the mf.
I don't think there's a next best move when you have a mate in 1

@saurabhsangeeth

Of course there's a next best move. Consider: Rd3 loses your R. So clearly that would be worse than the two options indicated by the little arrows. In other words, those two options are BETTER than losing your rook on d3, and we can take the engine's word for it that those are the two best options after the mating move, which is the best option. Remember, the computer doesn't care about human emotions like: "Duh! It's obvious!". It is providing objectively best, 2nd best, 3rd best, options, whether or not one would be insane (or extremely weak) to miss the best option. I don't see a problem with that.

Enough of this rant let me do my job
-Stockfish
(JK)

I'm just here for the Captcha. Sorry guys.

@Zubbubu
@asdf5656 said in #6:
> The server analysis only goes 3,500,000 nodes deep (correct me if this number is wrong).
> Otherwise server analyses would take forever.

The answer I received on discord from dev revoof:

-----quote
revoof:
here in the code is the go command: github.com/niklasf/fishnet/blob/4639eccf202526dd91dc20d7daa4d9d78abc2ad7/src/stockfish.rs#L331-L335.
if you trace it back all the way to lila, you will find github.com/ornicar/lila/blob/36472373153769f84a94c9db95e9292608c85360/conf/base.conf#L422.
so it's a fixed node limit, and depth may vary. indeed analysis in the browser surpasses it quite quickly, when modern webassembly features are supported by the browser
-----end quote
analysis.nodes = 1500000 # sf 15 dev

So the answer is that depth varies and that the "go" command is based on
a maximum number of nodes as 1.5 million. aka 1.5 mN.

Note: That is the way fishnet works - the Lichess analysis mode. The browser uses depth as the control; not nodes.

@jomega
Thank you for the information, but in the morass of details a simple point is not clear to me. There are two distinct evaluations: the arrow indicator and the analysis. Are you saying one is on the server , the other on the browser ?? Are they both stockfish but different depths? You're going into a lot of detail but my original question remains.