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

Evaluate Position instead of (Position, Move) #323

Open
lrozenblyum opened this issue Jul 7, 2019 · 0 comments
Open

Evaluate Position instead of (Position, Move) #323

lrozenblyum opened this issue Jul 7, 2019 · 0 comments
Milestone

Comments

@lrozenblyum
Copy link
Owner

We should RnD on whether it's now better to evaluate just Position.

Benefits

  1. performance (now for every evaluator we calculate new Position (Position, move)
  2. ability to define more strong 'symmetry' via assert
    (e.g. for each move
    eval(Position) = 1 - eval( Position.toMirror() )

Caused by #293

See initial idea
#130 (comment)

@lrozenblyum lrozenblyum added this to the 0.6 milestone Jul 7, 2019
@lrozenblyum lrozenblyum modified the milestones: 0.6, 0.7 Aug 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant