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

PoC #1

Open
vstirbu opened this issue Nov 28, 2024 · 0 comments · May be fixed by #2
Open

PoC #1

vstirbu opened this issue Nov 28, 2024 · 0 comments · May be fixed by #2

Comments

@vstirbu
Copy link
Owner

vstirbu commented Nov 28, 2024

This is an experiment to explore the possibility of decoupling the compilation steps. The initial plan is to have a generic Qiskit backend that offloads the execution to a QPU proxy that handles the circuit adaptation to IQM hw:

sequenceDiagram

box q8s Job
    participant p as Program
    participant fe as Q8sBackend
end
box k8s Service
    participant api as HTTP API
    participant be as IQMBackend
end
participant qpu as QPU

activate p
    p -->> fe: new Q8sBackend
    activate fe
        p -->> fe: run(circuit)
        fe ->> api: POST circuit
        activate api
        api -->> be: new IQMBackend
        activate be
            api -->> be: transpile(circuit, qpu)
            api -->> be: run(transpiled_circuit)
            be ->> qpu: transpiled_circuit
            activate qpu
                qpu -->> be: result
            deactivate qpu
            be -->> api: result
        deactivate be
        api -->> fe: 200 OK result
        deactivate api
    fe -->> p: result
    deactivate fe
deactivate p
Loading
@vstirbu vstirbu linked a pull request Dec 9, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant