Skip to content
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

Why is sagemaker-experiments not included in all SageMaker Studio images? #150

Open
peter-wimsey opened this issue Jan 14, 2022 · 1 comment
Assignees

Comments

@peter-wimsey
Copy link

Hi there,

Apologies if this is not the right place to ask.

I am reading up on experiments in SageMaker and am a bit confused about the role of this library. Will it be merged into the generic sagemaker library as mentioned elsewhere? Am I supposed to use the UI-based tools in SageMaker Studio instead?

The library is not included in the "Data Science" image but is included in the "Pytorch 1.8 CPU" image. Have not tried the others.

Thanks

@danabens danabens self-assigned this Jun 27, 2022
@danabens
Copy link
Member

the role of this library

At a high level this library provides abstractions around SageMaker's experiment management APIs to create, read, update, list, delete Experiments, Trials, and Trial Components. Another major component of this library is the Tracker class which has methods for logging artifacts and metrics from your training scripts.

Will it be merged into the generic sagemaker library

That is the direction we are headed. Fewer packages/dependencies to manage for SageMaker functionality.

Am I supposed to use the UI-based tools in SageMaker Studio

The SageMaker Studio UI is intended to be used for training analysis and experiment tracking. i.e. you can compare multiple training runs visually with charts, graphs, and artifacts.

The library is not included in the "Data Science" image

Will investigate, thanks for pointing this out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants