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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keras 3.0 Logging With MLflow #10415
Conversation
Documentation preview for 3a4e6ef will be available here when this CircleCI job completes successfully. More info
|
@@ -0,0 +1,8 @@ | |||
Getting Started with MLflow + Keras 3.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add a landing page for this that is similar to the one created for transformers in this PR? #10360
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Jesse, well written!
Some minor comments. For the images, could you try uploading the images to imgur.com and link it here? It's not a perfect solution but should work for us now.
docs/source/deep-learning/keras/quickstart/quickstart_keras_core.ipynb
Outdated
Show resolved
Hide resolved
docs/source/deep-learning/keras/quickstart/quickstart_keras_core.ipynb
Outdated
Show resolved
Hide resolved
docs/source/deep-learning/keras/quickstart/quickstart_keras_core.ipynb
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Let's fix the build-doc CI, the error msg is:
/home/circleci/project/docs/source/deep-learning/keras/quickstart/quickstart_keras_core.ipynb:15: WARNING: Content block expected for the "raw" directive; none found.
/home/circleci/project/docs/source/deep-learning/keras/quickstart/quickstart_keras_core.ipynb:15: WARNING: Content block expected for the "raw" directive; none found.
/home/circleci/project/docs/source/deep-learning/keras/quickstart/quickstart_keras_core.ipynb:15: WARNING: Content block expected for the "raw" directive; none found.
/home/circleci/project/docs/source/deep-learning/keras/quickstart/quickstart_keras_core.ipynb:951: WARNING: Title level inconsistent:
}, | ||
"source": [ | ||
"# Get Started with Keras 3.0 + MLflow\n", | ||
"**Author:** Jesse Chan<br>\n", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Our current doc does not show the author name, we can delete the author/date block.
} | ||
], | ||
"source": [ | ||
"!pip install -q keras-core mlflow jax jaxlib torch tensorflow" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For some reason our sphinx lint complains about this line. Let's inline this with text block to bypass the warning in doc-build.
|
||
.. raw:: html | ||
|
||
<a href="quickstart/quickstart_tensorflow.html" class="download-btn">View the Quickstart</a> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<a href="quickstart/quickstart_tensorflow.html" class="download-btn">View the Quickstart</a> | |
<a href="quickstart/quickstart_keras_core.html" class="download-btn">View the Quickstart</a> |
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
d72adba
to
56f606a
Compare
Signed-off-by: Jesse Chan <jesse.chan@databricks.com>
馃洜 DevTools 馃洜
Install mlflow from this PR
Checkout with GitHub CLI
Related Issues/PRs
#xxxWhat changes are proposed in this pull request?
How is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/artifacts
: Artifact stores and artifact loggingarea/build
: Build and test infrastructure for MLflowarea/docs
: MLflow documentation pagesarea/examples
: Example codearea/gateway
: AI Gateway service, Gateway client APIs, third-party Gateway integrationsarea/model-registry
: Model Registry service, APIs, and the fluent client calls for Model Registryarea/models
: MLmodel format, model serialization/deserialization, flavorsarea/recipes
: Recipes, Recipe APIs, Recipe configs, Recipe Templatesarea/projects
: MLproject format, project running backendsarea/scoring
: MLflow Model server, model deployment tools, Spark UDFsarea/server-infra
: MLflow Tracking server backendarea/tracking
: Tracking Service, tracking client APIs, autologgingInterface
area/uiux
: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/docker
: Docker use across MLflow's components, such as MLflow Projects and MLflow Modelsarea/sqlalchemy
: Use of SQLAlchemy in the Tracking Service or Model Registryarea/windows
: Windows supportLanguage
language/r
: R APIs and clientslanguage/java
: Java APIs and clientslanguage/new
: Proposals for new client languagesIntegrations
integrations/azure
: Azure and Azure ML integrationsintegrations/sagemaker
: SageMaker integrationsintegrations/databricks
: Databricks integrationsHow should the PR be classified in the release notes? Choose one:
rn/none
- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/breaking-change
- The PR will be mentioned in the "Breaking Changes" sectionrn/feature
- A new user-facing feature worth mentioning in the release notesrn/bug-fix
- A user-facing bug fix worth mentioning in the release notesrn/documentation
- A user-facing documentation change worth mentioning in the release notes