Skip to content

Feature: (embedded) Natural Resonance Theory (NRT) analysis for periodic system might be useful and attractive #3695

@kirk0830

Description

@kirk0830

Background

In chemical-related community, people may care about the strength of chemical bond, which is a classical model to interpret the stability of substances and reaction thermodynamics and kinetics. Although bond order analysis like Mayer bond order analysis and several population analysis methods are well-developed, a decomposition of chemical bonds into "covalent component" and "ionic component" might still be helpful for analysis chemical bond strength with more details. Natural Resonance Theory (NRT) is a method projecting optimized wavefunction onto several Valence-Bond (VB)-like many-electron wavefunctions, normalize the projection, like decompose the optimized wavefunction into several interested resonance structure. An example would be, even if two chemical bonds have identical bond orders, they may still be different in bond composition, I mean how many percentage of covalent part and how many ionic part, this will be a reference to discuss about thermal stability of substances. But, all these are, unfortunately mainly in classical quantum chemistry field well-developed where isolated systems are main to investigate.
Instead in periodic system, two aspects are worthwhile to talk about, the first one is support of periodic system wavefunction analysis by Multiwfn, the other is the condition of still "to-be-developed" wavefunction analysis methods. LCAO methods of constructing wavefunction provide good chances and easy mode for/of transferring those analysis methods to periodic system calculation.

Application example:

Reference:

Describe the solution you'd like

Eventually more and more analysis methods should be supported because one single wavefunction solving software is far from enough, people care more about properties one software can calculate.

Task list only for developers

  • Notice possible changes of behavior
  • Explain the changes of codes in core modules of ESolver, HSolver, ElecState, Hamilt, Operator or Psi

Notice Possible Changes of Behavior (Reminder only for developers)

No response

Notice any changes of core modules (Reminder only for developers)

No response

Notice Possible Changes of Core Modules (Reminder only for developers)

No response

Additional Context

No response

Task list for Issue attackers (only for developers)

  • Review and understand the proposed feature and its importance.
  • Research on the existing solutions and relevant research articles/resources.
  • Discuss with the team to evaluate the feasibility of implementing the feature.
  • Create a design document outlining the proposed solution and implementation details.
  • Get feedback from the team on the design document.
  • Develop the feature following the agreed design.
  • Write unit tests and integration tests for the feature.
  • Update the documentation to include the new feature.
  • Perform code review and address any issues.
  • Merge the feature into the main branch.
  • Monitor for any issues or bugs reported by users after the feature is released.
  • Address any issues or bugs reported by users and continuously improve the feature.

Metadata

Metadata

Labels

Feature DiscussedThe features will be discussed first but will not be implemented soon

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions