Skip to content

Hidden cut demo #1401

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

Open
wants to merge 21 commits into
base: master
Choose a base branch
from
Open

Hidden cut demo #1401

wants to merge 21 commits into from

Conversation

simidzija
Copy link


Title: Hidden cut demo

Summary: Completed first draft of hidden cut demo.

Relevant references: N/A

Possible Drawbacks: N/A

Related GitHub Issues: N/A


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

  • GOALS — Why are we working on this now?

    Show a PL implementation of a recent paper (arxiv 2410.12706)

  • AUDIENCE — Who is this for?

    Anyone interested in entanglement or hidden subgroup problems.

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

    Entanglement, Hidden Subgroup Problem, Hidden Cut, StateHSP

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

  • Tutorial
  • Demo
  • How-to

@cognigami cognigami self-requested a review June 10, 2025 20:21
# when it takes light itself 33 billion years to travel between the qubits is one of the most
# philosophically loaded questions at the heart of quantum foundations.
#
# Despite entanglement being so philosophically provocative, it’s somewhat surprising that in fact it
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# Despite entanglement being so philosophically provocative, it’s somewhat surprising that in fact it
# Despite entanglement being so philosophically provocative, it’s somewhat surprising that it is so

# problem related to unentanglement, called the *hidden cut problem*. In this problem we assume that
# we’re given a state consisting of many components. As we discussed, it’ll generally be the case that
# most of these components are entangled with one another. But in the hidden cut problem we are
# guaranteed that it’s possible to split the components up into two groups, so that between the two
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# guaranteed that it’s possible to split the components up into two groups, so that between the two
# guaranteed that it’s possible to split the components into two groups, so that between the two

# , where :math:`\ket{\psi_A}` is a state of system :math:`A` and :math:`\ket{\psi_B}` is a state of
# system :math:`B`. We also use the term *separable* or *factorizable* to describe an unentagled
# state. We’ll usually not bother writing the tensor product sign and just write
# :math:`\ket{\psi} = \ket{\psi_A}\ket{\psi_B}`. And if :math:`\ket{\psi}` isn’t unentangled we say
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"And if ..." could we drop this sentence?

#
# \ket{\psi} = \ket{\psi_S}\ket{\psi_{\bar S}},
#
# but we aren’t told what :math:`S` and :math:`\bar S` are. The hidden cut problem asks us, given
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we move the interjection to the end of the sentence? "The hidden cut problem asks us to determine :math:S and :math:\bar S, given only :math:\ket\psi."

@cognigami
Copy link
Contributor

This is failing because the build environment doesn't include galois (I think). Working on it with the maintainers.

Copy link

Thank you for opening this pull request.

You can find the built site at this link.

Deployment Info:

  • Pull Request ID: 1401
  • Deployment SHA: 809fc69818e2104e12e1c26331e68b90f394eb10
    (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.

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 this pull request may close these issues.

2 participants