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

Test the correctness of the modified MD module #4248

Closed
wants to merge 17 commits into from

Conversation

Zjhjunhao
Copy link

Reminder

  • Have you linked an issue with this pull request?
  • Have you added adequate unit tests and/or case tests for your pull request?
  • Have you noticed possible changes of behavior below or in the linked issue?
  • Have you explained the changes of codes in core modules of ESolver, HSolver, ElecState, Hamilt, Operator or Psi? (ignore if not applicable)

Linked Issue

Fix #...

Unit Tests and/or Case Tests for my changes

  • A unit test is added for each new feature or bug fix.

What's changed?

  • Example: My changes might affect the performance of the application under certain conditions, and I have tested the impact on various scenarios...

Any changes of core modules? (ignore if not applicable)

  • Example: I have added a new virtual function in the esolver base class in order to ...


void Verlet::anderson_set_vel(void)
{
double deviation;
Copy link
Collaborator

Choose a reason for hiding this comment

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

initialize the variable

@@ -269,38 +269,82 @@ void MSST::rescale(std::ofstream& ofs, const double& volume)

void MSST::propagate_vel(void)
{
if (mdp.my_rank == 0)
#ifndef __MPI
Copy link
Collaborator

Choose a reason for hiding this comment

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

is there a better way to write "MPI" and "not MPI" codes?

@mohanchen mohanchen changed the title Test the correctness of the modified code Test the correctness of the modified MD module May 30, 2024
@mohanchen
Copy link
Collaborator

Since no updates for a few weeks, I will close this PR.

@mohanchen mohanchen closed this Jun 15, 2024
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