Hartmut Kaiser
Hartmut Kaiser
Very nice! I like it.
> Another inherent problem is that we use currently use arrays as a method of conveying range data. Really? I thought we were using lists. :/
FWIW, #616 implements this for 1d arrays. Full support for 2d arrays will be added by a separate PR.
@stevenrbrandt things work for 1D arrays, yes. I had left this ticket open as 2D/3D support is mostly missing.
The only scenario I could think of for this to happen would be that HPX finds the same component module twice (Release/Debug?) At the point of failure, could you ask...
As suspected, this has turned out to be an issue happening when both, a release and a debug version are installed in the same place.
@ct-clmsn could you try creating an execution log (using `--hpx:debug-hpx-log=`)? There you should see any error generated while loading. In Python you can add this option to `phylanx.PhylanxSession` by adding...
> should I post the log in here? @ct-clmsn that or post it somewhere and leave the link here. Alternatively, just send it directly to me.
@ct-clmsn the logs say for instance `/opt/lib/phylanx/libphylanx_arithmetics.so: HPX(dynamic_link_failure)`. This is the standard error message generated by the system if a) the system was not able the module (file not found)...
@ct-clmsn there is a difference between component and plugins and those are loaded through separate mechanism. This explains why for some modules one of those load functions fails. This shouldn't...