On Tue, Apr 1, 2014 at 9:50 PM, Sebastian Berg
wrote:
> On Di, 2014-04-01 at 16:25 +0100, Nathaniel Smith wrote:
>> On Tue, Apr 1, 2014 at 3:57 PM, Sebastian Berg
>> wrote:
>> > If `a` has exactly one dimension more then `b`, the first case is used.
>> > Otherwise (..., M, K) is used instead. To
On Di, 2014-04-01 at 16:25 +0100, Nathaniel Smith wrote:
> On Tue, Apr 1, 2014 at 3:57 PM, Sebastian Berg
> wrote:
> > If `a` has exactly one dimension more then `b`, the first case is used.
> > Otherwise (..., M, K) is used instead. To make sure you always get the
> > expected result, it may be b
On 04/01/2014 04:25 PM, Nathaniel Smith wrote:
> On Tue, Apr 1, 2014 at 3:57 PM, Sebastian Berg
> wrote:
>> If `a` has exactly one dimension more then `b`, the first case is used.
>> Otherwise (..., M, K) is used instead. To make sure you always get the
>> expected result, it may be best to make s
On Tue, Apr 1, 2014 at 3:57 PM, Sebastian Berg
wrote:
> If `a` has exactly one dimension more then `b`, the first case is used.
> Otherwise (..., M, K) is used instead. To make sure you always get the
> expected result, it may be best to make sure that the number of
> broadcasting (...) dimensions
On Di, 2014-04-01 at 15:31 +0100, Bob Dowling wrote:
> Versions:
>
> >>> sys.version
> '3.3.2 (default, Mar 5 2014, 08:21:05) \n[GCC 4.8.2 20131212 (Red Hat
> 4.8.2-7)]'
>
> >>> numpy.__version__
> '1.8.0'
>
>
>
> Problem:
>
> I'm trying to unpick the shape requirements of numpy.linalg.solve
Versions:
>>> sys.version
'3.3.2 (default, Mar 5 2014, 08:21:05) \n[GCC 4.8.2 20131212 (Red Hat
4.8.2-7)]'
>>> numpy.__version__
'1.8.0'
Problem:
I'm trying to unpick the shape requirements of numpy.linalg.solve().
The help text says:
solve(a, b) -
a : (..., M, M) array_like
C
