Re: [matplotlib-devel] Strange moray patterns with pcolor
On Jun 25, 2008, at 8:38 PM, Michael Droettboom wrote: > Ahh -- 0.91 avoided this by using non-antialiased rendering by > default for pcolor as well as pcolormesh. That's probably what Rob > is seeing when he went from 0.91 to 0.98. Indeed. Now that I think about it in the light of the discussion here, it may be that I have seen this behavior before, but not by default. What surprised me is that I was getting this sort of result using the same function as previously. A sample showing the different behavior might be something like: x, y = meshgrid(arange(50), arange(100)) y *= 1 + sin(x/30.0) y += 10.0*sqrt(x) z = (x+y)**2 figure() pcolor(x, y, z) figure() pcolor(x, y, z, antialiased=False) # pcolormesh gives similar results to antialiased=False # further tests with missing values in y y = np.ma.masked_where(y< 100, y) pcolor(x, y, z, antialiased=False) # pcolormesh fails. -Rob Rob Hetland, Associate Professor Dept. of Oceanography, Texas A&M University http://pong.tamu.edu/~rob phone: 979-458-0096, fax: 979-845-6331 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] examples in the axes docs
I noticed Michael just made a commit adding plot directive examples in the doc strings. I think this is a great idea, and very cool, since the html docs for a given function will not only link to a complete code example, but also have inline figures and links to various output high res or vector formats. See for example, at the bottom of the help for the hexbin function http://matplotlib.sourceforge.net/doc/html/api/axes_api.html#matplotlib.axes.Axes.hexbin or http://matplotlib.sourceforge.net/doc/html/api/pyplot_api.html#matplotlib.pyplot.hexbin but I'd like to encourage everyone to clean up the examples they link to, preferably so that they use the recommended idioms import numpy as np import matplotlib.pyplot as plt Having a bunch of 'from pylab import *' code in our examples is probably not a good idea as we are trying to encourage new users to be more explicit about namespaces. We may also want to consider explicitly putting examples we literal include into pyplots rather than linking to them through the mpl_examples dir so we have more control over them vis-a-vis making sure they look good at the rendered sizes and helping prevent developers not working on the docs from inadvertently making changes to the example that foul up the docs. I have mixed feelings about this last point because of the redundancy -- the alternative is just to clean them in place and makes sure developers know not to much with them w/o checking the effect on the docs. But these minor nits aside, a very good idea Michael. JDH - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] examples in the axes docs
I was just about to write an e-mail about this. I just put a few in to see what would blow up on other people's machines... ;) Like John, I also have mixed feelings about moving the examples to pyplots. Maybe we need a new subdirectory under examples called "doc_examples" or something, and examples that are part of the docs get *moved*, not copied, into there. Not a great solution either, but I'd hate for either the doc examples or regular examples to get neglected or out-of-sync just because there's now two very similar things to update. A related issue with using some of the existing examples directly is that they are multi-figure, which the documentation infrastructure doesn't easily support -- plus, I don't think we want 7 examples for a single function inline in the docs anyway. But it might be nice, for example, to include an example of common usage, and then a link to more advanced features. Cheers, Mike John Hunter wrote: > I noticed Michael just made a commit adding plot directive examples in > the doc strings. I think this is a great idea, and very cool, since > the html docs for a given function will not only link to a complete > code example, but also have inline figures and links to various output > high res or vector formats. See for example, at the bottom of the > help for the hexbin function > > > http://matplotlib.sourceforge.net/doc/html/api/axes_api.html#matplotlib.axes.Axes.hexbin > > or > > > http://matplotlib.sourceforge.net/doc/html/api/pyplot_api.html#matplotlib.pyplot.hexbin > > but I'd like to encourage everyone to clean up the examples they link > to, preferably so that they use the recommended idioms > > import numpy as np > import matplotlib.pyplot as plt > > Having a bunch of 'from pylab import *' code in our examples is > probably not a good idea as we are trying to encourage new users to be > more explicit about namespaces. > > We may also want to consider explicitly putting examples we literal > include into pyplots rather than linking to them through the > mpl_examples dir so we have more control over them vis-a-vis making > sure they look good at the rendered sizes and helping prevent > developers not working on the docs from inadvertently making changes > to the example that foul up the docs. I have mixed feelings about > this last point because of the redundancy -- the alternative is just > to clean them in place and makes sure developers know not to much with > them w/o checking the effect on the docs. > > But these minor nits aside, a very good idea Michael. > -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] examples in the axes docs
Michael Droettboom wrote: > I was just about to write an e-mail about this. I just put a few in to > see what would blow up on other people's machines... ;) > > Like John, I also have mixed feelings about moving the examples to > pyplots. > > Maybe we need a new subdirectory under examples called "doc_examples" or > something, and examples that are part of the docs get *moved*, not > copied, into there. Not a great solution either, but I'd hate for > either the doc examples or regular examples to get neglected or > out-of-sync just because there's now two very similar things to update. I think a special place for doc examples is a very good idea; I don't see any real disadvantage. Eric > > A related issue with using some of the existing examples directly is > that they are multi-figure, which the documentation infrastructure > doesn't easily support -- plus, I don't think we want 7 examples for a > single function inline in the docs anyway. But it might be nice, for > example, to include an example of common usage, and then a link to more > advanced features. > > Cheers, > Mike > > John Hunter wrote: >> I noticed Michael just made a commit adding plot directive examples in >> the doc strings. I think this is a great idea, and very cool, since >> the html docs for a given function will not only link to a complete >> code example, but also have inline figures and links to various output >> high res or vector formats. See for example, at the bottom of the >> help for the hexbin function >> >> >> http://matplotlib.sourceforge.net/doc/html/api/axes_api.html#matplotlib.axes.Axes.hexbin >> >> or >> >> >> http://matplotlib.sourceforge.net/doc/html/api/pyplot_api.html#matplotlib.pyplot.hexbin >> >> but I'd like to encourage everyone to clean up the examples they link >> to, preferably so that they use the recommended idioms >> >> import numpy as np >> import matplotlib.pyplot as plt >> >> Having a bunch of 'from pylab import *' code in our examples is >> probably not a good idea as we are trying to encourage new users to be >> more explicit about namespaces. >> >> We may also want to consider explicitly putting examples we literal >> include into pyplots rather than linking to them through the >> mpl_examples dir so we have more control over them vis-a-vis making >> sure they look good at the rendered sizes and helping prevent >> developers not working on the docs from inadvertently making changes >> to the example that foul up the docs. I have mixed feelings about >> this last point because of the redundancy -- the alternative is just >> to clean them in place and makes sure developers know not to much with >> them w/o checking the effect on the docs. >> >> But these minor nits aside, a very good idea Michael. >> - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] examples in the axes docs
On Thu, Jun 26, 2008 at 3:14 PM, Eric Firing <[EMAIL PROTECTED]> wrote: > I think a special place for doc examples is a very good idea; I don't see > any real disadvantage. I'm not real keen on this if it means moving the example from the existing location, since the examples directory should be organized to help the users learn rather than as a convenience to the developer. The "doc_example" is not to useful to the user, who should be thinking in terms of "pylab" or "api" or "dates" or "events" or "images". I think I prefer in-place references or copies over this. JDH - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] examples in the axes docs
On Thu, Jun 26, 2008 at 01:50:29PM -0500, John Hunter wrote: > I noticed Michael just made a commit adding plot directive examples in > the doc strings. I think this is a great idea, and very cool, since > the html docs for a given function will not only link to a complete > code example, but also have inline figures and links to various output > high res or vector formats. See for example, at the bottom of the > help for the hexbin function > > http://matplotlib.sourceforge.net/doc/html/api/axes_api.html#matplotlib.axes.Axes.hexbin Wow, guys this is really cool. I do hope that you are going to talk about this at the SciPy08 conference. This is solid gold, IMHO. Gaël - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] Student sponsorship for the SciPy08 conference
We are delighted to announce that the Python Software Foundation has answered our call and is providing sponsoring to the SciPy08 conference. We will use this money to sponsor the registration fees and travel for up to 10 college or graduate students to attend the conference. The PSF did not provide all the founds required for all 10 students and once again Enthought Inc. (http://www.enthought.com) is stepping up to fill in. To apply, please send a short description of what you are studying and why you’d like to attend to [EMAIL PROTECTED] Please include telephone contact information. Thanks a lot to Travis Vaught from Enthought for bringing this project to a success. Please don't hesitate to forward this announcement to anybody who might be interested. Gaël, on behalf of the Scipy08 organisation committee SciPy coneference site: http://conference.scipy.org - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] mathtext bug
Hi,
just want to point to a bug (2002836) reported on sourceforge.
I could track this a little bit more down and found that a subscript
like r'x_{\leftarrow}' fails, whereas r'x_\leftarrow' works (!); also
fails e.g. for r'x_{\leftrightarrow}'. Anything that starts with \right
or \Left works, too.
Seems to be related to Parser.autoDelim ?!
Manuel
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
