Repository navigation
AFQMC - #189
Merged
Merged
AFQMC#189
Conversation
MatthewRHermes
approved these changes
Apr 6, 2026
Collaborator
|
failed unittest is unrelated to PR |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR ports the AFQMC implementation from trot with minimal changes beyond adapting it to PySCF. It adds the AFQMC features described in the recent preprint, including mean field and coupled cluster based trial states, LNO-AFQMC, and free projection.
Two implementation details to flag:
pyscf.afqmc has a JAX runtime dependency, but JAX is not added as a mandatory forge dependency. If JAX is not installed, importing pyscf.afqmc raises a clear error with install guidance.
pyscf.afqmc currently requires python >= 3.10, but this is not imposed as a repo-wide requirement for the rest of the code.
Includes contributions from @Ydrnan, @jokurian, @zh-yichi, @Baljit11, @eirik-kjonstad, @shufay, and @sanshar.