NWChemEx / NWChemEx/SimDE

Make EXC a specialization of `BraKet`?

Open
#98 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
0
Forks
0
Avg merge
10h 7m
Merged PRs (30d)
4

Description

Sorry, I now see that I completely misread the diff. I originally thought the ExchangeCorrelationEnergy PT was replacing the ExchangeCorrelationPotential PT, but that's not at all what happened. Making ExchangeCorrelationPotential a specialization of TwoCenterAOTensorRepresentation is the way to go.

As for making EXC a specialization of BraKet, we don't have to do this now (I'll open an issue to revisit this), but I do think it would simplify the code if we do so (in particular I think we get rid of the edge case in the energy evaluation). The name BraKet is perhaps not the greatest, but the BraKet property type covers matrix elements between two (possibly different) many-electron wavefunctions; so it's not just for expectation values. In the context of general DFT, there's no wavefunction so BraKet doesn't make sense, but at least for KS DFT there is a wavefunction so BraKet seems viable. BraKet is templated on the bra and ket wavefunction types, so if it doesn't make sense for BraKet to be defined for anything other than an expectation value we can restrict bra == ket

Originally posted by @ryanmrichard in https://github.com/NWChemEx-Project/SimDE/issues/96#issuecomment-1232027326

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named. Start by reading issue 96 and locating the BraKet and ExchangeCorrelation types; clarify whether the specialization should be pursued and what behavior is expected for energy evaluation. Done requires an agreed scope and corresponding implementation and tests, but this issue does not define concrete acceptance criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
backend-api-design
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.