The problem:
Link-level tomography is done to assign a cost to the routing daemon. This should be a process that is done before applications are run in QuISP. So the tomography calculation should not be inside the finish() function of the Hardware Monitor.
Suggested Solution:
Create a new module which handles tomography because it is a common subroutine that should be done at both connection-level and link-level. Bonus points if the tomography module can perform state tomography on multipartite states (need to generalize the way Stoke's parameters are defined in current implementation).
The problem: Link-level tomography is done to assign a cost to the routing daemon. This should be a process that is done before applications are run in QuISP. So the tomography calculation should not be inside the
finish()function of the Hardware Monitor.Suggested Solution: Create a new module which handles tomography because it is a common subroutine that should be done at both connection-level and link-level. Bonus points if the tomography module can perform state tomography on multipartite states (need to generalize the way Stoke's parameters are defined in current implementation).