QROM demo

[KetpuntoG]

Before submitting

Please complete the following checklist when submitting a PR:

• [ ] Ensure that your tutorial executes correctly, and conforms to the guidelines specified in the README.

• [ ] Remember to do a grammar check of the content you include.

• [ ] All tutorials conform to PEP8 standards. To auto format files, simply pip install black, and then run black -l 100 path/to/file.py.

When all the above are checked, delete everything above the dashed line and fill in the pull request template.

---

Title:

Summary:

Relevant references:

Possible Drawbacks:

Related GitHub Issues:

---

If you are writing a demonstration, please answer these questions to facilitate the marketing process.

• GOALS — Why are we working on this now?

  Eg. Promote a new PL feature or show a PL implementation of a recent paper.

• AUDIENCE — Who is this for?

  Eg. Chemistry researchers, PL educators, beginners in quantum computing.

• KEYWORDS — What words should be included in the marketing post?

• Which of the following types of documentation is most similar to your file? (more details here)

• [ ] Tutorial

• [ ] Demo

• [ ] How-to

[github-actions[bot]]

👋 Hey, looks like you've updated some demos!

🐘 Don't forget to update the dateOfLastModification in the associated metadata files so your changes are reflected in Glass Onion (search and recommendations).

Please hide this comment once the field(s) are updated. Thanks!

[KetpuntoG]

[sc-63852]

[github-actions[bot]]

Thank you for opening this pull request.

You can find the built site at this link.

Deployment Info:

• Pull Request ID: 1123
• Deployment SHA: e5bc6c0993c61cbe00a02a7e8676c4aae73b803e (The Deployment SHA refers to the latest commit hash the docs were built from)

Note: It may take several minutes for updates to this pull request to be reflected on the deployed site.

[josh146]

@KetpuntoG I think this can be changed to merge into the master branch now

[KetpuntoG]

@KetpuntoG I think this can be changed to merge into the master branch now

This includes a lot of changed files and can complicate the review. I will wait for Juan Miguel's review and then I will make the change to master to avoid problems Do you know of a way to rebase and not modify extra files @josh146 ?

[KetpuntoG]

Reopened only to continue the review here

[mudit2812]

@KetpuntoG I think this can be changed to merge into the master branch now

This includes a lot of changed files and can complicate the review. I will wait for Juan Miguel's review and then I will make the change to master to avoid problems Do you know of a way to rebase and not modify extra files @josh146 ?

This might require some fancy git commands. I don't have any suggestions other than using stack overflow or other forums/tools of the sort.