Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Moving up the if position is or has been on the PV reduction, and add a cutnode component #5795

Closed
wants to merge 1 commit into from

Conversation

FauziAkram
Copy link
Contributor

@FauziAkram FauziAkram commented Jan 18, 2025

Moving up the if position is or has been on the PV reduction, and add a cutnode component.
This conflicts with the previous PR, so just choose one to merge.

Passed STC:
LLR: 2.97 (-2.94,2.94) <0.00,2.00>
Total: 16896 W: 4532 L: 4241 D: 8123
Ptnml(0-2): 46, 1905, 4269, 2168, 60
https://tests.stockfishchess.org/tests/view/678ac9b1c00c743bc9e9fc43

Passed LTC:
LLR: 2.94 (-2.94,2.94) <0.50,2.50>
Total: 98388 W: 25154 L: 24705 D: 48529
Ptnml(0-2): 54, 10859, 26954, 11238, 89
https://tests.stockfishchess.org/tests/view/678ad353c00c743bc9e9fcf8

bench: 1498159

bench: 1498159
Copy link

clang-format 18 needs to be run on this PR.
If you do not have clang-format installed, the maintainer will run it when merging.
For the exact version please see https://packages.ubuntu.com/noble/clang-format-18.

(execution 12843341241 / attempt 1)

@cj5716
Copy link
Contributor

cj5716 commented Jan 18, 2025

IMO, the previous PR is better because this one merges the previous PR and another patch, even though the previous PR is a passer on its own.

@Disservin
Copy link
Member

yes the other one is better

@Disservin Disservin closed this Jan 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants