-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
[PaddlePaddle] Add autologging support for PaddlePaddle #4751
Conversation
@jinminhao Thanks for the contribution! The DCO check failed. Please sign off your commits by following the instructions here: https://github.com/mlflow/mlflow/runs/3446744880. See https://github.com/mlflow/mlflow/blob/master/CONTRIBUTING.rst#sign-your-work for more details. |
31d96ec
to
0698bc9
Compare
Signed-off-by: Minhao Jin <minhaoj@andrew.cmu.edu>
Signed-off-by: Minhao Jin <minhaoj@andrew.cmu.edu>
Signed-off-by: Minhao Jin <minhaoj@andrew.cmu.edu>
Signed-off-by: Minhao Jin <minhaoj@andrew.cmu.edu>
Signed-off-by: Minhao Jin <minhaoj@andrew.cmu.edu>
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! Thanks @jinminhao for the contribution!
* support autolog Signed-off-by: Minhao Jin <minhaoj@andrew.cmu.edu> * update structure Signed-off-by: Minhao Jin <minhaoj@andrew.cmu.edu> * fix doc Signed-off-by: Minhao Jin <minhaoj@andrew.cmu.edu> * update Signed-off-by: Minhao Jin <minhaoj@andrew.cmu.edu> * make code simpler and fix lint Signed-off-by: Minhao Jin <minhaoj@andrew.cmu.edu> * update Signed-off-by: Minhao Jin <minhaoj@andrew.cmu.edu> * fix lint Signed-off-by: Minhao Jin <minhaoj@andrew.cmu.edu> * update Signed-off-by: Minhao Jin <minhaoj@andrew.cmu.edu> * update Signed-off-by: Minhao Jin <minhaoj@andrew.cmu.edu> * delete autolog example Signed-off-by: Minhao Jin <minhaoj@andrew.cmu.edu> * delete best weights Signed-off-by: Minhao Jin <minhaoj@andrew.cmu.edu> * update Signed-off-by: Minhao Jin <minhaoj@andrew.cmu.edu> * update Signed-off-by: Minhao Jin <minhaoj@andrew.cmu.edu> * update Signed-off-by: Minhao Jin <minhaoj@andrew.cmu.edu> * refacotr Signed-off-by: harupy <hkawamura0130@gmail.com> * clean up Signed-off-by: harupy <hkawamura0130@gmail.com> * refactor Signed-off-by: harupy <hkawamura0130@gmail.com> Co-authored-by: harupy <hkawamura0130@gmail.com> Signed-off-by: Anjali Samad <samad.anjali.14@gmail.com>
What changes are proposed in this pull request?
Add autologging support for paddlepaddle
How is this patch tested?
Unit tests
Release Notes
Is this a user-facing change?
(Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger 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/model-registry
: Model Registry service, APIs, and the fluent client calls for Model Registryarea/models
: MLmodel format, model serialization/deserialization, flavorsarea/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/breaking-change
- The PR will be mentioned in the "Breaking Changes" sectionrn/none
- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" 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