Skip to content

Conversation

JonathonMisiewicz
Copy link
Contributor

Description

PR #2022 labeled ground-state properties with the method name... even when the method name included "EOM-". So even though ccsd and eom-ccsd compute the same ground state dipole, they weren't given the same name. This PR fixes that.

More fixes to come, but the next PR will be heftier.

Obligatory @bgpeyton ping.

Checklist

  • eom tests pass

Status

  • Ready for review
  • Ready for merge

@JonathonMisiewicz JonathonMisiewicz added api Involves the Psi4 API. How do users access "stuff"? cc For all issues involving the CC module, ground-state energies to response properties. labels Apr 5, 2022
@JonathonMisiewicz JonathonMisiewicz added this to the Psi4 1.6 milestone Apr 5, 2022
Copy link
Contributor

@bgpeyton bgpeyton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah, was this choking in OEProp when you pushed an EOM wfn? or was it computing properly and just giving the redundant name? regardless, good catch.

@JonathonMisiewicz
Copy link
Contributor Author

ah, was this choking in OEProp when you pushed an EOM wfn? or was it computing properly and just giving the redundant name? regardless, good catch.

Computing properly and not giving the expected CCSD DIPOLE. This led to an error when I fixed a bug in AJ's code. That should be fixed in the next cc series PR.

@@ -96,11 +96,11 @@ for transition, data in test_data.items(): # TEST
for property, value in data.items(): # TEST
# Change these numbers to 6 ASAP # TEST
if "EINSTEIN" not in property: # TEST
compare_values(value, wfn.variable(f"CC {transition} {property}"), 6, f"CC {transition} {property}") # TEST
compare_values(value, wfn.variable(f"CCSD {transition} {property}"), 6, f"CCSD {transition} {property}") # TEST
compare_values(value, wfn.variable(f"CC {transition} {property}"), 4, f"CC {transition} {property}") # TEST
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

any clue what the above # Change these numbers to 6 ASAP is about, here? it's suspect if these oscillator strengths aren't matching to at least 1e-6.

Copy link
Contributor Author

@JonathonMisiewicz JonathonMisiewicz Apr 6, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's unjustifiable to check these quantities to 1e-6 when cc refuses to enforce lambda convergence any tighter than 1e-4. I have plans to fix this. See cclambda's sin list.

But that scale of refactoring is outside the scope of this review.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wow. that is highly irregular, and definitely a problem. I'll be looking forward to these refactors. thanks!

Copy link
Contributor

@zachglick zachglick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@JonathonMisiewicz JonathonMisiewicz merged commit b7c163e into psi4:master Apr 6, 2022
@JonathonMisiewicz JonathonMisiewicz deleted the oeprop branch April 6, 2022 13:01
zachglick pushed a commit to zachglick/psi4 that referenced this pull request Apr 18, 2022
* Remove EOM- from prop name when irrelevant

* Loosen cc55
zachglick pushed a commit to zachglick/psi4 that referenced this pull request Apr 18, 2022
* Remove EOM- from prop name when irrelevant

* Loosen cc55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Involves the Psi4 API. How do users access "stuff"? cc For all issues involving the CC module, ground-state energies to response properties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants