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
[MNIST on TPUs](https://colab.research.google.com/drive/1-_LKx4HwAxl5M6xPJmqAAu444LTDQoa3)
112
112
113
113
## What is it?
114
114
[READ THIS QUICK START PAGE](https://pytorch-lightning.readthedocs.io/en/stable/new-project.html)
115
115
116
116
Lightning is a way to organize your PyTorch code to decouple the science code from the engineering.
117
-
It's more of a PyTorch style-guide than a framework.
117
+
It's more of a PyTorch style-guide than a framework.
118
118
119
119
In Lightning, you organize your code into 3 distinct categories:
120
120
@@ -130,16 +130,16 @@ The rest of the code is automated by the [Trainer](https://pytorch-lightning.rea
130
130

131
131
132
132
## Testing Rigour
133
-
All the automated code by the Trainer is [tested rigorously with every new PR](https://github.com/PyTorchLightning/pytorch-lightning/tree/master/tests).
133
+
All the automated code by the Trainer is [tested rigorously with every new PR](https://github.com/PyTorchLightning/pytorch-lightning/tree/master/tests).
134
134
135
-
For every PR we test all combinations of:
136
-
- PyTorch 1.3, 1.4, 1.5
137
-
- Python 3.6, 3.7, 3.8
138
-
- Linux, OSX, Windows
139
-
- Multiple GPUs
135
+
For every PR we test all combinations of:
136
+
- PyTorch 1.3, 1.4, 1.5
137
+
- Python 3.6, 3.7, 3.8
138
+
- Linux, OSX, Windows
139
+
- Multiple GPUs
140
140
141
-
**How does performance compare with vanilla PyTorch?**
142
-
We have tests to ensure we get the EXACT same results in under 600 ms difference per epoch. In reality, lightning adds about a 300 ms overhead per epoch.
141
+
**How does performance compare with vanilla PyTorch?**
142
+
We have tests to ensure we get the EXACT same results in under 600 ms difference per epoch. In reality, lightning adds about a 300 ms overhead per epoch.
143
143
[Check out the parity tests here](https://github.com/PyTorchLightning/pytorch-lightning/tree/master/benchmarks).
144
144
145
145
Overall, Lightning guarantees rigorously tested, correct, modern best practices for the automated parts.
@@ -181,7 +181,7 @@ This is how lightning separates the science (red) from engineering (blue).
181
181
If your code is not a huge mess you should be able to organize it into a LightningModule in less than 1 hour.
182
182
If your code IS a mess, then you needed to clean up anyhow ;)
183
183
184
-
[Check out this step-by-step guide](https://towardsdatascience.com/from-pytorch-to-pytorch-lightning-a-gentle-introduction-b371b7caaf09).
184
+
[Check out this step-by-step guide](https://towardsdatascience.com/from-pytorch-to-pytorch-lightning-a-gentle-introduction-b371b7caaf09).
185
185
[Or watch this video](https://www.youtube.com/watch?v=QHww1JH7IDU).
186
186
187
187
@@ -192,7 +192,7 @@ If your code IS a mess, then you needed to clean up anyhow ;)
192
192
Although your research/production project might start simple, once you add things like GPU AND TPU training, 16-bit precision, etc, you end up spending more time engineering than researching. Lightning automates AND rigorously tests those parts for you.
193
193
194
194
## Support
195
-
-[8 core contributors](https://pytorch-lightning.readthedocs.io/en/latest/governance.html) who are all a mix of professional engineers, Research Scientists, Ph.D. students from top AI labs.
195
+
-[8 core contributors](https://pytorch-lightning.readthedocs.io/en/latest/governance.html) who are all a mix of professional engineers, Research Scientists, Ph.D. students from top AI labs.
196
196
- 100+ community contributors.
197
197
198
198
Lightning is also part of the [PyTorch ecosystem](https://pytorch.org/ecosystem/) which requires projects to have solid testing, documentation and support.
@@ -335,7 +335,7 @@ Lightning has out-of-the-box integration with the popular logging/visualizing fr
@@ -393,27 +393,27 @@ If you have any questions, feel free to:
393
393
---
394
394
395
395
## FAQ
396
-
**How do I use Lightning for rapid research?**
396
+
**How do I use Lightning for rapid research?**
397
397
[Here's a walk-through](https://pytorch-lightning.readthedocs.io/en/latest/introduction_guide.html)
398
398
399
-
**Why was Lightning created?**
399
+
**Why was Lightning created?**
400
400
Lightning has 3 goals in mind:
401
401
402
402
1. Maximal flexibility while abstracting out the common boilerplate across research projects.
403
403
2. Reproducibility. If all projects use the LightningModule template, it will be much much easier to understand what's going on and where to look! It will also mean every implementation follows a standard format.
404
404
3. Democratizing PyTorch power-user features. Distributed training? 16-bit? know you need them but don't want to take the time to implement? All good... these come built into Lightning.
405
405
406
-
**How does Lightning compare with Ignite and fast.ai?**
406
+
**How does Lightning compare with Ignite and fast.ai?**
407
407
[Here's a thorough comparison](https://medium.com/@_willfalcon/pytorch-lightning-vs-pytorch-ignite-vs-fast-ai-61dc7480ad8a).
408
408
409
-
**Is this another library I have to learn?**
409
+
**Is this another library I have to learn?**
410
410
Nope! We use pure Pytorch everywhere and don't add unnecessary abstractions!
0 commit comments