Skip to content

Commit

Permalink
bump version for release
Browse files Browse the repository at this point in the history
  • Loading branch information
joachimbrand committed Nov 26, 2023
1 parent d6e0dc9 commit 249cea4
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Project.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "Rimu"
uuid = "c53c40cc-bd84-11e9-2cf4-a9fde2b9386e"
authors = ["Joachim Brand <j.brand@massey.ac.nz>"]
version = "0.10.1"
version = "0.10.2"

[deps]
Arrow = "69666777-d1a9-59fb-9406-91d4454c9d45"
Expand Down

2 comments on commit 249cea4

@joachimbrand
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@JuliaRegistrator register

Release notes:

A non-breaking restructure of the keyword arguments for lomc!(). More parameters of an FCIQMC calculation can be passed directly as keyword arguments to lomc!() reducing the need to pre-construct the initial vector and strategy-type arguments.

The script BHM-example.jl is redone.

Changed and modified keyword argument to lomc!()

  • address (new) - used for starting vector and initial shift
  • threading (reinstated) - controls parallelism and is used for initial starting vector
  • shift (new) - initial value of shift
  • (now documented) - initial time step
  • targetwalkers (new) - target norm for DoubleLogUpdate

New functions

  • default_starting_vector - the default starting vector for lomc!

The keyword argument params::FciqmcRunStrategy is now obsolete (though still accepted). In practice it should now rarely be necessary to explicitly construct the starting vector v and the s_strat::ShiftStrategy=DoubleLogUpdate keyword argument.

Breaking changes

No breaking changes.

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

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.10.2 -m "<description of version>" 249cea46f0c2fc04743f4840cbd3d4c0af707baf
git push origin v0.10.2

Please sign in to comment.