Skip to content

Conversation

@stijnh
Copy link
Member

@stijnh stijnh commented Dec 8, 2025

The search strategies from PyATF are not guaranteed to always give a unique point. It is possible that get_next_coordinates actually returns the same configurations multiple times. However, these should not count towards the evaluation limit (max_feval).

This commit makes it so that only unique configuration evaluations are counted towards the limit.

The search strategies from PyATF are not guaranteed to always give a unique point. It is possible that
`get_next_coordinates` actually returns the same configurations multiple times. However, these should
not count towards the evaluation limit (`max_feval`).

This commit makes it so that only unique configuration evaluations are counted towards the limit.
@stijnh stijnh force-pushed the pyatf-eval-count-fix branch from b45ded8 to e1a42eb Compare December 8, 2025 14:11
@sonarqubecloud
Copy link

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