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

[UX] post_run_summary should indicate it did something #63

Open
eddiebergman opened this issue Apr 25, 2024 · 0 comments
Open

[UX] post_run_summary should indicate it did something #63

eddiebergman opened this issue Apr 25, 2024 · 0 comments
Labels

Comments

@eddiebergman
Copy link
Contributor

If you run python -m neps_examples.basic_usage.hyperparameters, youll get a log that NePs ran.
Now what?

It's not clear that anything was written to disk or where it was written to. If you run the example again, you essentially just get this:

INFO:neps:Starting neps.run using root directory results/hyperparameters_example
INFO:neps:Running bayesian_optimization as the searcher
INFO:neps:Algorithm: bayesian_optimization

INFO:neps:Maximum total evaluations is reached, shutting down

Ideally we should indicate that post_run_summary writes a file somewhere and even more ideally, at the end of execution, indicate what was saved/stored/ran.

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

No branches or pull requests

1 participant