-
Notifications
You must be signed in to change notification settings - Fork 395
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
TRAINS Integration with keras-tuner #334
Comments
@bmartinn Thank you for the suggestion. My questions is: Are we able to achieve this without the pull request? I think you can achieve this by passing the logger to tuner, right? |
@haifeng-jin Yes you are correct :) |
@bmartinn I think it would be better to put it in TRAINS for easier modification if you update anything. Also to save the maintenance burden of Keras Tuner. Thanks. |
Sure @haifeng-jin , one question, could I get notified if the Logger interface changes ? |
@bmartinn I think the only way is to read the release notes. |
@haifeng-jin initial integration should already be in the text Trains RC :) |
Hi Guys,
I love what you guys are building here, really nice and clean interface to use :)
I thought it might be beneficial to add a deeper integration between TRAINS and keras-tuner.
Specifically to add a TrainsTunerLogger to be used with keras.tuner so that users will have a summary of all the different runs.
At the moment if you add a TensorBoard callback and initialize Trains, all the experiments (and graphs) will be logged,
but what seems to me may add additional value, would be a summary of everything.
This is what I came up with, what do you think?
The text was updated successfully, but these errors were encountered: