From: Kenneth M. <ken...@sb...> - 2004-07-30 16:57:44
|
Does any exist? I looked through the distribution and didn't see anything, but then, that doesn't prove anything :-) Thanks, Ken McDonald |
From: Peter G. <pgr...@ge...> - 2004-08-01 01:27:03
|
Hi: How many colors do images created via: imshow(Zi, cmap=cm.jet) (Zi = some data matrix) have? Are these true color? 256? Is there a simple way to define these things? Thanks. -- Peter Groszkowski Gemini Observatory Tel: +1 808 974-2509 670 N. A'ohoku Place Fax: +1 808 935-9235 Hilo, Hawai'i 96720, USA |
From: John H. <jdh...@ac...> - 2004-08-02 15:53:41
|
>>>>> "Peter" == Peter Groszkowski <pgr...@ge...> writes: Peter> Hi: How many colors do images created via: Peter> imshow(Zi, cmap=cm.jet) Peter> (Zi = some data matrix) have? Peter> Are these true color? 256? Is there a simple way to define Peter> these things? The following image parameters can be configured from your rc file ### images image.aspect : free # free | preserve image.interpolation : bilinear # see help(imshow) for options image.cmap : jet # gray | jet image.lut : 256 # the size of the colormap lookup table image.origin : upper # lower | upper The image.lut parameter controls the size of the lookup table. You can change the default in the rc file, or dynamically in a single python session using the rc function. Eg, # default cmap is now 100 level grayscale by cm.jet and cm.gray unaffected >>> rc('image', lut=100, cmap='gray') >>> imshow(X) # show X with default cmap But you can also create your own color maps at any time using the cm.get_cmap function >>> jet512 = cm.get_cmap('jet', 512) >> imshow(X, cmap=jet512) Should work. JDH |
From: Peter G. <pgr...@ge...> - 2004-08-02 23:33:46
|
> ..... > But you can also create your own color maps at any time using the > cm.get_cmap function > > >>> jet512 = cm.get_cmap('jet', 512) > >> imshow(X, cmap=jet512) > > Should work. > Yes, thanks. Just one more question. Recently (in the last couple of versions I think), there has been a change and now the 'o' line markers (circles) are filled in by default. For example: plot(xp,yp,'ok') gives sold black circles. I would like my circles to not be filled; just have the border so that the inside is transparent. Is this something that is settable? Thanks, -- Peter Groszkowski Gemini Observatory Tel: +1 808 974-2509 670 N. A'ohoku Place Fax: +1 808 935-9235 Hilo, Hawai'i 96720, USA |
From: John H. <jdh...@ac...> - 2004-08-03 13:06:28
|
>>>>> "Peter" == Peter Groszkowski <pgr...@ge...> writes: Peter> Yes, thanks. Just one more question. Recently (in the last Peter> couple of versions I think), there has been a change and Peter> now the 'o' line markers (circles) are filled in by Peter> default. For example: Peter> plot(xp,yp,'ok') Peter> gives sold black circles. Just do >>> plot(x, y, 'ok', markerfacecolor=None) This raises the question of what the default behavior of plot should be. If you say >>> plot(x, y, 'ro') should the red apply to the facecolor, edgecolor, or both? Both is the current behavior, which I think is in accord with the principal of least surprise. If it should apply to only one, say the edge color, the facecolor would fall back on lines.markerfacecolor. I could add some aliases like mfc=markerfacecolor, ec=edgecolor, lw=linewidth if people often find themselves overriding the defaults and think these are useful shortcuts. I've already added these to the rc command, and adding them to the lines/patches classed would be easy. JDH |
From: Peter G. <pgr...@ge...> - 2004-08-03 18:57:08
|
John Hunter wrote: >>>>>>"Peter" == Peter Groszkowski <pgr...@ge...> writes: >>>>>> >>>>>> > > Peter> Yes, thanks. Just one more question. Recently (in the last > Peter> couple of versions I think), there has been a change and > Peter> now the 'o' line markers (circles) are filled in by > Peter> default. For example: > > Peter> plot(xp,yp,'ok') > > Peter> gives sold black circles. > >Just do > > >>> plot(x, y, 'ok', markerfacecolor=None) > > > Aghh.. yes. Thanks. >This raises the question of what the default behavior of plot should >be. If you say > > >>> plot(x, y, 'ro') > >should the red apply to the facecolor, edgecolor, or both? > I think both is good. It seems like it's really easy to change in any case. >I could add some aliases like mfc=markerfacecolor, ec=edgecolor, >lw=linewidth if people often find themselves overriding the defaults >and think these are useful shortcuts. > Might be a good idea. On another note, interesting to see how much matplotlib has matured in the last six months. Great job John! Peter |
From: Peter G. <pgr...@ge...> - 2004-08-04 01:25:49
|
Hi John: DayMulitLocator is missing from the following line: from ticker import YearLocator, MonthLocator, WeekdayLocator, \ DayLocator, HourLocator, MinuteLocator, DateFormatter in axes.py -- Peter Groszkowski Gemini Observatory Tel: +1 808 974-2509 670 N. A'ohoku Place Fax: +1 808 935-9235 Hilo, Hawai'i 96720, USA |
From: John H. <jdh...@ac...> - 2004-08-02 16:08:33
|
>>>>> "Kenneth" == Kenneth McDonald <ken...@sb...> writes: Kenneth> Does any exist? I looked through the distribution and Kenneth> didn't see anything, but then, that doesn't prove Kenneth> anything :-) There is no official documentation, but there are a few resources * The class documentation at http://matplotlib.sourceforge.net/classdocs.html * the examples embedding_in*.py in the examples directory. * examples/pythonic_matplotlib.py describes the translation from the matlab style interface to the pythonic, OO interface * Another good resource is matlab.py. This is just a thin wrapper to the API, so you can look and see how it is done there, translating all the gcf() calls to your figure instance, all the gca() calls to your axes instance, and so on. Other than that, you can post here... I'm working on some additional documentation but it is not ready yet. JDH |