You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the next few months, in order to make the ABACUS framework more suitable for collaborative development, the ABACUS development team will focus on several aspects of code refactoring to remove unnecessary data structure dependencies and decouple all code elements, thus achieving higher development efficiency.
The name of the plan and the associated issue label is "The Absolute Zero".
The followings are the things we will do
Refactor the grid integral code under the LCAO basis set (including CPU and GPU code).
Remove all global classes of GlobalC and try to eliminate GlobalV global variables; for the remaining GlobalV global variables, they will be made non-arbitrarily modifiable by the user.
Redesign the INPUT class and its usage methods. In the future, INPUT will not be treated as a globally accessible class. The new INPUT class will be easier to support Python integration.
Redesign the Cell class to decouple unnecessary elements from modules within Cell. The new Cell class will also be tailored for easier Python integration.
Refactor the HSolver module to support multiple precision calculations and various hardware computations, with the hope of isolating the HSolver module and providing Python integration for it.
ESolver reconstruction to better accommodate the concurrent development of various DFT methods, including the DP method.
Adopt a uniform format for standardizing the filenames of physical quantities and use a unified code framework to standardize the output of physical quantities.
Delete LCAO_Matrix, ORB_control, Local_Orbital_wfc, Local_Orbital_Charge, LCAO_gen_fixedH in esolver_ks_lcao.h
Additional Context
No response
Task list for Issue attackers (only for developers)
Identify the specific code file or section with the code quality issue.
Investigate the issue and determine the root cause.
Research best practices and potential solutions for the identified issue.
Refactor the code to improve code quality, following the suggested solution.
Ensure the refactored code adheres to the project's coding standards.
Test the refactored code to ensure it functions as expected.
Update any relevant documentation, if necessary.
Submit a pull request with the refactored code and a description of the changes made.
This discussion was converted from issue #4159 on May 23, 2024 01:58.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Describe the Code Quality Issue
In the next few months, in order to make the ABACUS framework more suitable for collaborative development, the ABACUS development team will focus on several aspects of code refactoring to remove unnecessary data structure dependencies and decouple all code elements, thus achieving higher development efficiency.
The name of the plan and the associated issue label is "The Absolute Zero".
The followings are the things we will do
Additional Context
No response
Task list for Issue attackers (only for developers)
Beta Was this translation helpful? Give feedback.
All reactions