-
Notifications
You must be signed in to change notification settings - Fork 1
/
numpysane.py
executable file
·2510 lines (1905 loc) · 89.2 KB
/
numpysane.py
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
#!/usr/bin/python
r'''more-reasonable core functionality for numpy
* SYNOPSIS
>>> import numpy as np
>>> import numpysane as nps
>>> a = np.arange(6).reshape(2,3)
>>> b = a + 100
>>> row = a[0,:] + 1000
>>> a
array([[0, 1, 2],
[3, 4, 5]])
>>> b
array([[100, 101, 102],
[103, 104, 105]])
>>> row
array([1000, 1001, 1002])
>>> nps.glue(a,b, axis=-1)
array([[ 0, 1, 2, 100, 101, 102],
[ 3, 4, 5, 103, 104, 105]])
>>> nps.glue(a,b,row, axis=-2)
array([[ 0, 1, 2],
[ 3, 4, 5],
[ 100, 101, 102],
[ 103, 104, 105],
[1000, 1001, 1002]])
>>> nps.cat(a,b)
array([[[ 0, 1, 2],
[ 3, 4, 5]],
[[100, 101, 102],
[103, 104, 105]]])
>>> @nps.broadcast_define( (('n',), ('n',)) )
... def inner_product(a, b):
... return a.dot(b)
>>> inner_product(a,b)
array([ 305, 1250])
* DESCRIPTION
Numpy is a very widely used toolkit for numerical computation in Python. Despite
its popularity, some of its core functionality is mysterious and/or incomplete.
The numpysane library seeks to fill those gaps by providing its own replacement
routines. Many of the replacement functions are direct translations from PDL
(http://pdl.perl.org), a numerical computation library for perl. The functions
provided by this module fall into three broad categories:
- Broadcasting support
- Nicer array manipulation
- Basic linear algebra
** Broadcasting
Numpy has a limited support for broadcasting
(http://docs.scipy.org/doc/numpy/user/basics.broadcasting.html), a generic way
to vectorize functions. A broadcasting-aware function knows the dimensionality
of its inputs, and any extra dimensions in the input are automatically used for
vectorization.
*** Broadcasting rules
A basic example is an inner product: a function that takes in two
identically-sized 1-dimensional arrays (input prototype (('n',), ('n',)) ) and
returns a scalar (output prototype () ). If one calls a broadcasting-aware inner
product with two arrays of shape (2,3,4) as input, it would compute 6 inner
products of length-4 each, and report the output in an array of shape (2,3).
In short:
- The most significant dimension in a numpy array is the LAST one, so the
prototype of an input argument must exactly match a given input's trailing
shape. So a prototype shape of (a,b,c) accepts an argument shape of (......,
a,b,c), with as many or as few leading dimensions as desired.
- The extra leading dimensions must be compatible across all the inputs. This
means that each leading dimension must either
- equal 1
- be missing (thus assumed to equal 1)
- equal to some positive integer >1, consistent across all arguments
- The output is collected into an array that's sized as a superset of the
above-prototype shape of each argument
More involved example: A function with input prototype ( (3,), ('n',3), ('n',),
('m',) ) given inputs of shape
(1,5, 3)
(2,1, 8,3)
( 8)
( 5, 9)
will return an output array of shape (2,5, ...), where ... is the shape of each
output slice. Note again that the prototype dictates the TRAILING shape of the
inputs.
*** What about the stock broadcasting support?
The numpy documentation dedicates a whole page explaining the broadcasting
rules, but only a small number of numpy functions provide any broadcasting
support. It's fairly inconsistent, and most functions have no broadcasting
support and no mention of it in the documentation. And as a result, this is not
a prominent part of the numpy ecosystem and there's little user awareness that
it exists.
*** What this module provides
This module contains functionality to make any arbitrary function broadcastable,
in either C or Python. In both cases, the input and output prototypes are
declared, and these are used for shape-checking and vectorization each time the
function is called.
The functions can have either
- A single output, returned as a numpy array. The output specification in the
prototype is a single shape tuple
- Multiple outputs, returned as a tuple of numpy arrays. The output
specification in the prototype is a tuple of shape tuples
*** Broadcasting in python
This is invoked as a decorator, applied to any function. An example:
>>> import numpysane as nps
>>> @nps.broadcast_define( (('n',), ('n',)) )
... def inner_product(a, b):
... return a.dot(b)
Here we have a simple inner product function to compute ONE inner product. The
'broadcast_define' decorator adds broadcasting-awareness: 'inner_product()'
expects two 1D vectors of length 'n' each (same 'n' for the two inputs),
vectorizing extra dimensions, as needed. The inputs are shape-checked, and
incompatible dimensions will trigger an exception. Example:
>>> import numpy as np
>>> a = np.arange(6).reshape(2,3)
>>> b = a + 100
>>> a
array([[0, 1, 2],
[3, 4, 5]])
>>> b
array([[100, 101, 102],
[103, 104, 105]])
>>> inner_product(a,b)
array([ 305, 1250])
Another related function in this module broadcast_generate(). It's similar to
broadcast_define(), but instead of adding broadcasting-awareness to an existing
function, it returns a generator that produces tuples from a set of arguments
according to a given prototype. Similarly, broadcast_extra_dims() is available
to report the outer shape of a potential broadcasting operation.
Stock numpy has some rudimentary support for all this with its vectorize()
function, but it assumes only scalar inputs and outputs, which severely limits
its usefulness. See the docstrings for 'broadcast_define' and
'broadcast_generate' in the INTERFACE section below for usage details.
*** Broadcasting in C
The python broadcasting is useful, but it is a python loop, so the loop itself
is computationally expensive if we have many iterations. If the function being
wrapped is available in C, we can apply broadcasting awareness in C, which makes
a much faster loop.
The "numpysane_pywrap" module generates code to wrap arbitrary C code in a
broadcasting-aware wrapper callable from python. This is an analogue of PDL::PP
(http://pdl.perl.org/PDLdocs/PP.html). This generated code is compiled and
linked into a python extension module, as usual. This functionality documented
separately: https://github.com/dkogan/numpysane/blob/master/README-pywrap.org
After I wrote this, I realized there is some support for this in stock numpy:
https://docs.scipy.org/doc/numpy-1.13.0/reference/c-api.ufunc.html
Note: I have not tried using these APIs.
** Nicer array manipulation
Numpy functions that move dimensions around and concatenate matrices are
unintuitive. For instance, a simple concatenation of a row-vector or a
column-vector to a matrix requires arcane knowledge to accomplish reliably. This
module provides new functions that can be used for these basic operations. These
new functions do have well-defined and sensible behavior, and they largely come
from the interfaces in PDL (http://pdl.perl.org). These all respect the core
rules of numpy broadcasting:
- LEADING length-1 dimensions don't affect the meaning of an array, so the
routines handle missing or extra length-1 dimensions at the front
- The inner-most dimensions of an array are the TRAILING ones, so whenever an
axis specification is used, it is strongly recommended (sometimes required) to
count the axes from the back by passing in axis<0
A high level description of the functionality is given here, and each function
is described in detail in the INTERFACE section below. In the following
examples, I use a function "arr" that returns a numpy array with given
dimensions:
>>> def arr(*shape):
... product = reduce( lambda x,y: x*y, shape)
... return numpy.arange(product).reshape(*shape)
>>> arr(1,2,3)
array([[[0, 1, 2],
[3, 4, 5]]])
>>> arr(1,2,3).shape
(1, 2, 3)
*** Concatenation
This module provides two functions to do this
**** glue
Concatenates some number of arrays along a given axis ('axis' must be given in a
kwarg). Implicit length-1 dimensions are added at the start as needed.
Dimensions other than the glueing axis must match exactly. Basic usage:
>>> row_vector = arr( 3,)
>>> col_vector = arr(5,1,)
>>> matrix = arr(5,3,)
>>> numpysane.glue(matrix, row_vector, axis = -2).shape
(6,3)
>>> numpysane.glue(matrix, col_vector, axis = -1).shape
(5,4)
**** cat
Concatenate some number of arrays along a new leading axis. Implicit length-1
dimensions are added, and the logical shapes of the inputs must match. This
function is a logical inverse of numpy array iteration: iteration splits an
array over its leading dimension, while cat joins a number of arrays via a new
leading dimension. Basic usage:
>>> numpysane.cat(arr(5,), arr(5,)).shape
(2,5)
>>> numpysane.cat(arr(5,), arr(1,1,5,)).shape
(2,1,1,5)
*** Manipulation of dimensions
Several functions are available, all being fairly direct ports of their PDL
(http://pdl.perl.org) equivalents
**** clump
Reshapes the array by grouping together 'n' dimensions, where 'n' is given in a
kwarg. If 'n' > 0, then n leading dimensions are clumped; if 'n' < 0, then -n
trailing dimensions are clumped. Basic usage:
>>> numpysane.clump( arr(2,3,4), n = -2).shape
(2, 12)
>>> numpysane.clump( arr(2,3,4), n = 2).shape
(6, 4)
**** atleast_dims
Adds length-1 dimensions at the front of an array so that all the given
dimensions are in-bounds. Any axis<0 may expand the shape. Adding new leading
dimensions (axis>=0) is never useful, since numpy broadcasts from the end, so
clump() treats axis>0 as a check only: the requested axis MUST already be
in-bounds, or an exception is thrown. This function always preserves the meaning
of all the axes in the array: axis=-1 is the same axis before and after the
call. Basic usage:
>>> numpysane.atleast_dims(arr(2,3), -1).shape
(2, 3)
>>> numpysane.atleast_dims(arr(2,3), -2).shape
(2, 3)
>>> numpysane.atleast_dims(arr(2,3), -3).shape
(1, 2, 3)
>>> numpysane.atleast_dims(arr(2,3), 0).shape
(2, 3)
>>> numpysane.atleast_dims(arr(2,3), 1).shape
(2, 3)
>>> numpysane.atleast_dims(arr(2,3), 2).shape
[exception]
**** mv
Moves a dimension from one position to another. Basic usage to move the last
dimension (-1) to the front (0)
>>> numpysane.mv(arr(2,3,4), -1, 0).shape
(4, 2, 3)
Or to move a dimension -5 (added implicitly) to the end
>>> numpysane.mv(arr(2,3,4), -5, -1).shape
(1, 2, 3, 4, 1)
**** xchg
Exchanges the positions of two dimensions. Basic usage to move the last
dimension (-1) to the front (0), and the front to the back.
>>> numpysane.xchg(arr(2,3,4), -1, 0).shape
(4, 3, 2)
Or to swap a dimension -5 (added implicitly) with dimension -2
>>> numpysane.xchg(arr(2,3,4), -5, -2).shape
(3, 1, 2, 1, 4)
**** transpose
Reverses the order of the two trailing dimensions in an array. The whole array
is seen as being an array of 2D matrices, each matrix living in the 2 most
significant dimensions, which implies this definition. Basic usage:
>>> numpysane.transpose( arr(2,3) ).shape
(3,2)
>>> numpysane.transpose( arr(5,2,3) ).shape
(5,3,2)
>>> numpysane.transpose( arr(3,) ).shape
(3,1)
Note that in the second example we had 5 matrices, and we transposed each one.
And in the last example we turned a row vector into a column vector by adding an
implicit leading length-1 dimension before transposing.
**** dummy
Adds a single length-1 dimension at the given position. Basic usage:
>>> numpysane.dummy(arr(2,3,4), -1).shape
(2, 3, 4, 1)
**** reorder
Reorders the dimensions in an array using the given order. Basic usage:
>>> numpysane.reorder( arr(2,3,4), -1, -2, -3 ).shape
(4, 3, 2)
>>> numpysane.reorder( arr(2,3,4), 0, -1, 1 ).shape
(2, 4, 3)
>>> numpysane.reorder( arr(2,3,4), -2 , -1, 0 ).shape
(3, 4, 2)
>>> numpysane.reorder( arr(2,3,4), -4 , -2, -5, -1, 0 ).shape
(1, 3, 1, 4, 2)
** Basic linear algebra
*** inner
Broadcast-aware inner product. Identical to numpysane.dot(). Basic usage to
compute 4 inner products of length 3 each:
>>> numpysane.inner(arr( 3,),
arr(4,3,)).shape
(4,)
>>> numpysane.inner(arr( 3,),
arr(4,3,))
array([5, 14, 23, 32])
*** dot
Broadcast-aware non-conjugating dot product. Identical to numpysane.inner().
*** vdot
Broadcast-aware conjugating dot product. Same as numpysane.dot(), except this
one conjugates complex input, which numpysane.dot() does not
*** outer
Broadcast-aware outer product. Basic usage to compute 4 outer products of length
3 each:
>>> numpysane.outer(arr( 3,),
arr(4,3,)).shape
array(4, 3, 3)
*** norm2
Broadcast-aware 2-norm. numpysane.norm2(x) is identical to numpysane.inner(x,x):
>>> numpysane.norm2(arr(4,3))
array([5, 50, 149, 302])
*** mag
Broadcast-aware vector magnitude. mag(x) is functionally identical to
sqrt(numpysane.norm2(x)) and sqrt(numpysane.inner(x,x))
>>> numpysane.mag(arr(4,3))
array([ 2.23606798, 7.07106781, 12.20655562, 17.3781472 ])
*** trace
Broadcast-aware matrix trace.
>>> numpysane.trace(arr(4,3,3))
array([12., 39., 66., 93.])
*** matmult
Broadcast-aware matrix multiplication. This accepts an arbitrary number of
inputs, and adds leading length-1 dimensions as needed. Multiplying a row-vector
by a matrix
>>> numpysane.matmult( arr(3,), arr(3,2) ).shape
(2,)
Multiplying a row-vector by 5 different matrices:
>>> numpysane.matmult( arr(3,), arr(5,3,2) ).shape
(5, 2)
Multiplying a matrix by a col-vector:
>>> numpysane.matmult( arr(3,2), arr(2,1) ).shape
(3, 1)
Multiplying a row-vector by a matrix by a col-vector:
>>> numpysane.matmult( arr(3,), arr(3,2), arr(2,1) ).shape
(1,)
** What's wrong with existing numpy functions?
Why did I go through all the trouble to reimplement all this? Doesn't numpy
already do all these things? Yes, it does. But in a very nonintuitive way.
*** Concatenation
**** hstack()
hstack() performs a "horizontal" concatenation. When numpy prints an array, this
is the last dimension (the most significant dimensions in numpy are at the end).
So one would expect that this function concatenates arrays along this last
dimension. In the special case of 1D and 2D arrays, one would be right:
>>> numpy.hstack( (arr(3), arr(3))).shape
(6,)
>>> numpy.hstack( (arr(2,3), arr(2,3))).shape
(2, 6)
but in any other case, one would be wrong:
>>> numpy.hstack( (arr(1,2,3), arr(1,2,3))).shape
(1, 4, 3) <------ I expect (1, 2, 6)
>>> numpy.hstack( (arr(1,2,3), arr(1,2,4))).shape
[exception] <------ I expect (1, 2, 7)
>>> numpy.hstack( (arr(3), arr(1,3))).shape
[exception] <------ I expect (1, 6)
>>> numpy.hstack( (arr(1,3), arr(3))).shape
[exception] <------ I expect (1, 6)
The above should all succeed, and should produce the shapes as indicated. Cases
such as "numpy.hstack( (arr(3), arr(1,3)))" are maybe up for debate, but
broadcasting rules allow adding as many extra length-1 dimensions as we want
without changing the meaning of the object, so I claim this should work. Either
way, if you print out the operands for any of the above, you too would expect a
"horizontal" stack() to work as stated above.
It turns out that normally hstack() concatenates along axis=1, unless the first
argument only has one dimension, in which case axis=0 is used. In a system where
the most significant dimension is the last one, this is only correct if everyone
has only 2D arrays. The correct way to do this is to concatenate along axis=-1.
It works for n-dimensionsal objects, and doesn't require the special case logic
for 1-dimensional objects.
**** vstack()
Similarly, vstack() performs a "vertical" concatenation. When numpy prints an
array, this is the second-to-last dimension (remember, the most significant
dimensions in numpy are at the end). So one would expect that this function
concatenates arrays along this second-to-last dimension. Again, in the special
case of 1D and 2D arrays, one would be right:
>>> numpy.vstack( (arr(2,3), arr(2,3))).shape
(4, 3)
>>> numpy.vstack( (arr(3), arr(3))).shape
(2, 3)
>>> numpy.vstack( (arr(1,3), arr(3))).shape
(2, 3)
>>> numpy.vstack( (arr(3), arr(1,3))).shape
(2, 3)
>>> numpy.vstack( (arr(2,3), arr(3))).shape
(3, 3)
Note that this function appears to tolerate some amount of shape mismatches. It
does it in a form one would expect, but given the state of the rest of this
system, I found it surprising. For instance "numpy.hstack( (arr(1,3), arr(3)))"
fails, so one would think that "numpy.vstack( (arr(1,3), arr(3)))" would fail
too.
And once again, adding more dimensions make it confused, for the same reason:
>>> numpy.vstack( (arr(1,2,3), arr(2,3))).shape
[exception] <------ I expect (1, 4, 3)
>>> numpy.vstack( (arr(1,2,3), arr(1,2,3))).shape
(2, 2, 3) <------ I expect (1, 4, 3)
Similarly to hstack(), vstack() concatenates along axis=0, which is "vertical"
only for 2D arrays, but not for any others. And similarly to hstack(), the 1D
case has special-cased logic to make it work properly.
The correct way to do this is to concatenate along axis=-2. It works for
n-dimensionsal objects, and doesn't require the special case for 1-dimensional
objects.
**** dstack()
I'll skip the detailed description, since this is similar to hstack() and
vstack(). The intent was to concatenate across axis=-3, but the implementation
takes axis=2 instead. This is wrong, as before. And I find it strange that these
3 functions even exist, since they are all special-cases: the concatenation axis
should be an argument, and at most, the edge special case (hstack()) should
exist. This brings us to the next function
**** concatenate()
This is a more general function, and unlike hstack(), vstack() and dstack(), it
takes as input a list of arrays AND the concatenation dimension. It accepts
negative concatenation dimensions to allow us to count from the end, so things
should work better. And in many cases that failed previously, they do:
>>> numpy.concatenate( (arr(1,2,3), arr(1,2,3)), axis=-1).shape
(1, 2, 6)
>>> numpy.concatenate( (arr(1,2,3), arr(1,2,4)), axis=-1).shape
(1, 2, 7)
>>> numpy.concatenate( (arr(1,2,3), arr(1,2,3)), axis=-2).shape
(1, 4, 3)
But many things still don't work as I would expect:
>>> numpy.concatenate( (arr(1,3), arr(3)), axis=-1).shape
[exception] <------ I expect (1, 6)
>>> numpy.concatenate( (arr(3), arr(1,3)), axis=-1).shape
[exception] <------ I expect (1, 6)
>>> numpy.concatenate( (arr(1,3), arr(3)), axis=-2).shape
[exception] <------ I expect (3, 3)
>>> numpy.concatenate( (arr(3), arr(1,3)), axis=-2).shape
[exception] <------ I expect (2, 3)
>>> numpy.concatenate( (arr(2,3), arr(2,3)), axis=-3).shape
[exception] <------ I expect (2, 2, 3)
This function works as expected only if
- All inputs have the same number of dimensions
- All inputs have a matching shape, except for the dimension along which we're
concatenating
- All inputs HAVE the dimension along which we're concatenating
A common use case that violates these conditions: I have an object that contains
N 3D vectors, and I want to add another 3D vector to it. This is essentially the
first failing example above.
**** stack()
The name makes it sound exactly like concatenate(), and it takes the same
arguments, but it is very different. stack() requires that all inputs have
EXACTLY the same shape. It then concatenates all the inputs along a new
dimension, and places that dimension in the location given by the 'axis' input.
If this is the exact type of concatenation you want, this function works fine.
But it's one of many things a user may want to do.
**** Thoughts on concatenation
This module introduces numpysane.glue() and numpysane.cat() to replace all the
above functions. These do not refer to anything being "horizontal" or
"vertical", nor do they talk about "rows" or "columns": these concepts simply
don't apply in a generic N-dimensional system. These functions are very explicit
about the dimensionality of the inputs/outputs, and fit well into a
broadcasting-aware system.
Since these functions assume that broadcasting is an important concept in the
system, the given axis indices should be counted from the most significant
dimension: the last dimension in numpy. This means that where an axis index is
specified, negative indices are encouraged. glue() forbids axis>=0 outright.
***** Example for further justification
An array containing N 3D vectors would have shape (N,3). Another array
containing a single 3D vector would have shape (3,). Counting the dimensions
from the end, each vector is indexed in dimension -1. However, counting from the
front, the vector is indexed in dimension 0 or 1, depending on which of the two
arrays we're looking at. If we want to add the single vector to the array
containing the N vectors, and we mistakenly try to concatenate along the first
dimension, it would fail if N != 3. But if we're unlucky, and N=3, then we'd get
a nonsensical output array of shape (3,4). Why would an array of N 3D vectors
have shape (N,3) and not (3,N)? Because if we apply python iteration to it, we'd
expect to get N iterates of arrays with shape (3,) each, and numpy iterates from
the first dimension:
>>> a = numpy.arange(2*3).reshape(2,3)
>>> a
array([[0, 1, 2],
[3, 4, 5]])
>>> [x for x in a]
[array([0, 1, 2]), array([3, 4, 5])]
*** Manipulation of dimensions
**** atleast_xd()
Numpy has 3 special-case functions atleast_1d(), atleast_2d() and atleast_3d().
For 4d and higher, you need to do something else. These do surprising things:
>>> numpy.atleast_3d(arr(3)).shape
(1, 3, 1)
**** transpose()
Given a matrix (a 2D array), numpy.transpose() swaps the two dimensions, as
expected. Given anything else, it does not do what is expected:
>>> numpy.transpose(arr(3, )).shape
(3,)
>>> numpy.transpose(arr(3,4, )).shape
(4, 3)
>>> numpy.transpose(arr(3,4,5,6,)).shape
(6, 5, 4, 3)
I.e. numpy.transpose() reverses the order of ALL dimensions in the array. So if
we have N 2D matrices in a single array, numpy.transpose() doesn't transpose
each matrix.
*** Basic linear algebra
**** inner() and dot()
numpy.inner() and numpy.dot() are strange. In a real-valued n-dimensional
Euclidean space, a "dot product" is just another name for an "inner product".
Numpy disagrees.
It looks like numpy.dot() is matrix multiplication, with some wonky behaviors
when given higher-dimension objects, and with some special-case behaviors for
1-dimensional and 0-dimensional objects:
>>> numpy.dot( arr(4,5,2,3), arr(3,5)).shape
(4, 5, 2, 5) <--- expected result for a broadcasted matrix multiplication
>>> numpy.dot( arr(3,5), arr(4,5,2,3)).shape
[exception] <--- numpy.dot() is not commutative.
Expected for matrix multiplication, but not for a dot
product
>>> numpy.dot( arr(4,5,2,3), arr(1,3,5)).shape
(4, 5, 2, 1, 5) <--- don't know where this came from at all
>>> numpy.dot( arr(4,5,2,3), arr(3)).shape
(4, 5, 2) <--- 1D special case. This is a dot product.
>>> numpy.dot( arr(4,5,2,3), 3).shape
(4, 5, 2, 3) <--- 0D special case. This is a scaling.
It looks like numpy.inner() is some sort of quasi-broadcastable inner product, also
with some funny dimensioning rules. In many cases it looks like numpy.dot(a,b) is
the same as numpy.inner(a, transpose(b)) where transpose() swaps the last two
dimensions:
>>> numpy.inner( arr(4,5,2,3), arr(5,3)).shape
(4, 5, 2, 5) <--- All the length-3 inner products collected into a shape
with not-quite-broadcasting rules
>>> numpy.inner( arr(5,3), arr(4,5,2,3)).shape
(5, 4, 5, 2) <--- numpy.inner() is not commutative. Unexpected
for an inner product
>>> numpy.inner( arr(4,5,2,3), arr(1,5,3)).shape
(4, 5, 2, 1, 5) <--- No idea
>>> numpy.inner( arr(4,5,2,3), arr(3)).shape
(4, 5, 2) <--- 1D special case. This is a dot product.
>>> numpy.inner( arr(4,5,2,3), 3).shape
(4, 5, 2, 3) <--- 0D special case. This is a scaling.
'''
import numpy as np
from functools import reduce
import itertools
import types
import inspect
from distutils.version import StrictVersion
# setup.py assumes the version is a simple string in '' quotes
__version__ = '0.41'
def _product(l):
r'''Returns product of all values in the given list'''
return reduce( lambda a,b: a*b, l )
def _clone_function(f, name):
r'''Returns a clone of a given function.
This is useful to copy a function, updating its metadata, such as the
documentation, name, etc. There are also differences here between python 2
and python 3 that this function handles.
'''
def get(f, what):
what2 = 'func_{}'.format(what)
what3 = '__{}__' .format(what)
try:
return getattr(f, what2)
except:
try:
return getattr(f, what3)
except:
pass
return None
return types.FunctionType(get(f, 'code'),
get(f, 'globals'),
name,
get(f, 'defaults'),
get(f, 'closure'))
class NumpysaneError(Exception):
def __init__(self, err): self.err = err
def __str__(self): return self.err
def _eval_broadcast_dims( args, prototype ):
r'''Helper function to evaluate a given list of arguments in respect to a given
broadcasting prototype. This function will flag any errors in the
dimensionality of the inputs. If no errors are detected, it returns
dims_extra,dims_named
where
dims_extra is the outer shape of the broadcast
This is a list: the union of all the leading shapes of all the
arguments, after the trailing shapes of the prototype have been stripped
dims_named is the sizes of the named dimensions
This is a dict mapping dimension names to their sizes
'''
# First I initialize dims_extra: the array containing the broadcasted
# slices. Each argument calls for some number of extra dimensions, and the
# overall array is as large as the biggest one of those
Ndims_extra = 0
for i_arg in range(len(args)):
Ndims_extra_here = len(args[i_arg].shape) - len(prototype[i_arg])
if Ndims_extra_here > Ndims_extra:
Ndims_extra = Ndims_extra_here
dims_extra = [1] * Ndims_extra
def parse_dim( name_arg,
shape_prototype, shape_arg, dims_named ):
def range_rev(n):
r'''Returns a range from -1 to -n.
Useful to index variable-sized lists while aligning their ends.'''
return range(-1, -n-1, -1)
# first, I make sure the input is at least as dimension-ful as the
# prototype. I do this by prepending dummy dimensions of length-1 as
# necessary
if len(shape_prototype) > len(shape_arg):
ndims_missing_here = len(shape_prototype) - len(shape_arg)
shape_arg = (1,) * ndims_missing_here + shape_arg
# MAKE SURE THE PROTOTYPE DIMENSIONS MATCH (the trailing dimensions)
#
# Loop through the dimensions. Set the dimensionality of any new named
# argument to whatever the current argument has. Any already-known
# argument must match
for i_dim in range_rev(len(shape_prototype)):
dim_prototype = shape_prototype[i_dim]
if not isinstance(dim_prototype, int):
# This is a named dimension. These can have any value, but ALL
# dimensions of the same name must thave the SAME value
# EVERYWHERE
if dim_prototype not in dims_named:
dims_named[dim_prototype] = shape_arg[i_dim]
dim_prototype = dims_named[dim_prototype]
# The prototype dimension (named or otherwise) now has a numeric
# value. Make sure it matches what I have
if dim_prototype != shape_arg[i_dim]:
raise NumpysaneError("Argument {} dimension '{}': expected {} but got {}".
format(name_arg,
shape_prototype[i_dim],
dim_prototype,
shape_arg[i_dim]))
# I now know that this argument matches the prototype. I look at the
# extra dimensions to broadcast, and make sure they match with the
# dimensions I saw previously
Ndims_extra_here = len(shape_arg) - len(shape_prototype)
# MAKE SURE THE BROADCASTED DIMENSIONS MATCH (the leading dimensions)
#
# This argument has Ndims_extra_here dimensions to broadcast. The
# current shape to broadcast must be at least as large, and must match
for i_dim in range_rev(Ndims_extra_here):
dim_arg = shape_arg[i_dim - len(shape_prototype)]
if dim_arg != 1:
if dims_extra[i_dim] == 1:
dims_extra[i_dim] = dim_arg
elif dims_extra[i_dim] != dim_arg:
raise NumpysaneError("Argument {} prototype {} extra broadcast dim {} mismatch: previous arg set this to {}, but this arg wants {}".
format(name_arg,
shape_prototype,
i_dim,
dims_extra[i_dim],
dim_arg))
dims_named = {} # parse_dim() adds to this
for i_arg in range(len(args)):
parse_dim( i_arg,
prototype[i_arg], args[i_arg].shape,
dims_named )
return dims_extra,dims_named
def _broadcast_iter_dim( args, prototype, dims_extra ):
r'''Generator to iterate through all the broadcasting slices.
'''
# pad the dimension of each arg with ones. This lets me use the full
# dims_extra index on each argument, without worrying about overflow
args = [ atleast_dims(args[i], -(len(prototype[i])+len(dims_extra)) ) for i in range(len(args)) ]
# per-arg dims_extra indexing varies: len-1 dimensions always index at 0. I
# make a mask that I apply each time
idx_slice_mask = np.ones( (len(args), len(dims_extra)), dtype=int)
for i in range(len(args)):
idx_slice_mask[i, np.array(args[i].shape,dtype=int)[:len(dims_extra)]==1] = 0
for idx_slice in itertools.product( *(range(x) for x in dims_extra) ):
# tuple(idx) because of wonky behavior differences:
# >>> a
# array([[0, 1, 2],
# [3, 4, 5]])
#
# >>> a[tuple((1,1))]
# 4
#
# >>> a[list((1,1))]
# array([[3, 4, 5],
# [3, 4, 5]])
yield tuple( args[i][tuple(idx_slice *
idx_slice_mask[i])] for i in range(len(args)) )
def broadcast_define(prototype, prototype_output=None, out_kwarg=None):
r'''Vectorizes an arbitrary function, expecting input as in the given prototype.
SYNOPSIS
>>> import numpy as np
>>> import numpysane as nps
>>> @nps.broadcast_define( (('n',), ('n',)) )
... def inner_product(a, b):
... return a.dot(b)
>>> a = np.arange(6).reshape(2,3)
>>> b = a + 100
>>> a
array([[0, 1, 2],
[3, 4, 5]])
>>> b
array([[100, 101, 102],
[103, 104, 105]])
>>> inner_product(a,b)
array([ 305, 1250])
The prototype defines the dimensionality of the inputs. In the inner product
example above, the input is two 1D n-dimensional vectors. In particular, the
'n' is the same for the two inputs. This function is intended to be used as
a decorator, applied to a function defining the operation to be vectorized.
Each element in the prototype list refers to each input, in order. In turn,
each such element is a list that describes the shape of that input. Each of
these shape descriptors can be any of
- a positive integer, indicating an input dimension of exactly that length
- a string, indicating an arbitrary, but internally consistent dimension
The normal numpy broadcasting rules (as described elsewhere) apply. In
summary:
- Dimensions are aligned at the end of the shape list, and must match the
prototype
- Extra dimensions left over at the front must be consistent for all the
input arguments, meaning:
- All dimensions of length != 1 must match
- Dimensions of length 1 match corresponding dimensions of any length in
other arrays
- Missing leading dimensions are implicitly set to length 1
- The output(s) have a shape where
- The trailing dimensions are whatever the function being broadcasted
returns
- The leading dimensions come from the extra dimensions in the inputs
Calling a function wrapped with broadcast_define() with extra arguments
(either positional or keyword), passes these verbatim to the inner function.
Only the arguments declared in the prototype are broadcast.
Scalars are represented as 0-dimensional numpy arrays: arrays with shape (),
and these broadcast as one would expect:
>>> @nps.broadcast_define( (('n',), ('n',), ()))
... def scaled_inner_product(a, b, scale):
... return a.dot(b)*scale
>>> a = np.arange(6).reshape(2,3)
>>> b = a + 100
>>> scale = np.array((10,100))
>>> a
array([[0, 1, 2],
[3, 4, 5]])
>>> b
array([[100, 101, 102],
[103, 104, 105]])
>>> scale
array([ 10, 100])
>>> scaled_inner_product(a,b,scale)
array([[ 3050],
[125000]])
Let's look at a more involved example. Let's say we have a function that
takes a set of points in R^2 and a single center point in R^2, and finds a
best-fit least-squares line that passes through the given center point. Let
it return a 3D vector containing the slope, y-intercept and the RMS residual
of the fit. This broadcasting-enabled function can be defined like this:
import numpy as np
import numpysane as nps
@nps.broadcast_define( (('n',2), (2,)) )
def fit(xy, c):
# line-through-origin-model: y = m*x
# E = sum( (m*x - y)**2 )
# dE/dm = 2*sum( (m*x-y)*x ) = 0
# ----> m = sum(x*y)/sum(x*x)
x,y = (xy - c).transpose()
m = np.sum(x*y) / np.sum(x*x)
err = m*x - y
err **= 2
rms = np.sqrt(err.mean())
# I return m,b because I need to translate the line back
b = c[1] - m*c[0]
return np.array((m,b,rms))
And I can use broadcasting to compute a number of these fits at once. Let's
say I want to compute 4 different fits of 5 points each. I can do this:
n = 5
m = 4
c = np.array((20,300))
xy = np.arange(m*n*2, dtype=np.float64).reshape(m,n,2) + c
xy += np.random.rand(*xy.shape)*5
res = fit( xy, c )
mb = res[..., 0:2]
rms = res[..., 2]
print "RMS residuals: {}".format(rms)
Here I had 4 different sets of points, but a single center point c. If I
wanted 4 different center points, I could pass c as an array of shape (4,2).
I can use broadcasting to plot all the results (the points and the fitted
lines):
import gnuplotlib as gp
gp.plot( *nps.mv(xy,-1,0), _with='linespoints',
equation=['{}*x + {}'.format(mb_single[0],
mb_single[1]) for mb_single in mb],
unset='grid', square=1)