Skip to content

Commit

Permalink
Make ProjMPS accessible (#5)
Browse files Browse the repository at this point in the history
  • Loading branch information
emstoudenmire authored May 10, 2024
1 parent 03fe935 commit 896e1b2
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 2 deletions.
2 changes: 1 addition & 1 deletion Project.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "ITensorMPS"
uuid = "0d1a4710-d33b-49a5-8f18-73bdf49b47e2"
authors = ["Matthew Fishman <[email protected]>", "Miles Stoudenmire <[email protected]>"]
version = "0.1.4"
version = "0.1.5"

[deps]
ITensorTDVP = "25707e16-a4db-4a07-99d9-4d67b7af0342"
Expand Down
2 changes: 1 addition & 1 deletion src/ITensorMPS.jl
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ using ITensorTDVP: ITensorTDVP
const alternating_update_dmrg = ITensorTDVP.dmrg
# Not re-exported, but this makes these types and functions accessible
# as `ITensorMPS.x`.
using ITensors.ITensorMPS: AbstractSum, sortmergeterms
using ITensors.ITensorMPS: AbstractSum, ProjMPS, sortmergeterms
@reexport using ITensors.ITensorMPS:
@OpName_str,
@SiteType_str,
Expand Down
1 change: 1 addition & 0 deletions test/runtests.jl
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@ using Test: @test, @test_broken, @testset
# ?
@test_broken ITensorMPS.sortmergeterms === ITensors.sortmergeterms
@test ITensorMPS.AbstractSum === ITensors.ITensorMPS.AbstractSum
@test ITensorMPS.ProjMPS === ITensors.ITensorMPS.ProjMPS
end
end
end

2 comments on commit 896e1b2

@mtfishman
Copy link
Member

Choose a reason for hiding this comment

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

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

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

Registration pull request created: JuliaRegistries/General/106577

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.1.5 -m "<description of version>" 896e1b2977c686bc1df21143b40a888f7d08fc07
git push origin v0.1.5

Please sign in to comment.