fix a bug about "end_indx" in opavg_driver.f90 #198
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There is a bug in line 99: "end_indx(1, 2, myid+1): end_indx(1, 2, myid+1)", it should be "end_indx(1, 2, myid+1): end_indx(2, 2, myid+1)".
|
Thanks Yilin! I think we should prioritize merging this and disseminating the new version. Did you run a test to see this fixed the issue? If so can you copy or attach the code here. At some point, it would be good to put this in the test suite later on. |
I agree. I did run a test, which is attached here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is a bug in line 99: "end_indx(1, 2, myid+1): end_indx(1, 2, myid+1)", it should be "end_indx(1, 2, myid+1): end_indx(2, 2, myid+1)". This will fix the problem about calculating the expectation value of an operator by using opavg.x.