matplotlib-users Mailing List for matplotlib

On Wed, Mar 3, 2010 at 4:09 PM, R Fritz <rfritz@u.washington.edu> wrote:
> Thank you very much. You have just made me a much happier grad student.
>
> I hope this answer gets added to the FAQ!

Make us much happier developers :-)

http://matplotlib.sourceforge.net/faq/howto_faq.html#contribute-to-matplotlib-documentation

JDH

Thank you very much. You have just made me a much happier grad student.

I hope this answer gets added to the FAQ!
-- 
Randolph Fritz
  design machine group, architecture department, university of washington
rfritz@u.washington.edu -or- rfr...@gm...

On 2010-03-02 18:23:24 -0800, Jae-Joon Lee said:

> The current implementation of PolarAxes does not support that.
> However, you can workaround this easily using a custom axes.
> 
> In http://matplotlib.sourceforge.net/examples/pylab_examples/polar_demo.html
> 
> Instead of
> 
> ax = fig.add_axes([0.1, 0.1, 0.8, 0.8], polar=True, axisbg='#d5de9c')
> 
> use following code
> 
> from matplotlib.projections.polar import PolarAxes
> from matplotlib.transforms import Affine2D
> 
> class PolarAxes2(PolarAxes):
>     def PolarTransform(self):
>         return Affine2D().translate(-.5*np.pi,0) + PolarAxes.PolarTransform()
> 
> ax = PolarAxes2(fig, [0.1, 0.1, 0.8, 0.8], axisbg='#d5de9c')
> ax = fig.add_axes(ax)
> 
> Regards,
> 
> -JJ
> 
> 
> On Tue, Mar 2, 2010 at 8:44 PM, R Fritz <rfritz@u.washington.edu> wrote:
> > You can see an example on the second page of
> > <http://lightolier.com/MKACatpdfs/8011.PDF>.  Scroll down.  The plot is
> > next to the table titled, "candlepower summary."  It's a quadrant
> > rather than a full circle, and it's clipped to a box, but it's still a
> > polar plot.
> >
> > The only problem I have with what matplotlib does is that it seems
> > determined to put zero at the right, rather than at the bottom.  I want
> > to turn the axis 90 degrees.
> >
> > Randolph
> >
> > On 2010-03-02 14:50:51 -0800, Jae-Joon Lee said:
> >
> >> Do you have any link to an example plot?
> >> I googled it but not much luck.
> >> Is it like a polar plot without the bottom half?
> >>
> >> Regards,
> >>
> >> -JJ
> >>
> >> On Tue, Mar 2, 2010 at 1:48 AM, R Fritz <rfritz@u.washington.edu> wrote:
> >> > I'd like to be able to generate type C photometry plots with
> >> > matplotlib. The standard co-ordinate system for these has 0 degrees at
> >> > the bottom (nadir) of the plot, with values increasing
> >> > counterclockwise. Is there anyway I can transform the co-ordinates that
> >> > matplotlib uses to do this?
> >> > --
> >>> Randolph Fritz
> >>> >  design machine group, architecture department, university of washington
> >>> > rfritz@u.washington.edu -or- rfr...@gm...

On Wed, Mar 3, 2010 at 3:23 PM, John Hunter <jd...@gm...> wrote:

> OK, I just manually added this via a diff/patch.  Keep your eyes out
> for flakiness.  I did try a matplotlib.test before committing and got
> one error about the hexbin extent so there may be a little cleanup to
> do.  I ignored that because nothing in the diff I applied should
> affect that so I thought it might be pre-existing or spurious

The hexbin error was pre-existing and was introduced in a commit I
made to support LogNorm as arg to hexbin (r8149).  I just committed a
new fix for this in HEAD

Hi,

On 3 March 2010 00:18, Gökhan Sever wrote:
>
>
> On Tue, Mar 2, 2010 at 5:57 PM, Andrea Gavana <and...@gm...>
> wrote:
>>
>> Hi All,
>>
>>    I believe this question has been already asked in the past (I
>> found something at
>>
>> http://old.nabble.com/A-good,-interactive-plotting-package-td15396445.html).
>>
>> I use matplotlib extensively in our applications, and some of my users
>> repetitively asked for a way to customize *in runtime* the plots my
>> apps generate. I.e., the app brings up a figure with a bunch of lines,
>> points and texts, and they would like to change this linewidth, the
>> colour of that point, the appearance of an axis, the legend keys and
>> so on. I am currently answering "it can't be done at the moment" :-D.
>> It is obviously not true, it just require some (a lot, maybe) work.
>
> I can list three ways to interact with active plots:
>
> 1-)  Using keyboard shortcuts: Changing scaling  using "k" and "l" keys are
> my favorite. See more at
> http://matplotlib.sourceforge.net/users/navigation_toolbar.html
>
> 2-) Using the interactive navigation toolbar and with a small extension
> written by Pierre Raybaut (on Qt4Agg backend) For a screenshot see
> http://img156.imageshack.us/img156/9210/mplqtextra.png
> This is open to development. Actually many of the command line mpl interface
> could be integrated into that window.
>
> 3-) Directly from within IPython shell. That's another useful way of
> updating figure properties (e.g. adding labels, changing font) IPython and
> matplotlib are very well integrated in that manner. Similarly, Mayavi does a
> great job of integrating shell and UI.

Only the second approach slightly resembles what I have in mind.
Navigating the plot using shortcuts and the MPL toolbars is less than
1% of what you can do to customize a MPL plot. Asking a user who knows
nothing about Python (or programming in general) to use the IPython
shell to modify the plot in runtime is unrealistic at best.

The second approach looks interesting (pity it's been done using Qt,
but then, the world is not perfect either...). I could use some of
that code to build something that looks like a *beginning* of a
possible customization of plots (using THE GUI toolkit). I thought
this issue could have been important, as any other 2D/3D plotting
toolkits (commercial and not commercial) have some (or a lot) of
ability to customize their plots once they have been generated...

Andrea.

"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.alice.it/infinity77/
http://thedoomedcity.blogspot.com/

On Wed, Mar 3, 2010 at 12:21 PM, Michael Droettboom <md...@st...> wrote:
> Jae-Joon Lee wrote:
>>
>> I fixed this in the maintenance branch.
>> But I'm failing with the svnmerge.
>> I thought this issue has been fixed but I'm not sure what I'm doing
>> wrong.
>
> I thought I had fixed it, but it seems to have broken again immediately
> after.  I'm not sure how much additional time I want to spend on the problem
> given that the transition to git is imminent ;)
>
> Mike
>>
>>  I cannot spend much more time on this right now, but John, if
>> you can, please merge the change and commit them for me.

OK, I just manually added this via a diff/patch.  Keep your eyes out
for flakiness.  I did try a matplotlib.test before committing and got
one error about the hexbin extent so there may be a little cleanup to
do.  I ignored that because nothing in the diff I applied should
affect that so I thought it might be pre-existing or spurious

JDH

The patch I applied:


Index: doc/_static/favicon.ico
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream

Property changes on: doc/_static/favicon.ico
___________________________________________________________________
Added: svn:mime-type
   + application/octet-stream

Index: doc/_templates/layout.html
===================================================================
--- doc/_templates/layout.html  (revision 8160)
+++ doc/_templates/layout.html  (revision 8175)
@@ -23,8 +23,8 @@
 </script>
 <object><noscript><p><img
src="http://apps.sourceforge.net/piwik/matplotlib/piwik.php?idsite=1"
alt="piwik"/></p></noscript></object>
 <!-- End Piwik Tag -->
+<link rel="shortcut icon" href="_static/favicon.ico">

-
 <div style="background-color: white; text-align: left; padding: 10px
10px 15px 15px">
 <a href="{{ pathto('index') }}"><img src="{{
 pathto("_static/logo2.png", 1) }}" border="0" alt="matplotlib"/></a>
Index: doc/_templates/indexsidebar.html
===================================================================
--- doc/_templates/indexsidebar.html    (revision 8160)
+++ doc/_templates/indexsidebar.html    (revision 8175)
@@ -9,7 +9,7 @@
 </p>

 <p>Sandro Tosi has a new book
-<a href="http://www.packtpub.com/matplotlib-python-development/book">Matplotlib
for python
+<a href="http://www.packtpub.com/matplotlib-python-development/book?utm_source=matplotlib.sourceforge.net&utm_medium=link&utm_content=pod&utm_campaign=mdb_002124">Matplotlib
for python
 developers</a>
 also
 at <a href="http://www.amazon.com/Matplotlib-Python-Developers-Sandro-Tosi/dp/1847197906">amazon</a>.</p>
Index: doc/devel/coding_guide.rst
===================================================================
--- doc/devel/coding_guide.rst  (revision 8160)
+++ doc/devel/coding_guide.rst  (revision 8175)
@@ -75,8 +75,8 @@

 * install ``svnmerge.py`` in your PATH::

-    > wget http://svn.collab.net/repos/svn/trunk/contrib/client-side/\
-      svnmerge/svnmerge.py
+    > wget http://svn.apache.org/repos/asf/subversion/trunk/contrib/\
+      client-side/svnmerge/svnmerge.py

 * get a svn checkout of the branch you'll be making bugfixes to and
   the trunk (see above)
Index: doc/users/artists.rst
===================================================================
--- doc/users/artists.rst       (revision 8160)
+++ doc/users/artists.rst       (revision 8175)
@@ -419,7 +419,7 @@
     # and notice that the ax.add_patch method has set the axes
     # instance
     In [267]: print rect.get_axes()
-    Subplot(49,81.25)
+    Axes(0.125,0.1;0.775x0.8)

     # and the transformation has been set too
     In [268]: print rect.get_transform()
@@ -434,7 +434,7 @@
     (0.0, 1.0)

     # but the data limits have been updated to encompass the rectangle
-    In [271]: print ax.dataLim.get_bounds()
+    In [271]: print ax.dataLim.bounds
     (1.0, 1.0, 5.0, 12.0)

     # we can manually invoke the auto-scaling machinery
Index: lib/matplotlib/finance.py
===================================================================
--- lib/matplotlib/finance.py   (revision 8160)
+++ lib/matplotlib/finance.py   (revision 8175)
@@ -597,8 +597,8 @@
     maxy = max([volume for d, open, close, high, low, volume in quotes])
     corners = (minpy, miny), (maxx, maxy)
     ax.update_datalim(corners)
-    #print 'datalim', ax.dataLim.get_bounds()
-    #print 'viewlim', ax.viewLim.get_bounds()
+    #print 'datalim', ax.dataLim.bounds
+    #print 'viewlim', ax.viewLim.bounds

     ax.add_collection(barCollection)
     ax.autoscale_view()
Index: lib/matplotlib/artist.py
===================================================================
--- lib/matplotlib/artist.py    (revision 8160)
+++ lib/matplotlib/artist.py    (revision 8175)
@@ -41,9 +41,9 @@
             renderer.stop_rasterizing()

     # the axes class has a second argument inframe for its draw method.
-    def draw_wrapper(artist, renderer, *kl):
+    def draw_wrapper(artist, renderer, *args, **kwargs):
         before(artist, renderer)
-        draw(artist, renderer, *kl)
+        draw(artist, renderer, *args, **kwargs)
         after(artist, renderer)

     # "safe wrapping" to exactly replicate anything we haven't overridden above
Index: lib/matplotlib/patches.py
===================================================================
--- lib/matplotlib/patches.py   (revision 8160)
+++ lib/matplotlib/patches.py   (revision 8175)
@@ -1383,12 +1383,12 @@
     pad = props.pop('pad', 4)
     pad = renderer.points_to_pixels(pad)
     bbox = artist.get_window_extent(renderer)
-    l,b,w,h = bbox.bounds
-    l-=pad/2.
-    b-=pad/2.
-    w+=pad
-    h+=pad
-    r = Rectangle(xy=(l,b),
+    l, b, w, h = bbox.bounds
+    l -= pad/2.
+    b -= pad/2.
+    w += pad
+    h += pad
+    r = Rectangle(xy=(l, b),
                   width=w,
                   height=h,
                   fill=fill,
@@ -1407,8 +1407,8 @@
     to test whether the artist is returning the correct bbox.
     """

-    l,b,w,h = bbox.get_bounds()
-    r = Rectangle(xy=(l,b),
+    l, b, w, h = bbox.bounds
+    r = Rectangle(xy=(l, b),
                   width=w,
                   height=h,
                   edgecolor=color,
@@ -3174,7 +3174,7 @@
                 cos_t, sin_t = get_cos_sin(x1, y1, x0, y0)
                 verticesA, codesA = self._get_bracket(x0, y0, cos_t, sin_t,
                                                       self.widthA*scaleA,
-                                                      self.legnthA*scaleA)
+                                                      self.lengthA*scaleA)
                 vertices_list.append(verticesA)
                 codes_list.append(codesA)

Index: lib/matplotlib/backends/backend_wxagg.py
===================================================================
--- lib/matplotlib/backends/backend_wxagg.py    (revision 8160)
+++ lib/matplotlib/backends/backend_wxagg.py    (revision 8175)
@@ -171,7 +171,7 @@
     """
     Convert the region of a wx.Image bounded by bbox to a wx.Bitmap.
     """
-    l, b, width, height = bbox.get_bounds()
+    l, b, width, height = bbox.bounds
     r = l + width
     t = b + height

@@ -238,7 +238,7 @@

     Note: agg must be a backend_agg.RendererAgg instance.
     """
-    l, b, width, height = bbox.get_bounds()
+    l, b, width, height = bbox.bounds
     r = l + width
     t = b + height

I am a new user to python and I discovered something rather annoying and
wondered if a better default solution could be determined.  I am not sure if
this has already been discussed before but a quick look on google and the
Nabble forum didn't yield any obvious clues so I decided to create a new
post.

My original problem was that I was unable to specify labelled arbitrary
ticks in logscale plots.  For example:

import matplotlib.pyplot as mpl

mpl.plot([1,2,3],[4,5,6])
mpl.xticks([1.0, 2.0, 2.3, 2.35])
mpl.show()

will correctly output the changed ticks and label them.  However:

mpl.loglog([1,2,3],[4,5,6])
mpl.xticks([1.0, 2.0, 2.3, 2.35])
mpl.show()

will only display the minor ticks and fail to label any of them other than
the the value 1.0.  This is also true for the semilogx() function.  I think
this was because the default format is given as 10^n, where n is an integer
and there are no integers that can describe the 2.0, 2.3 and 2.35 values
above.  To solve the problem I used:

import matplotlib.pyplot as mpl
from matplotlib.ticker import FuncFormatter

def label_form(x, pos):
    return str(float(x))

mpl.loglog([1,2,3],[4,5,6])
mpl.xticks([1.0, 2.0, 2.3, 2.35])
mpl.gca().xaxis.set_major_formatter(FuncFormatter(label_form)) 
mpl.show()

which wasted a fair couple of hours of my life!  Imho I would prefer it if
the default format was in scientific exponential notation: 2.3e10 or
standard form: 2.3x10^10 for logscale plots.  A selection criteria could be
applied for the case of floats = 1.0, 10.0, 100.0 such that it could print
in the 10^n format.  In any case, I think it is more important to allow
labels to be displayed in an uglier format when requested rather than
ignored, without informing the user, for the sake of aesthetics.  I also
noticed that for linear plots the format of the numbers is to print a float
and then put the exponential part separately beside the axis.  For example:

mpl.plot([1,2,3],[4e10,5e10,6e10])
mpl.xticks([1.0, 2.0, 2.3, 2.35])
mpl.show()

Although this is looks neat, it would have looked odd to have it in this
format for publication.  I would prefer to divide my data by 1.0e10 and put
in the ylabel "Data ($10^10$ units)" or just have each number in scientific
exponential format or standard form.  As an example of this in practise, it
is sometimes convenient to publish temperature plots in astrophysics in T_9,
which is the temperature in 10^9 K.

What do you think?  If this has already been discussed in detail, I
apologise for bringing it up again.  In which case, I would appreciate a
link to the thread/web page.
-- 
View this message in context: http://old.nabble.com/Default-format-of-numbers-on-logscale-and-arbitrary-tick-marks-tp27772714p27772714.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Jae-Joon Lee wrote:
> I fixed this in the maintenance branch.
> But I'm failing with the svnmerge.
> I thought this issue has been fixed but I'm not sure what I'm doing
> wrong.
I thought I had fixed it, but it seems to have broken again immediately 
after.  I'm not sure how much additional time I want to spend on the 
problem given that the transition to git is imminent ;)

Mike
>  I cannot spend much more time on this right now, but John, if
> you can, please merge the change and commit them for me.
>
> Regards,
>
> -JJ
>
>
> On Wed, Mar 3, 2010 at 11:42 AM, John Hunter <jd...@gm...> wrote:
>   
>> On Wed, Mar 3, 2010 at 10:09 AM, Matthias Michler
>> <Mat...@gm...> wrote:
>>     
>>> Hello list,
>>>
>>> I get an error, when calling "ax.redraw_in_frame()" (see below).
>>>
>>> I think this is due to the fact that the draw_wrapper expects args instead of
>>> kwargs for the "draw" of an Axes instance and therefore provide a patch,
>>> which adds an additional star.
>>>
>>> Could any of the developers have a look at it, please?
>>>       
>> JJ, this looks like something you are most qualified to look at.
>> Could we standardize on *args and **kwargs for the naming convention
>> of optional arguments and keyword arguments to help avoid some
>> ambiguity?
>>
>> JDH
>>
>> ------------------------------------------------------------------------------
>> Download Intel&#174; 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
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>>     
>
> ------------------------------------------------------------------------------
> Download Intel&#174; 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
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>   

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

I fixed this in the maintenance branch.
But I'm failing with the svnmerge.
I thought this issue has been fixed but I'm not sure what I'm doing
wrong. I cannot spend much more time on this right now, but John, if
you can, please merge the change and commit them for me.

Regards,

-JJ


On Wed, Mar 3, 2010 at 11:42 AM, John Hunter <jd...@gm...> wrote:
> On Wed, Mar 3, 2010 at 10:09 AM, Matthias Michler
> <Mat...@gm...> wrote:
>> Hello list,
>>
>> I get an error, when calling "ax.redraw_in_frame()" (see below).
>>
>> I think this is due to the fact that the draw_wrapper expects args instead of
>> kwargs for the "draw" of an Axes instance and therefore provide a patch,
>> which adds an additional star.
>>
>> Could any of the developers have a look at it, please?
>
> JJ, this looks like something you are most qualified to look at.
> Could we standardize on *args and **kwargs for the naming convention
> of optional arguments and keyword arguments to help avoid some
> ambiguity?
>
> JDH
>
> ------------------------------------------------------------------------------
> Download Intel&#174; 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
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

On Wed, Mar 3, 2010 at 10:45 AM, Matthias Michler
<Mat...@gm...> wrote:

>> v0_99_maint is the current maintenance branch/
>
> I checked out
> https://matplotlib.svn.sourceforge.net/svnroot/matplotlib/branches/v0_99_maint/
> and included my changes of trunk as you can see in the attached patch.
>
> Furthermore I replaced a (minor) typo in
> lib/matplotlib/patches.py:
> -                                                      self.legnthA*scaleA)
> +                                                      self.lengthA*scaleA)
>
> Does this patch fulfill your needs?


Yep.  For some reason the artists.rst part was rejected even though I
couldn't figure out why.  I just manually applied that portion.  I am
trying to rebuild the site docs now, so I will ping you when this is
complete and uploaded.

Thanks for taking the trouble to redo this on the branch!

JDH

You're right...here it is.


---------------------------------------
Bruce W. Ford
Clear Science, Inc.
br...@cl...
bru...@na...
http://www.ClearScienceInc.com
Phone/Fax: 904-379-9704
8241 Parkridge Circle N.
Jacksonville, FL  32211
Skype:  bruce.w.ford
Google Talk: fo...@gm...



On Wed, Mar 3, 2010 at 10:27 AM, Jeff Whitaker <js...@fa...> wrote:
> Bruce Ford wrote:
>>
>> All,
>>
>> It took a fair bit of trial and error to coax a KML-friendly image out
>> of matplotlib and to understand what was and was not necessary.  Below
>> is a demo script demonstrating how to accomplish a KML-friendly image
>> with and without a basemap.  I hope this will help someone out.
>>
>> What do I mean by a KML-friendly image?  In KML you can overlay a
>> complicated geo-referenced image but it is geo-referenced based on the
>> boundaries of the image.  So, for the image to be correctly displayed
>> in a KML document, the edges of the image have to be relatable to a
>> latitude or longitude.  Most of the time this will mean you are using
>> Basemap and you'll need an image that encompasses only the bounding
>> box and nothing outside...no whitespace, extra room for titling, etc.
>>
>> The below examples accomplish this.  Turns out, the two key elements are
>>
>> (1)  ax = pyplot.axes((0,0,1,1))
>>
>> and if you are using Basemap:
>>
>> (2) a kwarg in Basemap:  fix_aspect=False
>>
>> Thanks!
>>
>> Bruce
>>
>
> Bruce:  That's great, I've always wondered how to do that.   However your
> example didn't make it to the list, perhaps you forgot to attach it?
>
>
> -Jeff
>
> --
> Jeffrey S. Whitaker         Phone  : (303)497-6313
> Meteorologist               FAX    : (303)497-6449
> NOAA/OAR/PSD  R/PSD1        Email  : Jef...@no...
> 325 Broadway                Office : Skaggs Research Cntr 1D-113
> Boulder, CO, USA 80303-3328 Web    : http://tinyurl.com/5telg
>
>

On Wed, Mar 3, 2010 at 10:09 AM, Matthias Michler
<Mat...@gm...> wrote:
> Hello list,
>
> I get an error, when calling "ax.redraw_in_frame()" (see below).
>
> I think this is due to the fact that the draw_wrapper expects args instead of
> kwargs for the "draw" of an Axes instance and therefore provide a patch,
> which adds an additional star.
>
> Could any of the developers have a look at it, please?

JJ, this looks like something you are most qualified to look at.
Could we standardize on *args and **kwargs for the naming convention
of optional arguments and keyword arguments to help avoid some
ambiguity?

JDH

On Wed, Mar 3, 2010 at 10:25 AM, Matthias Michler
<Mat...@gm...> wrote:
> On Wednesday 03 March 2010 17:02:58 John Hunter wrote:
>> On Wed, Mar 3, 2010 at 9:56 AM, Matthias Michler
>>
>> <Mat...@gm...> wrote:
>> > I attached a patch with modified documentation and further replacements
>> > of 'get_bounds' in current svn. Could any of the developers have a look
>> > at it and commit these changes or should a post the patch at the
>> > patch-tracker?
>>
>> The patch looks good -- could I trouble you to make a patch against
>> the maintenance branch, which I can then merge into the trunk
>>
>> http://matplotlib.sourceforge.net/devel/coding_guide.html#svn-checkouts
>>
>> Thanks!
>> JDH
>
> Hi John,
>
> I'm sorry. I didn't do this before and propably I won't manage it today.

No need to apologize -- I appreciate you taking the time to make the
patch.  Since this bug affects the branch and the trunk, I'd like to
see if fixed in both places since we plan to do a release of the
maintenance branch first and then the trunk.  The easiest way to do
this in our workflow is to fix the branch and merge to the trunk.

> Which of the maintance branches do you mean?
> v0_91_maint/
> v0_98_5_maint/
> v0_99_maint/
> or something completely different?

v0_99_maint is the current maintenance branch/

>
> By the way I think the link on "devel/coding_guide.html" to get "svnmerge.py"
> seems to be broken:
> http://svn.collab.net/repos/svn/trunk/contrib/client-side/svnmerge/svnmerge.py
> and in the attached patch "doc_devel_coding_guide.patch" I replaced it by:
> http://svn.apache.org/repos/asf/subversion/trunk/contrib/client-side/svnmerge/svnmerge.py


OK, thanks, I'll try and apply this.

JDH

Bruce Ford wrote:
> All,
>
> It took a fair bit of trial and error to coax a KML-friendly image out
> of matplotlib and to understand what was and was not necessary.  Below
> is a demo script demonstrating how to accomplish a KML-friendly image
> with and without a basemap.  I hope this will help someone out.
>
> What do I mean by a KML-friendly image?  In KML you can overlay a
> complicated geo-referenced image but it is geo-referenced based on the
> boundaries of the image.  So, for the image to be correctly displayed
> in a KML document, the edges of the image have to be relatable to a
> latitude or longitude.  Most of the time this will mean you are using
> Basemap and you'll need an image that encompasses only the bounding
> box and nothing outside...no whitespace, extra room for titling, etc.
>
> The below examples accomplish this.  Turns out, the two key elements are
>
> (1)  ax = pyplot.axes((0,0,1,1))
>
> and if you are using Basemap:
>
> (2) a kwarg in Basemap:  fix_aspect=False
>
> Thanks!
>
> Bruce
>   

Bruce:  That's great, I've always wondered how to do that.   However 
your example didn't make it to the list, perhaps you forgot to attach it?


-Jeff

-- 
Jeffrey S. Whitaker         Phone  : (303)497-6313
Meteorologist               FAX    : (303)497-6449
NOAA/OAR/PSD  R/PSD1        Email  : Jef...@no...
325 Broadway                Office : Skaggs Research Cntr 1D-113
Boulder, CO, USA 80303-3328 Web    : http://tinyurl.com/5telg

On Wed, Mar 3, 2010 at 9:56 AM, Matthias Michler
<Mat...@gm...> wrote:

> I attached a patch with modified documentation and further replacements
> of 'get_bounds' in current svn. Could any of the developers have a look at it
> and commit these changes or should a post the patch at the patch-tracker?

The patch looks good -- could I trouble you to make a patch against
the maintenance branch, which I can then merge into the trunk

http://matplotlib.sourceforge.net/devel/coding_guide.html#svn-checkouts

Thanks!
JDH

All,

It took a fair bit of trial and error to coax a KML-friendly image out
of matplotlib and to understand what was and was not necessary.  Below
is a demo script demonstrating how to accomplish a KML-friendly image
with and without a basemap.  I hope this will help someone out.

What do I mean by a KML-friendly image?  In KML you can overlay a
complicated geo-referenced image but it is geo-referenced based on the
boundaries of the image.  So, for the image to be correctly displayed
in a KML document, the edges of the image have to be relatable to a
latitude or longitude.  Most of the time this will mean you are using
Basemap and you'll need an image that encompasses only the bounding
box and nothing outside...no whitespace, extra room for titling, etc.

The below examples accomplish this.  Turns out, the two key elements are

(1)  ax = pyplot.axes((0,0,1,1))

and if you are using Basemap:

(2) a kwarg in Basemap:  fix_aspect=False

Thanks!

Bruce
---------------------------------------
Bruce W. Ford
Clear Science, Inc.
br...@cl...
http://www.ClearScienceInc.com
Phone/Fax: 904-379-9704
8241 Parkridge Circle N.
Jacksonville, FL  32211
Skype:  bruce.w.ford
Google Talk: fo...@gm...

That was it

Thanks :)


John Hunter-4 wrote:
> 
> On Tue, Mar 2, 2010 at 5:13 AM, Dunx <du...@ho...> wrote:
>>
>> Hi,
>>
>> I know about the difference between pylab.psd and mlab.psd, but in theory
>> the only difference between the returned values is:
>>
>> pylab.psd = 10*log10(mlab.psd)
>>
>> Except this is not true, there is noticeable difference:
>>
>> pylab.psd = 23.4962 (all these pylab.psd values are read from graph)
>> 10*log10(mlab.psd) = 17.2852
>>
>> pylab.psd = 18.8973
>> 10*log10(mlab.psd) = 12.8149
>>
>> pylab.psd = 4.92
>> 10*log10(mlab.psd) = -2.247
>>
>> These all look suspiciously out by around 2pi, although by no means
>> exact.
>> Any ideas?
>>
>> code is:
>> pylab.psd(input, NFFT=512, Fs=sampleRate, window=blackman(512)) #graph
>> x,y = mlab.psd(input, NFFT=512, Fs=sampleRate, window=blackman(512))
>> #look
>> at x
> 
> What version of mpl are you using?  Could you try setting your
> matplotlib rc parameter path.simplify to False?  There is a known bug
> in the released version of mpl that causes path simplification to
> render lines improperly.  Looking at the code, Axes.psd just calls
> mlab.psd and then plots 10*log10(pxx), so if there is a difference the
> most likely culprit is a rendering bug.
> See http://matplotlib.sourceforge.net/users/customizing.html for
> information on how to change your default matplotlib rc parameters.
> 
> Christoph, this is a serious bug that merits a branch bugfix release
> ASAP.  I will do the src release if you can do the win32 release.
> Perhaps we can find someone who can build the OSX binaries for us
> since my OSX box is dead.  By I don't want to hold the release for
> want of OSX binaries since this is a recurrent and serious problem.
> 
> JDH
> 
> ------------------------------------------------------------------------------
> Download Intel&#174; 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
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
> 

-- 
View this message in context: http://old.nabble.com/PSD-amplitude-disparity-tp27754632p27766635.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Hi Matthias,

On Wed, 3 Mar 2010 09:30:32 +0100
Matthias Michler <Mat...@gm...> wrote:

> Therefore it is assumed (in the rcsetup.py) that the given string
> needs to be devided into sub-strings, which are separated by commas.
> For your particular case - in my opinion - the solution is to provide
> a list of string(s) instead of a string 
> 
> matplotlib.rcParams['text.latex.preamble']=[r"\usepackage[garamond,sfscaled=false]
> {mathdesign}"]

indeed, providing a list of string(s) solves my problem.


	Thanks

	Heiko


-- 
-- Nach der Schießerei mit einem Toten vor dem Hamburger Hauptbahnhof
-- fahndet die Polizei weiter nach dem Täter.
-- (aus einer Meldung der Deutschen Presse-Agentur.) 
-- Heiko Bauke @ http://www.mpi-hd.mpg.de/personalhomes/bauke

Hi,

I have just upgraded Python, matplotlib etc. After this matplotlib is
having trouble displaying tick values. Values that only require one
character are displayed fine but other values (e.g. -1, 1.5, 10 etc.)
cannot be displayed. Boxes are displayed in their place.

I tried changing the tick font and the size of the font but this did not
help. Putting multiple digit values in the x-label works fine.

Any suggestions?
Thanks,
Damien

Important: This transmission is intended only for the use of the
addressee. It is confidential and may contain privileged information or
copyright material. If you are not the intended recipient, any use or
further disclosure of this communication is strictly forbidden. If you
have received this transmission in error, please notify me immediately
by telephone and delete all copies of this transmission as well as any
attachments.
 

The current implementation of PolarAxes does not support that.
However, you can workaround this easily using a custom axes.

In http://matplotlib.sourceforge.net/examples/pylab_examples/polar_demo.html

Instead of

ax = fig.add_axes([0.1, 0.1, 0.8, 0.8], polar=True, axisbg='#d5de9c')

use following code

from matplotlib.projections.polar import PolarAxes
from matplotlib.transforms import Affine2D

class PolarAxes2(PolarAxes):
    def PolarTransform(self):
        return Affine2D().translate(-.5*np.pi,0) + PolarAxes.PolarTransform()

ax = PolarAxes2(fig, [0.1, 0.1, 0.8, 0.8], axisbg='#d5de9c')
ax = fig.add_axes(ax)

Regards,

-JJ


On Tue, Mar 2, 2010 at 8:44 PM, R Fritz <rfritz@u.washington.edu> wrote:
> You can see an example on the second page of
> <http://lightolier.com/MKACatpdfs/8011.PDF>.  Scroll down.  The plot is
> next to the table titled, "candlepower summary."  It's a quadrant
> rather than a full circle, and it's clipped to a box, but it's still a
> polar plot.
>
> The only problem I have with what matplotlib does is that it seems
> determined to put zero at the right, rather than at the bottom.  I want
> to turn the axis 90 degrees.
>
> Randolph
>
> On 2010-03-02 14:50:51 -0800, Jae-Joon Lee said:
>
>> Do you have any link to an example plot?
>> I googled it but not much luck.
>> Is it like a polar plot without the bottom half?
>>
>> Regards,
>>
>> -JJ
>>
>> On Tue, Mar 2, 2010 at 1:48 AM, R Fritz <rfritz@u.washington.edu> wrote:
>> > I'd like to be able to generate type C photometry plots with
>> > matplotlib. The standard co-ordinate system for these has 0 degrees at
>> > the bottom (nadir) of the plot, with values increasing
>> > counterclockwise. Is there anyway I can transform the co-ordinates that
>> > matplotlib uses to do this?
>> > --
>>> Randolph Fritz
>>> >  design machine group, architecture department, university of washington
>>> > rfritz@u.washington.edu -or- rfr...@gm...
>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; 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
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

I tried to put some code to check overlapping texts.
The code runs, but I'm not sure if the code is correct. Texts still
overlap but I haven't checked if this is due to the incorrect code or
the input.
But I believe it gives you enough idea how to fix things.

You have several hundreds of candidate points for a few cases. No
doubt it takes so long.

Regards,

-JJ

On Mon, Mar 1, 2010 at 6:07 AM, Andrea Gavana <and...@gm...> wrote:
> Hi Jae-Joon & All,
>
> On 28 February 2010 03:09, Jae-Joon Lee wrote:
>> If I read your correctly,
>>
>>       for l, b in zip(x, y):
>>
>>          # And here  I work with data coordinates (!)
>>
>>           dashBox = Bbox.from_bounds(l, b, width+5, height+5)
>>           badness = 0
>>           for line in lines:
>>               if line.intersects_bbox(dashBox):
>>                   badness += 1
>>
>> x, y (therefore l, b) in data coordinate.
>> width, height?? this seems to be some wx specific coordinate, i have no idea.
>> lines (therefore line)  in display coordinate.
>>
>> converting x,y to display coordinate should straight forward. But I'm
>> not sure what kind of coordinate width and height has. Is it a method
>> of some class derived from matplotlib's Text?? If then, the extent of
>> the text can be measured using the get_window_extent method. This
>> requires a renderer instance, which should be known if the method is
>> called during the drawing time.
>>
>> Again, post a complete but simple(!) code.
>
> OK, I think I got a complete code. Not super-simple, but simple enough
> I believe. After you run it you'll see a bunch of points and lines
> with some text. If you left-click inside the axis this will start the
> calculations for the "optimal positioning". There are a couple of
> problems:
>
> 1) The code I have looks only for optimal positioning with respect to
> lines in the plot, it doesn't include texts (I don't know how to do
> it); You'll see what I mean if you run the code, the "optimally"
> positioned texts overlap with other text in the plot, and with
> themselves too (i.e., one "optimally" positioned text overlap with
> another "optimally" positioned text);
> 2) The code as it stands it's veeeeery slow. On my (relatively fast)
> computer, it takes almost 6 seconds to "optimally" position 14 labels.
>
> In order to run the code, you'll also need the "lines.txt" file, which
> contains the main lines coordinates. Sorry about this extra file but I
> wanted it to be as close as possible to my use-case.
>
> Thank you in advance for your suggestions.
>
> Andrea.
>
> "Imagination Is The Only Weapon In The War Against Reality."
> http://xoomer.alice.it/infinity77/
> http://thedoomedcity.blogspot.com/
>

You can see an example on the second page of 
<http://lightolier.com/MKACatpdfs/8011.PDF>.  Scroll down.  The plot is 
next to the table titled, "candlepower summary."  It's a quadrant 
rather than a full circle, and it's clipped to a box, but it's still a 
polar plot.

The only problem I have with what matplotlib does is that it seems 
determined to put zero at the right, rather than at the bottom.  I want 
to turn the axis 90 degrees.

Randolph

On 2010-03-02 14:50:51 -0800, Jae-Joon Lee said:

> Do you have any link to an example plot?
> I googled it but not much luck.
> Is it like a polar plot without the bottom half?
> 
> Regards,
> 
> -JJ
> 
> On Tue, Mar 2, 2010 at 1:48 AM, R Fritz <rfritz@u.washington.edu> wrote:
> > I'd like to be able to generate type C photometry plots with
> > matplotlib. The standard co-ordinate system for these has 0 degrees at
> > the bottom (nadir) of the plot, with values increasing
> > counterclockwise. Is there anyway I can transform the co-ordinates that
> > matplotlib uses to do this?
> > --
>> Randolph Fritz
>> >  design machine group, architecture department, university of washington
>> > rfritz@u.washington.edu -or- rfr...@gm...

On Tue, Mar 2, 2010 at 5:57 PM, Andrea Gavana <and...@gm...>wrote:

> Hi All,
>
>    I believe this question has been already asked in the past (I
> found something at
> http://old.nabble.com/A-good,-interactive-plotting-package-td15396445.html
> ).
>
> I use matplotlib extensively in our applications, and some of my users
> repetitively asked for a way to customize *in runtime* the plots my
> apps generate. I.e., the app brings up a figure with a bunch of lines,
> points and texts, and they would like to change this linewidth, the
> colour of that point, the appearance of an axis, the legend keys and
> so on. I am currently answering "it can't be done at the moment" :-D.
> It is obviously not true, it just require some (a lot, maybe) work.
>
> Now, I know nothing about the other backends, but I know something
> about wx and I believe it is doable. Obviously, if my job was software
> programming and not reservoir engineering I would already have given
> it a try, but unfortunately we only get 24 hours per day...
>
> I don't think anything like this already exists, but it's an innocent
> question and I hope I won't be kicked for asking :-D . If someone
> knows about a possible/existing implementation, or even a start of an
> implementation, please let me know.
>
> Thank you.
>
> Andrea.
>
> "Imagination Is The Only Weapon In The War Against Reality."
> http://xoomer.alice.it/infinity77/
> http://thedoomedcity.blogspot.com/
>
>
Hello,

I can list three ways to interact with active plots:

1-)  Using keyboard shortcuts: Changing scaling  using "k" and "l" keys are
my favorite. See more at
http://matplotlib.sourceforge.net/users/navigation_toolbar.html

2-) Using the interactive navigation toolbar and with a small extension
written by Pierre Raybaut (on Qt4Agg backend) For a screenshot see
http://img156.imageshack.us/img156/9210/mplqtextra.png
This is open to development. Actually many of the command line mpl interface
could be integrated into that window.

3-) Directly from within IPython shell. That's another useful way of
updating figure properties (e.g. adding labels, changing font) IPython and
matplotlib are very well integrated in that manner. Similarly, Mayavi does a
great job of integrating shell and UI.


-- 
Gökhan