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
Add quickstart for pytorch flavor #10737
Add quickstart for pytorch flavor #10737
Conversation
Documentation preview for 0b38386 will be available here when this CircleCI job completes successfully. More info
|
Signed-off-by: chenmoneygithub <chen.qian@databricks.com>
6835a47
to
22c2a70
Compare
docs/source/deep-learning/pytorch/quickstart/pytorch_quickstart.ipynb
Outdated
Show resolved
Hide resolved
docs/source/deep-learning/pytorch/quickstart/pytorch_quickstart.ipynb
Outdated
Show resolved
Hide resolved
docs/source/deep-learning/pytorch/quickstart/pytorch_quickstart.ipynb
Outdated
Show resolved
Hide resolved
docs/source/deep-learning/pytorch/quickstart/pytorch_quickstart.ipynb
Outdated
Show resolved
Hide resolved
docs/source/deep-learning/pytorch/quickstart/pytorch_quickstart.ipynb
Outdated
Show resolved
Hide resolved
docs/source/deep-learning/pytorch/quickstart/pytorch_quickstart.ipynb
Outdated
Show resolved
Hide resolved
docs/source/deep-learning/pytorch/quickstart/pytorch_quickstart.ipynb
Outdated
Show resolved
Hide resolved
docs/source/deep-learning/pytorch/quickstart/pytorch_quickstart.ipynb
Outdated
Show resolved
Hide resolved
"source": [ | ||
"## Connect to MLflow Tracking Server\n", | ||
"\n", | ||
"Before implementing the training loop, we need to configure the MLflow tracking server because we will log data into MLflow during training.\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.
We can replace this entire block with the page reference here: https://www.mlflow.org/docs/latest/getting-started/running-notebooks/index.html
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.
Personally I really like an integrated experience while reading through guides/tutorials, which means the guide/tutorial is the only doc I need to read to get the work done. If it is a ipython notebook, I should be able to click "run all" and wait for the result (filling some prompted info is required tho, like credentials or so).
docs/source/deep-learning/pytorch/quickstart/pytorch_quickstart.ipynb
Outdated
Show resolved
Hide resolved
docs/source/deep-learning/pytorch/quickstart/pytorch_quickstart.ipynb
Outdated
Show resolved
Hide resolved
docs/source/deep-learning/pytorch/quickstart/pytorch_quickstart.ipynb
Outdated
Show resolved
Hide resolved
docs/source/deep-learning/pytorch/quickstart/pytorch_quickstart.ipynb
Outdated
Show resolved
Hide resolved
docs/source/deep-learning/pytorch/quickstart/pytorch_quickstart.ipynb
Outdated
Show resolved
Hide resolved
Signed-off-by: chenmoneygithub <chen.qian@databricks.com>
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! Just some small nits
"source": [ | ||
"## Task Overview\n", | ||
"\n", | ||
"In this guide, we will demonstrate the functionality of MLflow with PyTorch through a simple MNIST image classification task. We will build a convolutional neural network as the image classifier, and log the following information to mlflow:\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.
Should we say FashionMnist here since Mnist is a different dataset
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.
good catch!
Signed-off-by: chenmoneygithub <chen.qian@databricks.com>
Signed-off-by: chenmoneygithub <chen.qian@databricks.com>
馃洜 DevTools 馃洜
Install mlflow from this PR
Checkout with GitHub CLI
Related Issues/PRs
#xxxWhat changes are proposed in this pull request?
Add a quickstart guide on pytorch flavor.
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/deployments
: MLflow Deployments client APIs, server, and third-party Deployments integrationsarea/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/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