Skip to content
This repository has been archived by the owner on Sep 27, 2021. It is now read-only.

periodic dihedral extrapolation #576

Merged
merged 5 commits into from
Aug 13, 2020
Merged

periodic dihedral extrapolation #576

merged 5 commits into from
Aug 13, 2020

Conversation

marvinbernhardt
Copy link
Contributor

When dealing with dihedrals I ran into problems with the extrapolation. potential_to_gromacs.sh would extrapolate both sides to 180°. If the new potential is then interpolated and the force is calculated, one obtains a very high force for x=180.

This pull request is the solution I came up with. It will ignore the gradient of the last points on the right side and extrapolate linearly to the same value one finds on the left side.

@junghans
Copy link
Member

So we set the force to same value on both side (https://github.com/votca/csg/blob/master/share/scripts/inverse/table_to_xvg.pl#L101)
but the value is too high, correct?

@codecov
Copy link

codecov bot commented Aug 10, 2020

Codecov Report

Merging #576 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff           @@
##           master    #576   +/-   ##
======================================
  Coverage    62.2%   62.2%           
======================================
  Files         124     124           
  Lines        7722    7722           
======================================
  Hits         4805    4805           
  Misses       2917    2917           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b02ead2...693b716. Read the comment docs.

@junghans
Copy link
Member

@marvinbernhardt I am all for merging this as dihedrals aren't very well supported currently. Have a look at my comments above. Do dihedrals always need to go from 0 to 180?

@junghans
Copy link
Member

@votca-bot changelog: add periodic extrapolation for dihedrals

@marvinbernhardt
Copy link
Contributor Author

So we set the force to same value on both side (https://github.com/votca/csg/blob/master/share/scripts/inverse/table_to_xvg.pl#L101)
but the value is too high, correct?

Yes, precisely

@marvinbernhardt
Copy link
Contributor Author

Ups, sorry reverted those codacy changes. Will change again.

@junghans
Copy link
Member

@marvinbernhardt I undid the last two commits, was there a special reason to split the option parsing? I think we can alllow periodic for the left as well, even though we don't have a use case yet.

@junghans junghans merged commit 00db20e into votca:master Aug 13, 2020
votca-bot added a commit to votca/votca that referenced this pull request Aug 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants