Fix: Preserve hyperparameter order when invoking training jobs #223
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.
Fixes #221.
Removed the alphanumeric sorting of the hyperparameters in
sagemaker-training-toolkit/src/sagemaker_training/mapping.py
Lines 65 to 78 in 628166c
This makes sure that training scripts are invoked with the same order of hyperparameters as passed in the
hyperparameters
argument to the SageMakerEstimator
class. This sorting was undocumented and as argued in issue #221 can cause issues for scripts where order of the arguments matters.I have updated the unit tests in
test_mapping.py
to verify that the order of the arguments is preserved.I ran the unit tests with
tox -e py310 -- -s -vv test/unit
and they passed. Let's see if the CI tests find anything...Merge Checklist
General
Tests
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.