Put the full PyTorch prototype in the jsonnet file. #1119
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* The current pattern in Kubeflow is to put the complete prototype in the jsonnet file. This way the result of ks generate is a .jsonnet file containing a full spec. This makes it easy for users to do complex modifications starting with the prototype as an example. * Configure the prototype to do mnist by default. Fix kubeflow#1114
|
/assign @johnugeorge |
|
/lgtm |
|
/retest |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ankushagarwal 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 |
|
/test all |
|
Cleaned up some old test gpu pods from the cluster. tests should pass now |
|
/retest |
|
/test all |
jlewi
added a commit
to jlewi/kubeflow
that referenced
this pull request
Jul 11, 2018
* The current pattern in Kubeflow is to put the complete prototype in the jsonnet file. This way the result of ks generate is a .jsonnet file containing a full spec. This makes it easy for users to do complex modifications starting with the prototype as an example. * Configure the prototype to do mnist by default. Fix kubeflow#1114
k8s-ci-robot
pushed a commit
that referenced
this pull request
Jul 12, 2018
* The current pattern in Kubeflow is to put the complete prototype in the jsonnet file. This way the result of ks generate is a .jsonnet file containing a full spec. This makes it easy for users to do complex modifications starting with the prototype as an example. * Configure the prototype to do mnist by default. Fix #1114
saffaalvi
pushed a commit
to StatCan/kubeflow
that referenced
this pull request
Feb 11, 2021
* The current pattern in Kubeflow is to put the complete prototype in the jsonnet file. This way the result of ks generate is a .jsonnet file containing a full spec. This makes it easy for users to do complex modifications starting with the prototype as an example. * Configure the prototype to do mnist by default. Fix kubeflow#1114
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current pattern in Kubeflow is to put the complete prototype in
the jsonnet file. This way the result of ks generate is a .jsonnet
file containing a full spec. This makes it easy for users to do
complex modifications starting with the prototype as an example.
Configure the prototype to do mnist by default.
Fix #1114
This change is