5 ms·
Technical Book on Deep Learning
- Cacti 9y agoMight help if you made the actual PDF more prominent. It took me a few minutes just to figure out where, you know, the book actually was. Change the README.md or move the child tex/pdf/etc. into into sub-dirs or something.
- randcraw 9y agoI still can't find the actual book. Too bad.
- colmvp 9y agoThe name of the file is White_book.pdf. I found it by downloading the repo, and sorting by file size.
- melling 9y agoHere's a post from yesterday with a link to the PDF: https://news.ycombinator.com/item?id=15186249 https://news.ycombinator.com/item?id=15186249 Points to this: https://arxiv.org/abs/1709.01412 https://arxiv.org/abs/1709.01412
- jlgosse 9y agoI just created a PR to include a link to the raw download link.
- Cozumel 9y agoLink to actual book: https://github.com/tomepel/Technical_Book_DL/raw/master/White_book.pdf https://github.com/tomepel/Technical_Book_DL/raw/master/Whit...
- tw1010 9y agoI love living in 2017 when stuff like this is just created out of the blue making my life just a little bit easier, and at almost no cost.
- corporateslave2 9y agoThe cost is the impermanence of knowledge capital
- tw1010 9y agoWhat do you mean by that?
- rlanday 9y agoYeah, everyone's machine learning Ph.D.s are useless now because you spent an afternoon reading a 100 page PDF.
- corporateslave3 9y agoYou would be surprised. Deep learning usurped a ton of knowledge about SVMs and such, and then TensorFlow/Keras made it easy to write and deploy good models with little knowledge. Clearly its more complex than that, but this is true for a good number of use cases.
- vladf 9y agoWarning: font is Palatino
- laichzeit0 9y agoOk I know about Comic Sans and Papyrus but what's the deal with Palatino?
- vladf 9y agoIt's math characters are nearly illegible. The font itself is OK, but the math it causes is rarely used for a reason.
- tomepel 9y agoI am the author of the document. My aesthetics sense is pretty limited as you have observed. I like the mathpazo font, but if you don't share my weird tastes, you can just download the repo, comment the \usepackage[sc]{mathpazo} line in formatAndDefs.tex and you're good to go.
- md8 9y agoarxiv link https://arxiv.org/abs/1709.01412 https://arxiv.org/abs/1709.01412
- mendeza 9y agoHow should one utilize the knowledge in the book? When do derivations play a role in deep learning? I am thinking it helps make decisions on what layers will help or not, or explain why this architecture improves some baseline. I would love to hear anyone's thought on the matter!
- gyom 9y agoIt's cool to see that much dedication. It's useful when people take the time to summarize knowledge in a book to serve as reference. But ... I have the feeling that the author, who is relatively new to the field (by his own admission), expanded a lot of formulas and made certain parts of the theory more complicated than it should be. Look around page 60. There are formulas with 6 summation signs in front of them, with all kinds of little indices floating around. How about page 37 ? In a way, the whole point about the chain rule (and software libraries that implement it) is that you can stay in "math world" to do the reasoning, and not think about the job of managing the computation. Same idea with expression as much as possible in terms linear algebra primitives. Matrix multiplication is easier to understand when it's not broken apart into sums whose indices you have to track.
- ssivark 9y agoSee author's note excerpted below; that was an explicit goal of the project. > This work has no benefit nor added value to the deep learning topic on its own. It is just the reformulation of ideas of brighter researchers to fit a peculiar mindset: the one of preferring formulas with ten indices but where one knows precisely what one is manipulating rather than (in my opinion sometimes opaque) matrix formulations where the dimension of the objects are rarely if ever specified. -- I think that having those things written out explicitly is of great help to those not fully comfortable with formal manipulations. It is particularly useful when implementing those operations in low-level code. I say this even though I personally find the Einstein notation [1] most convenient. [1]: https://en.wikipedia.org/wiki/Einstein_notation https://en.wikipedia.org/wiki/Einstein_notation
- gyom 9y agoI had not caught that note from the author. Thanks for pointing it out.