Skip to content
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

Samples - Added the continue_training_from_prod sample #4561

Conversation

Ark-kun
Copy link
Contributor

@Ark-kun Ark-kun commented Sep 28, 2020

This sample demonstrates a common training scenario.
New models are being trained starting from the production model (if it exists).
This sample produces two runs:

  1. The trainer will train the model from scratch and set as prod after testing it
  2. Exact same configuration, but the pipeline will discover the existing prod model (published by the 1st run) and warm-start the training from it.

This sample demonstrates a common training scenario.
New models are being trained starting from the production model (if it
exists).
This sample produces two runs:
1. The trainer will train the model from scratch and set as prod after
testing it
2. Exact same configuration, but the pipeline will discover the existing
prod model (published by the 1st run) and warm-start the training from
it.
@kubeflow-bot
Copy link

This change is Reviewable

@Bobgy
Copy link
Contributor

Bobgy commented Sep 29, 2020

/lgtm
/approve
thank you @Ark-kun

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Bobgy

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit 2471f26 into kubeflow:master Sep 29, 2020
Jeffwan pushed a commit to Jeffwan/pipelines that referenced this pull request Dec 9, 2020
This sample demonstrates a common training scenario.
New models are being trained starting from the production model (if it
exists).
This sample produces two runs:
1. The trainer will train the model from scratch and set as prod after
testing it
2. Exact same configuration, but the pipeline will discover the existing
prod model (published by the 1st run) and warm-start the training from
it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants