Skip to content

Potential Renamings (API breaking) #29

Description

@bkesk

Originally by Ryan Levy.

There are a few options that could be updated, or made consistent but would cause the API to change

  • write_model_hamilton 0cdf290ae21637f6fa49f10c88de98cf4fe51b9a
  • Beginning AFQMC 421a9563e42a0953969232eea2f491e07b94ef59
  • accumlate_interval to accumulate_interval This has been removed and absorbed into population control.
  • apply_constrain to apply_constraint to match use_cp_constraint
  • use_real_vbias sometimes enforces complex vbias, maybe project_vbias?

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