matplotlib-users Mailing List for matplotlib

Hi,

1.) For terminal just go to your finder and type in "terminal" in the
search bar, terminal should pop up
2.) I don't think you do, you might need to change the path variable to
point to the python you have. There are instructions for that in the
tutorial I linked to.
3.) I'm not sure what you're asking
4.) What do you mean you can't find them on your computer?
Start a terminal window and type
'python'
This should bring you to the interactive python environment.
Then type,
'import numpy'
Does it successfully import or do you get an error message?

(Also, click "Reply All" to keep this conversation to the list"
- Alexa

On Mon, Feb 13, 2012 at 10:11 AM, <a....@ya...> wrote:

> Hi Alex , thank you so much for your help. I have some questions:
>
> 1- where can I find the terminal in my computer
> 2- I have already had python 2.6.6 so do I need to delete it and start
> again.
> 3- my mac is  os x 10.6.8 so do I need to clean it while it is already do
> not have much download.
> 4- I download the scipy ,numpy and i have these modules successfully
> installed but I cannot find them in my computer.
>
>
> So could you help me ?
>
> Many thanks,
>
> Fadh
>
> ‏من جهاز الـ iPhone الخاص بي
>
> في 14/02/2012، الساعة 5:04 AM، كتب Alexa Villaume <ale...@gm...>:
>
> Hi Fadhah,
>
> This is the tutorial I used to install matplotlib on my computer and it
> was really easy to understand and follow the steps -
>
>
> <http://www.thisisthegreenroom.com/2011/installing-python-numpy-scipy-matplotlib-and-ipython-on-lion/>
> http://www.thisisthegreenroom.com/2011/installing-python-numpy-scipy-matplotlib-and-ipython-on-lion/
>
> If that doesn't help with your problems describe what they are more
> specifically and you'll be able to get better help
>
> Cheers,
> Alexa
>
>
> On Sun, Feb 12, 2012 at 5:39 PM, love ali < <a....@ya...>
> a....@ya...> wrote:
>
>> Dear all,
>>
>> I use the mac OS X 10.6.8 and I try to install the matplotlib but I
>> cannot run it in my computer so could you please help me?
>>
>>
>> Thanks,
>>
>> Fadhah
>>
>> ------------------------------------------------------------------------------
>> Try before you buy = See our experts in action!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>>  <http://p.sf.net/sfu/learndevnow-dev2>
>> http://p.sf.net/sfu/learndevnow-dev2
>> _______________________________________________
>> Matplotlib-users mailing list
>>  <Mat...@li...>
>> Mat...@li...
>>  <https://lists.sourceforge.net/lists/listinfo/matplotlib-users>
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>
>

Hi folks,

[ I'm broadcasting this widely for maximum reach, but I'd appreciate
it if replies can be kept to the *numpy* list, which is sort of the
'base' list for scientific/numerical work.  It will make it much
easier to organize a coherent set of notes later on.  Apology if
you're subscribed to all and get it 10 times. ]

As part of the PyData workshop (http://pydataworkshop.eventbrite.com)
to be held March 2 and 3 at the Mountain View Google offices, we have
scheduled a session for an open discussion with Guido van Rossum and
hopefully as many core python-dev members who can make it.  We wanted
to seize the combined opportunity of the PyData workshop bringing a
number of 'scipy people' to Google with the timeline for Python 3.3,
the first release after the Python language moratorium, being within
sight: http://www.python.org/dev/peps/pep-0398.

While a number of scientific Python packages are already available for
Python 3 (either in released form or in their master git branches),
it's fair to say that there hasn't been a major transition of the
scientific community to Python3.  Since there is no more development
being done on the Python2 series, eventually we will all want to find
ways to make this transition, and we think that this is an excellent
time to engage the core python development team and consider ideas
that would make Python3 generally a more appealing language for
scientific work.  Guido has made it clear that he doesn't speak for
the day-to-day development of Python anymore, so we all should be
aware that any ideas that come out of this panel will still need to be
discussed with python-dev itself via standard mechanisms before
anything is implemented.  Nonetheless, the opportunity for a solid
face-to-face dialog for brainstorming was too good to pass up.

The purpose of this email is then to solicit, from all of our
community, ideas for this discussion.  In a week or so we'll need to
summarize the main points brought up here and make a more concrete
agenda out of it; I will also post a summary of the meeting afterwards
here.

Anything is a valid topic, some points just to get the conversation started:

- Extra operators/PEP 225.  Here's a summary from the last time we
went over this, years ago at Scipy 2008:
http://mail.scipy.org/pipermail/numpy-discussion/2008-October/038234.html,
and the current status of the document we wrote about it is here:
file:///home/fperez/www/site/_build/html/py4science/numpy-pep225/numpy-pep225.html.

- Improved syntax/support for rationals or decimal literals?  While
Python now has both decimals
(http://docs.python.org/library/decimal.html) and rationals
(http://docs.python.org/library/fractions.html), they're quite clunky
to use because they require full constructor calls.  Guido has
mentioned in previous discussions toying with ideas about support for
different kinds of numeric literals...

- Using the numpy docstring standard python-wide, and thus having
python improve the pathetic state of the stdlib's docstrings?  This is
an area where our community is light years ahead of the standard
library, but we'd all benefit from Python itself improving on this
front.  I'm toying with the idea of giving a lighting talk at PyConn
about this, comparing the great, robust culture and tools of good
docstrings across the Scipy ecosystem with the sad, sad state of
docstrings in the stdlib.  It might spur some movement on that front
from the stdlib authors, esp. if the core python-dev team realizes the
value and benefit it can bring (at relatively low cost, given how most
of the information does exist, it's just in the wrong places).  But
more importantly for us, if there was truly a universal standard for
high-quality docstrings across Python projects, building good
documentation/help machinery would be a lot easier, as we'd know what
to expect and search for (such as rendering them nicely in the ipython
notebook, providing high-quality cross-project help search, etc).

- Literal syntax for arrays?  Sage has been floating a discussion
about a literal matrix syntax
(https://groups.google.com/forum/#!topic/sage-devel/mzwepqZBHnA).  For
something like this to go into python in any meaningful way there
would have to be core multidimensional arrays in the language, but
perhaps it's time to think about a piece of the numpy array itself
into Python?  This is one of the more 'out there' ideas, but after
all, that's the point of a discussion like this, especially
considering we'll have both Travis and Guido in one room.

- Other syntactic sugar? Sage has "a..b" <=> range(a, b+1), which I
actually think is  both nice and useful... There's also the question
of allowing "a:b:c" notation outside of [], which has come up a few
times in conversation over the last few years. Others?

- The packaging quagmire?  This continues to be a problem, though
python3 does have new improvements to distutils.  I'm not really up to
speed on the situation, to be frank.  If we want to bring this up,
someone will have to provide a solid reference or volunteer to do it
in person.

- etc...

I'm putting the above just to *start* the discussion, but the real
point is for the rest of the community to contribute ideas, so don't
be shy.

Final note: while I am here commiting to organizing and presenting
this at the discussion with Guido (as well as contacting python-dev),
I would greatly appreciate help with the task of summarizing this
prior to the meeting as I'm pretty badly swamped in the run-in to
pydata/pycon.  So if anyone is willing to help draft the summary as
the date draws closer (we can put it up on a github wiki, gist,
whatever), I will be very grateful.  I'm sure it will be better than
what I'll otherwise do the last night at 2am :)

Cheers,

f

ps - to the obvious question about webcasting the discussion live for
remote participation: yes, we looked into it already; no,
unfortunately it appears it won't be possible.  We'll try to at least
have the audio recorded (and possibly video) for posting later on.

pps- if you are close to Mountain View and are interested in attending
this panel in person, drop me a line at fer...@be....
We have a few spots available *for this discussion only* on top of the
pydata regular attendance (which is long closed, I'm afraid).  But
we'll need to provide Google with a list of those attendees in
advance.  Please indicate if you are a core python committer in your
email, as we'll give priority for this overflow pool to core python
developers (but will otherwise accommodate as many people as Google
lets us).

On Mon, Feb 13, 2012 at 2:59 PM, Jerzy Karczmarczuk <
jer...@un...> wrote:

>
>  reckoner:
>
>
>>
>> >>> th= array([ 4.65542641,  5.32920696,  2.20928291])
>> >>> p=patch.Polygon(array([cos(th),sin(th)]).T)
>> >>> print p.contains_point((0,0))
>> 1
>> >>> print matplotlib.nxutils.pnpoly(0,0,p.get_path().vertices)
>> 0
>>
>> Thanks!
>>
>>
>>
> I can confirm this for both the current development branch and v1.1.x.
> Strange....
>
> Ben Root
>
>   HYPOTHESIS (I have no time to check now everything..., I did my best.)
>
> If radius=None, it is converted into radius=1 in contains_point (in Patch).
> (This is the linewidth !)
> I am not sure whether it is ok, i.e. in pixels. If this value is
> considered to be relative to axes, it is enormous!
>
> p.contains_point((0,0),radius=0.01)
>
> gives 0 as it should.
>
> Jerzy Karczmarczuk
>
> P.S. I suggest anyway that reckoner submits a complete program with
> imports. What is "patch"??
>
>
>
Jerzy is right.  contains() and contains_point() both takes a radius
argument as this function is intended for use when mouse-clicking.  If no
radius is given, it uses the object's linewidth and passes it to the path's
contains_point() function with its transform.  I *suspect* that the problem
is that the transforms haven't been fully defined yet and might be
incorrectly testing this.

This needs a bit more investigation to see if this is the intended behavior
or if something needs to be fixed.

As a side note, "patch" is an imported module via "from matplotlib import
patches as patch".  Not standard among mpl devs, but not out of the
ordinary.

Ben Root

> reckoner:
>
>
>
>     >>> th= array([ 4.65542641,  5.32920696,  2.20928291])
>     >>> p=patch.Polygon(array([cos(th),sin(th)]).T)
>     >>> print p.contains_point((0,0))
>     1
>     >>> print matplotlib.nxutils.pnpoly(0,0,p.get_path().vertices)
>     0
>
>     Thanks!
>
>
>
> I can confirm this for both the current development branch and 
> v1.1.x.  Strange....
>
> Ben Root
>
HYPOTHESIS (I have no time to check now everything..., I did my best.)

If radius=None, it is converted into radius=1 in contains_point (in Patch).
(This is the linewidth !)
I am not sure whether it is ok, i.e. in pixels. If this value is 
considered to be relative to axes, it is enormous!

p.contains_point((0,0),radius=0.01)

gives 0 as it should.

Jerzy Karczmarczuk

P.S. I suggest anyway that reckoner submits a complete program with 
imports. What is "patch"??

Hmm, on further review, it looks like this is what triplot does!

I'll give it a try...

On 2/13/12 3:30 PM, Howard wrote:
> Hi all
>
> I'm using tricontourf with a triangulation object to draw a surface.  
> For debugging purposes, I'd like to draw just the unfilled triangles.  
> Is there a simple way to do this?
>
> Thanks
> Howard
> -- 
> Howard Lander <mailto:ho...@re...>
> Senior Research Software Developer
> Renaissance Computing Institute (RENCI) <http://www.renci.org>
> The University of North Carolina at Chapel Hill
> Duke University
> North Carolina State University
> 100 Europa Drive
> Suite 540
> Chapel Hill, NC 27517
> 919-445-9651


-- 
Howard Lander <mailto:ho...@re...>
Senior Research Software Developer
Renaissance Computing Institute (RENCI) <http://www.renci.org>
The University of North Carolina at Chapel Hill
Duke University
North Carolina State University
100 Europa Drive
Suite 540
Chapel Hill, NC 27517
919-445-9651

Hi all

I'm using tricontourf with a triangulation object to draw a surface.  
For debugging purposes, I'd like to draw just the unfilled triangles.  
Is there a simple way to do this?

Thanks
Howard
-- 
Howard Lander <mailto:ho...@re...>
Senior Research Software Developer
Renaissance Computing Institute (RENCI) <http://www.renci.org>
The University of North Carolina at Chapel Hill
Duke University
North Carolina State University
100 Europa Drive
Suite 540
Chapel Hill, NC 27517
919-445-9651

On Mon, Feb 13, 2012 at 1:33 PM, reckoner <rec...@gm...> wrote:

> Here's a better example:
>
> >>> th= array([ 4.65542641,  5.32920696,  2.20928291])
> >>> p=patch.Polygon(array([cos(th),sin(th)]).T)
> >>> print p.contains_point((0,0))
> 1
> >>> print matplotlib.nxutils.pnpoly(0,0,p.get_path().vertices)
> 0
>
> Thanks!
>
>
>
I can confirm this for both the current development branch and v1.1.x.
Strange....

Ben Root

Here's a better example:

>>> th= array([ 4.65542641,  5.32920696,  2.20928291])
>>> p=patch.Polygon(array([cos(th),sin(th)]).T)
>>> print p.contains_point((0,0))
1
>>> print matplotlib.nxutils.pnpoly(0,0,p.get_path().vertices)
0

Thanks!




On 2/13/2012 8:47 AM, reckoner wrote:
> I'm trying to test whether or not the origin is contained inside the
> following triangle
> inscribed inside a circle:
>
>>>> th = array([ 2.3913423,  5.3133123,  1.8516171])
>>>> p=patch.Polygon(array([cos(th),sin(th)]).T)
>
>>>> p.contains_point((0,0))
>
> returns 0
>
> but,
>
>>>> matplotlib.nxutils.points_inside_poly([[0,0]],p.get_path().vertices)
>
> returns True
>
> What am I missing here?
>
> Thanks!
>
>
>

Le 13/02/2012 17:47, reckoner a écrit :

I'm trying to test whether or not the origin is contained inside the
following triangle
inscribed inside a circle:

> th = array([ 2.3913423,  5.3133123,  1.8516171])
> p=patch.Polygon(array([cos(th),sin(th)]).T)

What do you mean by "patch" here?

I tested

p=Polygon(array([cos(th),sin(th)]).T)
p.contains_point((0,0))

and the answer is 1.

Jerzy Karczmarczuk

Hi Fadhah,

This is the tutorial I used to install matplotlib on my computer and it was
really easy to understand and follow the steps -

http://www.thisisthegreenroom.com/2011/installing-python-numpy-scipy-matplotlib-and-ipython-on-lion/

If that doesn't help with your problems describe what they are more
specifically and you'll be able to get better help

Cheers,
Alexa


On Sun, Feb 12, 2012 at 5:39 PM, love ali <a....@ya...> wrote:

> Dear all,
>
> I use the mac OS X 10.6.8 and I try to install the matplotlib but I cannot
> run it in my computer so could you please help me?
>
>
> Thanks,
>
> Fadhah
>
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

I noticed what is causing one of these issues:

1) When I point-pick on the plot, the plot area still "jumps" (expands
> vertically a small amount).  It used to do this each time I point-picked,
> but after upgrading MPL it now just does it the *first* time only.  But is
> it possible it can be fixed so it doesn't jump at all?
>

I see why this happens.  When I point pick, a popup window pops up and
covers the plot.  I think this triggers a redraw.  What causes the jump in
my case is that the plot's title is set, in y coordinate, to 1.04.  That
is, the line is this:

        self.subplot.title.set_y(1.04)

This is interacting with the line in make_axes_area_auto_adjustable:

    if self.title.get_visible():
        artists.append(self.title)

Essentially, it is getting the bbox, taking into consideration the plot's
title and other artists.  But if the title is set to greater than 1.00,
when I point pick (and force a redraw?), it has to recalculate the plot's
axes areas and it adjusts things, so the user sees the small vertical
expansion ("jump").

The problem goes away if I set the plot's title to 1.00:

        self.subplot.title.set_y(1.00)

*However, this puts the title too close to the top of the plot area for my
aesthetic liking.*  I'd prefer a little larger margin.

There should be a simple fix that allows for the title to be a bit higher
off the plot area and yet not cause this jump.  It would be in the code at
the end of this email, but i don't know enough about bbox to fix it
yet...any hints?

Thanks,
Che

def axes_get_tightbbox(self, renderer):
    """
    return the tight bounding box of the axes.
    The dimension of the Bbox in canvas coordinate.
    """

    artists = []
    bb = []

    artists.append(self)

    if self.title.get_visible():
        artists.append(self.title)

    if self.xaxis.get_visible():
        artists.append(self.xaxis.label)
        bbx1, bbx2 = axis_get_ticklabel_extents(self.xaxis, renderer, True)
        bb.extend([bbx1, bbx2])
    if self.yaxis.get_visible():
        artists.append(self.yaxis.label)
        bby1, bby2 = axis_get_ticklabel_extents(self.yaxis, renderer, True)
        bb.extend([bby1, bby2])


    bb.extend([c.get_window_extent(renderer) for c in artists if
c.get_visible()])

    _bbox = mtransforms.Bbox.union([b for b in bb if b.width!=0 or
b.height!=0])

    return _bbox

I'm trying to test whether or not the origin is contained inside the 
following triangle
inscribed inside a circle:

>>> th = array([ 2.3913423,  5.3133123,  1.8516171])
>>> p=patch.Polygon(array([cos(th),sin(th)]).T)

>>> p.contains_point((0,0))

returns 0

but,

>>> matplotlib.nxutils.points_inside_poly([[0,0]],p.get_path().vertices)

returns True

What am I missing here?

Thanks!

Dear all, 

I use the mac OS X 10.6.8 and I try to install the matplotlib but I cannot run it in my computer so could you please help me?


Thanks, 

Fadhah