Skip to content

Commit

Permalink
bump Crystalline & OptimizationOptimJL compat; bump KdotP to v0.2.5
Browse files Browse the repository at this point in the history
  • Loading branch information
@thchr
thchr committed Oct 2, 2024
1 parent 0c38990 commit af399da
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
6 changes: 3 additions & 3 deletions Project.toml
View file
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "KdotP"
uuid = "c8045c5a-940e-4537-a0b9-cab4a5eb5ca1"
authors = ["Thomas Christensen <tchr@mit.edu> and contributors"]
version = "0.2.4"
version = "0.2.5"

[deps]
Combinatorics = "861a8166-3701-5b0c-9a16-15d98fcdc6aa"
Expand All @@ -17,10 +17,10 @@ Unicode = "4ec0a83e-493e-50e2-b9ac-8f72acf5a8f5"

[compat]
Combinatorics = "1"
Crystalline = "0.4.22, 0.5"
Crystalline = "0.6"
GellMannMatrices = "0.2"
Optimization = "3.21"
OptimizationOptimJL = "0.2.2"
OptimizationOptimJL = "0.2.2, 0.3"
PrecompileTools = "1"
PrettyTables = "2"
RowEchelon = "0.2"
Expand Down
2 changes: 1 addition & 1 deletion src/compare.jl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ function isweyl(H::MonomialHamiltonian{D}) where D
for σᵢ in (σ₁, σ₂, σ₃)
i′ = findfirst(==(σᵢ), H.hs)
if isnothing(i′)
return false # some σ₁, σ₂, σ₃ contribution is absent; cannot be a Weyl point'
return false # some σ₁, σ₂, σ₃ contribution is absent; cannot be a Weyl point
end
# **some** prefactor value; any (not-equal & not-too-simply-related) should be OK...
for a in eachindex(H.cs)
Expand Down

2 comments on commit af399da

@thchr
Copy link
Owner Author

@thchr thchr commented on af399da Oct 2, 2024

Choose a reason for hiding this comment

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

@JuliaRegistrator register

@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/116457

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.2.5 -m "<description of version>" af399dab5b7b63490ba871370d0ef831cbe626ee
git push origin v0.2.5

Please sign in to comment.