On Mon, Feb 16, 2009 at 10:49 PM, wrote:
>
> I'm trying to run multiple instances of GMRES at the same time (one inside
> another actually, used inside of the preconditioner routine) but am
> running in to some problems. My guess is there is a single set of internal
> variables associated with GM
Hi all,
I'm trying to run multiple instances of GMRES at the same time (one inside
another actually, used inside of the preconditioner routine) but am
running in to some problems. My guess is there is a single set of internal
variables associated with GMRES and when I initiate a new GMRES inside a
On Tue, Feb 17, 2009 at 12:23 AM, Yepez, Esteban wrote:
> Are there any patches from previous versions?
Do you mean for python itself or numpy ? For numpy, not that I know
of. For old python, there are some patches in the tracker, but none of
it has been integrated AFAIK.
> Can provide any other
On Tue, Feb 17, 2009 at 12:17:17AM +0100, Georg Brandl wrote:
> I'm all for it. In the case of autosummary, I'm guilty of not getting it
> in sooner. This will change soon. In other cases, I don't even know of
> the extension, probably because those who write it deem it as too
> project-specific
On Mon, Feb 16, 2009 at 4:06 PM, Ken Basye wrote:
> Hi List,
> I need to compute multiple outer products from 2-d data in the
> following way:
> Given a and b with shape, e.g, (10, 4), compute the 10 outer products
> of shape (4, 4) and get them into an array of shape (10, 4, 4).
> Currently I
Hi List,
I need to compute multiple outer products from 2-d data in the
following way:
Given a and b with shape, e.g, (10, 4), compute the 10 outer products
of shape (4, 4) and get them into an array of shape (10, 4, 4).
Currently I do this with a loop, but I'd really like some way to do it
On Sun, Feb 15, 2009 at 08:04, Gael Varoquaux
wrote:
> Hi all,
>
> Sorry for the multiple posting, this concerns various groups, and I'd
> rather the information not be lost.
>
> While working on getting our in-lab library ready to be merged with NiPy,
> I ran into some sort of 'sphinx extension m
Mon, 16 Feb 2009 14:27:41 -0500, josef.pktd wrote:
> another docutils 0.5 bug in the plot_directive (align doesn't work):
>
> from docutils.parsers.rst.directives.images import Image
> align = Image.align
>
> Image.align is not callable,
[clip]
Strange, it didn't do that to me with docutils 0
another docutils 0.5 bug in the plot_directive (align doesn't work):
from docutils.parsers.rst.directives.images import Image
align = Image.align
Image.align is not callable,
see
http://svn.berlios.de/viewcvs/docutils/trunk/docutils/docutils/parsers/rst/directives/images.py?view=markup
I re
Are there any patches from previous versions? Can provide any other suggestions?
On 2/15/09 12:30 AM, "David Cournapeau" wrote:
Yepez, Esteban wrote:
> Hello,
>
> I have having a hard time finding more information to help me, so I
> thought I'd ping you both.
>
> I need to x-compile numpy for a
Hi Axel,
axel.bre...@bnpparibas.com wrote:
> Hi,
>
> Which one is better numpy.linalg or scipy.linalg ?
>
scipy.linalg is more complete, but both numpy and scipy may use the
underlying LAPACK available on your platform.
> These modules have some common functions but with different
> help line
Hi,
Which one is better numpy.linalg or scipy.linalg ?
These modules have some common functions but with different
help lines.
Furthermore, numpy.scipy.linalg.svd seems to be more stable
than numpy.linalg.svd (are they using different LAPACK methods ?)
This message and any attachments (the
Gael,
You raise a very good point about the duplication of code around. As a
case in point, the patches you provided no longer apply to the
"canonical" (or at least original) versions of the plugins that began
life in matplotlib. Recent versions of Sphinx have a proper extension
API, so that
13 matches
Mail list logo
