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

movecount pruning reduction logic #2605

Closed
wants to merge 2 commits into from

Conversation

praveentml
Copy link

This patch applies a extension to search reduction logic in case the position is not ttPv && !PvNode and is pruned based on move count

passed STC

https://tests.stockfishchess.org/tests/view/5e8092bde42a5c3b3ca2ed35

LLR: 2.94 (-2.94,2.94) {-0.50,1.50}

Total: 78848 W: 15480 L: 15170 D: 48198 Elo +1.05

Ptnml(0-2): 1406, 9310, 17773, 9438, 1497

passed LTC

https://tests.stockfishchess.org/tests/view/5e80bb13e42a5c3b3ca2ed4b

LLR: 2.94 (-2.94,2.94) {0.25,1.75}

Total: 86596 W: 11451 L: 11033 D: 64112 Elo +1.44

Ptnml(0-2): 624, 7993, 25687, 8329, 665

Bench: 5138771

@praveentml
Copy link
Author

can someone help me to understand why these checks are failing ?

@vondele
Copy link
Member

vondele commented Mar 30, 2020

The bench number needs to be in the commit message, not just in this pull request, and must be the number that reflects this patch as applied to current master.
If you're using git, from the command line, try git commit --allow-empty -m "Bench: 5138771" or even better git rebase -i master and select 'reword' for the patch. Afterwards you might need to 'force push' your repository to github.

@praveentml
Copy link
Author

why do I see elo difference in committed messages and fishtest tests.. any guidance please

@vondele
Copy link
Member

vondele commented Mar 30, 2020

The perfect commit message has them included, which is most easily done by creating a 'PR branch' after the test has passed fishtesting. That's also useful for rebasing and squashing the PR in final form.

However, if the commits in the PR do not have that information, the maintainer needs to assemble that from the PR comments prior to merging. That's a bit more work for him, and error-prone, but that's also what is most common.

If a PR contains a single commit and all the information, the PR comment will be automatically prefilled on github, so the patch author only needs to write it a single time.

@praveentml
Copy link
Author

now the checks passed. what would be next steps ? Sorry for asking too many questions but since this is my first test which is passed and would like to understand the process

@vondele
Copy link
Member

vondele commented Mar 30, 2020

Basically, you're done, I'll merge this later.

Apart from a minor nit.... would you like to update the AUTHORS file as well, as part of this PR :-)

@praveentml
Copy link
Author

yes please :-)

@vondele
Copy link
Member

vondele commented Mar 30, 2020

you'll need to modify AUTHORS, git commit and git push that again.

@praveentml
Copy link
Author

praveentml commented Mar 30, 2020

Done. Thank you

@vondele vondele closed this in b7ecdaa Mar 30, 2020
@vondele
Copy link
Member

vondele commented Mar 30, 2020

merged, thanks!

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.

2 participants