Solve using telingo
The miscoto.query interface uses clyngor to communicate with the clingo
subprocesses that solve instances. To resolve #2 we will need to use telingo
for some tasks.
Query doesn't have unit tests, communication using clyngor is tested implicitly through tests of MisCoTo functions on a toy example. If telingo
is functionally equivalent clingo
, then the same tests can be used. Otherwise, we need to define unit tests that are specific to telingo
.
The choice of solver is determined by the encoding, which uses temporal constraints, or not. To avoid the risk of mismatch, extend commons to associate solvers and encodings, and use that association in query.
-
Unit tests of communication with telingo
-
Allow query to use telingo
as a solver. -
Modify commons, query to associate a solver with each encoding