Christopher Taylor

@hkaiser working on a thorough description!

The traversal technique is a little complicated because of paths. A default prefix traversal is good. Paths are a binary string (sequence) that represents a traversal pattern through the tree....

@hkaiser the semantics (numpy broadcast rules) can be a little tricky; implementer beware.

Also would like to note, when python runs with phylanx, the lib_path string used to load the shared object (module) correctly points to the right system path.

@hkaiser should I post the log in here?

@hkaiser the python and C++ lra logs are attached in this post. Thank you for investigating this issue! The python log is here: [lra.log](https://github.com/STEllAR-GROUP/phylanx/files/3015300/lra.log) The c++ log is here; apologies...

@hkaiser my LD_LIBRARY_PATH is set correctly. Resolves 'ldd' correctly on all shared objects. Noticed something in the logs. The lracpp.log and lra.log files show that the HPX(dynamic_link_failure) breaks on 'load_component_factory'...

@hkaiser an old friend suggested that since python is compiled in C, there could be some C/C++ name mangling taking place when Python loads the shared objects into memory (the...

@hkaiser in hindsight, LD_PRELOAD would also be broken and it's not, back to debugging.

@stevenrbrandt, * Would array_d accept an array shape and raw data as an input argument? * If the input is a shape, would the shape be generated across multiple machines...