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.

Sign up for GitHub

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

Jump to bottom

Save history of optima to database #141

Open
kiudee opened this issue Jun 28, 2021 · 0 comments
Open

Save history of optima to database #141

kiudee opened this issue Jun 28, 2021 · 0 comments
Labels
distributed Related to the distributed tuning framework enhancement New feature or request Priority: Low

Comments

@kiudee
Copy link
Owner

kiudee commented Jun 28, 2021 •
edited
Loading

The tuning server of the distributed framework computes the current optimum regularly. It is often interesting to look at the convergence of the parameters over time. That is why these optima should also be logged to the database.

This change requires setting up Alembic which allows us to version control patches to the database.
@kiudee kiudee added enhancement New feature or request Priority: Low distributed Related to the distributed tuning framework labels Jun 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
distributed Related to the distributed tuning framework enhancement New feature or request Priority: Low
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kiudee