matplotlib-devel Mailing List for matplotlib (Page 2)

On 6/14/07, Charlie Moad <cw...@gm...> wrote:
> I'm trying to get info on masking and I have been getting the
> following error for over month now. Is there anything you can do?
Just updated the site to fix these -- thanks.
JDH

---------- Forwarded message ----------
From: Tim Cradic <tc...@fa...>
Date: Jun 14, 2007 10:41 AM
Subject: numerix.ma.html access failure
To: cm...@us...
Charles,
I'm trying to get info on masking and I have been getting the
following error for over month now. Is there anything you can do?
Thanks,
Tim Cradic
An error has been encountered in accessing this page.
1. Server: matplotlib.sourceforge.net
 2. URL path: /matplotlib.numerix.ma.html
 3. Error notes: File does not exist:
/home/groups/m/ma/matplotlib/htdocs/matplotlib.numerix.ma.html
 4. Error type: 404
 5. Request method: GET
 6. Request query string:
 7. Time: 2007年06月14日 07:34:53 PDT (1181831693)
Reporting this problem: The problem you have encountered is with a
project web site hosted by SourceForge.net. This issue should be
reported to the SourceForge.net-hosted project (not to
SourceForge.net).
If this is a severe or recurring/persistent problem, please do one of
the following, and provide the error text (numbered 1 through 7,
above):
Contact the project via their designated support resources.

I have made changes in matplotlib svn to facilitate experimentation with 
the maskedarray module; I hope this will speed up the process of testing 
it and incorporating it into numpy as a replacement for numpy.core.ma.
mpl scripts now accept the switches --maskedarray and --ma to force the 
use of the corresponding modules when loaded via matplotlib.numerix.ma 
or matplotlib.numerix.npyma. The latter is a new module intended for 
internal use in matplotlib as we switch to exclusive use of numpy. It 
is needed so that people using numerix in their own code can still get 
whatever numeric package and associated masked array package they want, 
while internally we can use numpy and either numpy.ma or maskedarray. 
There is also a new rcParams['maskedarray'] boolean entry (default is 
False) for selection of the masked array module. It is commented out of 
matplotlibrc by default, and most mpl users can ignore it.
For switching to numpy inside of mpl, the ma import statement is:
import matplotlib.numerix.npyma as ma
I have not yet actually made this change anywhere; it needs to be made 
module-by-module as part of the switch to importing numpy directly 
instead of via numerix.
The npyma module and/or the import statement will need to change as 
maskedarray is moved from being a standalone package to a part of numpy, 
but this change should be quite easy and painless.
Eric
Pierre GM wrote:
> On Tuesday 12 June 2007 12:56:39 John Hunter wrote:
>> On 6/12/07, Robert Kern <rob...@gm...> wrote:
>>> John Hunter wrote:
>>>> Do record arrays support masks?
> 
> John,
> Have you tried mrecords, in the alternative maskedarray package available on 
> the scipy SVN ? It should support masked fields (by opposition to masked 
> records in numpy.core.ma). If not, would you mind giving a test and letting 
> me know your suggestions ?
> Thanks a lot in advance for any inputs.
> P.
> _______________________________________________
> Numpy-discussion mailing list
> Num...@sc...
> http://projects.scipy.org/mailman/listinfo/numpy-discussion

There is a question that has not been addressed yet: how to handle numpy 
masked arrays. There are two modules, mostly compatible: numpy.ma and 
maskedarray. The latter will (I hope) become the standard 
implementation; until it does, we should have an easy mechanism for 
switching from one to the other so that we can test maskedarray. We 
also need to make it easy to routinely use the latter when it does 
become standard.
Maybe this needs to be added to numerix, and we need to use numerix 
internally via a single line per module:
import matplotlib.numerix.ma as ma
I haven't thought this through yet.
Ideas? Comments?
Eric

So, it looks like the present release is OK and we don't need a bugfix 
release before we proceed with numpification--correct?
This will involve quite a bit of change in each file, so we should 
probably announce beforehand when we are going to work on a given file, 
so as to avoid collisions and duplication of effort. Personally, I 
expect to start with the shorter files I have worked on the most: 
contour, quiver, colorbar, colors. I don't mind attacking something 
like axes later. I'm not sure how much time I will be able to spend on 
this--certainly less than I would like--but fortunately it can be done 
piecemeal.
I have added some relevant instructions to the coding guide, based on
http://www.mail-archive.com/mat...@li.../msg00791.html
and subsequent discussion.
I think that we ended up with:
import numpy as npy
...
a = npy.array([1,2,3])
b = npy.sin(a)
...etc.
The rationale is that this avoids confusion with existing use of nx to 
mean the numerix module, and it parallels the numpy internal use of NPY_ 
in C code.
John, you generalized this as follows:
 * when we do the cleanup, we should replace all the 'from numerix
import something' with 'import numpy as nx; nx.something' as above.
Where possible when cleaning a given module for numerix, we should
standardize the other imports. Eg, instead of 'from cbook import
iterable' we should do 'import matplotlib.cbook as cbook;
cbook.iterable' Let's use this convention where we use absolute
imports renamed to relative imports, and qualify all module functions
in the code with the module names.
The diff for the CODING_GUIDE is attached; please check to see if I got 
it right. It may go beyond, or not completely cover, previous 
discussions, and I committed it to get the review process going. Please 
discuss and/or change it as needed. It is important that we have a 
clear picture of the desired end result before we spend time making 
extensive changes in just about every module.
Question: is there a functional difference between
from matplotlib import cbook
and
import matplotlib.cbook as cbook?
Eric
Andrew Straw wrote:
> Hi,
> 
> I just turned off the building of the Numeric and numarray extensions in 
> setup.py. (As is always good practice, you may have to delete your build 
> and install directories to insure the old extensions are not kept in place.)
> 
> I didn't clean up any infrastructure at this point, but I presume we 
> want to start using numpy internally rather than the numerix layer. If 
> that's true, we're free now to make use of all that numpy offers rather 
> than the lowest-common-denominator approach we had been following! Sweet!
> 
> Andrew
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Hi,
I just turned off the building of the Numeric and numarray extensions in 
setup.py. (As is always good practice, you may have to delete your build 
and install directories to insure the old extensions are not kept in place.)
I didn't clean up any infrastructure at this point, but I presume we 
want to start using numpy internally rather than the numerix layer. If 
that's true, we're free now to make use of all that numpy offers rather 
than the lowest-common-denominator approach we had been following! Sweet!
Andrew

Hi there,
the loc="best" mode seems to work fairly well now. Even if it may leave
room for further optimization, I would assume that it is the more
reasonable default than "upper right".
I believe, however, that such simple API-changes should not happen
one-by-one but that they should be collected and then be done all at
once at some point.
Greetings,
Norbert

Before we blow away the numerix internally, let's give this release a
few days to settle and do a point bug fix release if anything serious
comes out. I plan on doing an announcement on python-list tomorrow,
which should trigger a larger than normal number of downloads, so
let's give it a couple of days to shake out before we pull numerix.
Of course we can always branch, but I'd be happy to keep it simple.
JDH

http://cheeseshop.python.org/pypi/matplotlib/
http://sourceforge.net/project/showfiles.php?group_id=80706&package_id=82474
===============================================================
2007年06月02日 Released 0.90.1 at revision 3352
2007年06月02日 Display only meaningful labels when calling legend()
 without args. - NN
2007年06月02日 Have errorbar follow the color cycle even if line is not plotted.
 Suppress plotting of errorbar caps for capsize=0. - NN
2007年06月02日 Set markers to same alpha value as line. - NN
2007年06月02日 Fix mathtext position in svg backend. - NN
2007年06月01日 Deprecate Numeric and numarray for use as numerix. Props to
 Travis -- job well done. - ADS
2007年05月18日 Added LaTeX unicode support. Enable with the
 'text.latex.unicode' rcParam. This requires the ucs and
 inputenc LaTeX packages. - ADS
2007年04月23日 Fixed some problems with polar -- added general polygon
 clipping to clip the lines a nd grids to the polar axes.
 Added support for set_rmax to easily change the maximum
 radial grid. Added support for polar legend - JDH
2007年04月16日 Added Figure.autofmt_xdate to handle adjusting the bottom
 and rotating the tick labels for date plots when the ticks
 often overlap - JDH
2007年04月09日 Beginnings of usetex support for pdf backend. -JKS
2007年04月07日 Fixed legend/LineCollection bug. Added label support
 to collections. - EF
2007年04月06日 Removed deprecated support for a float value as a gray-scale;
 now it must be a string, like '0.5'. Added alpha kwarg to
 ColorConverter.to_rgba_list. - EF
2007年04月06日 Fixed rotation of ellipses in pdf backend
 (sf bug #1690559) -JKS
2007年04月04日 More matshow tweaks; documentation updates; new method
 set_bounds() for formatters and locators. - EF
2007年04月02日 Fixed problem with imshow and matshow of integer arrays;
 fixed problems with changes to color autoscaling. - EF
2007年04月01日 Made image color autoscaling work correctly with
 a tracking colorbar; norm.autoscale now scales
 unconditionally, while norm.autoscale_None changes
 only None-valued vmin, vmax. - EF
2007年03月31日 Added a qt-based subplot-adjustment dialog - DSD
2007年03月30日 Fixed a bug in backend_qt4, reported on mpl-dev - DSD
2007年03月26日 Removed colorbar_classic from figure.py; fixed bug in
 Figure.clf() in which _axobservers was not getting
 cleared. Modernization and cleanups. - EF
2007年03月26日 Refactored some of the units support -- units now live in
 the respective x and y Axis instances. See also
 API_CHANGES for some alterations to the conversion
 interface. JDH
2007年03月25日 Fix masked array handling in quiver.py for numpy. (Numeric
 and numarray support for masked arrays is broken in other
 ways when using quiver. I didn't pursue that.) - ADS
2007年03月23日 Made font_manager.py close opened files. - JKS
2007年03月22日 Made imshow default extent match matshow - EF
2007年03月22日 Some more niceties for xcorr -- a maxlags option, normed
 now works for xcorr as well as axorr, usevlines is
 supported, and a zero correlation hline is added. See
 examples/xcorr_demo.py. Thanks Sameer for the patch. -
 JDH
2007年03月21日 Axes.vlines and Axes.hlines now create and returns a
 LineCollection, not a list of lines. This is much faster.
 The kwarg signature has changed, so consult the docs.
 Modified Axes.errorbar which uses vlines and hlines. See
 API_CHANGES; the return signature for these three functions
 is now different
2007年03月20日 Refactored units support and added new examples - JDH
2007年03月19日 Added Mike's units patch - JDH
2007年03月18日 Matshow as an Axes method; test version matshow1() in
 pylab; added 'integer' Boolean kwarg to MaxNLocator
 initializer to force ticks at integer locations. - EF
2007年03月17日 Preliminary support for clipping to paths agg - JDH
2007年03月17日 Text.set_text() accepts anything convertible with '%s' - EF
2007年03月14日 Add masked-array support to hist. - EF
2007年03月03日 Change barh to take a kwargs dict and pass it to bar.
 Fixes sf bug #1669506.
2007年03月02日 Add rc parameter pdf.inheritcolor, which disables all
 color-setting operations in the pdf backend. The idea is
 that you include the resulting file in another program and
 set the colors (both stroke and fill color) there, so you
 can use the same pdf file for e.g. a paper and a
 presentation and have them in the surrounding color. You
 will probably not want to draw figure and axis frames in
 that case, since they would be filled in the same color. - JKS
2007年02月26日 Prevent building _wxagg.so with broken Mac OS X wxPython. - ADS
2007年02月23日 Require setuptools for Python 2.3 - ADS
2007年02月22日 WXAgg accelerator updates - KM
 WXAgg's C++ accelerator has been fixed to use the correct wxBitmap
 constructor.
 The backend has been updated to use new wxPython functionality to
 provide fast blit() animation without the C++ accelerator. This
 requires wxPython 2.8 or later. Previous versions of wxPython can
 use the C++ acclerator or the old pure Python routines.
 setup.py no longer builds the C++ accelerator when wxPython >= 2.8
 is present.
 The blit() method is now faster regardless of which agg/wxPython
 conversion routines are used.
2007年02月21日 Applied the PDF backend patch by Nicolas Grilly.
 This impacts several files and directories in matplotlib:
 - Created the directory lib/matplotlib/mpl-data/fonts/pdfcorefonts,
 holding AFM files for the 14 PDF core fonts. These fonts are
 embedded in every PDF viewing application.
 - setup.py: Added the directory pdfcorefonts to package_data.
 - lib/matplotlib/__init__.py: Added the default parameter
 'pdf.use14corefonts'. When True, the PDF backend uses
 only the 14 PDF core fonts.
 - lib/matplotlib/afm.py: Added some keywords found in
 recent AFM files. Added a little workaround to handle
 Euro symbol.
 - lib/matplotlib/fontmanager.py: Added support for the 14
 PDF core fonts. These fonts have a dedicated cache (file
 pdfcorefont.cache), not the same as for other AFM files
 (file .afmfont.cache). Also cleaned comments to conform
 to CODING_GUIDE.
 - lib/matplotlib/backends/backend_pdf.py:
 Added support for 14 PDF core fonts.
 Fixed some issues with incorrect character widths and
 encodings (works only for the most common encoding,
 WinAnsiEncoding, defined by the official PDF Reference).
 Removed parameter 'dpi' because it causes alignment issues.
 -JKS (patch by Nicolas Grilly)
2007年02月17日 Changed ft2font.get_charmap, and updated all the files where
 get_charmap is mentioned - ES
2007年02月13日 Added barcode demo- JDH
2007年02月13日 Added binary colormap to cm - JDH
2007年02月13日 Added twiny to pylab - JDH
2007年02月12日 Moved data files into lib/matplotlib so that setuptools'
 develop mode works. Re-organized the mpl-data layout so
 that this source structure is maintained in the
 installation. (I.e. the 'fonts' and 'images'
 sub-directories are maintained in site-packages.) Suggest
 removing site-packages/matplotlib/mpl-data and
 ~/.matplotlib/ttffont.cache before installing - ADS
2007年02月07日 Committed Rob Hetland's patch for qt4: remove
 references to text()/latin1(), plus some improvements
 to the toolbar layout - DSD

On 6/1/07, Andrew Straw <str...@as...> wrote:
> Charlie Moad wrote:
> > I have time to cut a release tomorrow. Are there any outstanding
> > issues that I should wait on?
> >
> I just committed a change that raises a DeprecationWarning on use of
> numarray or Numeric as the numerix backend -- we agreed on this back in
> early April.
Excellent, thanks. I will update the website "news flash" saying the
same. Charlie, full speed ahead with 0.90.1 and 0.91 will be numpy
only.
Thanks!
JDH

Charlie Moad wrote:
> I have time to cut a release tomorrow. Are there any outstanding
> issues that I should wait on?
> 
I just committed a change that raises a DeprecationWarning on use of
numarray or Numeric as the numerix backend -- we agreed on this back in
early April.
-Andrew

I have time to cut a release tomorrow. Are there any outstanding
issues that I should wait on?
- Charlie
On 6/1/07, Christopher Barker <Chr...@no...> wrote:
>
>
> John Hunter wrote:
> > I am not a wx user, so I leave it to the rest of you to
> > confirm and or vet these changes.
>
> I just built and tested SVN trunk on OS-X 10.4.9 with:
>
> python 2.4 with wxPython2.6.3
>
> and
>
> python 2.5 with wxPython2.8.4
>
> Not extensive testing, but it seems to work fine. Thanks!
>
> NOTE: I first installed it over the older one in python2.4 with
> wxPython2.6, and got a garbage image. Then I deleted the old one, and
> re-installed, and it worked fine. I suspect that I had an old
> accelerator with the old one, which doesn't work right with the new one.
> It wasn't over-written, as the accelerator isn't being built by default
> anymore.
>
>
>
> --
> Christopher Barker, Ph.D.
> Oceanographer
>
> Emergency Response Division
> NOAA/NOS/OR&R (206) 526-6959 voice
> 7600 Sand Point Way NE (206) 526-6329 fax
> Seattle, WA 98115 (206) 526-6317 main reception
>
> Chr...@no...
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Hi,
Why is the code for passing plot_kw only implemented for the vertical 
errorbars?
Here is a patch to make things symmetric if this is appropriate. (It 
is what I expected...)
This would fix the old problem discussed in
http://article.gmane.org/gmane.comp.python.matplotlib.general/425
Michael.
matplotlib/lib/matplotlib/axes.py

John Hunter wrote:
> I am not a wx user, so I leave it to the rest of you to
> confirm and or vet these changes.
I just built and tested SVN trunk on OS-X 10.4.9 with:
python 2.4 with wxPython2.6.3
and
python 2.5 with wxPython2.8.4
Not extensive testing, but it seems to work fine. Thanks!
NOTE: I first installed it over the older one in python2.4 with 
wxPython2.6, and got a garbage image. Then I deleted the old one, and 
re-installed, and it worked fine. I suspect that I had an old 
accelerator with the old one, which doesn't work right with the new one. 
It wasn't over-written, as the accelerator isn't being built by default 
anymore.
-- 
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

I've been running MPL 0.90 rev3250 since April 18 on numerous computers
around here using the wxAgg backend using stock wx on both Ubuntu Edgy
and Ubuntu Feisty. A quick look into exactly what that means shows that
Edgy is using 2.6 by default and 2.8 is used by Feisty. Therefore, I
conclude that, if your changes were present in that revision, everything
seems to be working OK for both 2.6 and 2.8.
Ken McIvor wrote:
> On May 31, 2007, at 12:42 PM, Christopher Barker wrote:
> 
>> I think all the real work is done, but I"m not totally sure what's
>> checked in now. There may be some changes needed to the build 
>> scripts so
>> that it doesn't try to build the accelerator by default.
>> 
>
> I'm not sure either. My modifications of setup.py, which disable the 
> accelerator for wxPython >= 2.8, should already be in the trunk. I 
> also modified backend_wxagg.py to ignore the accelerator when running 
> with 2.8. I haven't heard any negative feedback about these changes, 
> but I'm not sure anyone has rigorously tested them.
>
> 
>> I propose that we just stop building the accelerator, and if people 
>> want
>> better performance they need to switch to 2.8 (actually, I think the
>> pre-2.8 code could be improved with pure python too, but I"m not going
>> to bother, as I use 2.8 anyway)
>> 
>
> I'm fine with that, given that the difficulties of getting the 
> accelerator built under Debian and Ubuntu make it pretty useless to 
> my current target audience. It should be as simple making 
> BUILD_WXAGG default to False.
>
> Ken
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>