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
There was also some good content at the Kubeflow contributor summit in October 2019. I can't find any slides/recordings, but we should get hold of them and use them as input.
The Katib v1alpha3 API includes a new Suggestion CR which tracks the suggestions generated for each trial of an experiment by the corresponding algorithm service. The system architecture has been redesigned to make it more Kubernetes-native with better support for events. The v1alpha3 API also comes with a new metric collector implementation. Users can specify the metric collector type in the experiment config. Currently supported types are StdOutCollector(default), FileCollector and TFEventCollector. The internal database implementation is also refactored to support multiple database backends. This release also supports Prometheus metrics that includes controller runtime metrics and creation/deletion/success/failure counters for experiments and trials.
The text was updated successfully, but these errors were encountered:
Issue-Label Bot is automatically applying the label kind/feature to this issue, with a confidence of 0.94. Please mark this comment with 👍 or 👎 to give our bot feedback!
The Katib docs on the Kubeflow website don't do justice to the capabilities and UX provided by Katib:
https://www.kubeflow.org/docs/components/hyperparameter-tuning/hyperparameter/
The docs should be more visual, at least providing screenshots to get users oriented. Here's the current Katib starter page:
![image](https://user-images.githubusercontent.com/6138251/69773143-1757c600-11e6-11ea-988c-87f42f42c521.png)
There are some docs on GitHub which we should merge into the website docs:
https://github.com/kubeflow/katib/
There was also some good content at the Kubeflow contributor summit in October 2019. I can't find any slides/recordings, but we should get hold of them and use them as input.
The Kubeflow v0.7 blog post also has useful info:
The text was updated successfully, but these errors were encountered: