v0.14.1

Rimu v0.14.1

Diff since v0.14.0

Interface changes

• The Interface for AbstractHamiltonian and AbstractOperator are changing and will require an operator_column in future. The old interface is still supported for now #317

New features

• The `AbstractHamiltonian
• The function growth_estimator_analysis now allows passing time_step as a keyword argument
• New functions save_state and load_state allow saving DVecs and PDVecs #298, these can include OccupationNumberFS #307
• Convenient constructors for OccupationNumberFS #308
• AllOverlaps is available for excited states #302
• BasisSetRepresentation now works on any AbstractOperator #311
• Matrix free exact diagonalisation refactored and much improved.LinearMap from LinearMaps.jl implemented for AbstractOperators; used in ExactDiagonalizationProblem #306
• Complex-valued operators are now fully supported in ProjectorMonteCarloProblem #313, #315
• ExtendedHubbardReal1D now supports power-law interactions #319

Discontinued features

• save_dvec was already broken due to BSON.jl dependency #298

Bug fixes

• growth_witness now accepts time_step as a keyword argument.
• Bugs in OccupationNumberFS #307 , #308
• momentum_cutoff was not correctly implemented in FroehlichPolaron #316

Merged pull requests:

• Saving/loading vectors (#298) (@mtsch)
• AllOverlaps for Excited States (#302) (@jamie-tay)
• Allow passing time_step to StatsTools functions (#303) (@mtsch)
• CompatHelper: bump compat for KrylovKit in [weakdeps] to 0.9, (keep existing compat) (#304) (@github-actions[bot])
• Better exact diagonalisation (#306) (@mtsch)
• allow saving/loading OccupationNumberFS (#307) (@mtsch)
• Vacuum constructors for OccupationNumberFS (#308) (@joachimbrand)
• Import CompressionStrategy interface explicitly (#309) (@lch)
• Allow any operator in BasisSetRep (#311) (@mtsch)
• Complex Hamiltonians and Walkers (#313) (@jamie-tay)
• Fix check for starting vectors with a complex Hamiltonian (#315) (@jamie-tay)
• Bugfix: momentum_cutoff in FrohlichPolaron (#316) (@joachimbrand)
• Operator Column (#317) (@jamie-tay)
• Feacture/extended range interaction (#319) (@Skuwar1)
• Fix interface tests (#324) (@jamie-tay)

Closed issues:

• Saving DVecs and restarting long calculations from file (#213)

v0.14.0

Rimu v0.14.0

Diff since v0.13.1

Breaking changes

• IDs for replicas and spectral states are swapped: replica ids defining
  the row in the matrix of state_vectors now are appended first and
  spectral ids second. If there is only a single replica, or a single
  spectral state, the respective ids are ommitted.
• Remove BoseFS2C, BoseHubbardMom1D2C, BoseHubbardReal1D2C. These models were moved to another package, see RimuLegacyHamiltonians.jl
• MPIData was removed - use PDVec instead.
• The submodule Rimu.RMPI was removed. The relevant remaining functions are exported at top level.

New features

• new module Rimu.InterfaceTests with functions
• test_observable_interface
• test_operator_interface
• test_hamiltonian_interface
• test_hamiltonian_structure
• ReducedDensityMatrix
• build_basis is faster (using threading) and can work on address type

Deprecations

• in keyword arguments to ProjectorMonteCarloProblem
  • maxlength deprecated, replaced by max_length
  • walltime deprecated, replaced by walltime
• lomc! now prints a deprecation warning

Internal changes

• fix random seeding of tests
• Documentation rework and docstring changes
• remove lomc! from most tests

Bug fixes

• normalisation in single_particle_density

Merged pull requests:

• Excited states (#269) (@jamie-tay)
• Remove MPIData (#270) (@mtsch)
• Fast basis (#287) (@mtsch)
• Feature/reduced density matrix (#289) (@Skuwar1)
• Improve performance of ReducedDensityMatrix (#292) (@mtsch)
• CompatHelper: bump compat for VectorInterface to 0.5, (keep existing compat) (#294) (@github-actions[bot])
• Reduce allocations in ReducedDensityMatrix (#295) (@joachimbrand)
• Update behind commits (#296) (@Skuwar1)
• Move docs to RimuQMC (#297) (@mtsch)
• Interface tests - remove two component models (#299) (@joachimbrand)
• Fix normalisation in single_particle_density (#300) (@mtsch)
• Consistently apply snake_case (#301) (@joachimbrand)

v0.13.1

Rimu v0.13.1

Diff since v0.13.0

New features

• ExtendedHubbardMom1D, new Hamiltonian
• Momentum-space Hubbard Hamiltonians accept a complex hopping parameter: HubbardMom1D, HubbardMom1DEP
• AbstractObservable, new less restrictive supertype for AbstractHamiltonian and AbstractObservable

Bug fixes

See list of merged PRs.

Merged pull requests:

• Fix offdiagonals in two particle density matrix (#281) (@mtsch)
• Fix type instability in Displacements (#282) (@mtsch)
• Feature/dispersion in mom space (#283) (@Skuwar1)
• Fix UndefVarError when setting initial shift as vector (#284) (@mtsch)
• Feature/ExtendedHubbardMom1D (#286) (@Skuwar1)
• remove spurious bracket from show(RatioBlockingResult) (#288) (@christofbradly)
• AbstractObservable supertype (#291) (@joachimbrand)

v0.13.0

Rimu v0.13.0

Diff since v0.12.0

Breaking changes

• Changes to the AbstractHamiltonian interface: The function allowed_address_type is removed and replaced by the function allows_address_type, which takes two arguments, an operator and a type and returns a boolean.

New features

• AbstractOperator is a new abstract type that can be used for operators that are to be used as observables, e.g. for calculating their dot products in the context of a ReplicaStrategy. AbstractOperator is a supertype of AbstractHamiltonian and has a similar interface but doesn't require starting_address.
• VectorInterface.scalartype is defined for AbstractHamiltonian and AbstractOperator to define the underlying scalar type. In contrast, eltype defines the type returned by diagonal_element, offdiagonals, and the three-way dot product. This may be an array for AbstractOperator only. For AbstractHamiltonians the etype and scalartype should be identical.
• Attempting to use a complex Hamiltonian with ProjectorMonteCarloProblem throws an error.
• The SingleParticleExcitation and TwoParticleExcitation operators, which can be used to compute reduced density matrices were added.
• ExtendedHubbardReal1D now supports twisted boundary conditions and complex hopping strengths.
• The number of MPI calls during a projector Monte Carlo run has been reduced.

Merged pull requests:

• Extra boundary conditions (#265) (@Skuwar1)
• Fix the docstring of BasisSetRepresentation (#273) (@joachimbrand)
• Feature/reduced density matrix (#276) (@Skuwar1)
• Observables (#278) (@joachimbrand)
• Fix num_particles for OccupationNumberFS (#279) (@mtsch)
• Reduce the number of collective MPI calls (#280) (@mtsch)

Closed issues:

• Documentation: consistently denote Fock-space operators with hats (#230)
• ERROR: UndefVarError: ProjectorMonteCarloProblem not defined (#259)
• Documentation of releases is not properly saved (#266)

v0.12.0

Rimu v0.12.0

Diff since v0.11.2

Breaking release with a major rework of the user interface.
This release is a transition step where a much of the old user interface
is still there an usable but deprecated. If you get warning messages using
your scripts with this release, please follow instructions and update
your script to be ready for the next breaking release.

New user interface

• CommonSolve.solve is implemented for ProjectorMonteCarloProblem as the main entrance point
  to perform an FCIQMC calculation. Methods for solve, solve!, init are implemented.
  A report in form of a DataFrame can be returned from a simulation but the column names have changed.
• ExactDiagonalizationProblem together with the relevant solve method is a new access point for
  exact diagonalization of AbstractHamiltonians

See PR#248 for a more detailed description of the changes.

Other new features

• LatticeGeometry, PeriodicBoundaries, HardwallBoundaries and LadderBoundaries replaced with CubicGrid.
• Observables with eltype(op) <: AbstractArray are now supported in both dot and for use in AllOverlaps.
• New G2RealSpace operator, which is aware of the geometry and computes G_2 for all displacement vectors at the same time.

Deprecations

• lomc!
• targetwalkers as keyword argument to many ShiftStrategys is deprecated in favor of target_walkers
• FCIQMCRunStrategy and its subtype RunTillLastStep are deprecated.

Breaking changes

• LatticeGeometry no longer exists, PeriodicBoundaries, HardwallBoundaries and LadderBoundaries are no longer separate types. All user code should still run without modifications.
• removed TripleLogUpdate
• lomc! does not accept AbstractMatrix as argument
• new default style=IsDynamicSemistochastic() for default_starting_vector

Merged pull requests:

• Solve interface 3 (#248) (@joachimbrand)
• Exact diagonalization problem (#251) (@joachimbrand)
• Rework Geometry, add new G2 correlator (#254) (@mtsch)
• Bump julia-actions/cache from 1 to 2 (#256) (@dependabot[bot])
• Allow computing estimators directly on a PMCSimulation (#257) (@mtsch)
• Feature/rework mpi example (#258) (@joachimbrand)
• New communication strategy: AllToAll (#260) (@mtsch)
• CompatHelper: bump compat for KrylovKit in [weakdeps] to 0.8, (keep existing compat) (#267) (@github-actions[bot])
• Breaking changes before v1.0 release (#268) (@joachimbrand)
• Make it easier to run continuation runs (#272) (@mtsch)

v0.11.2

Rimu v0.11.2

Diff since v0.11.1

Non-breaking release with a new feature and a number of bug fixes and enhancements.

New features

• New observable ParticleNumberOperator #255

Bug fixes

• Avoid NaNs in harmonic oscillator Hamiltonians working around a bug in HypergeometricFunctions.jl #253

Other changes

• tweaked CI setup for MPI tests #252
• use explicit imports #249
• bump julia-actions/setup-julia #250

Merged pull requests:

• Use explicit imports (#249) (@joachimbrand)
• Bump julia-actions/setup-julia from 1 to 2 (#250) (@dependabot[bot])
• Tweak the CI setup for MPI tests (#252) (@mtsch)
• bugfix: dodge NaN in 3F2 (#253) (@christofbradly)
• ParticleNumberOperator (#255) (@joachimbrand)

v0.11.1

Rimu v0.11.1

Diff since v0.11.0

Non-breaking release with one major new feature and a number of bug fixes and enhancements.

New features

• New AbstractHamiltonian model FroehlichPolaron #237

Changed behaviour

• dimension works separately on address types and AbstractHamiltonian instances
• The AbstractHamiltonian interface definition (via the docstring) had some minor changes and clarification #244
• example scripts were polished #239

Bug fixes

• Testing of the AbstractHamiltonian interface was tightened; some minor bugs discovered and removed #244
• dimension #243

Merged pull requests:

• FroehlichPolaron Hamiltonian (#237) (@joachimbrand)
• Example script polishing (#239) (@mtsch)
• Use caching in GH actions (#240) (@mtsch)
• Bump peter-evans/find-comment from 1 to 3 (#241) (@dependabot[bot])
• Bump peter-evans/create-or-update-comment from 1 to 4 (#242) (@dependabot[bot])
• Fix bug in dimension (#243) (@joachimbrand)
• rework dimension (#244) (@joachimbrand)
• Skip docs and benchmarks on dependabot PRs (#245) (@mtsch)
• Dependabot benchmark and doc ignores, reorganize what action is run when (#246) (@mtsch)

v0.11.0

Rimu v0.11.0

Diff since v0.10.2

A minor breaking release with mostly new functionality and minor changes in behaviour that are strictly breaking, but most old scripts should run without changes.

New features

• Number non-conserving Fock state OccupationNumberFS #234
• Observables SuperfluidCorrelator and StringCorrelator for 1D Hubbard chains #227

Changed behaviour

• Fock states can be constructed by passing occupation numbers directly into constructors for BoseFS, FermiFS, and OccupationNumberFS #234
• Rules related to the initiator method are now exported and can be passed into lomc! with a keyword argument #236

Bug fixes

• in single_particle_density, #225
• in BernoulliSpawning, #233
• Benchmark tune file updated to work with latest package version

Breaking changes

• BoseFS(m::Integer) was previously interpreted as the vacuum state (zero particles) with m modes, but is now interpreted as a state with m particles in a single mode. Use BoseFS(m::Integer, 1=>0) to construct the vacuum state with m modes.

Merged pull requests:

• Fix bug with single_particle_density, integer vectors and CompositeFS (#225) (@mtsch)
• Fix formula in HubbardRealSpace documentation (#226) (@mtsch)
• SuperfluidCorrelator and StringCorrelator (#227) (@rohan-kumar-uoa)
• fix docstring of lomc! (#228) (@joachimbrand)
• Minor fix in RimuIO.load_df and bose_hubbard_interaction docstrings (#229) (@yangmr04)
• Fix probability in Bernoulli spawning (#233) (@mtsch)
• Number non-conserving Fock states (#234) (@joachimbrand)
• Fix failing benchmarks (#235) (@mtsch)
• Service update: Initiators (#236) (@joachimbrand)

Closed issues:

• Bug in single_particle_density with CompositeFS (#224)
• Potential bug in Bernoulli spawning (#232)

v0.10.2

Rimu v0.10.2

Diff since v0.10.1

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
• dτ (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.

Merged pull requests:

• Simplify lomc! arguments (#223) (@joachimbrand)

v0.10.1

Rimu v0.10.1

Diff since v0.10.0

New feature

• Metadata is added to the report DataFrame by lomc! (including custom user metadata). The metadata is also saved to Arrow files and transported by the load_df and save_df functions.

Merged pull requests:

• Metadata support for reports (#222) (@joachimbrand)