matplotlib-users Mailing List for matplotlib

On 10/18/07, Eric Firing <ef...@ha...> wrote:
> Jeremy Conlin wrote:
> > On 10/18/07, Eric Firing <ef...@ha...> wrote:
> >> Jeremy Conlin wrote:
> >>> On 10/17/07, Charles Seaton <cs...@st...> wrote:
> >>>> Jeremy,
> >>>>
> >>>> I ran across the answer to this last week while searching the list for
> >>>> info on datestr2num (both subjects happened to come up in the same
> >>>> exchange).
> >>>>
> >>>> http://www.nabble.com/First-impression-from-a-new-user-tf1716894.html#a4662446
> >>>>
> >>>> plot(x, y, linestyle='*steps*')
> >>>>
> >>>> Charles Seaton
> >>>
> >>> Well that's great! (I should have at least tried making such a plot
> >>> before posting. Sorry.) How come I couldn't find it in the
> >>> documentation? I can't find anything about available linestyles. Am
> >>> I looking the wrong location? I am looking at users_guide_0.9.0.pdf
> >> The user's guide tends to lag. To find the latest features, look at the
> >> CHANGELOG, the examples, and the docstrings. Ipython is a big help for
> >> looking at docstrings and trying things out. Are you familiar with it?
> >>
> >> Eric
> >>
> >
> > I am familiar with IPython and use it all the time as a replacement
> > for the standard Python interpreter. I don't always use the extra
> > features it offers. I just did
> >
> > help pylab.plot
>
> Even easier:
>
> pylab.plot?
>
> And for more detail (but mostly useful for matplotlib modules and
> functions rather than for their pylab wrappers), use two question marks
> to view the source code.
>
> To see available functions or attributes, use tab completion.
>
> Eric
>
>
> >
> > and there it was, what the available linestyles. Again lesson
> > learned, read the (available) documentation before asking the
> > questions. It is sometimes confusing where to go for the
> > documentation.
> >
> > Thanks,
> > Jeremy
>
>
Ooh, very nice. I'll try to incorporate those commands into my daily
repertoire.
Jeremy

Jeremy Conlin wrote:
> On 10/18/07, Eric Firing <ef...@ha...> wrote:
>> Jeremy Conlin wrote:
>>> On 10/17/07, Charles Seaton <cs...@st...> wrote:
>>>> Jeremy,
>>>>
>>>> I ran across the answer to this last week while searching the list for
>>>> info on datestr2num (both subjects happened to come up in the same
>>>> exchange).
>>>>
>>>> http://www.nabble.com/First-impression-from-a-new-user-tf1716894.html#a4662446
>>>>
>>>> plot(x, y, linestyle='*steps*')
>>>>
>>>> Charles Seaton
>>>
>>> Well that's great! (I should have at least tried making such a plot
>>> before posting. Sorry.) How come I couldn't find it in the
>>> documentation? I can't find anything about available linestyles. Am
>>> I looking the wrong location? I am looking at users_guide_0.9.0.pdf
>> The user's guide tends to lag. To find the latest features, look at the
>> CHANGELOG, the examples, and the docstrings. Ipython is a big help for
>> looking at docstrings and trying things out. Are you familiar with it?
>>
>> Eric
>>
> 
> I am familiar with IPython and use it all the time as a replacement
> for the standard Python interpreter. I don't always use the extra
> features it offers. I just did
> 
> help pylab.plot
Even easier:
pylab.plot?
And for more detail (but mostly useful for matplotlib modules and 
functions rather than for their pylab wrappers), use two question marks 
to view the source code.
To see available functions or attributes, use tab completion.
Eric
> 
> and there it was, what the available linestyles. Again lesson
> learned, read the (available) documentation before asking the
> questions. It is sometimes confusing where to go for the
> documentation.
> 
> Thanks,
> Jeremy

On 10/18/07, Eric Firing <ef...@ha...> wrote:
> Jeremy Conlin wrote:
> > On 10/17/07, Charles Seaton <cs...@st...> wrote:
> >> Jeremy,
> >>
> >> I ran across the answer to this last week while searching the list for
> >> info on datestr2num (both subjects happened to come up in the same
> >> exchange).
> >>
> >> http://www.nabble.com/First-impression-from-a-new-user-tf1716894.html#a4662446
> >>
> >> plot(x, y, linestyle='*steps*')
> >>
> >> Charles Seaton
> >
> >
> > Well that's great! (I should have at least tried making such a plot
> > before posting. Sorry.) How come I couldn't find it in the
> > documentation? I can't find anything about available linestyles. Am
> > I looking the wrong location? I am looking at users_guide_0.9.0.pdf
>
> The user's guide tends to lag. To find the latest features, look at the
> CHANGELOG, the examples, and the docstrings. Ipython is a big help for
> looking at docstrings and trying things out. Are you familiar with it?
>
> Eric
>
 am familiar with IPython and use it all the time as a replacement
for the standard Python interpreter. I don't always use the extra
features it offers. I just did
help pylab.plot
and there it was, what the available linestyles. Again lesson
learned, read the (available) documentation before asking the
questions. It is sometimes confusing where to go for the
documentation.
Thanks,
Jeremy

	Hi,
I have a small problem with label.
plot([0,1],[0,1])
xlabel(r'$ABCDEF$',fontsize=35)
(but the size doesn't change anything) I obtain the result visible on the 
figure join. I think there are a problem when using latex and how the first 
character is handle.
Thanks for matplotlib.
N.
PS: I'm using svn version:
pylab.__version__
'1.0.4.dev4241'

John,
svn works fine now. thanks.
John Hunter wrote:
> On 10/18/07, John Hunter <jd...@gm...> wrote:
> 
>> You should use the "c" argument for scatter -- this controls the facecolor.
>>
>> scatter(x,x+0.5, c='blue', s=50, alpha=0.5)
>>
>> This is a bit of an anachronism from matlab compatibility.
> 
> This is now fixed in svn, so you can use facecolor as well. Note that
> for constant size and color markers, plot will be significantly faster
> 
> ax.plot(x, x+0.5, mfc='blue', alpha=0.5, ms=20)
> 
> JDH

On 10/18/07, John Hunter <jd...@gm...> wrote:
> You should use the "c" argument for scatter -- this controls the facecolor.
>
> scatter(x,x+0.5, c='blue', s=50, alpha=0.5)
>
> This is a bit of an anachronism from matlab compatibility.
This is now fixed in svn, so you can use facecolor as well. Note that
for constant size and color markers, plot will be significantly faster
 ax.plot(x, x+0.5, mfc='blue', alpha=0.5, ms=20)
JDH

On 10/18/07, Manuel Metz <mm...@as...> wrote:
> It seems that the keywords facecolor (or color) and alpha can not be
> used simultaniously when using "scatter":
>
>
> import pylab
>
> x = pylab.npy.arange(0,10)
> pylab.scatter(x,x, s=50, alpha=0.5)
> pylab.scatter(x,x+0.5, facecolor='blue', s=50, alpha=0.5)
> pylab.show()
>
>
> The alpha value of the second call is not set correctly, but kept fix at
> alpha=1.0. Any idea ???
You should use the "c" argument for scatter -- this controls the facecolor.
scatter(x,x+0.5, c='blue', s=50, alpha=0.5)
This is a bit of an anachronism from matlab compatibility.
JDH

On 10/18/07, Jordan Atlas <jc...@co...> wrote:
> Hello,
>
> I'm having some trouble figuring out how to format the numerical
> labels on the tick marks of an axes. For example, in the plot linked
> below, I'd like the y-axis to display using scientific notation, and I'd
> like to control the precision level. I feel like this should be somehow
> possible using setp(yticklabels,...) but I haven't been able to find the
> relevant documentation or an example. Can someone point me in the right
> direction here?
You can set the formatter for the yaxis
 from matplotlib.ticker import FormatStrFormatter
 fmt = FormatStrFormatter('%1.4g') # or whatever
 ax.yaxis.set_major_formatter(fmt)
There is also a class tickers.ScalarFormatter for scientific
formatting that is customizable. You'll probably want to take a look
at it.
> Also, if someone has a suggestion for how to automatically avoid the
> axis label ('CW') being cut off like in the attachment, let me know (I'm
> letting the figure size get set automatically).
The easiest way to fix this is just to move the left border of your
axes over a bit
 fig = figure()
 fig.subplots_adjust(left=0.2)
 ax = fig.add_subplot(111) # now there is more space on the left
JDH

Hello,
 I'm having some trouble figuring out how to format the numerical 
labels on the tick marks of an axes. For example, in the plot linked 
below, I'd like the y-axis to display using scientific notation, and I'd 
like to control the precision level. I feel like this should be somehow 
possible using setp(yticklabels,...) but I haven't been able to find the 
relevant documentation or an example. Can someone point me in the right 
direction here?
 Also, if someone has a suggestion for how to automatically avoid the 
axis label ('CW') being cut off like in the attachment, let me know (I'm 
letting the figure size get set automatically).
 Please feel free to point me to a relevant section of the manual or 
to a function that I might be missing.
Thank you,
--Jordan
Here is the example: http://www.people.cornell.edu/pages/jca33/labels.pdf

It seems that the keywords facecolor (or color) and alpha can not be 
used simultaniously when using "scatter":
import pylab
x = pylab.npy.arange(0,10)
pylab.scatter(x,x, s=50, alpha=0.5)
pylab.scatter(x,x+0.5, facecolor='blue', s=50, alpha=0.5)
pylab.show()
The alpha value of the second call is not set correctly, but kept fix at 
alpha=1.0. Any idea ???
Manuel

Jeremy Conlin wrote:
> On 10/17/07, Charles Seaton <cs...@st...> wrote:
>> Jeremy,
>>
>> I ran across the answer to this last week while searching the list for
>> info on datestr2num (both subjects happened to come up in the same
>> exchange).
>>
>> http://www.nabble.com/First-impression-from-a-new-user-tf1716894.html#a4662446
>>
>> plot(x, y, linestyle='*steps*')
>>
>> Charles Seaton
> 
> 
> Well that's great! (I should have at least tried making such a plot
> before posting. Sorry.) How come I couldn't find it in the
> documentation? I can't find anything about available linestyles. Am
> I looking the wrong location? I am looking at users_guide_0.9.0.pdf
The user's guide tends to lag. To find the latest features, look at the 
CHANGELOG, the examples, and the docstrings. Ipython is a big help for 
looking at docstrings and trying things out. Are you familiar with it?
Eric

First you should look at the axes() command with its arguments to 
control the boundaries of the plot area inside the figure. I always use 
this to maximize the use of the figure space. I'm not sure, though, 
whether this works with the kind of plot you want. Check it out. The 
other thing that is related is the aspect ratio of the plot. A pie 
chart will only fill up as far as the shortest dimension available, so 
from your attachment you might try increasing the height or decreasing 
the width.
Wayne
Romain Bignon wrote:
> Hello,
>
> When I create a graph, margin is too wide. How can I reduce this?
>
> There is an example with this mail.
>
> Thanks.
>
> 
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 

Thank you Ken,
I ended up doing more or less as you suggested but it turns out that
with the new pick API is actually much easier:
 wxmpl.EVT_POINT(self, self.GetId(), self.onPoint)
 self.mpl_connect('pick_event', self.onPick)
 def onPoint(self,event):
 '''
 Called by the EVT_POINT of wxmpl. Generates a pick_event
 '''
 event.axes.pick(event)
 def onPick(self,event):
 '''
 Called upon a pick_event
 '''
 print 'You picked %s' % event.ind
GG
On 10/15/07, Ken McIvor <mc...@ii...> wrote:
> On Oct 12, 2007, at 4:28 PM, Giorgio F. Gilestro wrote:
> >
> > Do you know if there is a reason why I cannot succeed in generating a
> > pick_event using wxmpl?
>
> Yes, WxMpl disables all matplotlib events to ensure that figure
> zooming works correctly. I haven't had time to ensure that WxMpl will
> work reliably in all cases when matplotlib's events are enabled.
>
> > I know I could use EVT_POINT but I need the picker event to return
> > the event.ind
>
> Although it's a bit silly, one possible solution would be to have
> your EVT_POINT callback generate a mouse event. I think something
> like this might work, but I haven't tried it...
>
> from matplotlib.backend_bases import FigureCanvasBase
>
> def OnPoint(evt):
> figureCanvas = evt.axis.figure.canvas
> FigureCanvasBase.button_press_event(figureCanvas, evt.x, evt.y, 1)
>
>
> Ken
>