Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve Simon's algorithm kata #138

Open
3 tasks
tcNickolas opened this issue Jul 1, 2019 · 1 comment · May be fixed by #327
Open
3 tasks

Improve Simon's algorithm kata #138

tcNickolas opened this issue Jul 1, 2019 · 1 comment · May be fixed by #327

Comments

@tcNickolas
Copy link
Member

Simon's algorithm kata differs from the others in that Simon's algorithm has non-trivial classical processing involved, but the tasks of the kata cover only the (relatively simple) quantum part of the algorithm. This makes it less useful than it could be.

If we want to keep it as a C# project, there will be several steps to improving it:

  • Add C# tasks to cover classical processing in Simon's algorithm.
    They can be part of the same Q# project, it will just have several Tasksfiles.
  • Convert Q# tasks to Q# Notebook.
    This includes investigating whether %kata magic command can invoke C# tests with the updated Q# code.
  • Convert C# tasks to C# Notebook.
    There are several implementations of C# kernel for Jupyter, we need to pick one and use it.

It also could be that the best way to improve this kata is to convert it into Python.

I won't get to this in the next several months; if anybody is interested in picking this up, please let me know!

@tcNickolas tcNickolas added the help wanted Extra attention is needed label Jul 1, 2019
@tcNickolas
Copy link
Member Author

tcNickolas commented Apr 19, 2020

Pull request #327 took the second approach, using a companion Python notebook to cover classical parts of the algorithm.

@tcNickolas tcNickolas removed the help wanted Extra attention is needed label Sep 30, 2020
@tcNickolas tcNickolas linked a pull request Oct 11, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant