Skip to content

Commit 2ab2156

Browse files
Moo Jin KimMoo Jin Kim
Moo Jin Kim
authored and
Moo Jin Kim
committed
Update setup.md: Replace old Colab workflow tutorial with Moo Jin's new one
1 parent 8dc815e commit 2ab2156

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

setup.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ like GPUs (K80, P100) and TPUs which will be particularly useful for assignments
2828

2929
**Workflow**. Every assignment provides you with a download link to a zip file containing Colab notebooks and Python starter code. You can upload the folder to Drive, open the notebooks in Colab and work on them, then save your progress back to Drive. We encourage you to watch the tutorial video below which covers the recommended workflow using assignment 1 as an example.
3030

31-
<iframe style="display: block; margin: auto;" width="560" height="315" src="https://www.youtube.com/embed/IZUz4pRYlus" frameborder="0" allowfullscreen></iframe>
31+
<iframe width="560" height="315" src="https://www.youtube.com/embed/DsGd2e9JNH4" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
3232

3333
**Best Practices**. There are a few things you should be aware of when working with Colab. The first thing to note is that resources aren't guaranteed (this is the price for being free). If you are idle for a certain amount of time or your total connection time exceeds the maximum allowed time (~12 hours), the Colab VM will disconnect. This means any unsaved progress will be lost. <font color="red"><strong>Thus, get into the habit of frequently saving your code whilst working on assignments.</strong></font> To read more about resource limitations in Colab, read their FAQ [here](https://research.google.com/colaboratory/faq.html).
3434

0 commit comments

Comments
 (0)