-
Notifications
You must be signed in to change notification settings - Fork 0
feat: jumpstart hyperparameters and env variables #1
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
base: feat/jumpstart-retrieve-functions
Are you sure you want to change the base?
feat: jumpstart hyperparameters and env variables #1
Conversation
if region is None: | ||
region = JUMPSTART_DEFAULT_REGION_NAME | ||
|
||
assert region is not None |
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.
optional: to avoid assert, you can do:
_region = region if region is not None else JUMPSTART_DEFAULT_REGION_NAME
"py_version": "py3", | ||
} | ||
) | ||
assert specs1.training_ecr_specs == JumpStartECRSpecs( | ||
{ | ||
"framework": "pytorch", | ||
"framework_version": "1.9.0", | ||
"framework_version": "1.5.0", |
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.
just curious: why these changes? Are you weakening the test here?
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 changed the base model spec
5eea777
to
86d97ef
Compare
86d97ef
to
9c643e3
Compare
Issue #, if available:
Description of changes:
This PR adds utilities for accessing hyperparameters and environment variables associated with JumpStart models. The functions
hyperparameters.retrieve_default
andenvironment_variables.retrieve_default
have been added, which retrieve default hyperparameters (for training) and environment variables (for inference), respectively.Testing done:
The new utilities have undergone unit testing, and the values returned from the utilities are used in integration tests.
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.General
Tests
unique_name_from_base
to create resource names in integ tests (if appropriate)By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.