Skip to content

Need a formatted file to store some key values of ABACUS, #3104

Closed
@pxlxingliang

Description

@pxlxingliang

Background

Currently, most of the key parameters of ABACUS are output in a readable log file or printed on the screen, which is convenient for users to directly obtain this information by reading the log file, but it is not conducive to our post-processing of ABACUS or the connection with other third-party software.

Describe the solution you'd like

It is suggested to add a standard format data storage file, similar to VASP's vasprun.xml or QE's pwscf.xml, to store the key parameters during the calculation process, such as INPUT settings, fft grid points, symmetry, K points, energy, bands, fermi energy, force, stress, coordinate etc.
Of course, it doesn't have to be in XML format, JSON format is also very good.

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

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions