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.

Sign up for GitHub

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

Jump to bottom

The TEMPO and PT-TEMPO backend is hard to read #28

Open
gefux opened this issue Nov 16, 2021 · 1 comment
Open

The TEMPO and PT-TEMPO backend is hard to read #28

gefux opened this issue Nov 16, 2021 · 1 comment
Assignees
@gefux
Labels
tidy up Something needs to be tidied up

Comments

@gefux
Copy link
Member

gefux commented Nov 16, 2021

The actual tensor network code underpinning the TEMPO and PT-TEMPO implementations is way to hard to follow. It would be good to tidy up the code and leave a few (but not too many) helpful commands.
@gefux gefux added the tidy up Something needs to be tidied up label Nov 16, 2021
@gefux gefux self-assigned this Nov 16, 2021
@gefux
Copy link
Member Author

gefux commented Jan 27, 2024

Also, since we only have a single backend (using google's TensorNetwork), we should flatten out (remove) the backend structure and lift the computation into tempo.py and pt_tempo.py

@gefux gefux added this to the version 0.5 milestone Jan 27, 2024
@gefux gefux removed this from the version 0.5 milestone Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gefux gefux

Labels
tidy up Something needs to be tidied up
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gefux