-
Notifications
You must be signed in to change notification settings - Fork 24
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
We should have min/max target estimates of problems #58
Comments
This would be useful to automatically derivate ECDF logger's target bounds for a problem/suite. Then additional simple constructors would be interesting, like: IOHprofiler_ECDF_logger(IOHprofiler_Problem& pb, double max_evals, size_t buckets);
// derivates target bounds from pb and use square domain. |
Is it closed because it's done or close because it will not be added? |
I think because is it done (not super sure..) @jacobdenobel did you incorporate this one in the new code structure? I don' recall anything.. |
This was closed because #54 was merged, in a comment there it was mentioned that this also included a feat for fixing this issue. This is sligthly modified in the restructured version, and there is no seperate accessor for |
Thanks! (and always put a comment when closing issues, that way I will not bother you anymore ;-) |
This checks whether the optimum has been set or not. This is useful for automated filtering of problems with known optimum and allows to avoid a very long test. This brings back the (lost?) `empty` method mentionned in issue IOHprofiler#58.
This checks whether the optimum has been set or not. This is useful for automated filtering of problems with known optimum and allows to avoid a very long test. This brings back the (lost?) `empty` method mentionned in issue IOHprofiler#58.
This checks whether the optimum has been set or not. This is useful for automated filtering of problems with known optimum and allows to avoid a very long test. This brings back the (lost?) `empty` method mentionned in issue IOHprofiler#58.
This checks whether the optimum has been set or not. This is useful for automated filtering of problems with known optimum and allows to avoid a very long test. This brings back the (lost?) `empty` method mentionned in issue IOHprofiler#58.
On a separate accessors than optimum.
The text was updated successfully, but these errors were encountered: