QubitLab
IDELearnPlaygroundDocsCommunity
Log in
QubitLab
IDELearnPlaygroundDocsCommunity
Log in
QubitLab
IDELearnPlaygroundDocsCommunity
Log in
HomeLearnCatalogRanksPlaygroundDocs
01 · From an abstract qubit to a device0%

You are reading without signing in. Sign in or continue as guest to take quizzes and climb the ranks.

Learn/QC 203Hardware and Compilation·Lesson 1 of 6

From an abstract qubit to a device

Superconducting circuits, trapped ions, neutral atoms and photons: what each does well.

Intermediate12 min read4 sections · 2 questions+45
By the end you will be able to
  1. 01Name the four leading qubit platforms and one strength and weakness of each.
  2. 02Explain the DiVincenzo criteria in plain words.
PlatformQubitGate timeStrengthWeakness
Superconducting (IBM, Google)current in a circuit at 15 mK20–100 nsfast gates, mature fabricationshort coherence, fixed 2D topology
Trapped ions (Quantinuum, IonQ)electron levels of a single ion10–100 µsall-to-all connectivity, long coherence, best fidelitiesslow gates, hard to scale
Neutral atoms (QuEra, Pasqal)atoms held by laser tweezers≈ 1 µshundreds to thousands of qubits, reconfigurable layoutatom loss, slower cycles
Photonic (PsiQuantum, Xanadu)single photons in waveguides—room temperature, natural networkingprobabilistic gates, photon loss

Whatever the platform, a useful qubit must satisfy the same list (DiVincenzo, 2000): well-defined two-level systems, a way to initialise them, coherence much longer than a gate, a universal gate set, and a reliable measurement. The calibration panels in QubitLab are those criteria turned into numbers for one real IBM machine.

Hands-on

Same circuit, two chips

Compile this three-qubit GHZ circuit for fake_sherbrooke, then for fake_torino. Both are superconducting IBM chips, yet their native two-qubit gate differs: the two CNOTs become ECR gates on the older Eagle chip and CZ gates on the newer Heron chip, each wrapped in RZ and SX rotations. Every platform has its own native gate set, and the compiler translates for you.

OpenQASM 3
OPENQASM 3.0;
include "stdgates.inc";
qubit[3] q;
bit[3] c;
h q[0];
cx q[0], q[1];
cx q[1], q[2];
c = measure q;
Sign in to run (nothing is saved)
Open in the IDE Open in the Playground
Knowledge check

2 questions · one try each counts

Question 1

Which platform offers all-to-all connectivity natively?

Sign in to answer and climb the ranks; you will come back to this lesson.

Question 2

Which platform has the fastest gates but the shortest coherence time?

Sign in to answer and climb the ranks; you will come back to this lesson.

Key takeaway

Every platform trades speed against coherence and connectivity. The compiler's job, next lesson, is to hide those differences from your circuit.

Finished reading?

Knowledge check: 2 questions waiting above. Questions are optional. Mark it complete, or press Next: moving on marks it complete too.

Up next
Lesson 2 · 12 min
Classical Compiler vs. Quantum Transpiler
What happens when you press Compile, explained by comparing it with how C or Python code becomes machine instructions.
Further reading
  • Docs: hardware chapter
More in Hardware and Compilation
  • Transpilation and basis gates
  • Circuit Identities & Gate Cancellation
  • Topology and SWAP cost
Shor's algorithm: the overviewClassical Compiler vs. Quantum Transpiler
In this lesson0%
  1. Introduction
  2. Try it: Same circuit, two chips
  3. Knowledge check
  4. Key takeaway
QubitLab
IDELearnPlaygroundDocsCommunity
Log in
QubitLab
IDELearnPlaygroundDocsCommunity
Log in