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
Since this is the recommended debugging workflow, we should also demonstrate it in the script mode walkthroughs by adding equivalent commands in the 'SageMaker' variants of these notebooks - before the Estimator gets created.
This will help these notebooks illustrate the process/workflow of translating from in-notebook to notebook+job, better than just showing the final result.
Background
Today, we use in-notebook shell commands as the recommended script debugging workflow for the migration challenge - because our options are somewhat constrained for a workshop:
SageMaker SSH Helper has a bit of a learning curve for any data scientists not already familiar with online SSH-based debugging (and some setup required - although we could probably automate that).
We talk about these other options in the post-challenge wrap-up, but don't want to confuse the issue by introducing them up-front in the code.
The text was updated successfully, but these errors were encountered:
Feature request
We already provide example shell commands to invoke and test training scripts for all variants of the migration challenge. For example from SKLearn:
Since this is the recommended debugging workflow, we should also demonstrate it in the script mode walkthroughs by adding equivalent commands in the 'SageMaker' variants of these notebooks - before the
Estimator
gets created.This will help these notebooks illustrate the process/workflow of translating from in-notebook to notebook+job, better than just showing the final result.
Background
Today, we use in-notebook shell commands as the recommended script debugging workflow for the migration challenge - because our options are somewhat constrained for a workshop:
We talk about these other options in the post-challenge wrap-up, but don't want to confuse the issue by introducing them up-front in the code.
The text was updated successfully, but these errors were encountered: