GenericBackendV2

qiskit.providers.fake_provider.GenericBackendV2(num_qubits, basis_gates=None, *, coupling_map=None, control_flow=False, calibrate_instructions=None, dtm=None, seed=None)

Bases: BackendV2

Generic BackendV2 implementation with a configurable constructor. This class will return a BackendV2 instance that runs on a local simulator (in the spirit of fake backends) and contains all the necessary information to test backend-interfacing components, such as the transpiler. A GenericBackendV2 instance can be constructed from as little as a specified num_qubits, but users can additionally configure the basis gates, coupling map, ability to run dynamic circuits (control flow instructions), instruction calibrations and dtm. The remainder of the backend properties are generated by randomly sampling from default ranges extracted from historical IBM backend data. The seed for this random generation can be fixed to ensure the reproducibility of the backend output. This backend only supports gates in the standard library, if you need a more flexible backend, there is always the option to directly instantiate a Target object to use for transpilation.

Parameters

• num_qubits (int(opens in a new tab)) – Number of qubits that will be used to construct the backend’s target. Note that, while there is no limit in the size of the target that can be constructed, this backend runs on local noisy simulators, and these might present limitations in the number of qubits that can be simulated.

• basis_gates (list(opens in a new tab)[str(opens in a new tab)] | None) – List of basis gate names to be supported by the target. These must be part of the standard qiskit circuit library. The default set of basis gates is ["id", "rz", "sx", "x", "cx"] The "reset", "delay", and "measure" instructions are always supported by default, even if not specified via basis_gates.

• coupling_map (list(opens in a new tab)[list(opens in a new tab)[int(opens in a new tab)]] | CouplingMap | None) –

  Optional coupling map for the backend. Multiple formats are supported:

  1. CouplingMap instance
  2. List, must be given as an edge list representing the two qubit interactions supported by the backend, for example: [[0, 1], [0, 3], [1, 2], [1, 5], [2, 5], [4, 1], [5, 3]]

  If coupling_map is specified, it must match the number of qubits specified in num_qubits. If coupling_map is not specified, a fully connected coupling map will be generated with num_qubits qubits.

• control_flow (bool(opens in a new tab)) – Flag to enable control flow directives on the target (defaults to False).

• calibrate_instructions (bool(opens in a new tab) |InstructionScheduleMap | None) –

  Instruction calibration settings, this argument supports both boolean and InstructionScheduleMap as input types, and is None by default:

  1. If calibrate_instructions==None, no calibrations will be added to the target.

  2. If calibrate_instructions==True, all gates will be calibrated for all

     qubits using the default pulse schedules generated internally.

  3. If calibrate_instructions==False, all gates will be “calibrated” for

     all qubits with an empty pulse schedule.

  4. If an InstructionScheduleMap instance is given, the calibrations

     in this instruction schedule map will be appended to the target instead of the default pulse schedules (this allows for custom calibrations).

• dtm (float(opens in a new tab) | None) – System time resolution of output signals in nanoseconds. None by default.

• seed (int(opens in a new tab) | None) – Optional seed for generation of default values.

Attributes

coupling_map

dt

dtm

instruction_durations

instruction_schedule_map

instructions

max_circuits

meas_map

num_qubits

operation_names

operations

options

provider

target

version

name

description

online_date

backend_version

Methods

acquire_channel

control_channel

drive_channel

measure_channel

qubit_properties

run

set_options