molpro: 2021.2.1 -> 2024.3.0 #158
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
markuskowa
force-pushed
the
upd-molpro-2022
branch
from
a8b6b1b
to
243b300
Compare
markuskowa
force-pushed
the
upd-molpro-2022
branch
from
243b300
to
cb65d24
Compare
markuskowa
force-pushed
the
upd-molpro-2022
branch
from
2ab7e77
to
e00b01d
Compare
markuskowa
force-pushed
the
upd-molpro-2022
branch
from
e00b01d
to
56495f2
Compare
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.
https://www.molpro.net/manual/doku.php?id=recent_changes#new_features_of_molpro20243
The following things have changed:
a direct sequence of opt; freq; does not work any more (at least with numerical gradients). A mcscf block in between is now required.Analytic gradients ({rs2;noxec;}) are unstable, when run in a sandbox. It either fails in optg or freq, but runs fine, when run as user outside the sandbox.