matplotlib-devel Mailing List for matplotlib

Tony S Yu wrote:
> Did this email ever appear on list? I didn't see it after sending my  
> original post, but I found it on the Sourceforge mail archives. I'm  
> trying a different email address as an experiment.

Tony,

It did appear the first time, but I guess everyone who saw it figured 
someone else would deal with it.
> 
> In any case, any comments on the patch?

Looks reasonable to me.  I will apply it.

Eric

> 
> -Tony
> 
> On Aug 24, 2009, at 5:31 PM, Tony Yu wrote:
> 
>> I noticed that semilogx and semilogy don't check if the linear axis  
>> (y-axis for semilogx; x-axis for semilogy) is actually linear. Thus,  
>> if I call semilogx and then call semilogy *on the same plot*, I end  
>> up with a loglog plot.
>>
>> Below is a simple patch. I'm not sure how useful this fix is since  
>> most people wouldn't want to make these calls on the same plot  
>> (since the second call would override the first)---I was working  
>> interactively in IPython so it did make a difference.
>>
>> Cheers,
>> -Tony
>>
>>
>> Index: lib/matplotlib/axes.py
>> ===================================================================
>> --- lib/matplotlib/axes.py	(revision 7557)
>> +++ lib/matplotlib/axes.py	(working copy)
>> @@ -3615,6 +3615,7 @@
>>              }
>>
>>         self.set_xscale('log', **d)
>> +        self.set_yscale('linear')
>>         b =  self._hold
>>         self._hold = True # we've already processed the hold
>>         l = self.plot(*args, **kwargs)
>> @@ -3665,6 +3666,7 @@
>>              'nonposy': kwargs.pop('nonposy', 'mask'),
>>              }
>>         self.set_yscale('log', **d)
>> +        self.set_xscale('linear')
>>         b =  self._hold
>>         self._hold = True # we've already processed the hold
>>         l = self.plot(*args, **kwargs)
> 
> 
> ------------------------------------------------------------------------------
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Did this email ever appear on list? I didn't see it after sending my  
original post, but I found it on the Sourceforge mail archives. I'm  
trying a different email address as an experiment.

In any case, any comments on the patch?

-Tony

On Aug 24, 2009, at 5:31 PM, Tony Yu wrote:

> I noticed that semilogx and semilogy don't check if the linear axis  
> (y-axis for semilogx; x-axis for semilogy) is actually linear. Thus,  
> if I call semilogx and then call semilogy *on the same plot*, I end  
> up with a loglog plot.
>
> Below is a simple patch. I'm not sure how useful this fix is since  
> most people wouldn't want to make these calls on the same plot  
> (since the second call would override the first)---I was working  
> interactively in IPython so it did make a difference.
>
> Cheers,
> -Tony
>
>
> Index: lib/matplotlib/axes.py
> ===================================================================
> --- lib/matplotlib/axes.py	(revision 7557)
> +++ lib/matplotlib/axes.py	(working copy)
> @@ -3615,6 +3615,7 @@
>              }
>
>         self.set_xscale('log', **d)
> +        self.set_yscale('linear')
>         b =  self._hold
>         self._hold = True # we've already processed the hold
>         l = self.plot(*args, **kwargs)
> @@ -3665,6 +3666,7 @@
>              'nonposy': kwargs.pop('nonposy', 'mask'),
>              }
>         self.set_yscale('log', **d)
> +        self.set_xscale('linear')
>         b =  self._hold
>         self._hold = True # we've already processed the hold
>         l = self.plot(*args, **kwargs)

On Sat, Aug 29, 2009 at 10:58 AM, Michael Sarahan<mcs...@uc...> wrote:
> Here you go.  If you can think of anything else to include, I'll work
> on it.  I think the next thing I'll add is something on embedding
> images in the corners of plots.  figimage is the way to do this,
> right?

It depends on exactly what you are trying to do -- figimage is a pure
pixel dump, so it doesn't scale with DPI.  It is good for people who
want to put raw data into a figure, but not for much else.  You can
also use the "extent" argument to a regular image to

> The image is on that I took, so don't worry about licensing on it.  My
> images are licensed under Creative Commons.


Great -- I've pushed this out to the website.  Thanks a lot.  You can
see the fruits of your labors at

http://matplotlib.sourceforge.net/users/image_tutorial.html

If you want to make any more enhancements, the easiest way for me is
to submit a diff against the 0.99 release branch

 > svn co https://matplotlib.svn.sf.net/svnroot/matplotlib/branches/v0_99_maint
mpl99
  # make your edits
 > svn diff > imagetut.diff

See also, http://matplotlib.sourceforge.net/faq/howto_faq.html#contributing-howto

As for stuff to be added, here is a laundry list after a quick once
over, in no particular order

  * pointers to the matplotlib.colors, matplotlib.cm,
matplotlib.colorbar api docs

  * port the matplotlib.image module to have rest compliant docs,
incorporate them into the api docs, and link to them from the tutorial

  * discuss the image aspect settings with some examples

  * show how to use the matplotlib.cm objects, eg cm.jet, cm.hot in
addition to the strings 'jet', 'hot'

  * adjusting the size of the colorbar so it is the same height as your image

  * show how to create a custom colormap (there are examples for this
you could follow), either using listed colors or writing your own
linear segmented colormap

  * discuss figimage

  * discuss the extent argument

For many of these, if you don't know how to get started, read the doc
strings and then go to the search page and use the codex argument to
search for code examples.  Eg a search for "codex imshow extent" will
show image examples that use the extent kwarg

  http://matplotlib.sourceforge.net/search.html

Going forward, if you have further questions or need pointers to docs
or examples, please post to matplotlib-devel and let people know what
you are doing.  I sometimes get swallowed by all the stuff I am doing
so cannot always answer promptly, so it is good to have some backup.
I've take the liberty of CC-ing the devel list here in case others
want to jump in with suggestions or contributions to the tutorial

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

Thanks a lot for this -- the docs are making a lot of progress and
there is a ton of good stuff in mpl that still has no tutorial on how
to use it, so this is plugging one of those holes.

JDH

On Fri, Aug 28, 2009 at 9:47 PM, <jas...@cr...> wrote:
> Is there any chance someone could add a brief reference and link to the
> online svn repository somewhere on the front page of matplotlib?  Maybe
> in the sidebar under "Need help?":
>
> For details on what's new, see the detailed changelog
> <http://matplotlib.sourceforge.net/_static/CHANGELOG> **or browse the
> source code**. Anything that could require changes to your existing
> codes is logged in the api changes
> <http://matplotlib.sourceforge.net/api/api_changes.html> file.
>

Done, though I made the link point to trunk/matplotlib since I think
that is what most people will be interested in.

But bookmarks are helpful too :-)

JDH

Is there any chance someone could add a brief reference and link to the 
online svn repository somewhere on the front page of matplotlib?  Maybe 
in the sidebar under "Need help?":

For details on what's new, see the detailed changelog 
<http://matplotlib.sourceforge.net/_static/CHANGELOG> **or browse the 
source code**. Anything that could require changes to your existing 
codes is logged in the api changes 
<http://matplotlib.sourceforge.net/api/api_changes.html> file.


where "source code" links to 
http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/

I've run out of fingers and toes for counting how many times I have to 
click around and hunt this down (and I always forget to bookmark it or 
I'm on a new computer!)

Thanks,

Jason

--
Jason Grout