PlotNeuralNet: Latex Code for Drawing Neural Networks(github.com)
github.com
PlotNeuralNet: Latex Code for Drawing Neural Networks
https://github.com/HarisIqbal88/PlotNeuralNet
17 comments
I wonder if tikz/LaTeX is the best output format for this. When I'm making figures it has been fastest for me to have code that generates 90% the right thing, then tweak as necessary in Illustrator/Inkscape to get different parts to line up, combine subfigures, etc.
If I did anything with neural nets, I might take the time to bolt on an option for output to SVG. EPS or some other vector format would be great as well, but I am not that much of a wizard.
For more discussion on reproducibility and hardcoding figures, see for example: http://rajlaboratory.blogspot.com/2016/02/from-reproducibili...
If I did anything with neural nets, I might take the time to bolt on an option for output to SVG. EPS or some other vector format would be great as well, but I am not that much of a wizard.
For more discussion on reproducibility and hardcoding figures, see for example: http://rajlaboratory.blogspot.com/2016/02/from-reproducibili...
It would be really awesome if someone could package this into a Latex package. Then you could directly define your neural net inside of Latex instead of having to generate the Tex from python.
Otherwise, these graphics are wonderful to look at.
Otherwise, these graphics are wonderful to look at.
WOW! That's the kind of tool I needed. Working on simple NN now and then is hard to show to decision makers what processes were applied. Having a visual latex like that, makes life easier.
It's nice that they have a python interface. I know everyone has a fetish for TeX/LaTeX, but isn't it time for something better? Don't get me wrong, TeX has probably the best document rendering of anything I've ever come across, but the language itself is quite terrible. I get the impression that no one even knows how to use it anymore, and everyone is just copying and pasting code handed down from generations of professors and students.
I understand the limitations and design decisions made at the time, but I think it's time for something new. Maybe just using TeX as a backend language would be acceptable, though I think it would just be preferable to start anew. I know there's Scribble but I don't think it handles equations.
I understand the limitations and design decisions made at the time, but I think it's time for something new. Maybe just using TeX as a backend language would be acceptable, though I think it would just be preferable to start anew. I know there's Scribble but I don't think it handles equations.
A problem with trying to replace TeX is that the only real problem with it is aesthetic of implementation language. And its main strength is its stability.
Note, it is not that it renders documents well. While, I do appreciate that fact, the real strength is I am not constantly having to play gardener with all of the documents I've written. Any bitrot in my document will come from facts in it, not because this year's version decided that promises were better than callbacks. Or that "box-sizing: border-box" is the more natural way to do things. (Or yet another brand new construct to lay things out.)
I think a lot of this stability can be traced directly to Knuth. He has a discipline that is basically unmatched.
And it isn't like he hasn't had some misgivings about choices he has made. However, his main choice that he is willing to stick with is stability. And that is huge for long term use.
Note, it is not that it renders documents well. While, I do appreciate that fact, the real strength is I am not constantly having to play gardener with all of the documents I've written. Any bitrot in my document will come from facts in it, not because this year's version decided that promises were better than callbacks. Or that "box-sizing: border-box" is the more natural way to do things. (Or yet another brand new construct to lay things out.)
I think a lot of this stability can be traced directly to Knuth. He has a discipline that is basically unmatched.
And it isn't like he hasn't had some misgivings about choices he has made. However, his main choice that he is willing to stick with is stability. And that is huge for long term use.
LaTeX3[1][2] improves matters and LuaTeX[3] is getting more traction, so more and more parts get written in Lua and more stuff gets deprecated. What I don't really get why LuaTeX project is not very open and their source repository is not anonymously accessible. Would be so much better if they migrate ot GitHub or GitLab.
[1] https://github.com/latex3/latex3
[2] https://www.latex-project.org/help/documentation/ltx3info.pd...
[3] http://www.luatex.org/
[1] https://github.com/latex3/latex3
[2] https://www.latex-project.org/help/documentation/ltx3info.pd...
[3] http://www.luatex.org/
BTW the LuaTeX source isn't really hidden; there's an unofficial GitHub mirror at https://github.com/TeX-Live/luatex (or look at https://github.com/TeX-Live/texlive-source/tree/trunk/texk/w... specifically) and for their official SVN repository at https://serveur-svn.lri.fr/svn/modhel/luatex the username/password (anonsvn/anonsvn) are listed in a few places (e.g. here: http://www.luatex.org/development.html and in their mailing list announcements).
There are recent alternatives that seem pretty ambitious (I'll just mention https://www.tug.org/TUGboat/tb38-1/tb118cozens.pdf as a proof of existence). That I can see, though, any system capable enough to do as much is just as complex. Would be interested in being proved wrong, though.
As other people have mentioned, the LuaTeX folks have got a real good thing going. It is climbing the adoption curve but it makes reasonable some things that in the past have not really been reasonable to program (at least for me).
As other people have mentioned, the LuaTeX folks have got a real good thing going. It is climbing the adoption curve but it makes reasonable some things that in the past have not really been reasonable to program (at least for me).
Sure, just port the entire tex package ecosystem first would you? Tex isn't cumbersome enough to give up for anything less than feature parity with those.
That's clearly a major impediment. But we've overcome network effects many times in the past: MySpace, the JVM, x86_64, etc etc. It's just that no one really cares, and there's probably no money to be made in the process. Using LaTeX is never more than a slight to moderate inconvenience, but it's still unpleasant.
It's open source. Nothing's stopping you from doing what you want someone else to do.
This is more of a python generator for latex code that illustrates a neural network, not an package for drawing NN's with latex.
Yes, I was slightly disappointed to discover this fact.
From the title, I thought it would be something I'd be able to run semi-automatically on a neural net (presumably defined in a standard / widely-used format like a Tensorflow net) and have it spit out a nice diagram.
Don't get me wrong, this still seems super-useful. It's just not what I expected.
From the title, I thought it would be something I'd be able to run semi-automatically on a neural net (presumably defined in a standard / widely-used format like a Tensorflow net) and have it spit out a nice diagram.
Don't get me wrong, this still seems super-useful. It's just not what I expected.
I think this looks very good. More examples (with the generating python code) would be nice.
Are there good alternatives?
From what I know tikz, PowerPoint (or Keynote), or Inkscape are popular options. But they require manual work.
Are there good alternatives?
From what I know tikz, PowerPoint (or Keynote), or Inkscape are popular options. But they require manual work.
Under the hood this is generating tikz. I imagine with more TeX/LaTeX skills than I have, someone could embed much of this directly within LaTeX to hide tikz manual (and tedious) work.
I was JUST searching for something like this! This is great!
To add emphasis, anyone who ever used latex knows that it is a pain at the ass.