-
Notifications
You must be signed in to change notification settings - Fork 159
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
How to get evaluation metrics in output logs #392
Comments
@MelissaKR thanks for filing the issue. I noticed that your metric definition regex seeks to match On a side note, you mentioned that you "don't see any of these metrics in the logs". Could you clarify? |
@metrizable Thank you for your input. I will correct the difference in the accuracy metric. I was generally wondering where I can track model outputs for these metrics. I thought they'll be written out to the logs, or they'll show up in the "Metrics" section for the training job. |
sorry for the delayed response here. The metrics should be viewable in CloudWatch - scroll down to the "Monitor" section in the AWS console when looking at a training job. docs: https://docs.aws.amazon.com/sagemaker/latest/dg/training-metrics.html |
Hi @MelissaKR did you manage to resolve this? I am having the same issue |
I had a similar situation, but the cause was IAM Policy permissions; checking CloudWatch/Logs permissions may help. |
Hi,
This is my first time working with Sagemaker. I successfully trained a model, however, I'm having difficulty getting it to output evaluation metrics to the log files.
Here is a snippet of my model:
And this is how the model is fit:
When the training finishes, I don't see any of these metrics in the logs, nor in the 'training jobs' section. This is how the Metrics section looks:
Metrics
Name Regex
eval-accuracy eval-accuracy=(\d.\d+)
precision precision=(\d.\d+)
recall recall=(\d.\d+)
I don't know why it should be so obscure. I've run the script multiple times with sagemaker, and no luck so far! I'd appreciate any help!
The text was updated successfully, but these errors were encountered: