Suggestion: Option to use Self Analysis on Retries Evaluation

When we retry our mistakes in game reviews, it takes too much time for the cloud engine to evaluate a non-best move even though it is only a single line. I think it will be more convenient if we have an option to evaluate each retry line with self-analysis (will be faster) instead of the cloud, so we don't have to wait for almost 1 minute for every single move we make (especially if we keep making the wrong move).

Maybe you could change your settings during a game review? Is is that what you asked for?

(I don't know why the screenshot is so blurred, but hopefully you can see what I mean.

@SpielKalb Thank you, but I don't think that changes how the game review retries are evaluated? I'm assuming that the game review evaluation on retries moves is done on the cloud since it's quite slow right now; unless it's already self-analysis by default?

I'm not sure if a change of the settings works for an already analysed game with your retries. But it should  work, why is the option there in the first place? Just test it. 

I don't have access to the cloud function, so I can't compare.

It would be helpful if there'd be an opportunity to review your settings immediately before you start the analysis.  

The settings are actually simply to change which engine you prefer on self-analysis and game reviews (which uses the cloud), not to use self-analysis on the retries lines.

The Retry uses the cloud analysis Depth, so if you have a higher value, it will take longer. That's the way it should work, since you want the retry to match the depth of the analysis, or you'll end up with a mismatched evaluation that may not be correct.

Does it use cloud analysis or self-analysis? It seems slower than self-analysis even in the same depth to me. 

I'm not 100% certain, just know it uses the cloud depth. 

Thank you for the clarification! I just didn't like having to wait after each retry since it takes up a considerable amount of time to go through the whole game.

If you set your Game Review to depth 18 it will go much faster!

Wow, a staff member engaging in the forums, that's rare!

How about a pop-up window asking you which engine and depth you want to use?

That’s in the settings menu if you click on the gear to the top right of the board while you’re doing analysis!

If you've finished a game and want to start game review, this gear on the top right corner allows you only to change your board design and stuff.  Not the settings for the engine. The game review starts immediately with your previous settings.

You can only change your engine settings after the game review has been already done.

@drittman13 Thanks, I understand that setting the depth level will reduce the waiting time, but my point for the suggestion is that cloud analysis does not have a significant advantage over self-analysis when we only need to evaluate a single position (in this case, the retried move we make).

In a full game review, there are multiple chess positions that can be split into smaller problems, so sending the analysis to the cloud makes sense as we can utilize the cloud's parallel processing capability to get the report faster than doing it locally. However, when we do retries, we are only evaluating the quality of a single move, in which case a self-analysis would be faster if our local CPU is fast enough. It probably saves the time needed to send, queue, and receive the analysis request, a few seconds is a lot considering how many retries we are making per game review.

The issue is that there can be differences in the engine type/settings that users run locally vs the cloud. To make sure the retired move vs game review move has an apples-to-apples comparison of eval, they need to be evaluated with the same exact engine.

Yes, it makes perfectly sense to use the exact same engine and settings in the reply function which had done the analysis in the first place.

But what about my question about a pop-up window to choose the settings before the engine runs the review?

You can change your defaults to whatever you want from either an Analysis Board or previously analyzed game on the analysis tab. You use the settings great on that panel.

Thanks for your reply, @Martin_Stahl!

But here's a slight misunderstanding. I know the system well enough to know where I can find those settings. It's just a little awkward that you have to go back to the analysis board or one of your previous game reviews to change the settings.

In my opinion it would be much better to have a pop-up window when you start the game review. Of course with a button "Do not show this message again" to switch it of.  Or switch it on again in your settings. 

Edit: it doesn't have to be a pop-up window but only a button for the settings you can use on the same page from which you're about to start the review.

The pop-up every time would be annoying. A user preference setting for Insight game views of either Analysis Review or just Analysis would do the trick. 

I too get a little impatient waiting for the depth 26 Review to view the specific move. Going to Analysis with the active move positioned would be a nice alternative,.

One work-around is to click on multiple positions so they can be running in the background. Then review then one by one.

Another work-around rather than Review Retry is to switch to the Analysis tab while showing 5 lines. Then I get an appreciation of the possible move choices. Once on the Analysis tab Max Analysis uses the cloud so it should match the Review retry eval*.  The 5 show lines use the browser and given it is Stockfish 14 NNUE or classic, the move evaluation can be different from the cloud. Not a big deal but at times arriving at a different conclusion.

I vote for an Insight user preference setting for game view of either Analysis Review or Analysis.

*Occasionally some game positions have more than one move that evaluates as best. This can result in a different move recommendation that that presented in Review retry. Running consecutive Max Analysis in the case can result in different first moves.

Hmm ok, I always thought that the self-analysis engine is similar to the cloud one (stockfish, komodo, etc) and the browser could simply force the exact same settings when evaluating retries locally. If it's a very different engine then that makes sense that we have to do cloud even though it's a single position.