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

Merge release 2 #283

Merged
merged 25 commits into from
Oct 15, 2024
Merged

Merge release 2 #283

merged 25 commits into from
Oct 15, 2024

Conversation

dreamer2368
Copy link
Collaborator

@dreamer2368 dreamer2368 commented Oct 15, 2024

Merge release branch into ROMFPMD, from PR #277 to PR #281 . While PR #248 ~ #275 are included in the commit history, they are already merged via PR #276 and they do not have any effective change here.

jeanlucf22 and others added 24 commits June 3, 2024 22:33
* clean up/reorganize main.cc
* use shared_ptr in class MGmol
* Add possible periodic dimensions to xyz2in.py
* Exit with failure if density off by more than 2%
* adapt SiH4 test to catch that
* fix bug in DFTsolver that was leading to wrong density
* add example driver, showing use of MGmol as a force/energy computational engine

* clean up related functions in class Ions
Previously, the wrong eigenvalues (0) were printed out because eigenvalues outside solver were not up-to-date.
* Atomic potentials were not updated when atomic positions were changed
* Added test to make sure energies and forces are the same after positions
  move by one mesh spacing
* use specified initial conditions for wavefunctions
* use specified wavefunctions as solution, with unknown DM
* have them work in debug mode too
@dreamer2368 dreamer2368 force-pushed the merge_release2 branch 2 times, most recently from 11f9e10 to 23ea497 Compare October 15, 2024 19:19
@jeanlucf22
Copy link
Collaborator

Ooops... I should not have merged the previous one?

@dreamer2368
Copy link
Collaborator Author

Ooops... I should not have merged the previous one?

I think it should be fine. I updated ROMFPMD branch and re-performed the merge. Depending on how we merge, the merged branch reflects the previous PR history or not. It is not clear to me what determines it, but it seems that PR #276 did not update PR history of ROMFPMD branch. So this PR seems to merge all the previous PRs once again, but the actual change do not reflect them, since they are already merged by PR #276 .

@dreamer2368 dreamer2368 marked this pull request as ready for review October 15, 2024 19:35
@jeanlucf22 jeanlucf22 merged commit b32d686 into ROMFPMD Oct 15, 2024
2 checks passed
@jeanlucf22 jeanlucf22 deleted the merge_release2 branch October 15, 2024 19:42
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