Rod Van Meter

Right now, whenever you create a new function like Xpurify() that operates on qubits, you have to explicitly call ApplyMemoryError(). As of this writing, it isn't incorporated into entanglement swapping...

Would be nice if some info about the active RuleSets showed up here. What about currently in-progress quantum resources? Is here the right place, or somewhere else? 

EnoughResourceClause and the others should indicate in their names that they are Condition (or possibly Match) clauses. Rules consist of both Condition clauses and Action clauses. The terminology used in...

createConnectionSetupRequest() takes a (single) destination partner address and the length of the connection (in Bell pairs). It also needs to specify the E2E fidelity that the application requires. This will...

We need an RFC-style specification for the RuleEngine-to-RuleEngine communication. Every message should trigger a ConditionClause in the RE; if it doesn't, an appropriate error message should be generated.

e.g., https://link.aps.org/doi/10.1103/PhysRevA.100.052333

Aparicio network

1

This is the network that Lucho used for testing multiplexing schemes. We should attempt to recreate it, and to replicate the work. (It's possible that the .ned file still exists...

I think they have almost entirely diverged. See doc/Rule%20Engine.md and the accompanying figures.

Document ConnectionManager

1

This is one of the most important pieces of functionality, and turns out it's under-documented in both the old wiki and the current markdown & code.

Examine QuISP OMNeT++ coding choices

1

I think a lot of the things that are currently module parameters should instead be C++ class/module "data members". Compare: https://doc.omnetpp.org/omnetpp/manual/#sec:simple-modules:setting-parameters https://doc.omnetpp.org/omnetpp/manual/#sec:simple-modules:handlemessage go to 4.4.1.6 shows how to add “data...