matplotlib-users Mailing List for matplotlib (Page 10)

import matplotlib.ticker as tick
def showOnlySomeTicks(x, pos):
 s = str(int(x))
 if x == 5000:
 return '5e3'#'%.0e' % x
 return ''
ax = plt.axes([0.165,0.2,0.95-0.24,0.95-0.2])
ax.xaxis.set_minor_formatter(tick.FuncFormatter(showOnlySomeTicks))
Then in the code something just change xaxis to yaxis or vice versa. Can 
also set the major formatter like this. Not sure if this is what you 
were looking for but it seems you want custom tick labels. Can also set 
the location of the ticks and check ticker page below for more info.
For setting a different base check the multiplelocater from the ticker 
class here:
http://matplotlib.sourceforge.net/api/ticker_api.html
On 09/07/2011 08:03 PM, shaunh1 wrote:
> Hi,
>
> As the subject shows, I am trying to create a custom ticker (class??) that
> has pretty formatted log tick.
>
> Instead of just 10^-5, 10^-5, etc, is something more like
> [1-10^-2, 1-10^-3, 1-10^-4] etc
>
> I am histogram'n a set of data that is very close to 1, basically ranging
> from 0.990 and 0.9922, but mostly being centered on 0.9921. I would love to
> see meaningful labels.
>
> Any ideas?

Is there a way to reduce the lineweight of the axes frame edge?
Alternatively, is there a way to hide the edge of the frame without turning
the frame off?
Thanks,
Adam

On 9/8/11 1:51 AM, Jakob Malm wrote:
> Picking up on an old thread. Hopefully Jeff is still listening in...
>
> On 2010年04月04日 23:24, Jeff Whitaker wrote:
>> On 4/4/10 11:06 AM, Will Hewson wrote:
>>> Hi again Jeff et al...
>>>
>>> I've had a play around with the extra few lines of code - on paper this
>>> seems like it should solve the problems I'm experiencing. However, an
>>> error's being thrown up by the transform scalar function, as my lons and
>>> lats won't necessarily be increasing. The data I'm plotting is satellite
>>> data and so at the beginning and end of the orbit file lats go over the pole
>>> from 90 to -90, with a similar problem for the lons - whereby the data is
>>> taken across the satellite track. I've thought about sorting the data before
>>> passing it to transform_scalar but I'm always going to be left with the
>>> problem in either lats or lons.
>>>
>>> I've uploaded the file I'm currently working with this time. It's three
>>> columns of lons, lats and z values.
>>>
>>> Once again, many thanks for your help.
>>>
>>> Will.
>>>
>>> http://old.nabble.com/file/p28133659/test.plt test.plt
>>>
>> Will: Is it a regular lat/lon grid or a satellite swath? If it's the
>> latter, you can't use my solution.
>>
>> -Jeff
> What if it _is_ a satellite swath? Can I get around the problem of
> off-projection plotting with Basemap.pcolormesh()?
> Example code and plots can be found at
> http://pythonbits.blogspot.com/2011/09/i-have-problem-with-basemap-plotting.html
>
> Thanks,
> Jakob Malm
>
Jakob: I think that's the price you pay for the speed of pcolormesh (vs 
pcolor). It appears to make more assumptions about the structure of 
your data. I don't see any way around it.
-Jeff

Hi,
sorry that it has taken me so long to reply. Anyway, i could be wrong,
but i don't think that the code:
 xi = np.linspace(llcrnlon,urcrnlon,1000)
 yi = np.linspace(llcrnlat,urcrnlat,1000)
will produce a grid which gives the lat/lon coordinates with 1km
spacing. The reason being is that the distance between 2 lons (say
-117.731659 and -91.303642) is different depending on where you are in
terms of the latitude (i.e. the extreme examples are of course the north
pole vs the equator). So the above gives a regular grid in terms of
degrees but not in terms of distance.
Anyway, but the example was still helpful in terms of getting me started
with the griddata issue. In my experience the mlab.griddate fcn did not
work as well as the scipy.griddata (but that could be a user error as
well ... ). Not sure why though. It might be the size of my source data
and the destination grid. I had to upgrade to the 64-bit python to be
able to access enough memory.
thanks
matt
On 9/6/2011 12:36 PM, Aman Thakral wrote:
> Hi Matt,
>
> Something like this?:
>
> def create_map(ax, llcrnrlon,llcrnrlat,urcrnrlon,urcrnrlat):
> m =
> Basemap(llcrnrlon=llcrnrlon,llcrnrlat=llcrnrlat,urcrnrlon=urcrnrlon,urcrnrlat=urcrnrlat,resolution='i',projection='cyl',lon_0=(urcrnrlon+llcrnrlon)/2,lat_0=(urcrnrlat+llcrnrlat)/2)
> m.drawcoastlines()
> m.drawmapboundary()
> m.drawstates(linewidth=3)
> m.fillcontinents(color='lightgrey',lake_color='white')
> m.drawcountries(linewidth=3)
> return m
>
>
> def plotMapData(ax,data):
>
> lats = []
> lons = []
> val = []
> 
> for k,v in data.iteritems():
> lats.append(float(k[0]))
> lons.append(float(k[1]))
> val.append(float(v))
> 
> value = np.array(val)
> lat = np.array(lats)
> lon = np.array(lons)
> 
> llcrnlon = lon.min()-0.5
> llcrnlat = lat.min()-0.5
> urcrnlon = lon.max()+0.5
> urcrnlat = lat.max()+0.5
>
> xi = np.linspace(llcrnlon,urcrnlon,1000)
> yi = np.linspace(llcrnlat,urcrnlat,1000)
> zi = griddata(lon,lat,value,xi,yi)
>
> cmap = cm.jet
> m = create_map(ax,llcrnlon,llcrnlat,urcrnlon,urcrnlat)
> cs = ax.contour(xi,yi,zi,15,linewidth=0.5,cmap=cmap,alpha=0.5) 
> ax.contourf(xi,yi,zi,15,cmap=cmap,zorder=1000,alpha=0.5)
>
> colorscale = cm.ScalarMappable()
> colorscale.set_array(value)
> colorscale.set_cmap(cmap)
>
> colors = colorscale.to_rgba(value)
> ax.scatter(lon,lat,c=colors,zorder=1000,cmap=cmap,s=10)
> colorbar(colorscale, shrink=0.50, ax=ax,extend='both')
> 
>
> On Tue, Sep 6, 2011 at 1:28 PM, Matt Funk <mat...@gm...
> <mailto:mat...@gm...>> wrote:
>
> Hi,
> i want to interpolate irregular spaced satellite data onto a regular
> spaced grid. The regular spaced grid should have cell sizes of
> 1km^2. Is
> it possible to use basemap to create such a grid. It looked like it
> includes some facilities like that, but i am not sure if they are
> meant
> to be used by end user or more like internal fcns (the makegrid
> fcn for
> example).
>
> Any advice would be appreciated.
>
> thanks
> matt
>
> ------------------------------------------------------------------------------
> Special Offer -- Download ArcSight Logger for FREE!
> Finally, a world-class log management solution at an even better
> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
> download Logger. Secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsisghtdev2dev
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> <mailto:Mat...@li...>
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>
-- 
Matt Funk
Research Associate
Plant and Environmental Scienc. Dept.
New Mexico State University

On Thu, Sep 8, 2011 at 7:11 AM, xyz <mi...@op...> wrote:
> Hello,
> I have found
>
> http://matplotlib.sourceforge.net/plot_directive/mpl_examples/pylab_examples/histogram_demo_extended_05.hires.png
>
> http://matplotlib.sourceforge.net/plot_directive/mpl_examples/pylab_examples/histogram_demo_extended.py
>
> How is it possible to the following draw stacked bar charts with number
> in the chart:
> http://www.jpowered.com/php-scripts/stacked-bar-chart.htm
> http://gnuplot.sourceforge.net/demo_4.2/showcase_plot.png
>
> Thank you in advance.
>
>
The histogram() function is merely a convenience function that performs both
the histogramming calculation and calls bar() under the hood. Bar charts
are capable of being stacked using the "bottom" kwarg:
http://matplotlib.sourceforge.net/examples/pylab_examples/bar_stacked.html
As for numbers with the bars:
http://matplotlib.sourceforge.net/examples/pylab_examples/barchart_demo.html
http://matplotlib.sourceforge.net/examples/pylab_examples/barchart_demo2.html
I hope this helps!
Ben Root

On Thu, Sep 8, 2011 at 10:30 AM, Yves Revaz <yve...@ep...> wrote:
> Dear List,
>
> when I'm saving a plot with the option facecolor='k',
> around my image, there is still a one pixel white border.
>
> How is it possible to remove this ?
>
> try for example this very simple script:
> (using )
>
> import pylab as pt
> from numpy import *
>
> x = arange(0,10)
> y = x**2
> pt.plot(x,y)
>
> pt.savefig('qq.png',facecolor='k')
>
>
> Thanks in advance.
>
> yves
>
>
yves,
This might depend on the version of matplotlib and which backend you are
using. I currently do not see this white line on my development build of
mpl using the GTKAgg backend. What are you using?
Ben Root

Dear List,
when I'm saving a plot with the option facecolor='k',
around my image, there is still a one pixel white border.
How is it possible to remove this ?
try for example this very simple script:
(using )
import pylab as pt
from numpy import *
x = arange(0,10)
y = x**2
pt.plot(x,y)
pt.savefig('qq.png',facecolor='k')
Thanks in advance.
yves
-- 
 (o o)
--------------------------------------------oOO--(_)--OOo-------
 Dr. Yves Revaz
 Laboratory of Astrophysics
 Ecole Polytechnique Fédérale de Lausanne (EPFL)
 Observatoire de Sauverny Tel : ++ 41 22 379 24 28
 51. Ch. des Maillettes Fax : ++ 41 22 379 22 05
 1290 Sauverny e-mail : Yve...@ep...
 SWITZERLAND Web : http://www.lunix.ch/revaz/
----------------------------------------------------------------

Dear List,
how is it possible to change the color of the ticks of a colorbar,
created using :
cb = mpl.colorbar.ColorbarBase(ax, 
cmap=cmap,norm=norm,orientation='horizontal',format=formatter)
Thanks in advance !
yves
-- 
 (o o)
--------------------------------------------oOO--(_)--OOo-------
 Dr. Yves Revaz
 Laboratory of Astrophysics
 Ecole Polytechnique Fédérale de Lausanne (EPFL)
 Observatoire de Sauverny Tel : ++ 41 22 379 24 28
 51. Ch. des Maillettes Fax : ++ 41 22 379 22 05
 1290 Sauverny e-mail : Yve...@ep...
 SWITZERLAND Web : http://www.lunix.ch/revaz/
----------------------------------------------------------------

Hello,
I have found
http://matplotlib.sourceforge.net/plot_directive/mpl_examples/pylab_examples/histogram_demo_extended_05.hires.png
http://matplotlib.sourceforge.net/plot_directive/mpl_examples/pylab_examples/histogram_demo_extended.py
How is it possible to the following draw stacked bar charts with number 
in the chart:
http://www.jpowered.com/php-scripts/stacked-bar-chart.htm
http://gnuplot.sourceforge.net/demo_4.2/showcase_plot.png
Thank you in advance.

Picking up on an old thread. Hopefully Jeff is still listening in...
On 2010年04月04日 23:24, Jeff Whitaker wrote:
> On 4/4/10 11:06 AM, Will Hewson wrote:
>> Hi again Jeff et al...
>>
>> I've had a play around with the extra few lines of code - on paper this
>> seems like it should solve the problems I'm experiencing. However, an
>> error's being thrown up by the transform scalar function, as my lons and
>> lats won't necessarily be increasing. The data I'm plotting is satellite
>> data and so at the beginning and end of the orbit file lats go over the pole
>> from 90 to -90, with a similar problem for the lons - whereby the data is
>> taken across the satellite track. I've thought about sorting the data before
>> passing it to transform_scalar but I'm always going to be left with the
>> problem in either lats or lons.
>>
>> I've uploaded the file I'm currently working with this time. It's three
>> columns of lons, lats and z values.
>>
>> Once again, many thanks for your help.
>>
>> Will.
>>
>> http://old.nabble.com/file/p28133659/test.plt test.plt
>>
>
> Will: Is it a regular lat/lon grid or a satellite swath? If it's the
> latter, you can't use my solution.
>
> -Jeff
What if it _is_ a satellite swath? Can I get around the problem of
off-projection plotting with Basemap.pcolormesh()?
Example code and plots can be found at
http://pythonbits.blogspot.com/2011/09/i-have-problem-with-basemap-plotting.html
Thanks,
Jakob Malm

On Wed, Sep 7, 2011 at 12:09 AM, Jeffrey Spencer <jef...@gm...> wrote:
> Can I specify horizontal or vertical clipping?? Or what is the best way to
> get around this?
my understanding is that the clipping is done with a "closed" path. so
I don't think one can do such thing as horizontal clipping, etc. I
guess one way is to simply increase the size of the clipping box
toward the direction you want. Here is a simple example,
Regards,
-JJ
x = np.arange(0, 8, 0.01)
y = np.sin(x)
ax = subplot(111)
l1, = plot(x, y, lw=4)
import matplotlib.transforms as mtransforms
bbox_ = mtransforms.Bbox.from_bounds(0, 0, 1., 1 + 0.1) # increase the height
bbox = mtransforms.TransformedBbox(bbox_, ax.transAxes)
l1.set_clip_box(bbox)

On Wed, Sep 7, 2011 at 3:13 PM, Matthew Koichi Grimes <mk...@cs...>wrote:
> Thanks Ben, I for one would be very interested in any workarounds you might
> find that don't require an upgrade from 1.0.1.
>
> -- Matt
>
>
Ok, looks like the hiding of the 3d axes was a feature added after the v1.0
release (but before I started working on mplot3d). This patch should enable
the basic feature without interfering with existing functions. To hide the
axes, you would have to set the private member "_axis3don" to False, like
so:
ax = plt.gca(projection='3d')
ax._axis3don = False
If you do it this way, then you will get what you want now, and your code
will still be compatible with mplot3d when you upgrade (although the
preferred method would be to call set_axis_on() or set_axis_off()).
I hope that helps!
Ben Root

Thanks Ben, I for one would be very interested in any workarounds you might
find that don't require an upgrade from 1.0.1.
-- Matt
On Wed, Sep 7, 2011 at 4:04 PM, Benjamin Root <ben...@ou...> wrote:
> On Wed, Sep 7, 2011 at 2:43 PM, Joe Kington <jki...@wi...> wrote:
>
>> Interestingly, things work perfectly with the latest build from guithub.
>> Presumably the bug was fixed already?
>>
>>
> Uhm, sure! I totally intended for that nasty bug to be fixed for the
> upcoming release... <_<
>
> Seriously, though, I made many changes to mplot3d as a part of my
> refactoring efforts. I would not be surprised if things magically break or
> get fixed because of it. I am glad you can confirm that the latest build
> works. I will take a peek at the v1.0.1 branch and see if there is an
> obvious fix for them.
>
> Ben Root
>
>

On Wed, Sep 7, 2011 at 2:43 PM, Joe Kington <jki...@wi...> wrote:
> Interestingly, things work perfectly with the latest build from guithub.
> Presumably the bug was fixed already?
>
>
Uhm, sure! I totally intended for that nasty bug to be fixed for the
upcoming release... <_<
Seriously, though, I made many changes to mplot3d as a part of my
refactoring efforts. I would not be surprised if things magically break or
get fixed because of it. I am glad you can confirm that the latest build
works. I will take a peek at the v1.0.1 branch and see if there is an
obvious fix for them.
Ben Root

Interestingly, things work perfectly with the latest build from guithub.
Presumably the bug was fixed already?
On Wed, Sep 7, 2011 at 2:40 PM, Matthew Koichi Grimes <mk...@cs...>wrote:
> I tried Joe's code, with the call to ax.set_axis_off() moved to right after
> add_subplot(), as Ben suggested. The axes are still not disappearing, nor do
> they disappear when I interact with it (by rotating the plot).
>
> -- Matt
>
>
> On Wed, Sep 7, 2011 at 3:21 PM, Benjamin Root <ben...@ou...> wrote:
>
>> On Wed, Sep 7, 2011 at 2:14 PM, Joe Kington <jki...@wi...> wrote:
>>
>>> This no longer seems to work with matplotlib 1.0.1.
>>>
>>> As a quick example:
>>>
>>> import numpy as np
>>> import matplotlib.pyplot as plt
>>> from mpl_toolkits.mplot3d import Axes3D
>>>
>>> fig = plt.figure()
>>> ax = fig.add_subplot(111, projection='3d')
>>>
>>> x,y,z,c = np.random.random((4,10))
>>> ax.scatter(x, y, z, c=c)
>>> ax.set_axis_off()
>>>
>>> plt.show()
>>>
>>> The attached .png shows the result on my system... Is this a bug, or am I
>>> doing something strange?
>>>
>>> Thanks!
>>> -Joe
>>>
>>>
>> Hmmm, try putting that call right after the add_subplot() call. I don't
>> have time to test it out right now, but I wonder if the axes are being drawn
>> once prior to the call to set_axis_off(). I would also be interested to
>> know if the axes disappear when you interact with it.
>>
>> Ben Root
>>
>>
>

I tried Joe's code, with the call to ax.set_axis_off() moved to right after
add_subplot(), as Ben suggested. The axes are still not disappearing, nor do
they disappear when I interact with it (by rotating the plot).
-- Matt
On Wed, Sep 7, 2011 at 3:21 PM, Benjamin Root <ben...@ou...> wrote:
> On Wed, Sep 7, 2011 at 2:14 PM, Joe Kington <jki...@wi...> wrote:
>
>> This no longer seems to work with matplotlib 1.0.1.
>>
>> As a quick example:
>>
>> import numpy as np
>> import matplotlib.pyplot as plt
>> from mpl_toolkits.mplot3d import Axes3D
>>
>> fig = plt.figure()
>> ax = fig.add_subplot(111, projection='3d')
>>
>> x,y,z,c = np.random.random((4,10))
>> ax.scatter(x, y, z, c=c)
>> ax.set_axis_off()
>>
>> plt.show()
>>
>> The attached .png shows the result on my system... Is this a bug, or am I
>> doing something strange?
>>
>> Thanks!
>> -Joe
>>
>>
> Hmmm, try putting that call right after the add_subplot() call. I don't
> have time to test it out right now, but I wonder if the axes are being drawn
> once prior to the call to set_axis_off(). I would also be interested to
> know if the axes disappear when you interact with it.
>
> Ben Root
>
>

I see the same thing here (from within ipython -pylab), and moving the 
ax.set_axis_off() immediately after the add_subplot call doesn't 
change anything. Interacting with the plot doesn't change anything 
either.
Ethan
On Sep 7, 2011, at 1:21 PM, Benjamin Root wrote:
> On Wed, Sep 7, 2011 at 2:14 PM, Joe Kington <jki...@wi...> wrote:
> This no longer seems to work with matplotlib 1.0.1.
>
> As a quick example:
>
> import numpy as np
> import matplotlib.pyplot as plt
> from mpl_toolkits.mplot3d import Axes3D
>
> fig = plt.figure()
> ax = fig.add_subplot(111, projection='3d')
>
> x,y,z,c = np.random.random((4,10))
> ax.scatter(x, y, z, c=c)
> ax.set_axis_off()
>
> plt.show()
>
> The attached .png shows the result on my system... Is this a bug, or 
> am I doing something strange?
>
> Thanks!
> -Joe
>
>
> Hmmm, try putting that call right after the add_subplot() call. I 
> don't have time to test it out right now, but I wonder if the axes 
> are being drawn once prior to the call to set_axis_off(). I would 
> also be interested to know if the axes disappear when you interact 
> with it.
>
> Ben Root
>
> ------------------------------------------------------------------------------
> Using storage to extend the benefits of virtualization and iSCSI
> Virtualization increases hardware utilization and delivers a new 
> level of
> agility. Learn what those decisions are and how to modernize your 
> storage
> and backup environments for virtualization.
> http://www.accelacomm.com/jaw/sfnl/114/51434361/_______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

On Wed, Sep 7, 2011 at 2:14 PM, Joe Kington <jki...@wi...> wrote:
> This no longer seems to work with matplotlib 1.0.1.
>
> As a quick example:
>
> import numpy as np
> import matplotlib.pyplot as plt
> from mpl_toolkits.mplot3d import Axes3D
>
> fig = plt.figure()
> ax = fig.add_subplot(111, projection='3d')
>
> x,y,z,c = np.random.random((4,10))
> ax.scatter(x, y, z, c=c)
> ax.set_axis_off()
>
> plt.show()
>
> The attached .png shows the result on my system... Is this a bug, or am I
> doing something strange?
>
> Thanks!
> -Joe
>
>
Hmmm, try putting that call right after the add_subplot() call. I don't
have time to test it out right now, but I wonder if the axes are being drawn
once prior to the call to set_axis_off(). I would also be interested to
know if the axes disappear when you interact with it.
Ben Root

On Wed, Sep 7, 2011 at 1:34 PM, Matthew Koichi Grimes <mk...@cs...>wrote:
> How can I make a 3D plot without showing the axes?
>
> When plotting a 3d plot, Matplotlib not only draws the x, y, and z
> axes, it also draws light gray grids on the x-y, y-z, and x-z planes.
> I would like to draw a "free-floating" 3D graph, with none of these
> elements. My matplotlib.__version__ is 1.0.1.
>
> Stuff I've tried:
>
> # Doesn't work; this hides the plot, not the axes
> my_3d_axes.set_visible(False)
>
> # Doesn't do anything. Also, there's no get_zaxis() function.
> my_3d_axes.get_xaxis().set_visible(False)
> my_3d_axes.get_yaxis().set_visible(False)
>
> -- Matt
>
>
Matt,
Try "my_3d_axes.set_axis_off()". I should probably override set_visible()
to work as expected...
Ben Root

How can I make a 3D plot without showing the axes?
When plotting a 3d plot, Matplotlib not only draws the x, y, and z
axes, it also draws light gray grids on the x-y, y-z, and x-z planes.
I would like to draw a "free-floating" 3D graph, with none of these
elements. My matplotlib.__version__ is 1.0.1.
Stuff I've tried:
# Doesn't work; this hides the plot, not the axes
my_3d_axes.set_visible(False)
# Doesn't do anything. Also, there's no get_zaxis() function.
my_3d_axes.get_xaxis().set_visible(False)
my_3d_axes.get_yaxis().set_visible(False)
-- Matt

Hi,
As the subject shows, I am trying to create a custom ticker (class??) that
has pretty formatted log tick.
Instead of just 10^-5, 10^-5, etc, is something more like
[1-10^-2, 1-10^-3, 1-10^-4] etc
I am histogram'n a set of data that is very close to 1, basically ranging
from 0.990 and 0.9922, but mostly being centered on 0.9921. I would love to
see meaningful labels.
Any ideas?
-- 
View this message in context: http://old.nabble.com/1-10%5E-1-Custom-Log-Ticker-tp32414832p32414832.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Jae-Joon,
Thanks! That worked perfectly.
Brad
On Tue, Sep 6, 2011 at 6:46 PM, Jae-Joon Lee <lee...@gm...> wrote:
> In matplotlib, patches have two colors; facecolor and edgecolor.
> So, try something like this
>
> arrowprops=dict(facecolor=((0.549,0.176,0.0156)),
> edgecolor=(0.549,0.176,0.0156),
> shrink=0.02,width=1,headwidth=6,frac=0.05),
>
> Regards,
>
> -JJ
>
>
> On Wed, Sep 7, 2011 at 10:35 AM, Brad Malone <bra...@gm...>
> wrote:
> > Hi, I am trying to draw a brown arrow to a particular part of my figure
> but
> > am having some difficulty. The code I'm currently using is something
> like:
> >>
> >> annotate('notice
> >> this',xy=(119.628,-7.9158),xytext=(0.8,0.5),textcoords='axes fraction'
> >>
> >>
> ,arrowprops=dict(facecolor=((0.549,0.176,0.0156)),shrink=0.02,width=1,headwidth=
> >>
> >>
> 6,frac=0.05),fontsize=12,horizontalalignment='right',verticalalignment='top',color=((0.549,0.176,0.0156)))
> >
> > However, when I do this it only makes the HEAD of the arrow brown, while
> the
> > body of the arrow is still black. What am I missing?
> > Lastly (and unrelated to the topic) when I insert such a figure in Latex
> it
> > looks fine in my later-generated PDF. But if I increase the fontsize part
> of
> > the figure gets cut off. What's the best way to fix this? In the past I
> > would usually just toy around and mess with the BoundingBox in the *eps
> > file, but I wondered if there was a more legitimate way.
> > Thanks for the help! I appreciate it.
> > Brad
> >
> ------------------------------------------------------------------------------
> > Using storage to extend the benefits of virtualization and iSCSI
> > Virtualization increases hardware utilization and delivers a new level of
> > agility. Learn what those decisions are and how to modernize your storage
> > and backup environments for virtualization.
> > http://www.accelacomm.com/jaw/sfnl/114/51434361/
> > _______________________________________________
> > Matplotlib-users mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> >
> >
>

In matplotlib, patches have two colors; facecolor and edgecolor.
So, try something like this
 arrowprops=dict(facecolor=((0.549,0.176,0.0156)),
 edgecolor=(0.549,0.176,0.0156),
 shrink=0.02,width=1,headwidth=6,frac=0.05),
Regards,
-JJ
On Wed, Sep 7, 2011 at 10:35 AM, Brad Malone <bra...@gm...> wrote:
> Hi, I am trying to draw a brown arrow to a particular part of my figure but
> am having some difficulty. The code I'm currently using is something like:
>>
>> annotate('notice
>> this',xy=(119.628,-7.9158),xytext=(0.8,0.5),textcoords='axes fraction'
>>
>> ,arrowprops=dict(facecolor=((0.549,0.176,0.0156)),shrink=0.02,width=1,headwidth=
>>
>> 6,frac=0.05),fontsize=12,horizontalalignment='right',verticalalignment='top',color=((0.549,0.176,0.0156)))
>
> However, when I do this it only makes the HEAD of the arrow brown, while the
> body of the arrow is still black. What am I missing?
> Lastly (and unrelated to the topic) when I insert such a figure in Latex it
> looks fine in my later-generated PDF. But if I increase the fontsize part of
> the figure gets cut off. What's the best way to fix this? In the past I
> would usually just toy around and mess with the BoundingBox in the *eps
> file, but I wondered if there was a more legitimate way.
> Thanks for the help! I appreciate it.
> Brad
> ------------------------------------------------------------------------------
> Using storage to extend the benefits of virtualization and iSCSI
> Virtualization increases hardware utilization and delivers a new level of
> agility. Learn what those decisions are and how to modernize your storage
> and backup environments for virtualization.
> http://www.accelacomm.com/jaw/sfnl/114/51434361/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>

Hi, I am trying to draw a brown arrow to a particular part of my figure but
am having some difficulty. The code I'm currently using is something like:
annotate('notice
> this',xy=(119.628,-7.9158),xytext=(0.8,0.5),textcoords='axes fraction'
>
> ,arrowprops=dict(facecolor=((0.549,0.176,0.0156)),shrink=0.02,width=1,headwidth=
>
> 6,frac=0.05),fontsize=12,horizontalalignment='right',verticalalignment='top',color=((0.549,0.176,0.0156)))
However, when I do this it only makes the HEAD of the arrow brown, while the
body of the arrow is still black. What am I missing?
Lastly (and unrelated to the topic) when I insert such a figure in Latex it
looks fine in my later-generated PDF. But if I increase the fontsize part of
the figure gets cut off. What's the best way to fix this? In the past I
would usually just toy around and mess with the BoundingBox in the *eps
file, but I wondered if there was a more legitimate way.
Thanks for the help! I appreciate it.
Brad

On Wed, Sep 7, 2011 at 12:47 AM, Jeffrey Blackburne
<jbl...@al...> wrote:
> It would be nice to have. Since the patch edge seemed to be using a "round" style and I wanted "miter", my workaround was just to use a separate step plot to overlay the outline. But for more general cases (e.g., a bar plot not created from a histogram or if I wanted a "bevel" style), I'm not sure how I would do it.
>
> Thanks,
> Jeff
>
I also agree that this needs to be supported.
Meanwhile, a workaround is to use the patheffects module.
For example,
from matplotlib.patheffects import Stroke
b = bar([0, 1, 2], [1, 0.5, 2], linewidth=10, fc="none")
for p in b:
 p.set_path_effects([Stroke(joinstyle="miter")])
-JJ