On 2010-03-01 12:20-0800 David MacMahon wrote: > > This fixes a parameter ordering problem in plfimage's call to the minmax > operator function. > --- > src/plimage.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-)
To Hazen and David: David, I have some questions for you below. Hazen, I think it is time to test David's work concerning arbitrary 2D data. There has already been lots of time for comment on his implementation. I was glad to see there were no concerns expressed about the API additions. In fact, the only concerns expressed were about efficiency (from both David and Andrew) which I believe were answered sufficiently by David and Maurice so that it is time to at least test his new approach. Here is how I plan to do that on Linux (Debian Lenny). For source trees with and without the patch time make -j4 -k test_noninteractive >& make_testnoninteractive.out time make -j4 -k test_interactive >& make_testinteractive.out There is a lot of screen output for the second command, but the standand C examples now exit automatically for the interactive results using the -np option so that all you have to do to make the time results relevant is to stay on top of just a few special GUI's that have to be exited by hand. Would you be willing to do a similar series of tests on Mac OS X? If the time results and the *.out results show no serious regressions for me (or both of us if you are willing to do the Mac OS X tests as well), then I think it would be time to commit "the" patch (see question for David below) and start propagating the API changes to all our languages. David, I think the current patch is the third correction to your 2D work (if you count the patch that changes example 8 to use the new API). To make Hazen's and my job easier, would you be willing to now send one comprehensive corrected patch concerning your arbitrary 2D data work to this list? Would you be also willing to do the above tests on Mac OS X with and without your corrected patch? If so, and assuming there are no regressions please send me a column following the format in README.release describing the test. My agenda here is to get all developers routinely using the above tests both on a routine basis and whenever there is a major change like your 2D work. It is safe to say there are large variations in what constitutes a Mac OS X platform depending on the source/version of 3rd party libraries so the more testing each variation of that platform that is accessible to our developers the better. And similarly for Linux and Windows for exactly the same reasons. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); PLplot scientific plotting software package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel