Spaces:
Runtime error
Runtime error
Update app.py
Browse files
app.py
CHANGED
@@ -2,6 +2,25 @@ import streamlit as st
|
|
2 |
|
3 |
st.markdown("""
|
4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
5 |
# GPU Setup Instructions for NVIDIA GPU RTX 3070+
|
6 |
|
7 |
1. Upgrade pip: ```python.exe -m pip install --upgrade pip```
|
|
|
2 |
|
3 |
st.markdown("""
|
4 |
|
5 |
+
# Imperative?
|
6 |
+
Torch is more popular since its imperative which is often easier to understand.
|
7 |
+
What does imperative mean with respect to programming?
|
8 |
+
The open source community is amazing at solving for gaps. Competition is healthy since frameworks evolve.
|
9 |
+
Theano, Keras -> TF and Keras -> Pytorch and GPU libs.
|
10 |
+
Early was great, but hard to teach since they define computational graph up front.
|
11 |
+
Hard to debug.
|
12 |
+
Pytorch was strongest to use normal python. Everything you know works on GPU when necessary which causes a huge leap in teaching.
|
13 |
+
Pytorch is not easy for newcomers or researchers. API however writes NN in three lines of code using progressive API's
|
14 |
+
Fast AI library was critical.
|
15 |
+
Are we still limited by python? Is Swift an alternative? Torch or TF? Hard to say.
|
16 |
+
- Vision for tensorflow was good.
|
17 |
+
- Pytorch features interactive computation
|
18 |
+
- TF eager is tentimes slower than pytorch - caution might be dead end.
|
19 |
+
- Look at the code, develop your own perspective.
|
20 |
+
- SWIFT could be layer above GPU and be great.
|
21 |
+
|
22 |
+
|
23 |
+
|
24 |
# GPU Setup Instructions for NVIDIA GPU RTX 3070+
|
25 |
|
26 |
1. Upgrade pip: ```python.exe -m pip install --upgrade pip```
|