Qiskit / Qiskit/documentation

New content to explain the dimension change for the kernel matrix for train and test as 90x90, 30x90

Open
#4,057 0 comments 0 reactions 2 assignees View on GitHub

@kcmccormibm is already working on this.

Since Oct 13, 2025.

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

Description

URL to the relevant course

https://quantum.cloud.ibm.com/learning/en/courses/quantum-machine-learning/quantum-kernel-methods#steps-2-and-3-optimize-problem-and-execute-using-primitives

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

=================== I request a new content ================

Kernel matrix used for training is consisting of the training data of size 90 which gives a 90x90 kernel but the test kernel has a size of 30x90 where the kernel of the (test data, train data) is found out. A considerable explanation on the same and how svc handles it will be highly beneficial for a learner to understand the concept. I also request to show the kernel graphs for easier interpretation.

Image Fig. Kernel matrix for the train data Image Fig. Kernel matrix for the test data

Thank you for reading such a long message.

Best regards,
Sudikin Pramanik
PhD scholar
Quantum Machine Learning
IIT Ropar
India

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.