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

Binary format of charge density output #4964

Closed
14 tasks
kirk0830 opened this issue Aug 15, 2024 · 0 comments · Fixed by #4991
Closed
14 tasks

Binary format of charge density output #4964

kirk0830 opened this issue Aug 15, 2024 · 0 comments · Fixed by #4991
Assignees
Labels
Input&Output Suitable for coders without knowing too many DFT details

Comments

@kirk0830
Copy link
Collaborator

Background

The demand for restarting ABACUS calculation indicates the (infra-)feature caching the state of calculation as precise as possible, the binary format is evitable to be the most reasonable choice.

Describe the solution you'd like

By fixing this issue, I will let ABACUS output the binary charge density by default.

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.
@mohanchen mohanchen added the Input&Output Suitable for coders without knowing too many DFT details label Aug 16, 2024
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 a pull request may close this issue.

2 participants