Qiskit / Qiskit/documentation

[New Content Request]: End-to-End Quantum Kernel Estimation with Iris Dataset on Real Hardware

Open
#4,908 1 comment 0 reactions 2 assignees View on GitHub

@kcmccormibm is already working on this.

Since Mar 31, 2026.

content 📄 course 🎓
Dominant language
Jupyter Notebook
Stars
106
Forks
223
Avg merge
1d 8h
Merged PRs (30d)
72

Description

URL to the relevant tutorial

https://quantum.cloud.ibm.com/learning/en/courses/quantum-machine-learning/classical-ml-review

Select all that apply
  • new content request
  • typo
  • code bug
  • out-of-date content
  • broken link
  • other
Describe the fix or the content request.

In Quantum Machine Learning (QML), many learners struggle to transition from theoretical "Hello World" circuits to practical data applications on real hardware. I have successfully implemented a complete end-to-end workflow that:

  • Loads the classical Iris dataset using Scikit-Learn.
  • Encodes the features into a ZZFeatureMap.
  • Calculates a Quantum Kernel Matrix using UnitaryOverlap and the SamplerV2 primitive.
  • Executes the job on a real QPU (ibm_fez) using the Batch context manager for optimized queue handling.
  • Visualizes the resulting similarity matrix using a Seaborn heatmap.

I would like to contribute this as a practical lab exercise or an "Applied QML" section to help others see the physical results of quantum state overlap on real-world data.

What value does the new content bring?

Currently, many tutorials use local simulators which hide the complexities of ISA (Instruction Set Architecture) circuits and Batching. This content brings value by:

  • Demonstrating how to use the instance parameter to connect to specific "Open Plan" hubs.
  • Showing the physical reality of noise and diagonal values in real QPU results (as seen in the attached heatmap where the diagonal is ~0.8-0.9 instead of a perfect 1.0 due to gate errors).
  • Bridging the gap between the popular Python data science stack (pandas, seaborn, scikit-learn) and qiskit-ibm-runtime.
Image
For new content requests - if the request is accepted, do you want to write the content?

I will write (or already have written) a draft of the proposed content

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.