matplotlib-users Mailing List for matplotlib

On Wednesday 16 May 2007 01:29:56 pm Alexander Schmolck wrote:
> Darren Dale <dd...@co...> writes:
> > On Monday 14 May 2007 1:29:05 pm Alexander Schmolck wrote:
> >> Darren Dale <dd...@co...> writes:
> >> I'd *really* like the ability to ``usepackage`` for various reasons and
> >> it would clearly add useful functionality that is not otherwise
> >> obtainable.
> >>
> >> I understand concern about an additional support burden, but couldn't
> >> this be handled by explicitly noting that it's unsupported, possibly
> >> even printing out an unsubtle warning
>
> [...]
>
> > As far as I'm concerned, being unsupported disqualifies the feature from
> > being included in mpl.
>
> Well, if ever there was a compelling use-case for an
> undocumented/unsupported feature it would be this one, I think.
>
> We are talking about something that involves very little implementation
> effort (< 5 LOC or so), right? So provided it doesn't result in either an
> implementation burden or in additional support requests, why wouldn't you
> allow people to obtain functionality, at their own risk, that may be of
> high utility to them?
>
> For example, I use a few lower-case bold greek symbols in my work, and I
> also want to use them in my plots. Due to some arbitrary braindamage in
> latex, this essentially requires a ``\usepackage{bm}`` somewhere in your
> preamble, and there are other fairly standard things are as far as I can
> see impossible to obtain without (if it doesn't cause portability hassles
> of the type you mentioned etc., I think it might actually be worth-while
> considering to add things like 'bm' and 'ammssymb' to the
> default-preamble).
>
> I don't think me and other users editing texmanager by hand or resulting to
> some really nasty hacks in order to just extend simple template string
> being a better solution (or one that necessarily results in fewer support
> requests -- "oops, sorry I just noticed I actually screwed around with this
> file in order to change my latex-preamble").
>
> It wouldn't even be necessary to add some proper latex_preamble option, as
> long as there is some TexManager attribute that's easily enough to modify.

I'll give this some more thought.

Thanks a lot anyway! So I will have a look a Custom solution...

Darren Dale <dd...@co...> writes:

> On Monday 14 May 2007 1:29:05 pm Alexander Schmolck wrote:
>> Darren Dale <dd...@co...> writes:
>> I'd *really* like the ability to ``usepackage`` for various reasons and it
>> would clearly add useful functionality that is not otherwise obtainable.
>>
>> I understand concern about an additional support burden, but couldn't this
>> be handled by explicitly noting that it's unsupported, possibly even
>> printing out an unsubtle warning
[...]
> As far as I'm concerned, being unsupported disqualifies the feature from being 
> included in mpl.

Well, if ever there was a compelling use-case for an undocumented/unsupported
feature it would be this one, I think.

We are talking about something that involves very little implementation effort
(< 5 LOC or so), right? So provided it doesn't result in either an
implementation burden or in additional support requests, why wouldn't you
allow people to obtain functionality, at their own risk, that may be of high
utility to them?

For example, I use a few lower-case bold greek symbols in my work, and I also
want to use them in my plots. Due to some arbitrary braindamage in latex, this
essentially requires a ``\usepackage{bm}`` somewhere in your preamble, and
there are other fairly standard things are as far as I can see impossible to
obtain without (if it doesn't cause portability hassles of the type you
mentioned etc., I think it might actually be worth-while considering to add
things like 'bm' and 'ammssymb' to the default-preamble).

I don't think me and other users editing texmanager by hand or resulting to
some really nasty hacks in order to just extend simple template string being a
better solution (or one that necessarily results in fewer support requests --
"oops, sorry I just noticed I actually screwed around with this file in order
to change my latex-preamble").

It wouldn't even be necessary to add some proper latex_preamble option, as
long as there is some TexManager attribute that's easily enough to modify.

cheers,

'as

Hi,

On 5/16/07, Thorsten Kranz <tho...@go...> wrote:
> Hi, I have a question about the command "imshow". Is there a way to have
> such a colorplot only limited to a circular area?
>
> I want to have it look like the colorplots in
>
> http://www.uke.uni-hamburg.de/kliniken/neurologie/downloads/klinik-neurologie/Hummel_Figure7.jpg

I have used the same sort of plots for the polar regions, where you
sometimes want to concentrate on one single annulus. One thing you can
do is to have a mask, with the same size as your matrix. You calcualte
r_ij = sqrt(xi*xi + yj*yj), set a threshold U and let the mask be
equal to 1 if r<=U, or else 0. When you apply the mask, the area
outside your radius of interest will be masked out.

I know, I know... long winded :)

Cheers,
Jose

On 5/16/07, Thorsten Kranz <tho...@go...> wrote:
> Hi, I have a question about the command "imshow". Is there a way to have
> such a colorplot only limited to a circular area?
>
> I want to have it look like the colorplots in
>
> http://www.uke.uni-hamburg.de/kliniken/neurologie/downloads/klinik-neurologie/Hummel_Figure7.jpg
>
>
> Nice is also something like
> http://www.sol.lu.se/humlab/research/img/erp02.jpg
>
> Can it be done with matplotlib?


Not quite.  I recently added support for clipping to polygons in *Agg,
but I haven't ported this to all the mpl Artists yet.  In particular,
I haven't done it for images.  You might be able to do it yourself if
you wanted to explicitly set the alpha channel, so that alpha outside
the circle was 0.

JDH

It looks like I've successfully built the latest MPL svn (rev 3273) with
the latest WxPython 2.8.4.0 in Python 2.5.1 on win32 using MSVC 7.1.
Lots of (what I take it aren't important) type conversion warnings
came up, but this warning stood out:

building 'matplotlib._windowing' extension
C:\bin\Microsoft Visual Studio .NET 2003\Vc7\bin\cl.exe /c /nologo /Ox 
/MD /W3 /GX /DNDEBUG -IC:/include -IC:\bin\Python25\include 
-IC:\bin\Python25\PC /Tpsrc/_windowing.cpp 
/Fobuild\temp.win32-2.5\Release\src/_windowing.obj
_windowing.cpp
C:\bin\Microsoft Visual Studio .NET 2003\Vc7\bin\link.exe /DLL /nologo 
/INCREMENTAL:NO /LIBPATH:C:/lib /LIBPATH:C:\bin\Python25\libs 
/LIBPATH:C:\bin\Python25\PCBuild user32.lib /EXPORT:init_windowing 
build\temp.win32-2.5 \Release\src/_windowing.obj 
/OUT:lib\matplotlib\_windowing.pyd 
/IMPLIB:build\temp.win32-2.5\Release\src\_windowing.lib -mwindows
LINK : warning LNK4044: unrecognized option '/mwindows'; ignored
    Creating library build\temp.win32-2.5\Release\src\_windowing.lib and 
object build\temp.win32-2.5\Release\src\_windowing.exp

Is this important? MPL seems to work fine. I compiled using:

python setup.py build_ext --inplace --force

I've got the win32_static folder in my MPL root, extracted from
http://matplotlib.sourceforge.net/win32_static_vs.tar.gz, and I've
overwritten all the wxPython lib and header files there with those in
the latest wxPython2.8-win32-devel-2.8.4.0.tar.bz2

Cheers,

Martin

Hi everybody,

while thinking about the problem of disabling mpl-axes-interaction during 
key_press_events two ideas came to my mind:

One could add a <newproperty> (e.g. 'skip_mpl_events') to class Artist or 
class Axes(Artist). 

a) In the method key_press (of class FigureManagerBase) one could then use 
this attribute like:
 if event.inaxes.<newproperty> == True:
     return
to skip all built-in events like 'l' (activate log-scale), 'g' (activate 
grid), 'f' (toggle fullscreen mode) ... .

b) One could also use this <newproperty> in the axes methods
grid and toggle_log_lineary to skip the events.

Is this a suitable way of disabling the mpl-axes-interaction?

best regards,
Matthias

On Friday 27 April 2007 17:42, Matthias Michler wrote:
> Hi everybody,
>
> I use key_press_event's to handle my program.
> Therefore I want to skip the matplotlib usage of some keys e.g. 'f', 'g'
> and 'l'.
>
> I didn't find the right method to turn the usage off. Can anybody help me?
>
> Could this method be useful for buttons and sliders from widgets.py, too?
> Because one don't want to scale or set grid upon these widgets, isn't it?
>
> best regards and thanks in advance for any hints,
> Matthias

Hi, I have a question about the command "imshow". Is there a way to have
such a colorplot only limited to a circular area?

I want to have it look like the colorplots in

http://www.uke.uni-hamburg.de/kliniken/neurologie/downloads/klinik-neurologie/Hummel_Figure7.jpg


Nice is also something like
http://www.sol.lu.se/humlab/research/img/erp02.jpg

Can it be done with matplotlib?

So you might have noticed that I'm in neuroscience. Do you know any helpful
packages for this field?

Greets,
Thorsten