matplotlib-users Mailing List for matplotlib

On Mon, Oct 6, 2008 at 10:56 AM, Eric Firing <ef...@ha...> wrote:
> Christopher Barker wrote:
>
>> David Goldsmith wrote:
>>
>>> I feel like I must be missing something
>>>
>>
>> yup -- though it's an understandable miss...
>>
>
> I think the longstanding separation between the figure.dpi and the
> savefig.dpi is a continual gotcha that we can and should eliminate. Savefig
> should use the figure dpi, so that what is saved corresponds to what is on
> the screen, unless explicitly overridden. One way to reduce the problem,
> with what I hope is an adequate level of backwards compatibility, would be
> to have the savefig.dpi default to a special flag setting that means "track
> the figure.dpi". For example, savefig.dpi could be the string, 'screen', by
> default. This could still be overridden by a numerical rcParams setting, or
> by the explicit dpi kwarg setting in savefig() or print_figure().
>
> There are still other highly confusing dpi things internally--such as a
> renderer.dpi setting that is ignored during rendering.
>
> Comments?
>
This appears to have never been "fixed" (though I see no opposition
expressed looking back at the original thread in the archive) - having
forgotten about it and the fact that, at the time, it sent me running to
PIL, I got bitten by it again (luckily I had a vague recollection of this
thread before posting the same problem again and making a complete ass outta
myself). I'm not sure if I have the bleeding edge version of MPL, but as
I'm now working on the second different computer I've had since the OP, I'm
pretty sure I'm running a later version than I was back then. Did this
issue ever mature into a ticket?
DG
>
> Eric
>
>
>
>>
>> Attached are the results on my computer (see usage details below).
>>> Granted, I'm increasing the resolution each iteration,
>>>
>>
>> you are increasing the resolution of the figure, and of your calculations,
>> but NOT of the output image. The hint was that every image was the same
>> size: 1200X900 , which is 12"x9" at 100 dpi.
>>
>> It turns out that print_figure() doesn't respect the figures (native DPI),
>> it defaults to 100 dpi, but you can override it:
>>
>> > canvas.print_figure("test"+str(DPI)+"dpi.png", dpi=DPI)
>>
>> Then you'll get what I think you want.
>>
>> Maybe this will help:
>>
>> http://www.scipy.org/Cookbook/Matplotlib/AdjustingImageSize
>>
>> though it there, I talked about Figure.savefig(). I don't know if there is
>> a difference between that and Figure.print_figure()
>>
>> -Chris
>>
>>
>>
>
>

David MacQuigg wrote:
> I can't get Matplotlib to work with IDLE. 
Sorry, I don't know anything about IDLE, but...
> I'm running on Mac OS-X, so it looks like IPython is not an option.
Why not? I use Ipython on OS-X all the time, and it is fabulous, really 
fabulous.
> Also, I
> would rather stick with IDLE. It is the perfect IDE for non-CS students who
> shouldn't be spending their time on the complexities of a plotting package.
Spyder:
http://packages.python.org/spyder/
Looks really promising, but I don't think they've got OS-X packages yet.
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

I can't get Matplotlib to work with IDLE. plt.show() makes beutiful plots,
but IDLE is hung. Entering "exit" in the little pop-up console window
raises an exception in IDLE, and then leaves the plot window hung. It looks
like the old "dualing event loops" problem with IDLE, although the
Matplotlib docs don't use that phrase.
The way I ususally solve this is to use IDLE for editing my scripts, and a
separate shell to actually run them. Here, I'm not using a saved script. 
This needs to work interactively, for students using Python in a physics
class. I see that little console window, and it sure looks like that was
intended to do what I need, but I can't find any documentation on the
commands. How do I switch back and forth between IDLE and the plot window
without leaving some process in limbo? Even better, is there an option to
have the event loop automatically switch back to IDLE after each update?
I'm running on Mac OS-X, so it looks like IPython is not an option. Also, I
would rather stick with IDLE. It is the perfect IDE for non-CS students who
shouldn't be spending their time on the complexities of a plotting package.
-- 
View this message in context: http://old.nabble.com/Matplotlib-conflicts-with-IDLE-tp27473693p27473693.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

I'm working in IDLE in Win7. It seems to me it gets stuck in 
site-packages under C:\Python25. Maybe this is as simple as deleting the 
entry?
Well, yes there's a MPL folder under site-packages and an info MPL file 
of 540 bytes. There are also pylab.py, pyc,and py0 files under site. 
What to do next?
On 2/5/2010 7:13 AM, Wayne Watson wrote:
> I should have installed numpy first, and got some errors installing
> MPL. I don't see an uninstall in Control Panel Add/Rmv.
> 
-- 
My life in two words. "Interrupted Projects." -- WTW (quote originator)

> On Fri, Feb 5, 2010 at 10:10 AM, Eymen Alyaz <ea...@mp...>
> wrote:
>> Is there a way to automatically correct the area of figure and resize it
>> such that every box drawn is visible?
>
> If you're only interested in the saved ouput, you may use
> "bbox_inches" option of "savefig". It does not change the size of the
> figure currently displayed, but it does change the size of the figure
> that is to be saved. Unfortunately, the released version of mpl will
> not work. With svn version, you can do
> ...
Thank you for this quick reply. Your suggestion matched my intention of
plotting/ saving the figure. I will give the svn version a shot and try it
out.
Regards,
Eymen

On Fri, Feb 5, 2010 at 10:10 AM, Eymen Alyaz <ea...@mp...> wrote:
> Is there a way to automatically correct the area of figure and resize it
> such that every box drawn is visible?
>
Things like axes position is given in normalized figure coordinates,
thus while you can change the figure size but it is quite hard to keep
things in place. And, no, current mpl does not support that.
If you're only interested in the saved ouput, you may use
"bbox_inches" option of "savefig". It does not change the size of the
figure currently displayed, but it does change the size of the figure
that is to be saved. Unfortunately, the released version of mpl will
not work. With svn version, you can do
l = legend(bbox_to_anchor=(1.05, 1), loc=2, borderaxespad=0.)
savefig("a.eps", bbox_inches="tight", bbox_extra_artists=[l.legendPatch])
Regards,
-JJ

I should have installed numpy first, and got some errors installing 
MPL. I don't see an uninstall in Control Panel Add/Rmv.
-- 
My life in two words. "Interrupted Projects." -- WTW (quote originator)

Hello,
please try this.
from matplotlib.pyplot import *
plot([1,2,3], label="very loooooooong label")
plot([3,2,1], label="very loooooooong label2")
legend(bbox_to_anchor=(1.05, 1), loc=2, borderaxespad=0.)
show()
The code puts a legend with very long label text outside the figure.
When drawing only the beginning of the legend is visible.
Is there a way to automatically correct the area of figure and resize it
such that every box drawn is visible?
I know I can overcome this issue by using subplots. But this would only
work to a certain extend of the problem.
Regards
Eymen

Once you have an axes object, you can call set_xlim() and set_ylim() on 
it to change the limits of the x- and y- axes respectively. You should 
be able to call that and savefig() iteratively to produce plots of 
different subsets of the same data.
Let me know if you need more details,
Mike
On 02/05/2010 01:08 AM, David Carmean wrote:
> Hi,
>
> I just emigrated from Ploticus last week :) Am working on a project where
> I'm plotting the contents of a large .csv file with about 250,000 cells
> (unix system 5-minute load averages from a set of 50 servers, for about
> three weeks data now).
>
> I'm developing this in Spyder/Python(x,y)--completely unknown to me until
> last week--and the pan/zoom capability makes me wish/wonder two things:
>
> 1: I wish I could interactively save the zoomed view to disk, and
>
> 2: This behavior hints at the possiblity of a better way to go back
> and plot 15 1-day views of the original plot, than slicing up the
> source array and re-plotting.
>
>
> I'm .. so new to matplotlib/numpy that I'm sure I'm missing some
> key concepts/terminology that, once identified, will let me find my
> way to what I need to know. For example, I'm terribly confused right
> now by Axes.get_axes().
>
> Which classes/methods/examples/gallery examples should I look at?
>
> Thanks.
>
>
>
> ------------------------------------------------------------------------------
> The Planet: dedicated and managed hosting, cloud storage, colocation
> Stay online with enterprise data centers and the best network in the business
> Choose flexible plans and management services without long-term contracts
> Personal 24x7 support from experience hosting pros just a phone call away.
> http://p.sf.net/sfu/theplanet-com
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 

On 2/5/2010 12:51 AM, Wayne Watson wrote:
> what I'm looking for is a way to draw a zig-zag path
> indicating a path taken by a particle
Here is a 2d example:
 >>> import numpy as np
 >>> import matplotlib.pyplot as plt
 >>> locs = np.random.random_sample((2,30))
 >>> locs = np.random.random_sample((2,30)) - 0.5
 >>> locs = np.cumsum(locs, axis=-1)
 >>> x,y = locs
 >>> plt.plot(x,y)
hth,
Alan Isaac

Wayne Watson wrote:
> Simply explained what I'm looking for is a way to draw a zig-zag path 
> indicating a path taken by a particle. Maybe this is best done with some 
> tools outside of the normal plot capabilities?
Why doesn't plot handle this? What do you see as missing?
> 
> On 2/4/2010 9:02 PM, Wayne Watson wrote:
>> Is there a difference between the two (Subject). Perhaps plot connects
>> lines in the order of x? However, scatter does not connect any points?
>> 
Yes, plot connects points in the order in which they appear in the input 
sequence; scatter does not connect, and has additional capabilities for 
varying the symbol, size, and color.
Eric
> 

Hi,
I just emigrated from Ploticus last week :) Am working on a project where 
I'm plotting the contents of a large .csv file with about 250,000 cells
(unix system 5-minute load averages from a set of 50 servers, for about 
three weeks data now). 
I'm developing this in Spyder/Python(x,y)--completely unknown to me until 
last week--and the pan/zoom capability makes me wish/wonder two things:
1: I wish I could interactively save the zoomed view to disk, and
2: This behavior hints at the possiblity of a better way to go back 
and plot 15 1-day views of the original plot, than slicing up the 
source array and re-plotting.
I'm .. so new to matplotlib/numpy that I'm sure I'm missing some 
key concepts/terminology that, once identified, will let me find my 
way to what I need to know. For example, I'm terribly confused right 
now by Axes.get_axes().
Which classes/methods/examples/gallery examples should I look at?
Thanks.

Simply explained what I'm looking for is a way to draw a zig-zag path 
indicating a path taken by a particle. Maybe this is best done with some 
tools outside of the normal plot capabilities?
On 2/4/2010 9:02 PM, Wayne Watson wrote:
> Is there a difference between the two (Subject). Perhaps plot connects
> lines in the order of x? However, scatter does not connect any points?
> 
-- 
My life in two words. "Interrupted Projects." -- WTW (quote originator)

Is there a difference between the two (Subject). Perhaps plot connects 
lines in the order of x? However, scatter does not connect any points?
-- 
My life in two words. "Interrupted Projects." -- WTW (quote originator)