Can someone who has completed Fast.ai courses comment on the experience and then how you used the newly gained knowledge?
Fast.ai Part 2: Deep Learning from the Foundations
11–20 of 33 posts
Re: Fast.ai Part 2: Deep Learning from the Foundations
#12Happy to answer any questions you all might have.
Re: Fast.ai Part 2: Deep Learning from the Foundations
#13Great, thank you so much, Jeremy. One question, will a new version of the Machine learning course be made?
Re: Fast.ai Part 2: Deep Learning from the Foundations
#14My problem is that I can't think of any use cases for it, either in my personal life or work life.
I understand that the technologies have a lot of potential, and are currently used in many major projects and endeavors. I just keep drawing a blank when trying to answer the question, "what would I do with this?"
If I am someone who is goal-driven (rather than, say, learning something for the sake of learning), how can I motivate myself to pick this up?
Re: Fast.ai Part 2: Deep Learning from the Foundations
#15Can someone who has completed Fast.ai courses comment on the experience and then how you used the newly gained knowledge?
That being said, this course is completely different than anything done before. This course takes a look at the very most basic functionality of neural network libraries and proceeds to implement the fastai library totally from scratch. So it's really a great deep learning + tooling + api design + programming language + research implementation course all in one.
The last two lectures on Swift were especially fun. Python isn't great for deep learning because you always have to live at arms length from the implementation through a c++ wrapper. Swift can compile straight to the low level system commands. LLVM, MLIR. Still learning this so I'm not the best person to answer questions about this specifically. :)
So Swift has this awesome feature set of being well designed, pretty similar to Python, statically typed, and low level. These lectures are hosted by Jeremy Howard and Chris Lattner. Sometimes the most valuable learning I can do is to just listen to the banter between two exceptionally experienced experts, so this make the course that much more enjoyable.
Five starts would recommend. Get the t-shirt.
Re: Fast.ai Part 2: Deep Learning from the Foundations
#16I'm excited to see a couple lectures with Swift. All the work to add interoperability with Python and make swift-jupyter is very appreciated and feels like it's Xmas in June.
Why would you need Swift in Jupyter? Just implement your model's architecture in Python. Export it. Invoke it at runtime via Swift and TF.
This question is addressed extensively in the course. Check out the last two lectures, they do a great job of going over lots of different reasons.
Re: Fast.ai Part 2: Deep Learning from the Foundations
#17I've been meaning to learn ML/DL. My problem is that I can't think of any use cases for it, either in my personal life or work life. I understand that the technologies have a lot of potential, and are currently used in many major projects and endeavors. I just keep drawing a blank when trying to answer the question, "what would I do with this?" If I am someone who is goal-driven (rather than, say, learning something…
Re: Fast.ai Part 2: Deep Learning from the Foundations
#18I've been meaning to learn ML/DL. My problem is that I can't think of any use cases for it, either in my personal life or work life. I understand that the technologies have a lot of potential, and are currently used in many major projects and endeavors. I just keep drawing a blank when trying to answer the question, "what would I do with this?" If I am someone who is goal-driven (rather than, say, learning something…
1. Take webcam at desk. 2. Build model that detects whether he himself is sitting at his desk. 3. If it is not him, you've detected an intruder, so spray the intruder with a squirt gun or something.
We only got as far as a model that distinguished between him and other people, even deploying it according to this guide. https://course.fast.ai/deployment_render.html
Also the material is just really interesting. If you want to know how a lot of products work, this is one of the most fun ways to learn.
Re: Fast.ai Part 2: Deep Learning from the Foundations
#19Earlier quoted context omitted.
Why would you need Swift in Jupyter? Just implement your model's architecture in Python. Export it. Invoke it at runtime via Swift and TF.
You can but it's not ideal. What if you want to write your own cuda kernel for your experiment? Python isn't really setup for this easily unless you want to throw odd c++ integrations into your code. Swift is designed to be a direct match to the underlying instructions. This would make deep learning much more expressive and flexible in Swift, with less errors. This question is addressed extensively in the course. Che…
For custom kernel code, what you really want to use is a custom TF op. But I doubt that's what you're getting at anyway, because that's for more advanced use cases.
Re: Fast.ai Part 2: Deep Learning from the Foundations
#20Earlier quoted context omitted.
You can but it's not ideal. What if you want to write your own cuda kernel for your experiment? Python isn't really setup for this easily unless you want to throw odd c++ integrations into your code. Swift is designed to be a direct match to the underlying instructions. This would make deep learning much more expressive and flexible in Swift, with less errors. This question is addressed extensively in the course. Che…
That doesn't really make sense. The code you implement in Swift when in Jupyter needs to also be available at runtime to execute. Meaning you can do the exact same thing in Python, because your model architecture is going to be embedded in the exported model. For custom kernel code, what you really want to use is a custom TF op. But I doubt that's what you're getting at anyway, because that's for more advanced use ca…
Edit: HN isn't letting me reply deeper, so I'll reply to "what are the benefits over C++?" here. The first is that MLIR has dialects that support stuff like polyhedral compilation, which result in much more concise and understandable code, which is often faster too. The second is that using the same language from top to bottom means you can profile/debug/etc your code in one place, which is much more efficient. And you don't have to learn two languages. And you don't have to use C++, which (for me at least) is a big win! ;)