You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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: