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

PT-Gradient #127

Merged
merged 10 commits into from
Jun 1, 2024
Merged

PT-Gradient #127

merged 10 commits into from
Jun 1, 2024

Conversation

eoin-dp-oneill
Copy link
Contributor

@eoin-dp-oneill eoin-dp-oneill commented Apr 12, 2024

PT-Gradient

Here is a pull-request for the PT-Gradient code, with modifications according to feedback from Gerald et al.

  • [ x] The contribution has been discussed and agreed on in the Issue section.
  • [ x] Code contributions do its best to follow the zen of python.
  • [x ] The automated test are all positive:
    • [ x] tox -e py36 (to run pytest) the code tests.
    • [x ] tox -e style (to run pylint) the code style tests.
    • [x ] tox -e docs (to run sphinx) generate the documentation.
  • [x ] Added test for changed/added code.
  • [ x] API code contributions include input checks (defensive code).
  • [ x] API code contributions include helpful error messages.
  • [ x] The documentation has been updated:
    • [ x] docstring for all new functions/methods/classes/modules.
    • [x ] consistent style of all docstrings.
    • [ x] for new modules: /docs/pages/modules.rst has been updated.
    • [ x] for api contributions: /docs/pages/api.rst has been updated.
    • [ x] for api contributions: tutorials and examples have been updated.

There will be a separate pull request for the Performance Testing code.
Hope everything is acceptable here. Let me know if any other improvements/fixes could be made.

Best,
Eoin O.

@eoin-dp-oneill eoin-dp-oneill changed the title Dev v0.5 PT-Gradient Apr 13, 2024
@gefux gefux requested review from gefux and piperfw April 25, 2024 13:33
gefux added 2 commits May 1, 2024 12:06
* Simplify functionality state_gradient and compute_gradient_and_dynamics
* Overhall and simplify tutorial
* Overhall code style (pylint)
* Correct several doc strings
* Add numdifftools in requirements_ci
* Several more minor changes
@gefux gefux marked this pull request as draft May 1, 2024 14:09
@gefux gefux removed the request for review from piperfw May 1, 2024 14:11
@gefux gefux marked this pull request as ready for review May 1, 2024 14:11
Copy link
Member

@gefux gefux left a comment

Choose a reason for hiding this comment

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

Hi @eoin-dp-oneill.
Thank you for your contribution!
I've edited your code a bit in the last couple of days to make it ready for merging. I just pushed two commits to your branch implementing those changes.

One thing that I would need from you is to complete the two lines marked with '???' in gradients.py.
The compute_gradient_and_dynamics() function should a list of ndarrays (not tensornetwork.Node objects). However tensornetwork.Node.get_tensor() does not guarantee a specific order of axis when called without parameters. Could you (@eoin-dp-oneill) please specify the axes order and describe that order also in the docstring?

@gefux gefux merged commit 8d60437 into tempoCollaboration:dev-v0.5 Jun 1, 2024
@gefux
Copy link
Member

gefux commented Jun 1, 2024

Thank you, and congratulations!

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.

None yet

4 participants