Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Link level tomography should not be in finish() and it should update cost in Routing Daemon #511

Open
Naphann opened this issue Mar 1, 2023 · 0 comments
Labels
connection network-layer issues link link layer physical error models, simulation of new hardware elements tomography full tomo, CHSH, etc.

Comments

@Naphann
Copy link
Contributor

Naphann commented Mar 1, 2023

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).

@Naphann Naphann added link link layer connection network-layer issues tomography full tomo, CHSH, etc. physical error models, simulation of new hardware elements labels Mar 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
connection network-layer issues link link layer physical error models, simulation of new hardware elements tomography full tomo, CHSH, etc.
Projects
None yet
Development

No branches or pull requests

1 participant