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
Describe the feature you'd like
Similar to the Estimator abstraction, I would like to make use of SageMaker's CloudWatch metrics, based on job logs.
How would this feature be used? Please describe.
Not sure. Either an explicit argument in model_trainer or allowing the user to specify a create_job_args dictionary, to work around the abstraction if some API feature is not exposed:
(we could also just get rid of Name and Regex and just have a dict[MetricName, Pattern] there)
Describe alternatives you've considered
Using the Estimator class. I recently moved away from it, as the ModelTrainer abstraction makes more sense to me and other scientists/engineers on my team.
Additional context
n/a
The text was updated successfully, but these errors were encountered:
Describe the feature you'd like
Similar to the
Estimator
abstraction, I would like to make use of SageMaker's CloudWatch metrics, based on job logs.How would this feature be used? Please describe.
Not sure. Either an explicit argument in
model_trainer
or allowing the user to specify acreate_job_args
dictionary, to work around the abstraction if some API feature is not exposed:(we could also just get rid of
Name
andRegex
and just have adict[MetricName, Pattern]
there)Describe alternatives you've considered
Using the
Estimator
class. I recently moved away from it, as theModelTrainer
abstraction makes more sense to me and other scientists/engineers on my team.Additional context
n/a
The text was updated successfully, but these errors were encountered: