QuantumKatas icon indicating copy to clipboard operation
QuantumKatas copied to clipboard

Tutorials and programming exercises for learning Q# and quantum computing

Results 39 QuantumKatas issues
Sort by recently updated
recently updated
newest added

Hi! Thanks for these incredible tutorials. I'm reading the QFT Kata, and trying to understand the step from j/2^k -> 0.j_n...j_n-k in Task 1.7 Would anyone be able to elaborate...

Instead of manually applying the adjoints to clean up afterwards, we can use Q#'s very nice `within {...} apply {...}` syntax to do it for us.

### Problem If someone is flawlessly solving notebooks in order that the "Learning Path" suggests, then they will encounter the `ControlledOnInt` operation for the first time in [Oracles tutorial](https://github.com/microsoft/QuantumKatas/blob/main/tutorials/Oracles/Oracles.ipynb). This...

### Issue context While working on some notebooks like `QFT workbook` with jupyter locally, it generates cell ids to all type of cells(code, markdown, etc). This is on not a...

Hi, I've noticed that equations written in math mode are not always rendered correctly in a browser. Fixing this would make the learning experience better for people that use separate...

good first issue

The current approach for the RandomNumberGenerationTutorial tries to generate random numbers from [0, max) until it finds a value in [min, max]. You could make it a bit more efficient...

(This issue is the second part of #208) The katas offer a set of programming exercises on quantum computing and reference solutions to them, but we often hear that it...

help wanted

### Background - In #539 , we excluded tasks in CHSHGame workbook because some tasks required implementing two code cells at once before running the test, so the first of...

In [PR 539 : Updating notebooks validation script to exclude individual tasks](https://github.com/microsoft/QuantumKatas/pull/539), we excluded tasks in CHSHGame and MagicSquareGame because some tasks required implementing two code cells at once before...