-
Notifications
You must be signed in to change notification settings - Fork 14
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
Standard Frameworks #35
Comments
Hi @johnaohara, great Q and yes ideally we should move to Standard Frameworks. The current choices are primarily due to historic reasons. Early in the Autotune project, we had both optuna and java code bundled into the same docker image and at that time the goal was to keep it simple as well as make sure that the size of Docker image was manageable. Those points are no longer relevant and we are now free to move to Standard Frameworks functionally as well as for the tests |
I wanted to ask some questions about the architecture of the project in general. Is there a reason to not use standard python frameworks/test runners/build tools for HPO?
For example, rather than hand-crafting a REST endpoint based on a HTTP server, would it make sense to use something like Django Rest/Flask?
Similarly with unit/integration tests, would it make sense to use a standard python library for creating and running tests?
The text was updated successfully, but these errors were encountered: