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
The input_data.npy was neverthelss downloaded but the filename was then y. Initially I thought SageMaker had renamed the file, until I figured out that the filename was caused by the typo. When indicating for instance input_data. then the name of the downloaded file would be npy. Is this intended?
If I understand this correctly, when calling fit(), the name of the dataset doesn't stay as originally attended and instead for the following examples, this happened:
If you go to the corresponding training job you ran in the sagemaker console what URI do you have specified in Input data configuration section?
Also it would be really useful to know what values do you have for Channel name, S3 data type, S3 data distribution type in the same exact section?
When calling mxnet_estimator.fit({'train': 's3://sagemaker-rauscn/data/input_data.np'})
URI : s3://sagemaker-rauscn/data/input_data.np
Channel name: train
S3 data type: S3Prefix
S3 data distirbution type: FullyReplicated
Exactly. In my training script the following crashes: train = np.load("/opt/ml/input/data/train/input_data.npy")
However this works: train = np.load("/opt/ml/input/data/train/y")
From a user perspective, it is probably best to just get an error message if there is such a typo in the filename.
Activity
ChoiByungWook commentedon Dec 15, 2018
Hello @NRauschmayr,
Thank you for bringing this to our attention.
If I understand this correctly, when calling fit(), the name of the dataset doesn't stay as originally attended and instead for the following examples, this happened:
mxnet_estimator.fit({'train': 's3://rauscn-data/data/input_data.np') = /opt/ml/input/data/train/y
mxnet_estimator.fit({'train': 's3://rauscn-data/data/input_data.npy') = /opt/ml/input/data/train/npy
The dataset that was used to train was renamed to y and npy when referenced respectively for input_data.np and input_data.npy.
Did this happen when training on SageMaker or through local mode?
I was looking through our Python SDK and I don't think we modify the URI provided by the user.
Would you be able to provide more information on how you are instantiating your estimator?
Please let me know if there is anything I can clarify.
Thanks!
NRauschmayr commentedon Jan 3, 2019
Hello @ChoiByungWook,
yes exactly that is what happened
mxnet_estimator.fit({'train': 's3://rauscn-data/data/input_data.np')lead to/opt/ml/input/data/train/yI am creating the Estimator, like this:
nadiaya commentedon Jan 4, 2019
If you go to the corresponding training job you ran in the sagemaker console what
URIdo you have specified inInput data configurationsection?Also it would be really useful to know what values do you have for
Channel name,S3 data type,S3 data distribution typein the same exact section?Thanks!
NRauschmayr commentedon Jan 4, 2019
Hello @nadiaya,
When calling
mxnet_estimator.fit({'train': 's3://sagemaker-rauscn/data/input_data.np'})URI :
s3://sagemaker-rauscn/data/input_data.npChannel name:
trainS3 data type:
S3PrefixS3 data distirbution type:
FullyReplicatednadiaya commentedon Jan 4, 2019
But inside of the container for this training job you got:
/opt/ml/input/data/train/yinstead of the expected file?Let me escalate this issue to the appropriate service team.
NRauschmayr commentedon Jan 5, 2019
Exactly. In my training script the following crashes:
train = np.load("/opt/ml/input/data/train/input_data.npy")However this works:
train = np.load("/opt/ml/input/data/train/y")From a user perspective, it is probably best to just get an error message if there is such a typo in the filename.
fix: run UpdateTrainingJob tests only during allowed secondary status (…