parallel-solver

The parallel solver of arg2p: a catalog partitions the theory among workers, which build the arguments of their rules in parallel, sending each argument directly to the workers that build on it, and then find the direct attacks on their own arguments, each pair checked once. The catalog gathers the graph and labels it as the standard solver does, with any semantics and graph extension.

The same catalog and workers run on one thread (LocalCluster), on the threads of the JVM (ThreadedCluster), on the threads of Node.js (WorkerCluster) or on the Web Workers of a browser (WebWorkerCluster). On a machine the nodes share the terms of their messages; between processes the messages are written as Prolog text (MessageCodec).

Each cluster is a Site, which can be federated with others, on any machine and engine, over Links (WebSocketLinks, RtcLinks between browsers, MemoryLinks), found on a local network by their beacons (LanDiscovery): the sites lend one another their workers, and a graph is built by the workers of all of them.

Each cluster is also a solver of arg2p, with the interface of Arg2p (ClusterSolver, AsyncClusterSolver where the workers run on other threads of JavaScript): the catalog solves any goal on the standard solver, whose graph builder and query mode take the graph the workers built for it. Each tells what its federation does (FederationStats).

The parallel solver of arg2p: a catalog partitions the theory among workers, which build the arguments of their rules in parallel, sending each argument directly to the workers that build on it, and then find the direct attacks on their own arguments, each pair checked once. The catalog gathers the graph and labels it as the standard solver does, with any semantics and graph extension.

The same catalog and workers run on one thread (LocalCluster), on the threads of the JVM (ThreadedCluster), on the threads of Node.js (WorkerCluster) or on the Web Workers of a browser (WebWorkerCluster). On a machine the nodes share the terms of their messages; between processes the messages are written as Prolog text (MessageCodec).

Each cluster is a Site, which can be federated with others, on any machine and engine, over Links (WebSocketLinks, RtcLinks between browsers, MemoryLinks), found on a local network by their beacons (LanDiscovery): the sites lend one another their workers, and a graph is built by the workers of all of them.

Each cluster is also a solver of arg2p, with the interface of Arg2p (ClusterSolver, AsyncClusterSolver where the workers run on other threads of JavaScript): the catalog solves any goal on the standard solver, whose graph builder and query mode take the graph the workers built for it. Each tells what its federation does (FederationStats).

The parallel solver of arg2p: a catalog partitions the theory among workers, which build the arguments of their rules in parallel, sending each argument directly to the workers that build on it, and then find the direct attacks on their own arguments, each pair checked once. The catalog gathers the graph and labels it as the standard solver does, with any semantics and graph extension.

The same catalog and workers run on one thread (LocalCluster), on the threads of the JVM (ThreadedCluster), on the threads of Node.js (WorkerCluster) or on the Web Workers of a browser (WebWorkerCluster). On a machine the nodes share the terms of their messages; between processes the messages are written as Prolog text (MessageCodec).

Each cluster is a Site, which can be federated with others, on any machine and engine, over Links (WebSocketLinks, RtcLinks between browsers, MemoryLinks), found on a local network by their beacons (LanDiscovery): the sites lend one another their workers, and a graph is built by the workers of all of them.

Each cluster is also a solver of arg2p, with the interface of Arg2p (ClusterSolver, AsyncClusterSolver where the workers run on other threads of JavaScript): the catalog solves any goal on the standard solver, whose graph builder and query mode take the graph the workers built for it. Each tells what its federation does (FederationStats).