matplotlib-users Mailing List for matplotlib

On Mon, Jun 11, 2012 at 2:05 PM, wiswit <cha...@gm...> wrote:
> While in emacs or vim, you cannot simple select lines and execute them, so
> you have to frequently copy and code and use %cpaste or %paste to paste the
> code.

In emacs you can activate ipython in your emacs.el file and then you
can send arbitrary snippets you highlight, with C-c |.  In vim, Paul
Ivanov's vim-ipython integration
(https://github.com/ivanov/vim-ipython) gives even more powerful and
detailed control.

Not saying the issues being discussed don't exist, but we do have some
tools to partially address them (the questions about the MPL api are
obviously beyond IPython's control).

Cheers,

f

I think this is worth discussing. But I have only 1.3 years experience with
matplotlib and python. Basically, I do the same as you. But I think there
are few tips I would like to follow:

1. I would agree to make one major theme plot one script file. Avoid make
very long scripts with many plots. It's much more difficult to revisit. 
2. I would avoid writing too much fancy loops as it takes much more time
when you want to make some change later.
3. I would like to divide complex figures into simple ones. like I would use
scatter to plot only scatter, and plot for only plotting lines. but not use
plot to plot both. I think this allows more flexible way in the future to
make necessary modifications.

But I still don't manage to find a good way for efficiently modifying
scripts and interactive plotting. It's very nice to have interactive
plotting (with --pylab) using ipython notebook, but when you want to make
some substitutions, it's much more tedious than in an editor like vim/emacs.
While in emacs or vim, you cannot simple select lines and execute them, so
you have to frequently copy and code and use %cpaste or %paste to paste the
code. And....., a lot lot windows shifting.... 

Chao


pybokeh wrote:
> 
> Maybe workflow may not be the appropriate term.  Essentially, when I want
> to plot something using matplotlib, I find myself having to look up the
> api
> docs or examples online because quite frankly, matplotlib's syntax is very
> hard to remember.  I use ipython and use tab browsing, help(), dir(), etc,
> and that seem to help to some extent.  I absolutely love matplotlib, but
> when I want to put a chart up quickly, matplotlib is just a "hassle"
> depending on what chart you want to create.  I do expect this since
> plotting with matplotlib, you are essentially creating a chart
> "programmatically", instead of GUI interface environment.  But still, I
> feel like an improvement could still be made in making charts simpler with
> matplotlib.
> 
> While surfing the web, I ran into this module called Canvas:
> https://github.com/mdipierro/canvas
> 
> Canvas appears to be what I am after or what I wish matplotlib's future
> syntax should strive for.
> 
> Currently, I store my matplotlib chart source code in folders with the
> file
> name describing what chart it creates (for example, "box_plot.py" or
> "control_chart.py", etc.) and use them as "cheat sheets" when I need to
> make a chart.  I am curious what other matplotlib users do?  Otherwise, I
> do find myself sometimes just creating the chart in Excel as a 1st option,
> and make charts in matplotlib if it is something Excel can't handle.
> 
> Thanks in advance,
> Daniel
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
> 

-- 
View this message in context: http://old.nabble.com/What-is-your-matplotlib-workflow--tp33987463p33996351.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Le 11/06/2012 22:30, magurling a écrit :
> I just wanted the axis line to end at the last y tick

> I've never used an explicit axis. What will axis('tight') actually do?

In your case plt.axis('tight') will constrain the axes to your plotted 
object, no space above, below, or at the right. The "good" plot
gives x from 0 to 0.10, and y from -20.5 to 69. (The other: to 70).
The tight_layout directive is used mainly when you have several subplots.

Jerzy Karczmarczuk

Jerzy Karczmarczuk-2 wrote:
> 
> What do you really want?
> 

I just wanted the axis line to end at the last y tick



> I would suggest using an explicit axis, e.g.
> 
> plt.axis([0,0.10,-25,80])
> 
> (or between -30 and 100, or 'tight', etc.)
> 

I've never used an explicit axis. What will axis('tight') actually do?



> Perhaps you wanted axis('tight') rather than your tight_layout?
> 

I actually wanted tight_layout. good.py and bad.py were just my attempt to
reduce the problem to the fewest lines of code before posting it. The actual
problem script has a lot more going on and tight_layout works well in that
script for reasons unrelated to this problem. Sorry if I made things unclear
by leaving the tight_layout line in the scripts that I posted. 
-- 
View this message in context: http://old.nabble.com/y-axis-misbehavior-tp33977870p33996132.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Tony Yu-3 wrote:
> 
> `yticks()` just sets the ticks, which shows up correctly in both plots. It
> sounds like what you want to specify is the axis limit. You can add the
> following (e.g. after the call to `yticks`):
> 
>    plt.ylim(ymin=-30)
> 

Thanks Tony for clearing up my misunderstanding of what yticks() is doing.
Using ylim() gives me what I was after.
-- 
View this message in context: http://old.nabble.com/y-axis-misbehavior-tp33977870p33996062.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

On Mon, Jun 11, 2012 at 12:23 PM, Gustavo Goretkin <
gus...@gm...> wrote:

> The problem is that the function in _path.cpp expects a path radius
> argument, r.
>
> Here is the signature:
> point_in_path(double x, double y, double r, PathIterator& path,
>               const agg::trans_affine& trans)
>
> but the invocation in python looks like this:
>
> point_in_path(point[0], point[1], self, transform)
>
>
Unless someone undid the fix, this was already fixed in master, I believe.
The current python invocation is:

 result = point_in_path(point[0], point[1], radius, self, transform)

Ben Root

I can't reproduce this on version >= 1.1.0. What version of matplotlib
are you using?


On 11 June 2012 17:23, Gustavo Goretkin <gus...@gm...> wrote:
> The problem is that the function in _path.cpp expects a path radius
> argument, r.
>
> Here is the signature:
> point_in_path(double x, double y, double r, PathIterator& path,
>               const agg::trans_affine& trans)
>
> but the invocation in python looks like this:
>
> point_in_path(point[0], point[1], self, transform)
>
>
>
> On Sat, Jun 9, 2012 at 9:27 PM, Gustavo Goretkin
> <gus...@gm...> wrote:
>>
>> I think I'm experiencing a bug.
>>
>> Here is a minimum example:
>>
>> import matplotlib.patches as mpatches
>> path = mpatches.Rectangle((0,0),width=1,height=1).get_path()
>> print path.contains_point(point=(.5,.5))
>>
>> it raises an IndexError: Unexpected SeqBase<T> length.
>>
>> I think this is a problem in the contains_point method which calls a C
>> function point_in_path inside of matplotlib._path
>>
>> Thanks!
>> Gustavo
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

The problem is that the function in _path.cpp expects a path radius
argument, r.

Here is the signature:
point_in_path(double x, double y, double r, PathIterator& path,
              const agg::trans_affine& trans)

but the invocation in python looks like this:

point_in_path(point[0], point[1], self, transform)


On Sat, Jun 9, 2012 at 9:27 PM, Gustavo Goretkin <gus...@gm...
> wrote:

> I think I'm experiencing a bug.
>
> Here is a minimum example:
>
> import matplotlib.patches as mpatches
> path = mpatches.Rectangle((0,0),width=1,height=1).get_path()
> print path.contains_point(point=(.5,.5))
>
> it raises an IndexError: Unexpected SeqBase<T> length.
>
> I think this is a problem in the contains_point method which calls a C
> function point_in_path inside of matplotlib._path
>
> Thanks!
> Gustavo
>