You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to save and load an LSTM-network. I have 2 notebooks, in the first I instantiate the estimator and use Estimator.fit() to train and save it. Then in the second notebook, I try to load it again with Estimator.attach(). However when I try this I'm getting the following keyError:
When initializing the estimator, I don't specify any hyperparameters:
When taking a look in the _init from the Estimator-class we can see that it defaults to None when no hyperparameters are specified:
But when taking a look in the response I get from .describe_training_job(), no key 'HyperParameters' is included. It seems that hyperparameters with an empty value don't get passed, resulting in this keyError I'm getting.
Is there a way when instantiating an estimator to give it 'fake' hyperparameters so that at least something gets passed along, skipping the keyError.
The text was updated successfully, but these errors were encountered:
System Information
Describe the problem
I'm trying to save and load an LSTM-network. I have 2 notebooks, in the first I instantiate the estimator and use

Estimator.fit()
to train and save it. Then in the second notebook, I try to load it again withEstimator.attach()
. However when I try this I'm getting the following keyError:When initializing the estimator, I don't specify any hyperparameters:


When taking a look in the _init from the Estimator-class we can see that it defaults to None when no hyperparameters are specified:
But when taking a look in the response I get from .describe_training_job(), no key 'HyperParameters' is included. It seems that hyperparameters with an empty value don't get passed, resulting in this keyError I'm getting.

Is there a way when instantiating an estimator to give it 'fake' hyperparameters so that at least something gets passed along, skipping the keyError.
The text was updated successfully, but these errors were encountered: