John Biddiscombe
John Biddiscombe
A discussion at CSCS took place where the anti-boost argument went as follows Q: The idea is that eventually the features in HPX will be available via the c++ standard?...
I have an unusual setup ... an hpx thread is working on some message sending, to improve latency, I call `parcelport->progress()` which jumps into the parcelport code and in effect...
I have previously implemented a custom bootstrapping routine that allows the libfabric parcelport to initialize itself by sending addresses from worker nodes to the root/agas node so that address vectors...
The paper referenced here https://arxiv.org/abs/1908.05790 describes a benchmark suite for task-based programming APIs. We should add HPX support to the benchmark suite to see how we compare to other runtimes....
## New feature During recent discussions with the kokkos people and also as a result of our failed attempt to have executors made variadic, we speculated that task management could...
## Expected Behavior Binding of cores should be the same on successive runs with unchanged parameters What I actually get appears to be semi-random and changes from run to run...
It frequently occurs that we have loops of the kind ``` for (int i=0; i
Attempting to port some CMS (from CERN c.f. @felicepantaleo, @rovere) software to HPX from TBB has hit a problem - the CMS code makes fairly liberal use of tbb concurrent...
Currently there are two ways for actions to be handled ``` async(policy=async || policy==sync, action, locality, args...) ``` This is an asynchronous call that is executed remotely and returns a...
When loading the dot file shown below, using ``` A = nx.drawing.nx_agraph.to_agraph(nx.drawing.nx_pydot.read_dot(dot_file)) A.layout('dot') A.draw('image.png') Image(filename='image.png') ``` I receive the following warning - and the image has all black filled boxes...