Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix: improve the precision according to issue#4183 #4460

Merged
merged 2 commits into from
Jun 22, 2024

Conversation

kirk0830
Copy link
Collaborator

@kirk0830 kirk0830 commented Jun 21, 2024

Reminder

  • Have you linked an issue with this pull request?
  • Have you added adequate unit tests and/or case tests for your pull request?
  • Have you noticed possible changes of behavior below or in the linked issue?
  • Have you explained the changes of codes in core modules of ESolver, HSolver, ElecState, Hamilt, Operator or Psi? (ignore if not applicable)

Linked Issue

Fix #4183

Unit Tests and/or Case Tests for my changes

  • A unit test is added for each new feature or bug fix.

What's changed?

  • Example: My changes might affect the performance of the application under certain conditions, and I have tested the impact on various scenarios...

Any changes of core modules? (ignore if not applicable)

  • Example: I have added a new virtual function in the esolver base class in order to ...

@mohanchen mohanchen merged commit 4c0b682 into deepmodeling:develop Jun 22, 2024
13 checks passed
@mohanchen mohanchen added the Input&Output Suitable for coders without knowing too many DFT details label Jun 22, 2024
@kirk0830 kirk0830 deleted the scf-stdout-2 branch June 22, 2024 05:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Input&Output Suitable for coders without knowing too many DFT details
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Refactor: a better looking of SCF stdout
2 participants