Changeset 333e84 for pcp/src


Ignore:
Timestamp:
Apr 21, 2008, 2:51:03 PM (17 years ago)
Author:
Frederik Heber <heber@…>
Children:
1da479
Parents:
515271
Message:

CalculateForce(): FIX - P0-perturbation took longer and results were not the same compared to initial commit

There were actually two things that came out to have the same cause:
-P0 minimisation took longer than P1,P2,RxP0,...,RxP2 (especially even against the latter)
-minimisation results, i.e. shielding was not the same anymore and in my c2h4 test setting, the two 13C-shielding had a greater mismatch (2.1539 <-> 2.1507 and later 2.12 <-> 2.153)
The cause was the commented-out line PsiStep=MaxPsiStep, which was clearly nonsense and had me puzzled even on checkin

File:
1 edited

Legend:

Unmodified
Added
Removed
  • pcp/src/run.c

    r515271 r333e84  
    10801080    while ((R->LevSNo > R->InitLevSNo) || (!Stop && R->LevSNo == R->InitLevSNo)) {
    10811081      // occupied
    1082       //R->PsiStep = R->MaxPsiStep; // reset in-Psi-minimisation-counter, so that we really advance to the next wave function
     1082      R->PsiStep = R->MaxPsiStep; // reset in-Psi-minimisation-counter, so that we really advance to the next wave function
    10831083      R->OldActualLocalPsiNo = R->ActualLocalPsiNo; // reset OldActualLocalPsiNo, as it might still point to a perturbed wave function from last level
    10841084      UpdateGramSchOldActualPsiNo(P,Psi);
Note: See TracChangeset for help on using the changeset viewer.