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

Logging restarts in the bi-objective case #1073

Closed
brockho opened this issue Jun 9, 2016 · 2 comments
Closed

Logging restarts in the bi-objective case #1073

brockho opened this issue Jun 9, 2016 · 2 comments

Comments

@brockho
Copy link
Contributor

brockho commented Jun 9, 2016

For some reason, the bi-objective logger does not log restarts in .rdat files as in the single-objective case. Discussing with @ttusar about how to reconstruct the data sets from the archive files, it might be the best solution to log these restarts directly in the archive files (as additional comment lines) instead of writing .rdat files. Like that, runs can be fully reconstructed from the archive folder (as soon as the largest evaluation count per problem is written as well). Note that both the additional lines in the .adat and the .rdat files would be only produced for the convenience of the user without affecting the postprocessing.

@nikohansen
Copy link
Contributor

The code-experiment/build/python/example_experiment2.py now records the stopping conditions from the algorithm after each launch.

@brockho
Copy link
Contributor Author

brockho commented Jan 19, 2021

Can this be closed? From discussions in the recent past, we realized that independent restarts do not make sense in our setting where the performance measure is based on the hypervolume of the entire set of non-dominated solutions, found so far.

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

2 participants