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

Optimize lightning.tensor by adding direct MPS sites data set #983

Draft
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

LuisAlfredoNu
Copy link
Contributor

Before submitting

Please complete the following checklist when submitting a PR:

  • All new features must include a unit test.
    If you've fixed a bug or added code that should be tested, add a test to the
    tests directory!

  • All new functions and code must be clearly commented and documented.
    If you do make documentation changes, make sure that the docs build and
    render correctly by running make docs.

  • Ensure that the test suite passes, by running make test.

  • Add a new entry to the .github/CHANGELOG.md file, summarizing the
    change, and including a link back to the PR.

  • Ensure that code is properly formatted by running make format.

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


Context:
Optimize lightning.tensor by adding direct MPS sites data set

Description of the Change:
Add the functionality for State Preparation from MPS data. (MPSPrep gate)

Create a new constructor for MPSTNCuda that accepts the following arguments
    A vector of pointers to extend the MPS sites.
    A vector of pointers to tensor data of each site.

Benefits:
Avoid the decomposition from state vector to MPS sites which are expensive and inefficient

Possible Drawbacks:

Related GitHub Issues:
[sc-74709]

Copy link
Contributor

github-actions bot commented Nov 6, 2024

Hello. You may have forgotten to update the changelog!
Please edit .github/CHANGELOG.md with:

  • A one-to-two sentence description of the change. You may include a small working example for new features.
  • A link back to this PR.
  • Your name (or GitHub username) in the contributors section.

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