Compatibility with Pytket

[DanCocking]

What feature should we add?

Cross-compatibility with other libraries such as Qiskit, cirq etc. More specifically the ability to "import" and "export" circuits to and from QuanGuru or use the abilities of QuanGuru on circuits built elsewhere and vice versa. This functionality can be quickly achieved by interfacing with Pytket a package that provides access to many different backends from Qiskit to hardware. It can also build its circuits from other packages circuits as well as OpenQasm so it can provide the ability to transform other packages circuit design API into QuanGuru's circuit desgin API.

Proposed Solution

• Add support to convert QuanGuru circuits to pytket. This pytket object should be directly interacted with. This may require tool to flattern QuanGuru circuits into flatter dictionaries.
• Add support to use Pytket Circuits to perform simulation using a wrapper of pytket circuits in the form of a quanguru protocol
• Add wrapper for some of the more simple functionalities so the user does not need to worry about the conversion (eg. add .draw method to visualise a Quanguru qSystem and .qasm to get qasm representation

To users this should appear as a simple quantumSystem.createPytketCircuit(self) call that returns a new pytket Circuit that has the same state as QuanGurus quantum system (plus subsystems). It could also be implemented in an entirely new class that acts as a wrapper to pytkets circuits.

Why/Motivation

There are specific types of simulation that QuanGuru is significantly better at (such as exact simulation for >2 qubit gates), similarly, QuanGuru is lacking features compared to some of the larger projects such as ability to graph and less optimised simulation in many cases.

[github-actions[bot]]

Branch 227-Compatibility_with_other_tools_using_OpenQASM created!

[DanCocking]

First step is to create a wrapper around Pytket circuits so they can be represented as protocols within QuanGuru and contribute to simulations within QuanGuru. It should access properties of the Circuit and provide an interface that QuanGuru can understand.

[DanCocking]

Due to Pytekt Circuits not being from QuanGuru they do not have any Param Bounds — this means that if a pytket circuit is changed we cannot automatically inform the wrapper object. This is an issue since this means that the unitary and systems will not update when the circuit changes and so you will be working with an outdated version of the circuit.

Solution

• add method for loading the current Circuit into the wrapper object. This must be run by the user when they want to update the wrapper to any changes to the circuit it holds.

  Why This Solution

• allows users to know exactly the state of the wrapper object
• ensures the wrapper is updated before it is used
• Gives extended flexibility to users -- users may have multiple protocols based off the same Circuit that are slightly different
• In most cases a Circuit will be built then assigned to a protocol so this will not be necessary as it is done by default on initiation