-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Unify generation of model uploaded code location #228
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #228 +/- ##
==========================================
- Coverage 92.53% 91.51% -1.03%
==========================================
Files 49 45 -4
Lines 3257 3195 -62
==========================================
- Hits 3014 2924 -90
- Misses 243 271 +28
Continue to review full report at Codecov.
|
Rebased on the recently released 1.5.0 to update CHANGELOG and accommodate introduction of PyTorch |
- Extract repeated key_prefix calculation in different models (base, mxnet, tensorflow, chainer, pytorch) into a common utility method in fw_utils.py - The generated location now always respects the code_location prefix if present but it also concatenates either the model name or image-derived name to it - This is related to 2.b in #226
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.
I'm going to wait until #230 is merged before kicking off the TC tests on this one
Update eval frequency param for TensorBoard notebook for TensorFlow 1.6
Since Spark Processing jobs will not be available by GA, the relevant Spark Processor code has been removed for now.
Since Spark Processing jobs will not be available by GA, the relevant Spark Processor code has been removed for now.
Since Spark Processing jobs will not be available by GA, the relevant Spark Processor code has been removed for now.
Issue #, if available: 226 point 2.b
Description of changes:
Merge Checklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.