phylanx icon indicating copy to clipboard operation
phylanx copied to clipboard

An Asynchronous Distributed C++ Array Processing Toolkit

Results 101 phylanx issues
Sort by recently updated
recently updated
newest added

flyby: fixing hpx deprecated headers

type: feature request
submodule: backend
category: primitives

added kubernetes remote deployment scripts.

type: compatibility issue
type: enhancement

Make it possible to connect new resources to a running Phylanx calculation. This doesn't actually work. I need guidance. Problems: (1) Not sure how to use params with the longer...

type: compatibility issue
type: enhancement
category: PhySL
category: @Phylanx

We should add a way that simplifies adding trivial primitives. Often the functionality of a primitive can be expressed by a single function. In this case, a user should be...

type: feature request
category: PhySL

``` import bp bp.function() ``` Results in the following error ``` NotImplementedError: Phylanx does not support non-NumPy member functions.Cannot transform: bp.bp_cpu ``` The NumPy mention is misleading here. Can we...

type: defect

Tree transducers require an input tree stored in [Chomsky normal form](https://en.wikipedia.org/wiki/Chomsky_normal_form) (a binary tree structure). Transducers additionally require a set of binary encodings, called paths, of a tree's topology. Each...

submodule: backend

Phylanx would benefit greatly from automatic differentiation. It would be worth exploring if Phylanx should have direct support in [Tangent]. It might be easier to distribute Tangent with Phylanx to...

type: feature request
type: optimization
submodule: frontend
submodule: middleware

Early experiment results show that the timing reported from the topmost node in the execution tree is wrong. This requires some investigation.

type: defect
category: primitives

This example shows that upon defining a variable, Phylanx creates a copy of a list instead of referencing it. This behavior is different than Python's. ### Regular Python Code ```python...

type: defect
category: PhySL
category: @Phylanx

I double-checked the Javascript and dug into the performance data, and confirmed that the timing issues are on the Phylanx end, not the vis side of things. The timing data...

type: defect
category: primitives