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

Automatic performance estimating #2

Open
donRumata03 opened this issue Dec 3, 2020 · 2 comments
Open

Automatic performance estimating #2

donRumata03 opened this issue Dec 3, 2020 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@donRumata03
Copy link
Owner

It would be great to be able to estimate optimization algorithm performance automatically.
Now the creator has no ideas which algorithm is better is worth continuing developing.
This might prevent situations like this one #1

@donRumata03 donRumata03 added the enhancement New feature or request label Dec 3, 2020
@donRumata03 donRumata03 self-assigned this Dec 3, 2020
@donRumata03
Copy link
Owner Author

donRumata03 commented Dec 3, 2020

It probably makes sense to estimate performance this way:

Given some points (specific for a function) and a score for each, we compute total verdict (taking the number of fitness function computations, used to achieve the point, into account).

@donRumata03
Copy link
Owner Author

To compute the number of iterations required to achieve a given point (target function value), it makes sense to use binary or n-ary search on logariphmated space between a really big and a small number (probably, 0) of max_iterations transmitted to the algorithm. The boolean predicate for the x-ary search shows if the function succeed to achieve the given value in this iterations. If it didn't even success to find this value in max amount of iterations, do something with the creator of the algorithm!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant