abacus-develop
abacus-develop copied to clipboard
kpar calculation error
Describe the bug
When I set kpar=4 in LCAO calculations, during the SCF, abacus is stopped abnormal:
* * * * * *
<< Start SCF iteration.
ITER TMAG AMAG ETOT/eV EDIFF/eV DRHO TIME/s
GE1 3.15e+01 3.29e+01 -1.01320040e+05 0.00000000e+00 6.8200e-02 25.27
GE2 3.36e+01 3.44e+01 -1.01333408e+05 -1.33677580e+01 3.2150e-02 23.02
GE3 3.37e+01 3.50e+01 -1.01335339e+05 -1.93134518e+00 1.7747e-02 23.00
GE4 3.47e+01 3.60e+01 -1.01335678e+05 -3.38426245e-01 1.0694e-02 22.99
GE5 3.47e+01 3.66e+01 -1.01335964e+05 -2.86198516e-01 5.7317e-03 22.91
GE6 3.49e+01 3.67e+01 -1.01335999e+05 -3.54613168e-02 3.6981e-03 23.06
GE7 3.49e+01 3.68e+01 -1.01335992e+05 7.67498555e-03 2.6695e-03 23.00
GE8 3.48e+01 3.68e+01 -1.01335997e+05 -4.89171828e-03 1.6578e-03 23.00
GE9 3.47e+01 3.68e+01 -1.01336001e+05 -4.65089043e-03 3.4829e-04 23.00
GE10 3.47e+01 3.68e+01 -1.01336001e+05 -1.05952656e-04 2.6453e-04 22.94
GE11 3.48e+01 3.68e+01 -1.01336001e+05 -8.33600483e-05 1.2761e-04 22.96
GE12 3.48e+01 3.68e+01 -1.01336001e+05 -1.66829337e-05 5.5800e-05 22.93
GE13 3.48e+01 3.68e+01 -1.01336001e+05 -2.45205620e-06 3.6140e-05 22.95
GE14 3.48e+01 3.68e+01 -1.01336001e+05 -1.84446519e-06 2.0335e-05 22.99
GE15 3.48e+01 3.68e+01 -1.01336001e+05 -4.00123322e-07 1.1107e-05 22.99
GE16 3.48e+01 3.68e+01 -1.01336001e+05 -2.39393406e-07 6.4698e-06 22.98
GE17 3.48e+01 3.68e+01 -1.01336001e+05 -9.89573590e-08 4.1572e-06 23.00
GE18 3.48e+01 3.68e+01 -1.01336001e+05 -2.81515558e-08 2.7041e-06 22.95
GE19 3.48e+01 3.68e+01 -1.01336001e+05 -1.12234994e-08 1.6258e-06 23.01
GE20 3.48e+01 3.68e+01 -1.01336001e+05 -2.37586757e-09 8.2842e-07 22.94
GE21 3.48e+01 3.68e+01 -1.01336001e+05 1.96751533e-09 5.5777e-07 22.97
===================================================================================
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
= RANK 0 PID 38 RUNNING AT dp-lbg-14037-13933528
= KILLED BY SIGNAL: 9 (Killed)
===================================================================================
Expected behavior
No response
To Reproduce
No response
Environment
No response
Additional Context
No response
Task list for Issue attackers (only for developers)
- [ ] Verify the issue is not a duplicate.
- [ ] Describe the bug.
- [ ] Steps to reproduce.
- [ ] Expected behavior.
- [ ] Error message.
- [ ] Environment details.
- [ ] Additional context.
- [ ] Assign a priority level (low, medium, high, urgent).
- [ ] Assign the issue to a team member.
- [ ] Label the issue with relevant tags.
- [ ] Identify possible related issues.
- [ ] Create a unit test or automated test to reproduce the bug (if applicable).
- [ ] Fix the bug.
- [ ] Test the fix.
- [ ] Update documentation (if necessary).
- [ ] Close the issue and inform the reporter (if applicable).