Skip to content

Classical Evaluation Improved, but Search is no longer "Tuned" for it. [Regression on Classical-only Search] #3365

@BM123499

Description

@BM123499

First of all, I came here in good faith to talk about a whole section of Stockfish, Classical Evaluation, and I hope we have a clean discussion about it us all.
NNUE has been introduced in Stockfish and improved it a lot, it's undeniable and I not here to speak about how much it improved, but how our following commits may have weakened SF_classical. SF_NNUE and SF_classical have different kind of evaluation and they have different speed.
It's not difficult to see that our tunings and new logics in search.cpp are tuned for hybrid evaluation, so, for other types of evaluation, they may cause a regression.
Of course, for most people, the hybrid evaluation is a way to go. But, for those that for any reason can't (or decided not to) use NNUE, Stockfish 12 (or further) may cause regression on its HCE analyses.

And thanks so far for reading this and hope we improve SF even further.

Reference to SF_classical

Tests, all using HCE Search:
SF_13 vs SF_12
SF_13 vs SF_classical
SF13_dev vs SF_classical

Edited message

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions