gg?dZddlZddlmZddlmZmZmZmZmZm Z m Z ddl Z ddl m Z ddlmZddlmZddlmZdd lmZdd lmZdd lmZmZdd lmZmZmZdd lm Z ddl!m"Z"m#Z#ddl$m%Z%ddl&m'Z'ddl(m)Z)ddl*m+Z+ddl,m-Z-ddl.m/Z/ej0e1Z2e deeeefZ3e-ddddde-ddddde-ddddd e/d!d"# dFd(e3d)e ed*e ee4d!e eed+e eeeee5fde ed,e eeeefd-e e4d.e e4d/e e4d0e e4de e%d1e e6d2e e6de ee4e5fd3e e5d4e e5d5e ee ee6ee5gefd6e ee4ee4fd7e4d8e e7d9e e+d:e e'd;e e4de e5d?e8d@e3f:dAZ9dBZ:dCZ;dDZr/Es HD 1 :class:`~.QuantumCircuit` object, depending on the local environment and configuration. The prioritization of transpilation target constraints works as follows: if a ``target`` input is provided, it will take priority over any ``backend`` input or loose constraints (``basis_gates``, ``inst_map``, ``coupling_map``, ``backend_properties``, ``instruction_durations``, ``dt`` or ``timing_constraints``). If a ``backend`` is provided together with any loose constraint from the list above, the loose constraint will take priority over the corresponding backend constraint. This behavior is independent of whether the ``backend`` instance is of type :class:`.BackendV1` or :class:`.BackendV2`, as summarized in the table below. The first column in the table summarizes the potential user-provided constraints, and each cell shows whether the priority is assigned to that specific constraint input or another input (`target`/`backend(V1)`/`backend(V2)`). ============================ ========= ======================== ======================= User Provided target backend(V1) backend(V2) ============================ ========= ======================== ======================= **basis_gates** target basis_gates basis_gates **coupling_map** target coupling_map coupling_map **instruction_durations** target instruction_durations instruction_durations **inst_map** target inst_map inst_map **dt** target dt dt **timing_constraints** target timing_constraints timing_constraints **backend_properties** target backend_properties backend_properties ============================ ========= ======================== ======================= Args: circuits: Circuit(s) to transpile backend: If set, the transpiler will compile the input circuit to this target device. If any other option is explicitly set (e.g., ``coupling_map``), it will override the backend's. basis_gates: List of basis gate names to unroll to (e.g: ``['u1', 'u2', 'u3', 'cx']``). If ``None``, do not unroll. inst_map: DEPRECATED. Mapping of unrolled gates to pulse schedules. If this is not provided, transpiler tries to get from the backend. If any user defined calibration is found in the map and this is used in a circuit, transpiler attaches the custom gate definition to the circuit. This enables one to flexibly override the low-level instruction implementation. This feature is available iff the backend supports the pulse gate experiment. coupling_map: Directed coupling map (perhaps custom) to target in mapping. If the coupling map is symmetric, both directions need to be specified. Multiple formats are supported: #. ``CouplingMap`` instance #. List, must be given as an adjacency matrix, where each entry specifies all directed two-qubit interactions supported by backend, e.g: ``[[0, 1], [0, 3], [1, 2], [1, 5], [2, 5], [4, 1], [5, 3]]`` backend_properties: properties returned by a backend, including information on gate errors, readout errors, qubit coherence times, etc. Find a backend that provides this information with: ``backend.properties()`` initial_layout: Initial position of virtual qubits on physical qubits. If this layout makes the circuit compatible with the coupling_map constraints, it will be used. The final layout is not guaranteed to be the same, as the transpiler may permute qubits through swaps or other means. Multiple formats are supported: #. ``Layout`` instance #. Dict * virtual to physical:: {qr[0]: 0, qr[1]: 3, qr[2]: 5} * physical to virtual:: {0: qr[0], 3: qr[1], 5: qr[2]} #. List * virtual to physical:: [0, 3, 5] # virtual qubits are ordered (in addition to named) * physical to virtual:: [qr[0], None, None, qr[1], None, qr[2]] layout_method: Name of layout selection pass ('trivial', 'dense', 'sabre'). This can also be the external plugin name to use for the ``layout`` stage. You can see a list of installed plugins by using :func:`~.list_stage_plugins` with ``"layout"`` for the ``stage_name`` argument. routing_method: Name of routing pass ('basic', 'lookahead', 'stochastic', 'sabre', 'none'). Note This can also be the external plugin name to use for the ``routing`` stage. You can see a list of installed plugins by using :func:`~.list_stage_plugins` with ``"routing"`` for the ``stage_name`` argument. translation_method: Name of translation pass (``"translator"`` or ``"synthesis"``) This can also be the external plugin name to use for the ``translation`` stage. You can see a list of installed plugins by using :func:`~.list_stage_plugins` with ``"translation"`` for the ``stage_name`` argument. scheduling_method: Name of scheduling pass. * ``'as_soon_as_possible'``: Schedule instructions greedily, as early as possible on a qubit resource. (alias: ``'asap'``) * ``'as_late_as_possible'``: Schedule instructions late, i.e. keeping qubits in the ground state when possible. (alias: ``'alap'``) If ``None``, no scheduling will be done. This can also be the external plugin name to use for the ``scheduling`` stage. You can see a list of installed plugins by using :func:`~.list_stage_plugins` with ``"scheduling"`` for the ``stage_name`` argument. instruction_durations: Durations of instructions. Applicable only if scheduling_method is specified. The gate lengths defined in ``backend.properties`` are used as default. They are overwritten if this ``instruction_durations`` is specified. The format of ``instruction_durations`` must be as follows. The `instruction_durations` must be given as a list of tuples [(instruction_name, qubits, duration, unit), ...]. | [('cx', [0, 1], 12.3, 'ns'), ('u3', [0], 4.56, 'ns')] | [('cx', [0, 1], 1000), ('u3', [0], 300)] If unit is omitted, the default is 'dt', which is a sample time depending on backend. If the time unit is 'dt', the duration must be an integer. dt: Backend sample time (resolution) in seconds. If ``None`` (default), ``backend.configuration().dt`` is used. approximation_degree (float): heuristic dial used for circuit approximation (1.0=no approximation, 0.0=maximal approximation) timing_constraints: An optional control hardware restriction on instruction time resolution. A quantum computer backend may report a set of restrictions, namely: - granularity: An integer value representing minimum pulse gate resolution in units of ``dt``. A user-defined pulse gate should have duration of a multiple of this granularity value. - min_length: An integer value representing minimum pulse gate length in units of ``dt``. A user-defined pulse gate should be longer than this length. - pulse_alignment: An integer value representing a time resolution of gate instruction starting time. Gate instruction should start at time which is a multiple of the alignment value. - acquire_alignment: An integer value representing a time resolution of measure instruction starting time. Measure instruction should start at time which is a multiple of the alignment value. This information will be provided by the backend configuration. If the backend doesn't have any restriction on the instruction time allocation, then ``timing_constraints`` is None and no adjustment will be performed. seed_transpiler: Sets random seed for the stochastic parts of the transpiler optimization_level: How much optimization to perform on the circuits. Higher levels generate more optimized circuits, at the expense of longer transpilation time. * 0: no optimization * 1: light optimization * 2: heavy optimization * 3: even heavier optimization If ``None``, level 2 will be chosen as default. callback: A callback function that will be called after each pass execution. The function will be called with 5 keyword arguments, | ``pass_``: the pass being run. | ``dag``: the dag output of the pass. | ``time``: the time to execute the pass. | ``property_set``: the property set. | ``count``: the index for the pass execution. The exact arguments passed expose the internals of the pass manager, and are subject to change as the pass manager internals change. If you intend to reuse a callback function over multiple releases, be sure to check that the arguments being passed are the same. To use the callback feature, define a function that will take in kwargs dict and access the variables. For example:: def callback_func(**kwargs): pass_ = kwargs['pass_'] dag = kwargs['dag'] time = kwargs['time'] property_set = kwargs['property_set'] count = kwargs['count'] ... transpile(circ, callback=callback_func) output_name: A list with strings to identify the output circuits. The length of the list should be exactly the length of the ``circuits`` parameter. unitary_synthesis_method (str): The name of the unitary synthesis method to use. By default ``'default'`` is used. You can see a list of installed plugins with :func:`.unitary_synthesis_plugin_names`. unitary_synthesis_plugin_config: An optional configuration dictionary that will be passed directly to the unitary synthesis plugin. By default this setting will have no effect as the default unitary synthesis method does not take custom configuration. This should only be necessary when a unitary synthesis plugin is specified with the ``unitary_synthesis_method`` argument. As this is custom for each unitary synthesis plugin refer to the plugin documentation for how to use this option. target: A backend transpiler target. Normally this is specified as part of the ``backend`` argument, but if you have manually constructed a :class:`~qiskit.transpiler.Target` object you can specify it manually here. This will override the target from ``backend``. hls_config: An optional configuration class :class:`~qiskit.transpiler.passes.synthesis.HLSConfig` that will be passed directly to :class:`~qiskit.transpiler.passes.synthesis.HighLevelSynthesis` transformation pass. This configuration class allows to specify for various high-level objects the lists of synthesis algorithms and their parameters. init_method: The plugin name to use for the ``init`` stage. By default an external plugin is not used. You can see a list of installed plugins by using :func:`~.list_stage_plugins` with ``"init"`` for the stage name argument. optimization_method: The plugin name to use for the ``optimization`` stage. By default an external plugin is not used. You can see a list of installed plugins by using :func:`~.list_stage_plugins` with ``"optimization"`` for the ``stage_name`` argument. ignore_backend_supplied_default_methods: If set to ``True`` any default methods specified by a backend will be ignored. Some backends specify alternative default methods to support custom compilation target-specific passes/plugins which support backend-specific compilation techniques. If you'd prefer that these defaults were not used this option is used to disable those backend-specific defaults. num_processes: The maximum number of parallel processes to launch for this call to transpile if parallel execution is enabled. This argument overrides ``num_processes`` in the user configuration file, and the ``QISKIT_NUM_PROCS`` environment variable. If set to ``None`` the system default or local user configuration will be used. qubits_initially_zero: Indicates whether the input circuit is zero-initialized. Returns: The transpiled circuit(s). Raises: TranspilerError: in case of bad inputs to transpiler (like conflicting parameters) or errors in passes c3@K|]}t|tVdSr,) isinstancer).0cs r. ztranspile..Ns, 5 5q:a " " 5 5 5 5 5 5r0z+Transpiling schedules is not supported yet.rNtranspile_optimization_levelversionzKThe `transpile` function will stop supporting inputs of type `BackendV1` ( z ) in the `backend` parameter in a future release no earlier than 2.0. `BackendV1` is deprecated and implementations should move to `BackendV2`.)category stacklevelignorez9.+qiskit\.providers\.backend_compat\.BackendV2Converter.+qiskit)rWmessagemodulez]When scheduling circuits without backend, 'instruction_durations' should be usually provided.get_scheduling_stage_pluginget_translation_stage_pluginz/.*``inst_map`` is deprecated as of Qiskit 1.3.*z9.*``timing_constraints`` is deprecated as of Qiskit 1.3.*z<.*``instruction_durations`` is deprecated as of Qiskit 1.3.*z9.*``backend_properties`` is deprecated as of Qiskit 1.3.*rEr5r6r7r!r)r(r*r8r9r:r;r<r>r?rCrDrFrGrHr=rK)rArJ)rOlistrallwarningswarn UserWarning_log_transpile_timer get_configgetgetattrDeprecationWarningcatch_warningsfilterwarningsrhasattrr]r^_parse_output_name_parse_coupling_map_check_circuits_coupling_maprrunzipr#)$r4r5r6r*r7r)r8r9r:r;r<r!r=r>r(r?r@rArBrCrDrErFrGrHrIrJrKarg_circuits_list start_timeend_timeconfigpm out_circuitsr#circs$ r. transpilerx+sv#8T22, (- *>  21 0/ "6!5 ,O! "&>%=# $-L,K% &"z' ($ ) *!4 3+ ,r- .#8"7/ 31 1 1 1 1 1 1 1 1 1 1 1 1 1 1 f66(X]6SSL+|44 d vvH H---As%-D::D>D>8CKK  K c d}||}n ||j}|D]<}t|j}|$||krt d|d|jd|d=dS)NzNumber of qubits (z) in z is greater than maximum (z) in the coupling_map)size num_qubitslenqubitsrr#)r4cmapr5 max_qubitscircuitr{s r.rnrnsJ YY[[  ' ((  !zJ'>'>)NZNNglNN,6NNN  r0cTd||z dzdd}t|dS)NzTotal Transpile Time - iz.5fz (ms))loggerinfo)rrrslog_msgs r.rdrds7S(Z*?4)GSSSSG KKr0ct|tr(td|Drt|St|trt d|S)Nc3fK|],}t|tot|dkV-dS)rTN)rOr_r|)rPis r.rRz&_parse_coupling_map..sL..01 1d+A! ......r0zOnly a single input coupling map can be used with transpile() if you need to target different coupling maps for different circuits you must call transpile() multiple times)rOr_r`rr)r7s r.rmrms,%% #..5A...++ <((( L$ ' '    r0c|t|tr%t|dkr|gStdt|trJt|t|krt d|Dr|Stdtdt |dd|DS)NrVzYExpected a list object of length equal to that of the number of circuits being transpiledc3@K|]}t|tVdSr,)rOstr)rPr#s r.rRz%_parse_output_name..s=99*. 4%%999999r0z}The length of output_name list must be equal to the number of transpiled circuits and the output_name list should be strings.zBThe parameter output_name should be a string or alist of strings: z was used.cg|] }|j Sr-)r#)rPrs r. z&_parse_output_name..s555 555r0)rOrr|rr_r`type)rBr4s r.rlrls k3 ' ' 8}}!!#}$&)  T * * 8}}K 0 000S992=999660#"%."B$($5$5BBB  65H5555r0)NNNNNNNNNNNNr2NNNNNr3NNNNNFNT)>__doc__loggingrtypingrrrrrr r rarZr qiskit.circuit.quantumcircuitr qiskit.dagcircuitr qiskit.providers.backendrqiskit.providers.backend_compatr)qiskit.providers.models.backendpropertiesr qiskit.pulserrqiskit.transpilerrrrqiskit.transpiler.basepassesrqiskit.transpiler.exceptionsrr'qiskit.transpiler.instruction_durationsr7qiskit.transpiler.passes.synthesis.high_level_synthesisr%qiskit.transpiler.preset_passmanagersrqiskit.transpiler.targetr qiskit.utilsrqiskit.utils.deprecate_pulser getLogger__name__rrrintfloatdictboolrxrnrdrmrlr-r0r.rs?! FFFFFFFFFFFFFFFFFF888888((((((,,,,,,>>>>>>GGGGGG99999999>>>>>>>>>>111111QQQQQQQQLLLLLLMMMMMMNNNNNN++++++&&&&&&<<<<<<  8 $ $ GKu^T.=Q-Q'R S S S  $B   $?   $Z Z+P+PQQQ"&'+7;BF6::>#'$((,'+@D,/37%)(,Y]37$-6:#&*!%)-49#'"&9DDD g D$s)$Dt234 D 5d49o!=>? D !!23 DU64#567DC=DSMD! D }D$$<=D D#5/D!c3h0D c]!D"! #D$x:uk3 OQT TUV%D&%T#Y/0'D(")D*&.d^+D, V -D.#/D0#1D2"#3D4.25D6C=7D8 9D:;DDDRQ6DN $    !6!6!6!6!6r0