On Sun, Jul 17, 2011 at 3:35 PM, Ralf Gommers
wrote:
>
> On Sun, Jul 17, 2011 at 7:15 PM, Tony Yu wrote:
>
>>
>> Am I doing something wrong here?
>>
>> You're not, it's a Sphinx bug that Pauli already has a fix for. See
> http://projects.scipy.org/numpy/ticket/1772
>
> Ralf
>
I thought I searche
More concrete feedback about Sturla's proposal: The problem I have is if you do
A = B**-1
Then, A is some 'magic' object, not a NumPy array. That means that it is very
different from Matlab's \, which restricts the context, you simply can't do
A = B \
I think
A.solve(u)
is a lot clearer in t
Something related: This autumn I expect to invest a significant amount of time
(more than four weeks full-time) in a package for lazily evaluated, polymorphic
linear algebra.
Matrix = linear operator, a type seperate from arrays -- arrays are treated as
vectors/stacked vectors
Matrices can be
On 7/14/2011 8:04 PM, Christoph Gohlke wrote:
A patch for the build issues is attached. Remove the build directory
before rebuilding.
Christoph,
I had other issues (I think in one case, a *.c file was not getting
re-built from the *.c.src file. But anyway, at the end the patch appears
to wor
In numpy.distutils.system info:
default_x11_lib_dirs = libpaths(['/usr/X11R6/lib','/usr/X11/lib',
'/usr/lib'], platform_bits)
default_x11_include_dirs = ['/usr/X11R6/include','/usr/X11/include',
'/usr/include']
These def
On Sun, Jul 17, 2011 at 05:52:19PM +0200, Ralf Gommers wrote:
>
>Looks very interesting.
>
>One thing that is surprising to me is that the quaternion dtype is
>inserted in to the numpy namespace. For dtypes that are planned to be
>integrated with numpy later on perhaps this makes
On Sat, Jul 16, 2011 at 08:16:44PM -0400, Anne Archibald wrote:
> The next interesting question is, how well does scipy.interpolate deal
> with them? For really good rotational paths I seem to recall you want
> specialized splines, but simply interpolating in the quaternion domain
> is not a bad qu
On Mon, Jul 11, 2011 at 9:31 PM, Ralf Gommers
wrote:
> Hi Christoph,
>
> On Mon, Jul 11, 2011 at 3:57 AM, Christoph Gohlke wrote:
>
>> Hello,
>>
>> building numpy 1.6.1rc2 on Windows, i7-2600K CPU, with msvc9 failed with
>> the following error:
>>
>> File "numpy/core/setup_common.py", line 271, i
On Sun, Jul 17, 2011 at 7:15 PM, Tony Yu wrote:
> I'm building documentation using Sphinx, and it seems that numpydoc is
> raising
> a lot of warnings. Specifically, the warnings look like "failed to import
> ", "toctree
> references unknown document u''", "toctree contains reference
> to nonexis
On 7/17/2011 1:57 PM, Sturla Molden wrote:
> I suggest inverting a NumPy matrix could result in an unsolved linear
> system type, instead of actually computing the matrix inverse and
> returning a new matrix.
1. Too implicit.
2. Too confusing for new users.
2a. Too confusing for students.
The problem I am thinking we might try to might fix is that programmers
with less numerical competence is unaware that the matrix expression
(X**-1) * Y
should be written as
np.linalg.solve(X,Y)
I've seen numerous times matrix expressions being typed exactly as
written in linear algeb
I'm building documentation using Sphinx, and it seems that numpydoc is
raising
a lot of warnings. Specifically, the warnings look like "failed to import
", "toctree
references unknown document u''", "toctree contains reference
to nonexisting document ''---for each method defined. The
example below
On Sat, Jul 16, 2011 at 4:50 PM, Martin Ling wrote:
> Hi all,
>
> I have just pushed a package to GitHub which adds a quaternion dtype to
> NumPy: https://github.com/martinling/numpy_quaternion
>
> Some backstory: on Wednesday I gave a talk at SciPy 2011 about an
> inertial sensing simulation pac
13 matches
Mail list logo
