Conversation
| :toctree: generated/ | ||
| :nosignatures: | ||
|
|
||
| optuna.integration.TFKerasPruningCallback |
There was a problem hiding this comment.
Not sure, but should I refer to optuna_integration.tfkeras.TFKerasPruningCallback instead?
There was a problem hiding this comment.
I'm not sure, but if we use optuna-integration, we must install optuna too. So, I think it is fine to use each integration module in optuna namespace.
There was a problem hiding this comment.
Thanks for your reply. In this PR, let us prioritize consistency, and let's discuss it separately.
Codecov Report
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. @@ Coverage Diff @@
## main #21 +/- ##
======================================
Coverage ? 0.00%
======================================
Files ? 10
Lines ? 531
Branches ? 0
======================================
Hits ? 0
Misses ? 531
Partials ? 0 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
HideakiImamura
left a comment
There was a problem hiding this comment.
Thanks for the PR. I have several comments. PTAL.
| :toctree: generated/ | ||
| :nosignatures: | ||
|
|
||
| optuna.integration.TFKerasPruningCallback |
There was a problem hiding this comment.
I'm not sure, but if we use optuna-integration, we must install optuna too. So, I think it is fine to use each integration module in optuna namespace.
c2ad88e to
1dd2ebd
Compare
|
Thank you for your careful review. Fixed the broken link and applied |
|
Thanks! |
Motivation
This PR is a part of optuna/optuna#4484. It isolates the
tf.kerasintegration.Description of the changes
Move
optuna/integration/tfkeras.pytooptuna_integration/tfkeras.py