Wolfram/QuantumFramework | Paclet Repository

Wolfram`QuantumFramework`

QiskitTarget

	QiskitTarget [spec] builds a qiskit transpiler target from the device specification spec, an Association of qiskit Target.from_configuration parameters.
	tgt["prop"] gives the property prop of a QiskitTarget object tgt, one of "NumQubits" , "OperationNames" , "CouplingMap" or "Spec" .

Details and Options

▪

QiskitTarget

describes a device for transpilation: its native gate set, qubit connectivity, and (optionally) per-instruction errors and durations. It is the device argument of

QuantumQASM

"Target"

option.

▪

spec is an Association whose keys are qiskit

Target.from_configuration

parameters:

"BasisGates"

"NumQubits"

"CouplingMap"

"InstructionDurations"

"ConcurrentMeasurements"

"Dt"

"TimingConstraints"

"CustomNameMapping"

. Keys are CamelCase and map to qiskit's snake_case names; the raw snake_case name is accepted too. The accepted key set is read from the installed qiskit, so it tracks the

qiskit Target.from_configuration documentation

of whichever version is installed.

▪

Each value takes qiskit's own form:

"NumQubits"

an integer;

"CouplingMap"

a list of directed integer pairs

{{c,t},…}

;

"Dt"

a number of seconds;

"InstructionDurations"

"ConcurrentMeasurements"

"TimingConstraints"

and

"CustomNameMapping"

the structures qiskit's

Target.from_configuration

expects.

▪

"BasisGates"

is a list of qiskit standard gate names — the names are defined by the installed qiskit, not by

QiskitTarget

, and vary by version. In the bundled qiskit 2.4.1 there are 54, including the single-qubit

"x"

"y"

"z"

"h"

"s"

"sx"

"t"

"rx"

"ry"

"rz"

"p"

"u"

"u3"

, the two-qubit

"cx"

"cz"

"cy"

"ch"

"swap"

"iswap"

"ecr"

"rzz"

"rxx"

, and the three-qubit

"ccx"

"ccz"

"cswap"

. The names listed here are those of qiskit 2.4.1; a different qiskit version may add, rename, or remove gate names, so the list could differ from what is shown. The complete, version-correct list is qiskit's standard gate-name mapping, obtainable with

qiskit.circuit.library.get_standard_gate_name_mapping

or from qiskit's

circuit-library documentation

. A name outside that set must be supplied through

"CustomNameMapping"

▪

The keys are validated against the installed qiskit at call time, so an unknown key gives a

Failure

(see Possible Issues) and any current or future qiskit

Target

parameter is accepted without a change to

QiskitTarget

▪

QiskitTarget

stores the validated specification rather than a serialized qiskit

Target

; the live target is rebuilt from the spec when it is used (inside

QuantumQASM

), so the same object works across qiskit sessions and versions.

▪

measure

and

reset

are added on every qubit automatically — they are universal but

Target.from_configuration

omits them for a bare unitary basis — so a target built from

{"x","sx","rz","cz"}

still transpiles circuits that contain measurements.

▪

QiskitTarget

displays as a summary panel showing its qubit count, native gate names, and number of coupling edges.

	Property	Result
	"NumQubits"	the number of qubits
	"OperationNames"	the sorted native operation names, including measure and reset
	"CouplingMap"	the directed coupling pairs
	"Spec"	the normalized specification Association

Examples

(10)

Basic Examples

(1)

A device target from a native gate set, a qubit count, and a coupling map: A larger, linearly connected device: Once built, query a property — here the qubit count:

In[1]:=