Skip to content

Evaluation speed optimization #6

@GoogleCodeExporter

Description

@GoogleCodeExporter
Instead of calculating the material value for each player every time in the
evaluation ( by iterating through all pieces ), it would be a good idea to
keep the board's material value inside the Board class and simply updating
it. That way it will shave some time off, after several million evaluations.


Original issue reported on code.google.com by Claudiu Bogdan Mihail on 25 Jun 2009 at 12:18

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions