Skip to main content
The Classiq executor supports execution on IBM simulators and hardware.

​
Usage

​
Execution on IBM Simulators

from classiq import IBMBackendPreferences

preferences = IBMBackendPreferences(backend_name="Name of requested quantum simulator")
The supported simulators are fake hardware simulators.

​
Execution on IBM Hardware

Execution on IBM hardware requires a valid IBM Quantum Cloud API access token, and access to the requested hardware with an IBM Quantum hub, group, and project name. The access token is the API token that appears at the top of the IBM Quantum Cloud page, when you are logged in. You must create an account with IBM quantum if you do not have one already. IBM Backend Preferences configuration options are described in the sections above and in IBM hardware noise simulation (emulate). 
from classiq import (
    IBMBackendPreferences,
)

preferences = IBMBackendPreferences(
    backend_name="Name of requsted quantum hardware",
    access_token="A Valid API access token to IBM Quantum",
    channel="IBM Cloud Channel",
    instance_crn="IBM Cloud Instance CRN",
    emulate=False,
)

​
IBM hardware noise simulation (emulate)

Set emulate=True on IBMBackendPreferences to run a simulator with a Qiskit noise model inferred from a real IBM Quantum device name (for example ibm_pittsburgh, ibm_boston). You do not pass a separate noise model; backend_name must be one of the IBM backends supported for this path in the SDK (see validation errors if the name is not supported). Requirements and limitations
  • Use real IBM hardware backend names (not fake_* simulators); fake backends already run locally and cannot be combined with emulate=True.
  • With emulate=True, execution does not use IBM Quantum hardware; it uses IBM’s Hardware noise model profile on Classiq’s resources.
from classiq import IBMBackendPreferences

preferences = IBMBackendPreferences(
    backend_name="ibm_pittsburgh",
    access_token="…",
    channel="ibm_cloud",
    instance_crn="…",
    emulate=True,
)

​
Supported Backends

Included hardware:
  • “ibm_kingston”
  • “ibm_boston”
  • “ibm_marrakesh”
  • “ibm_torino”
  • “ibm_fez”
  • “ibm_pittsburg”