Re: [matplotlib-devel] semilogx and semilogy don't reset linear scale

2009-08-30 Thread Andrew Straw
Eric Firing wrote:
>> Specifically, it looks like the farthest left xticklabel is no longer
>> getting displayed. Personally, I think it looks better this way, but now
>> that the test suite is coming online, we will finally start noticing
>> little things like this.
> 
> I agree that the newer version, without the first label, is better--but
> I can't imagine how the change to semilogx and semilogy could make a
> difference like this.  It must be something else.

Well, if you look at

http://mpl-buildbot.code.astraw.com/builders/build%20and%20test%3A%20Mac%20OS%20X%20x86%20(sage%20buildslave)/builds/34/steps/test/logs/stdio

versus

http://mpl-buildbot.code.astraw.com/builders/build%20and%20test%3A%20Mac%20OS%20X%20x86%20(sage%20buildslave)/builds/35/steps/test/logs/stdio

that's where the difference happened, thus leading to my assertion. What
changed between those two builds was r7585. Perhaps something else is
responsible, though...

>>
>> Eric, if you think the new image is OK, can you download it from
>> http://mpl.code.astraw.com/mac-osx-x86-sage/test_matplotlib.TestAxes.empty_datetime/actual.gif
>>
>> and then check it into
>> test/test_matplotlib/baseline/TestAxes/empty_datetime.png
> 
> Done (with *.png, not actual.gif).

Ahh yes, good catch. Thanks for correcting this.

> 
> Eric
> 
>>
>> In fact, I just checked in a KnownFail test decorator heavily based on
>> numpy's implementation, so once this test starts passing, the Mac OS X
>> buildslave should have all the tests returning success or knownfail.

And look -- a buildslave is not failing!
http://mpl-buildbot.code.astraw.com/waterfall

-Andrew

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] semilogx and semilogy don't reset linear scale

2009-08-30 Thread Eric Firing
Andrew Straw wrote:
> Eric Firing wrote:
>>> Specifically, it looks like the farthest left xticklabel is no longer
>>> getting displayed. Personally, I think it looks better this way, but now
>>> that the test suite is coming online, we will finally start noticing
>>> little things like this.
>> I agree that the newer version, without the first label, is better--but
>> I can't imagine how the change to semilogx and semilogy could make a
>> difference like this.  It must be something else.
> 
> Well, if you look at
> 
> http://mpl-buildbot.code.astraw.com/builders/build%20and%20test%3A%20Mac%20OS%20X%20x86%20(sage%20buildslave)/builds/34/steps/test/logs/stdio
> 
> versus
> 
> http://mpl-buildbot.code.astraw.com/builders/build%20and%20test%3A%20Mac%20OS%20X%20x86%20(sage%20buildslave)/builds/35/steps/test/logs/stdio
> 
> that's where the difference happened, thus leading to my assertion. What
> changed between those two builds was r7585. Perhaps something else is
> responsible, though...

7584 was the Tony's change on the branch; 7585 was the svnmerge to the 
trunk, which pulled in earlier changes that had not been merged yet. The 
others were just documentation, though, so I am still mystified.  Oh, well.

Eric

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


[matplotlib-devel] Can't save pdfs with MPL devel under Jaunty

2009-08-30 Thread Gael Varoquaux
It must be me being stupid build MPL under the latest Ubuntu (has it
become harder lately? I have this impression), but I can't save pdfs with
a development version of MPL:

/home/varoquau/dev/matplotlib/lib/matplotlib/backends/backend_pdf.py in
()
 42 from matplotlib.transforms import Affine2D, Bbox, BboxBase,
TransformedPath
 43 from matplotlib.path import Path
---> 44 from matplotlib import ttconv
 45 
 46 # Overview


ImportError: /home/varoquau/dev/matplotlib/lib/matplotlib/ttconv.so:
undefined symbol: _ZN14TTStreamWriter7putcharEi

Does anybody know what I am doing wrong?

Thanks,

Gaël

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] Can't save pdfs with MPL devel under Jaunty

2009-08-30 Thread Jouni K . Seppänen
Gael Varoquaux  writes:

> ImportError: /home/varoquau/dev/matplotlib/lib/matplotlib/ttconv.so:
> undefined symbol: _ZN14TTStreamWriter7putcharEi
>
> Does anybody know what I am doing wrong?

I just had a similar problem, and nuking the build directory and
rebuilding matplotlib fixed it. Have you tried "rm -rf build"?

-- 
Jouni K. Seppänen
http://www.iki.fi/jks


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] ginput default mouse configuration

2009-08-30 Thread Gael Varoquaux
On Sat, Aug 29, 2009 at 10:45:31PM -0500, John Hunter wrote:
> I've tried to apply your code properly.  Because it was not a patch,
> but a simple code file submission (and the original files have changed
> since your submission) and because I did not write the original ginput
> code, it was touch sledding to apply the patch.  I think I got it
> right, but I would like people who use ginput and blocking input to
> give it a test drive (I did what basic tests I could, not being a
> power user).

Thank John you for doing the grunt work. It pushed me enough to do the
review that you had asked for. I am attaching a patch correcting a bug,
as well as improving the docs, and fixing a few unecessary imports.

As a side note, you guys should run pyflakes on your codebase every once
in a while. You have a lot of unused imports. Also, there seems to be
bigger problems such as

finance.py:169: undefined name 'url'
font_manager.py:221: undefined name 'WindowsError'
config/checkdep.py:67: undefined name 'verbose'
cbook.py:787: undefined name '__Full'
cbook.py:1414: undefined name 'glob'
cbook.py:1577: undefined name 'x'
cbook.py:1577: undefined name 'y'
cbook.py:1577: undefined name 'xi'
cbook.py:1577: undefined name 'extrap'

And many others that I am passing.

These might be bugs, or might not. I didn't take the time to check.

Cheers,

Gaël
Index: blocking_input.py
===
--- blocking_input.py	(revision 7596)
+++ blocking_input.py	(working copy)
@@ -17,9 +17,6 @@
 Note: Subclass of BlockingMouseInput.  Used by clabel
 """
 
-import time
-import numpy as np
-
 from matplotlib import path, verbose
 from matplotlib.cbook import is_sequence_of_strings
 
@@ -151,7 +148,7 @@
 button = event.button
 
 if button == self.button_pop:
-self.mouse_event_pop(event,-1)
+self.mouse_event_pop(event)
 elif button == self.button_stop:
 self.mouse_event_stop(event)
 else:
@@ -162,7 +159,7 @@
 Process a key click event.  This maps certain keys to appropriate
 mouse click events.
 '''
-
+
 event = self.events[-1]
 key = event.key.lower()
 
Index: figure.py
===
--- figure.py	(revision 7596)
+++ figure.py	(working copy)
@@ -12,12 +12,11 @@
 
 """
 import numpy as np
-import time
 
 import artist
 from artist import Artist, allow_rasterization
 from axes import Axes, SubplotBase, subplot_class_factory
-from cbook import flatten, allequal, Stack, iterable, dedent
+from cbook import flatten, allequal, Stack, iterable
 import _image
 import colorbar as cbar
 from image import FigureImage
@@ -1114,6 +1113,12 @@
 
 Right clicking cancels last input.
 
+The buttons used for the various actions (adding points, removing
+points, terminating the inputs) can be overriden via the
+arguments *mouse_add*, *mouse_pop* and *mouse_stop*, that give
+the associated mouse button: 1 for left, 2 for middle, 3 for
+right.
+
 The keyboard can also be used to select points in case your mouse
 does not have one or more of the buttons.  The delete and backspace
 keys act like right clicking (i.e., remove last point), the enter key
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] Can't save pdfs with MPL devel under Jaunty

2009-08-30 Thread Gael Varoquaux
On Sun, Aug 30, 2009 at 01:35:47PM +0300, Jouni K. Seppänen wrote:
> Gael Varoquaux  writes:

> > ImportError: /home/varoquau/dev/matplotlib/lib/matplotlib/ttconv.so:
> > undefined symbol: _ZN14TTStreamWriter7putcharEi

> > Does anybody know what I am doing wrong?

> I just had a similar problem, and nuking the build directory and
> rebuilding matplotlib fixed it. Have you tried "rm -rf build"?

Hey Jouni,

Yes, that did fix the problem. I suspect it might be trivial :). Thanks a
lot.

Gaël

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] writing plain text to multi page pdf

2009-08-30 Thread Jouni K . Seppänen
Jouni K. Seppänen  writes:

>> The current interface looks easy enough to use -- it just needs to be
>> advertised better, eg in a FAQ ( I had to read the source to find it,
>> which works well enough for me, but not for everyone).  If you want to
>> write one up, I'll add it to the docs.
>
> I seem to recall that the ReST docstring of backend_pdf.PdfPages was
> included in the documentation at some point, but it is missing now from
> . 

I added some documentation again. Here's what I think probably happened
the previous time: I added doc/api/backend_pdf_api.rst and edited
doc/api/index_backend_api.rst, built the documentation locally to check
that it looks OK, then at some point ran "make.html clean" to debug some
doc problems... which destroyed my uncommitted doc changes by running
svn-clean.

How about changing "make.html clean" to be more careful? After building
the docs, "svn status" shows the following unversioned files:

?   build
?   examples
?   _static/matplotlibrc
?   _templates/gallery.html

"svn status --no-ignore" adds a lot of *.pyc files in various
subdirectories. Would removing all of these achieve the expected
cleaning effect?

-- 
Jouni K. Seppänen
http://www.iki.fi/jks


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] semilogx and semilogy don't reset linear scale

2009-08-30 Thread Jouni K . Seppänen
Eric Firing  writes:

> Andrew Straw wrote:
>> Eric Firing wrote:
 Specifically, it looks like the farthest left xticklabel is no longer
 getting displayed. Personally, I think it looks better this way, but now
 that the test suite is coming online, we will finally start noticing
 little things like this.
>>> I agree that the newer version, without the first label, is better--but
>>> I can't imagine how the change to semilogx and semilogy could make a
>>> difference like this.  It must be something else.
>> 
>> Well, if you look at
>> http://mpl-buildbot.code.astraw.com/builders/build%20and%20test%3A%20Mac%20OS%20X%20x86%20(sage%20buildslave)/builds/34/steps/test/logs/stdio
>> versus
>> http://mpl-buildbot.code.astraw.com/builders/build%20and%20test%3A%20Mac%20OS%20X%20x86%20(sage%20buildslave)/builds/35/steps/test/logs/stdio
>> 
>> that's where the difference happened, thus leading to my assertion. What
>> changed between those two builds was r7585. Perhaps something else is
>> responsible, though...
>
> 7584 was the Tony's change on the branch; 7585 was the svnmerge to the 
> trunk, which pulled in earlier changes that had not been merged yet. The 
> others were just documentation, though, so I am still mystified.  Oh, well.

If I'm reading the waterfall display correctly, it looks like my commit
7597 changed the result again. I only touched documentation and
docstrings... have you tried running the buildbot several times on the
same sources?

-- 
Jouni K. Seppänen
http://www.iki.fi/jks


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] Can't save pdfs with MPL devel under Jaunty

2009-08-30 Thread John Hunter
On Sun, Aug 30, 2009 at 5:41 AM, Gael
Varoquaux wrote:

> Yes, that did fix the problem. I suspect it might be trivial :). Thanks a
> lot.

This is a common problem, and the first line of defense against builds
or installs that aren't working properly.  We even have a FAQ entry:

  http://matplotlib.sourceforge.net/faq/installing_faq.html#source-install

JDH

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] semilogx and semilogy don't reset linear scale

2009-08-30 Thread Andrew Straw
Jouni K. Seppänen wrote:
> Eric Firing  writes:
>
>   
>> Andrew Straw wrote:
>> 
>>> Eric Firing wrote:
>>>   
> Specifically, it looks like the farthest left xticklabel is no longer
> getting displayed. Personally, I think it looks better this way, but now
> that the test suite is coming online, we will finally start noticing
> little things like this.
>   
 I agree that the newer version, without the first label, is better--but
 I can't imagine how the change to semilogx and semilogy could make a
 difference like this.  It must be something else.
 
>>> Well, if you look at
>>> http://mpl-buildbot.code.astraw.com/builders/build%20and%20test%3A%20Mac%20OS%20X%20x86%20(sage%20buildslave)/builds/34/steps/test/logs/stdio
>>> versus
>>> http://mpl-buildbot.code.astraw.com/builders/build%20and%20test%3A%20Mac%20OS%20X%20x86%20(sage%20buildslave)/builds/35/steps/test/logs/stdio
>>>
>>> that's where the difference happened, thus leading to my assertion. What
>>> changed between those two builds was r7585. Perhaps something else is
>>> responsible, though...
>>>   
>> 7584 was the Tony's change on the branch; 7585 was the svnmerge to the 
>> trunk, which pulled in earlier changes that had not been merged yet. The 
>> others were just documentation, though, so I am still mystified.  Oh, well.
>> 
>
> If I'm reading the waterfall display correctly, it looks like my commit
> 7597 changed the result again. I only touched documentation and
> docstrings... have you tried running the buildbot several times on the
> same sources?
>   

Curiouser and curiouser...

No, I hadn't considered that it might be non-deterministic. However,
looking at the absdiff image of test_matplotlib.TestAxes.empty_datetime,
this is a totally different failure than we were seeing with Eric's
patch. I should probably start archiving the results of the failed
images so we can go back in time looking at these things.

I'm going to ponder this for a while.

-Andrew


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] semilogx and semilogy don't reset linear scale

2009-08-30 Thread John Hunter
On Sun, Aug 30, 2009 at 10:24 AM, Andrew Straw wrote:

> No, I hadn't considered that it might be non-deterministic. However,
> looking at the absdiff image of test_matplotlib.TestAxes.empty_datetime,
> this is a totally different failure than we were seeing with Eric's
> patch. I should probably start archiving the results of the failed
> images so we can go back in time looking at these things.
>
> I'm going to ponder this for a while.

So now I am getting what looks like a font error on the sage buildbot,
even though I wasn't getting one before on this image.  Is this
because the new good was generated on linux with a different font
config, you think?  It would be really nice if we could crack this
font issue.

I tracked down and fixed the unitized tick formatter, and removed the
known failure decorator from that test, so we hopefully will see that
error drop out of the next build.

JDH

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] semilogx and semilogy don't reset linear scale

2009-08-30 Thread John Hunter
On Sun, Aug 30, 2009 at 11:42 AM, John Hunter wrote:

> So now I am getting what looks like a font error on the sage buildbot,
> even though I wasn't getting one before on this image.  Is this
> because the new good was generated on linux with a different font
> config, you think?  It would be really nice if we could crack this
> font issue.
>
> I tracked down and fixed the unitized tick formatter, and removed the
> known failure decorator from that test, so we hopefully will see that
> error drop out of the next build.


Hey this is strage now the baseline image is wrong (it has one line
and should have two).  Earlier didn't the baseline have two and the
actual have one?  Did someone upload the broken one line version as
the new baseline.  I can fix the baseline with the new actual, but I
am curious how this baseline image got in there.

JDH

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] semilogx and semilogy don't reset linear scale

2009-08-30 Thread John Hunter
On Sun, Aug 30, 2009 at 11:47 AM, John Hunter wrote:

> Hey this is strage now the baseline image is wrong (it has one line
> and should have two).  Earlier didn't the baseline have two and the
> actual have one?  Did someone upload the broken one line version as
> the new baseline.  I can fix the baseline with the new actual, but I
> am curious how this baseline image got in there.

OK, I figured this out.  The new failure was on formatter4, not
formatter5.  I didn't see that when I posted earlier.  It turns out
when we were working at scipy and I wrote that script to move new
saved-results into baseline, I inadvertently moved a bad formatter4
image into the baseline, so the baseline image was broken.  When I
fixed the bug, the unit test caught the difference.  I've updated the
baseline so now everything should be good for that particular test.

JDH

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] semilogx and semilogy don't reset linear scale

2009-08-30 Thread John Hunter
On Sun, Aug 30, 2009 at 12:57 PM, John Hunter wrote:

> OK, I figured this out.  The new failure was on formatter4, not
> formatter5.  I didn't see that when I posted earlier.  It turns out
> when we were working at scipy and I wrote that script to move new
> saved-results into baseline, I inadvertently moved a bad formatter4
> image into the baseline, so the baseline image was broken.  When I
> fixed the bug, the unit test caught the difference.  I've updated the
> baseline so now everything should be good for that particular test.

The empty_datetime continues to mystefy me.  The actual had ticks from
1..23 and the baseline had ticks from 2..00.  The current behavior on
my box is 1..23 and that seems fine to me, so I re-updated the
baseline with that file.  I'm attaching the actual and baseline from
the last buildbot before my update.  The sage box *should* pass on the
next build test because I've corrected the two known failures.  If
there is anything I am missing about this empty datetime test, let me
know
<><>--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


[matplotlib-devel] buildbot font discrepancies

2009-08-30 Thread John Hunter
Andrew, I think I may have a clue how to fix the font discrepancies.

Apple owns patents on some a byte code interpreter for hinting truetype fonts:

  http://freetype.sourceforge.net/patents.html

and freetype can be built with the patented stuff turned on but the
default is off -- freetype has non-patented auto-hinting which is what
is used by default.  However, according to a thread I found here (see
the first post by RobK) ubuntu hardy heron, which is what you are
using on the buildbot, has the patented stuff *turned on* by default:

  http://www.howtogeek.com/howto/ubuntu/enable-smooth-fonts-on-ubuntu-linux/

According to RobK, you can reconfigure your ubuntu system to turn
these off.  He suggests:

  To use autohinting, use the hint in this post, or just run the
following command:

  sudo dpkg-reconfigure fontconfig-config

  then choose “autohinter”, then choose “always”, then choose “no”

Give it a test and hopefully we will see both bots go green.

Then we can focus on more tests and nightly builds...

JDH

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] buildbot font discrepancies

2009-08-30 Thread John Hunter
On Sun, Aug 30, 2009 at 4:17 PM, John Hunter wrote:
> According to RobK, you can reconfigure your ubuntu system to turn
> these off.  He suggests:
>
>  To use autohinting, use the hint in this post, or just run the
> following command:
>
>  sudo dpkg-reconfigure fontconfig-config
>
>  then choose “autohinter”, then choose “always”, then choose “no”

If that doesn't work, this guy has more involved instructions on how
to rebuild ubuntu libfreetype and disable the bytecode patch

http://ubuntuforums.org/showthread.php?t=84359

JDH

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] semilogx and semilogy don't reset linear scale

2009-08-30 Thread Eric Firing
John Hunter wrote:
> On Sun, Aug 30, 2009 at 12:57 PM, John Hunter wrote:
> 
>> OK, I figured this out.  The new failure was on formatter4, not
>> formatter5.  I didn't see that when I posted earlier.  It turns out
>> when we were working at scipy and I wrote that script to move new
>> saved-results into baseline, I inadvertently moved a bad formatter4
>> image into the baseline, so the baseline image was broken.  When I
>> fixed the bug, the unit test caught the difference.  I've updated the
>> baseline so now everything should be good for that particular test.
> 
> The empty_datetime continues to mystefy me.  The actual had ticks from
> 1..23 and the baseline had ticks from 2..00.  The current behavior on
> my box is 1..23 and that seems fine to me, so I re-updated the
> baseline with that file.  I'm attaching the actual and baseline from
> the last buildbot before my update.  The sage box *should* pass on the
> next build test because I've corrected the two known failures.  If
> there is anything I am missing about this empty datetime test, let me
> know

So it sounds like there have been three different behaviors: 0 to 24, 1 
to 23, and 2 to 24.  I think what we are seeing here is differences in 
floating point behavior among different platforms, and/or differences in 
datetime implementation from one python version to another.  The 
standard python library datetime is being used to generate the floating 
point xlim in days.  It looks like (2009, 1, 20) and (2009, 1, 21) can 
end up as floating point numbers a hair above or a hair below the target 
integers, and that difference of a hair is enough to determine whether a 
tick is generated or not.

A side point here is that the precision of the floating point numbers is 
lousy for most applications, because of the choice of "year 1" as the 
origin.  This is a case of mpl following a bad choice by Matlab.

One way to get around the first problem--the datetime tick dependence on 
platform--would be to put fudge factors into the autoscaling so that the 
limits would be expanded some small amount.  More generally, the 
autoscaling could have margins, which might default to the tiny amount 
necessary to prevent the datetime indeterminacy, but might be put to 
other good uses by the user.  Often one really wants the  xlim and ylim 
to be a little wider than the data range, so that symbols are plotted 
entirely within the axes, for example.  This was suggested a very long 
time ago, and it has resurfaced many times in my mind, but obviously I 
never did anything about it.

Eric


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] buildbot font discrepancies

2009-08-30 Thread Andrew Straw
John Hunter wrote:
> On Sun, Aug 30, 2009 at 4:17 PM, John Hunter wrote:
>> According to RobK, you can reconfigure your ubuntu system to turn
>> these off.  He suggests:
>>
>>  To use autohinting, use the hint in this post, or just run the
>> following command:
>>
>>  sudo dpkg-reconfigure fontconfig-config
>>
>>  then choose “autohinter”, then choose “always”, then choose “no”
> 
> If that doesn't work, this guy has more involved instructions on how
> to rebuild ubuntu libfreetype and disable the bytecode patch
> 
> http://ubuntuforums.org/showthread.php?t=84359

OK, I disabled all Ubuntu patches to libfreetype and recompiled and
re-installed it. Unfortunately, I'm still getting the same failures.

Then I additionally installed fontconfig-config and did the
dpkg-reconfigure fontconfig-config step, setting everything to "Never".
Same failures.

These font errors make me unhappy. I think we should test some very
simple pure libfreetype C program outputs generated on the various
machines. I've just been playing with ftview, but that doesn't seem to
have a command-line interface to save directly to a file.

-Andrew

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] Color map gamma

2009-08-30 Thread Eric Firing
Reinier Heeres wrote:
> Eric, all,
> 
> Here's the latest version of my color map patch. I deferred your
> suggestion #4; perhaps we can fix that later.
> 
> Please let me know what you think; if everybody is ok with it I'll
> push to trunk.
> 
> Regards,
> Reinier

Looks good.  I haven't tested it--I trust you have taken care of that. I 
suggest one tiny change, then go ahead and commit:

In your change to cm.py, instead of importing and using the copy module, 
just do this:

+datad[cmapname] = list(cmapspec)
+datad[cmapname_r] = list(cmapspec)
+datad[cmapname_r].reverse()

Simpler, more readable, possibly faster (not that speed matters here).

Thanks again.

Eric

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


[matplotlib-devel] matplotlib buildbot mailing list

2009-08-30 Thread John Hunter
Andrew and I just spent a couple of hours on the phone trying to
reconcile our freetype rendering discrepancies, and after much tedious
poor-man's debugging, we finally figured out what was wrong.  We
thought we were using the same version of freetype but were not.  The
fault was mine: I configured my buildbot to recognize the right
version of freetype at buildtime but not runtime.  We've fixed this,
we now both run the same version of freetype, and we are getting
identical mpl images.  We are very excited by the sea of green at

  http://mpl-buildbot.code.astraw.com/waterfall

Now that we have two bots passing the regression tests, we have big plans:

  * enable buildbots for more platforms (solaris and win32, we already
have osx and linux)

  * enable buildbots for all supported versions of python (2.4, 2.5 and 2.6)

  * make the unit testing infrastructure in the "test" dir easier to
use and extend, so it becomes trivial to drop in a new test (and then
drop in a lot of tests)

  * enable tarballs and platform specific binary installers from the
buildbots which upload to a nightly directory that users can grab
stuff from

  * send out emails on any buildbot failures to the
matplotlib-buildbot mailing list

In preparation for the last point, I have created

  https://lists.sourceforge.net/lists/listinfo/matplotlib-buildbot

so subscribe if you are interested in getting notices of failures.
Andrew is taking a break before he configures the bot to email on
failures, but he'll probably have it activated soon.  We'll probably
force a failure by uploading a bad image as a baseline to debug the
email script, so there may be some false negatives coming out on the
list over the next day or two, but once we have everything working the
list should accurately reflect unit test failures.

Thanks to Andrew for pushing this through.  It's a big step forward to
go from the poor-man's unit testing that we have in backend_driver to
a real framework doing image diffs across platforms triggered by svn
commits.

JDH

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel