rossduncan
rossduncan
Just built the latest integration and matching seems to have become incredibly slow. To the point where interactive use looks like it's crashed, but it's taking minutes to come up...
It would be nice if you could specify a default set of rules to loaded whenever a new derivation is started without having to specify them every time
Currently the matcher requires edges to match exactly; i.e. if the rule has an (un)directed edge then it can only match against an (un)directed edge in the graph. For some...
This is hard to reproduce, but happens not infrequently. Sometimes when a subgraph is selected in the editor it is impossible to deselect without changing tools. This means that every...
Looks like the matcher doesn't see subgraphs inside !-boxes. See attached. The use case I actually want has edges extending outside the !-box, but the problem occurs without this complication.
I have created a rule consisting of two boundary nodes joined by an edge. On the LHS the edge is undirected, on the RHS it is directed. It seems that...
It would be extremely useful to run quantomatic without its GUI, as a batch job. At present if you try to run it without a windowing system it dies on...
Add a new simproc combinator, REWRITE_W_TRAVERSAL(rule, v, t) takes a rule, the name of a vertex 'v' within the rule (as a string), and a "traversal" object 't' which is...
improve REWRITE_TARGETTED by replacing the targeting function f : G --> V(g) with a function returning a _partial_ _dictionary_ of targets f : G --> (V(r) --> V(g)) which first...
Add a new simproc combinator: REWRITE_TARGETED_W_METRIC(rule, v, f, m) takes a rule, the name of a vertex 'v' within the rule (as a string), a targeting function 'f' from graphs...