Hartmut Kaiser

@ct-clmsn Hmm, I don't think this would explain things. We have Phylanx running on other machines and on various platforms (Linux, Windows, and soon Mac)...

This exposes the more general problem that PhySL does not support named arguments at this point. Alternatively we will have to touch on all primitives that require dtype support and...

@taless474 here are some more: - [x] `cumprod` (#884) - [x] `cumsum` (#884) - [x] `dstack`, `vstack`, `hstack`, `stack` (#884) - [ ] `vsplit`, `hsplit` - [ ] all numeric...

> This should be fixed in #1202, but it hasn't been merged yet I'm still waiting for the tests to cycle. I'll merge it asap.

> array_d( array ) : split up an existing array across localities We have `tile(array, ...)` that is doing exactly that (see: https://github.com/STEllAR-GROUP/phylanx/blob/master/src/plugins/matrixops/tile_operation.cpp#L32-L45)

@stevenrbrandt How should the distributed array be initialized? We have available the equivalents for `numpy.zeros`, `numpy.ones`, `numpy.empty`, etc. (all of those are mapped onto our `constant` primitive). We should however...

> @hkaiser `array_d(arg)` should not take a shape arg. It should work kind of like `numpy.array(arg)` does. It should convert a non-distributed array into a distributed one. The value `arg`...

> @hkaiser -- if we assume pure SPMD, then any non-distributed array must have an identical copy on each locality (unless it's a random array). I guess that means `array_d()`...

> array_d([[0,0,0,0],[0,0,0,0],[0,0,0,0],[0,0,0,0]]) -> each machine creates a 4x4 matrix tile of 0's. > > array_d(shape=((4,4), row)) -> _all_ machines create a 4x4 row order tile > > array_d(shape=( (4,4), [...

@stevenrbrandt I don't think having `fromfunction_d` would be appropriate. The numpy docs say that `fromfunction` returns whatever the function object passed to it returns, which could possibly be not an...