-
Notifications
You must be signed in to change notification settings - Fork 13
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
experiments: make notebook more like the pipeline #280
Conversation
example-get-started-experiments/code/notebooks/TrainSegModel.ipynb
Outdated
Show resolved
Hide resolved
so, what is the current behavior?
|
" with Live(\"results/evaluate\") as live:\n", | ||
" live.summary[\"dice_multi\"] = evaluate(learn)" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Experiment still gets saved here. dvc_exp_save=False
above is only needed to avoid having two experiments saved for each run since there are two different live instances for train and eval.
"from PIL import Image" | ||
"from PIL import Image\n", | ||
"\n", | ||
"os.chdir(\"..\")\n", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By changing to the root dir at the start, we end up with similar behavior to the pipeline and the notebook writes to dvc.yaml
there.
Studio project to see how it looks: https://studio.iterative.ai/user/dberenbaum/projects/exp-notebook-0nufj91gh8 |
This PR makes the notebook and pipeline code more similar by modifying the notebook code to use the same paths and otherwise reusing the code from the pipeline. The changes from the notebook to the pipeline were probably more realistic than making them both so similar, but it makes the repo harder to understand and maintain.