matplotlib-users Mailing List for matplotlib

I just tried this method and it does work if you are using integers or whole
numbers. However, I am working with time on my x axis. So when I zoom too
close, floating point numbers are required... Is there any way to just turn
off the exponent number in the right corner and force the x tick labels to
be integers or floating point depending on how close one is zoomed?



David Simpson-3 wrote:
> 
> I also had some trouble with exponents in an axis, getting
> 0.0 to 3.0 on the axis, with +1.998e3. I wanted the years
> 1998 to 2001 instead. I solved this using the following code
> (with the solution bits commented out):
> 
> #!/usr/bin/env python
> from pylab import *
> # from matplotlib.ticker import FormatStrFormatter
> 
> x = array([ 1998, 1999, 2000, 2001 ])
> y = array([   2.3, 4.5, 2.6, 7.2 ])
> 
> # ax=subplot(111)
> plot(x,y)
> 
> ## Needed to get 2001, not 1+2e3:
> # majorFormatter=FormatStrFormatter('%d')
> # ax.xaxis.set_major_formatter(majorFormatter)
> # show()
> 
> 
> Dave
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
> 


-----
Krishna Adrianto Pribadi
Test Engineer
Harley-Davidson Motor Co.
Talladega Test Facility
Vehicle Test Stands
-- 
View this message in context: http://old.nabble.com/Re%3A-Forcing-full-value-on-axis-%28Dave-Simpson%29-tp10175415p28260517.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

2010/4/14 Andreas Hilboll <li...@hi...>:
> So my question is: What do I need to do so that the colorbar actually  has
> the
> range as specified by my colorNorm?

We had a beautiful discussion about this recently under "Making a
data-driven colormap", maybe this helps.

Friedrich

Hi all!

I have a quick newbie question.
matplotlib's specgram() by default plots a spectrogram with a linear y-axis
(frequency).
However, for many applications, it's better to look at a log-frequency
spectrogram.

Is there an easy way to plot a spectrogram using a logarithmic frequency
axis?

Thanks for your help!

--David Ho

http://matplotlib.sourceforge.net/api/collections_api.html#matplotlib.collections.LineCollection 

Hello Matplotlib-Community,

I'm quite sure that I've seen a figure containing a multicolered graph
somewhere, maybe on stackoverflow or at scipy.org.
Unfortunately, I'm not able to find it anymore.
Anyone knows the link?
Anyone knows howto?

Thanks very much indeed,
greetings,
Martin

Hello,
I'd like to know if there's some way of copying a LineCollection or a
ContourSet (or any other Artist, actually) from one figure to another.
More precisely, I have to figures using identical axes (one being a
grayscale image and the other a thresholded version of the image) ; I have
written a script to tag parts of the thresholded image (which gives me
ContourSets), and I want to copy these to the grayscale image.
Any help would be greatly appreciated.
Thanks in advance,
Antony

Thomas Robitaille wrote:
> Hi,
> 
> Last year, I submitted a bug report regarding the fact that PatchCollection's match_original argument does not work properly, in a pretty simple script:
> 
> https://sourceforge.net/tracker/?func=detail&aid=2881485&group_id=80706&atid=560720
> 
> I came across the problem again several times recently, even with the svn version of matplotlib, and other people have also mentioned the issue to me. I just wanted to bring up this issue again, in case it can easily be fixed.
> 
> Thanks,
> 
> Thomas

My first fix was flawed; svn r8231 looks better.

Eric

Thomas Robitaille wrote:
> Hi,
> 
> Last year, I submitted a bug report regarding the fact that PatchCollection's match_original argument does not work properly, in a pretty simple script:
> 
> https://sourceforge.net/tracker/?func=detail&aid=2881485&group_id=80706&atid=560720
> 
> I came across the problem again several times recently, even with the svn version of matplotlib, and other people have also mentioned the issue to me. I just wanted to bring up this issue again, in case it can easily be fixed.
> 
> Thanks,
> 
> Thomas


Thomas,

Thanks for the reminder.  I think I have fixed the problem.

Eric

On Thu, Apr 15, 2010 at 5:16 AM, Peter Butterworth <bu...@gm...> wrote:
> matlab colors seem to follow html :
> http://www.mathworks.com/access/helpdesk/help/techdoc/ref/colorspec.html

for c, m, y
but not for green, where matplotlib does follow html ...

Hi,

Last year, I submitted a bug report regarding the fact that PatchCollection's match_original argument does not work properly, in a pretty simple script:

https://sourceforge.net/tracker/?func=detail&aid=2881485&group_id=80706&atid=560720

I came across the problem again several times recently, even with the svn version of matplotlib, and other people have also mentioned the issue to me. I just wanted to bring up this issue again, in case it can easily be fixed.

Thanks,

Thomas

matlab colors seem to follow html :
http://www.mathworks.com/access/helpdesk/help/techdoc/ref/colorspec.html
I would agree that "yellow" is not very readable at all. Could
possibly the short-hand colors be made user configurable in
.matplotlibrc to suit individual taste ?

In any case, this issue needs to be mentioned in the documentation.



On Wed, Apr 14, 2010 at 9:58 PM, Eric Firing <ef...@ha...> wrote:
> John Hunter wrote:
>>
>> On Wed, Apr 14, 2010 at 2:14 PM, Jae-Joon Lee <lee...@gm...>
>> wrote:
>>
>>> John, the relevant code to define the "colors" attribute seems to be
>>> written by you. Maybe this is some matlab convention? Can you comment
>>> on this?
>>
>> The original color letters did come from matlab, and some of the color
>> RGB choices, like the background for the subplot gray, I got using a
>> color picker on my screen for maximum compatibility, but I do not
>> recall if that was the case for 'm', 'c'  and 'y'.  Most likely these
>> were the rgb values of the matlab colors.
>>
>> The html colors were submitted later by another user, and apparently
>> we never checked for consistency.   I think this is a wart, and I
>> don't feel strongly about keeping it or changing it for consistency in
>> the trunk ahead of 1.0 (it should remain as is on the branch).  If we
>> change it on the trunk, we should change the single letter codes to
>> correspond to the html full color name standards, rather than the
>> other way around.
>
> I would be cautious about making this change. At least on my laptop screen,
> with the default white axes background, the single-letter colors show up
> better than the html versions.  It makes sense to me for the single-letter
> colors to be chosen for good visibility and contrast in actual use, not for
> consistency with the html names.  In fact, I see no good argument for
> consistency in this case.
>
> Eric
>
>
>>
>> JDH



-- 
thanks,
peter butterworth