I think this is worth discussing. But I have only 1.3 years experience with matplotlib and python. Basically, I do the same as you. But I think there are few tips I would like to follow:
1. I would agree to make one major theme plot one script file. Avoid make very long scripts with many plots. It's much more difficult to revisit. 2. I would avoid writing too much fancy loops as it takes much more time when you want to make some change later. 3. I would like to divide complex figures into simple ones. like I would use scatter to plot only scatter, and plot for only plotting lines. but not use plot to plot both. I think this allows more flexible way in the future to make necessary modifications. But I still don't manage to find a good way for efficiently modifying scripts and interactive plotting. It's very nice to have interactive plotting (with --pylab) using ipython notebook, but when you want to make some substitutions, it's much more tedious than in an editor like vim/emacs. While in emacs or vim, you cannot simple select lines and execute them, so you have to frequently copy and code and use %cpaste or %paste to paste the code. And....., a lot lot windows shifting.... Chao pybokeh wrote: > > Maybe workflow may not be the appropriate term. Essentially, when I want > to plot something using matplotlib, I find myself having to look up the > api > docs or examples online because quite frankly, matplotlib's syntax is very > hard to remember. I use ipython and use tab browsing, help(), dir(), etc, > and that seem to help to some extent. I absolutely love matplotlib, but > when I want to put a chart up quickly, matplotlib is just a "hassle" > depending on what chart you want to create. I do expect this since > plotting with matplotlib, you are essentially creating a chart > "programmatically", instead of GUI interface environment. But still, I > feel like an improvement could still be made in making charts simpler with > matplotlib. > > While surfing the web, I ran into this module called Canvas: > https://github.com/mdipierro/canvas > > Canvas appears to be what I am after or what I wish matplotlib's future > syntax should strive for. > > Currently, I store my matplotlib chart source code in folders with the > file > name describing what chart it creates (for example, "box_plot.py" or > "control_chart.py", etc.) and use them as "cheat sheets" when I need to > make a chart. I am curious what other matplotlib users do? Otherwise, I > do find myself sometimes just creating the chart in Excel as a 1st option, > and make charts in matplotlib if it is something Excel can't handle. > > Thanks in advance, > Daniel > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Matplotlib-users mailing list > Matplotlib-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > > -- View this message in context: http://old.nabble.com/What-is-your-matplotlib-workflow--tp33987463p33996351.html Sent from the matplotlib - users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
