Simulation Path Framework
The tool also provides a framework for exploiting arbitrary simulation paths (using the taskflow library) based on the methods proposed in .
A simulation path describes the order in which the individual MxV or MxM multiplications are conducted during the simulation of a quantum circuit.
It can be described as a list of tuples that identify the individual states/operations to be multiplied.
The initial state is always assigned
ID 0, while the i-th operation is assigned
The result of a multiplication is assigned the next highest, unused ID, e.g., in a circuit with
n gates the result of the first multiplication is assigned
The framework comes with several pre-defined simulation path strategies:
sequential(default): simulate the circuit sequentially from left to right using only MxV multiplications
pairwise_recursive: recursively group pairs of states and operations to form a binary tree of MxV/MxM multiplications
bracket: group certain number of operations according to a given
alternating: start the simulation in the middle of the circuit and alternate between applications of gates “from the left” and “from the right” (which might potentially be useful for equivalence checking)
as well as the option to translate strategies from the domain of tensor networks to decision diagrams (using the CoTenGra library), see [here](#cotengra).
Usage in Python
This example shall serve as a showcase on how to use the simulation path framework (via Python). First, create the circuit to be simulated using qiskit, e.g., in this case a three-qubit GHZ state:
from qiskit import * circ = QuantumCircuit(3) # the initial state corresponds to ID 0 circ.h(0) # corresponds to ID 1 circ.cx(0, 1) # corresponds to ID 2 circ.cx(0, 2) # corresponds to ID 3
Then, obtain the simulation path framework qiskit backend. You can choose between the
path_sim_qasm_simulator and the
The first just yields a dictionary with the counts of the measurements, while the latter also provides the complete statevector (which, depending on the amount of qubits, might not fit in the available memory).
from mqt import ddsim provider = ddsim.DDSIMProvider() backend = provider.get_backend("path_sim_qasm_simulator")
- Per default, the backend uses the
sequentialstrategy. For this particular example, this means:
first, the Hadamard operation is applied to the initial state (
[0, 1] -> 4)
then, the first CNOT is applied (
[4, 2] -> 5)
finally, the last CNOT is applied (
[5, 3] -> 6)
The corresponding simulation path is thus described by
[[0, 1], [4, 2], [5, 3]]and the final state is the one with ID
The simulation is started by calling the
execute function, which takes several optional configuration parameters (such as the simulation path strategy).
For a complete list of configuration options see [here](#configuration).
job = execute(circ, backend) result = job.result() counts = result.get_counts(circ) print(counts)
Instead of re-inventing the wheel, the framework allows to translate strategies from the domain of tensor networks to decision diagrams. To this end, the tensor network contraction library CoTenGra is used. In order to use this part of the framework, some extra dependencies have to be installed. This can be accomplished by running
pip install mqt.ddsim[tnflow] pip install -U git+https://github.com/jcmgray/cotengra.git
Then, in order to let CoTenGra determine a simulation path for a given circuit the
mode="cotengra" option has to be used when calling
job = execute(circ, backend, mode="cotengra")
Per default this uses a maximum of
1024 trials (option
cotengra_max_repeats) for CoTenGra and dumps a representation of the determined simulation path to a file in the current working directory (option
Optionally, a visualization of the simulation path can be generated by specifying
- The framework can be configured using multiple options (which can be passed to the
mode: the simulation path mode to use (
bracket_size: the bracket size used for the
bracketmode (default: `2`)
alternating_start: the id of the operation to start with in the
seed: the random seed used for the simulator (default
0, i.e., no particular seed)
In addition to the above, CoTenGra can be configured using the options described [above](#cotengra).
Usage as Standalone Executable
The path framework simulator is not exposed as standalone executable.