Skip to content

Require explicit construction of TimeEvolver for time_evolve #355

Closed

Description

@Yue-Zhengyuan

I want to stop supporting the high-level interface of time evolution

time_evolve(
        psi0::Union{InfinitePEPS, InfinitePEPO}, H::LocalOperator, dt::Number, nstep::Int,
        alg::SimpleUpdate, env0::SUWeight; symmetrize_gates::Bool = false,
        tol::Float64 = 0.0, t0::Number = 0.0, check_interval::Int = 500
    )

thus forcing users to first construct a TimeEvolver, and use

time_evolve(
        it::TimeEvolver{<:SimpleUpdate}; 
        tol::Float64 = 0.0, check_interval::Int = 500
    )

Reasons are:

  • For NTU Neighborhood Tensor Update (NTU) #144, ground state search needs a few more arguments than other purposes: a CTMRG environment, a CTMRG algorithm, and a tolerance for energy change between two checks. I feel frustrated to maintain additional logic in the high-level interface to ensure that a correct combination of arguments is supplied.

  • For ground state search, which already has an (BP or CTMRG) environment to evaluate expectation values, I want to introduce the ability to monitor quantities observables besides the energy during the evolution (Now I feel this is better not to be a built-in feature)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions