On Wed, Dec 16, 2009 at 4:45 PM, Joey Wilson <doughywil...@gmail.com> wrote: > Let me say why I think this feature is so essential. Anyone who is in > research or academia knows that figures often need to be edited when a > publication comes back from peer review. It's already happened to me many > times, and I've learned that I absolutely have to save my figures for later > editing to save myself a lot of time. Some people have argued that a script > that generates the plots/figures should be saved, and that if you need to > edit the figure, just re-run the script. The problem with this argument is > that scientific plots often take hours, days, or even weeks of computation > to generate. For example, generating a bit-error-rate curve in > communications takes days. Therefore, always re-running from a script is > just not practical.
Ignoring the issue of having saved matplotlib figures, I'd argue you should separate the parts of the code that do computation from those that do plotting into separate scripts. Is there anything keeping you from saving all of the results from the computation into (for instance) a NetCDF file? Then the plotting script can just read in the file and do the plotting. This is exactly how my workflow is set up. I'd be happy to address any concerns you see with doing things this way. Ryan -- Ryan May Graduate Research Assistant School of Meteorology University of Oklahoma ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
