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

Fix TM1/3 when using both batched algorithm and delayed updates #1404

Merged
merged 4 commits into from
Feb 28, 2019

Conversation

ye-luo
Copy link
Contributor

@ye-luo ye-luo commented Feb 26, 2019

  1. Fix Tmove v1 and v3 when using both batched algorithm and delayed updates
  2. Move the state machine invRow_id to the DiracDeterminat class
  3. ratio, ratioGrad, evalGrad inside DelayedUpdate class is not necessary and moved back to DiracDeterminat.

@ghost ghost assigned ye-luo Feb 26, 2019
@ghost ghost added the in progress label Feb 26, 2019
RatioTimer.stop();

// check invRow_id against WorkingIndex to ensure getInvRow() called before ratioGrad()
// This is not a safety check. Some code paths do call ratioGrad without calling evalGrad first.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Commentary: Unfortunate that this is needed, but how would anyone ever know to call evalGrad before calling ratioGrad?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. I have update the comment which is more clear as an optimization.

@ye-luo ye-luo merged commit 7dec28c into QMCPACK:develop Feb 28, 2019
@ghost ghost removed the in progress label Feb 28, 2019
@ye-luo ye-luo deleted the reduce-DU-interface branch March 13, 2019 05:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants