 |
 |
 |
| |
|
|
The aim of this tutorial is to introduce the users to the use of constant biases in PLUMED and their application to perform a simple Umbrella Sampling WHAM simulation.
The TARBALL for this tutorial contains the following files:
Also notice that the .solutions direction of the tarball contains correct input files for the exercises. This tutorial has been tested with version 2.5.
PLUMED can calculate conformational properties of a system a posteriori as well as on-the-fly. This information can be use to manipulate a simulation on-the-fly. This means adding energy terms in addition to those of the original Hamiltonian. This additional energy terms are usually referred as Bias. In the following we will see how to apply a constant bias potential with PLUMED. It is preferable to run each exercise in a separate folder.
A system at temperature \( T\) samples conformations from the canonical ensemble:
\[ P(q)\propto e^{-\frac{U(q)}{k_BT}} \]
. Here \( q \) are the microscopic coordinates and \( k_B \) is the Boltzmann constant. Since \( q \) is a highly dimensional vector, it is often convenient to analyze it in terms of a few collective variables (see Lugano tutorial: Brief guide to PLUMED syntax and analyzing trajectories ). The probability distribution for a CV \( s\) is
\[ P(s)\propto \int dq e^{-\frac{U(q)}{k_BT}} \delta(s-s(q)) \]
This probability can be expressed in energy units as a free energy landscape \( F(s) \):
\[ F(s)=-k_B T \log P(s) \]
. Now we would like to modify the potential by adding a term that depends on the CV only. That is, instead of using \( U(q) \), we use \( U(q)+V(s(q))\). There are several reasons why one would like to introduce this potential. One is to avoid that the system samples some un-desired portion of the conformational space. As an example, imagine that you want to study dissociation of a complex of two molecules. If you perform a very long simulation you will be able to see association and dissociation. However, the typical time required for association will depend on the size of the simulation box. It could be thus convenient to limit the exploration to conformations where the distance between the two molecules is lower than a given threshold. This could be done by adding a bias potential on the distance between the two molecules. Another example is the simulation of a portion of a large molecule taken out from its initial context. The fragment alone could be unstable, and one might want to add additional potentials to keep the fragment in place. This could be done by adding a bias potential on some measure of the distance from the experimental structure (e.g. on root-mean-square deviation). Whatever CV we decide to bias, it is very important to recognize which is the effect of this bias and, if necessary, remove it a posteriori. The biased distribution of the CV will be
\[ P'(s)\propto \int dq e^{-\frac{U(q)+V(s(q))}{k_BT}} \delta(s-s(q))\propto e^{-\frac{V(s(q))}{k_BT}}P(s) \]
and the biased free energy landscape
\[ F'(s)=-k_B T \log P'(s)=F(s)+V(s)+C \]
Thus, the effect of a bias potential on the free energy is additive. Also notice the presence of an undetermined constant \( C \). This constant is irrelevant for what concerns free-energy differences and barriers, but will be important later when we will learn the weighted-histogram method. Obviously the last equation can be inverted so as to obtain the original, unbiased free-energy landscape from the biased one just subtracting the bias potential
\[ F(s)=F'(s)-V(s)+C \]
Additionally, one might be interested in recovering the distribution of an arbitrary observable. E.g., one could add a bias on the distance between two molecules and be willing to compute the unbiased distribution of some torsional angle. In this case there is no straightforward relationship that can be used, and one has to go back to the relationship between the microscopic probabilities:
\[ P(q)\propto P'(q) e^{\frac{V(s(q))}{k_BT}} \]
The consequence of this expression is that one can obtained any kind of unbiased information from a biased simulation just by weighting every sampled conformation with a weight
\[ w\propto e^{\frac{V(s(q))}{k_BT}} \]
That is, frames that have been explored in spite of a high (disfavoring) bias potential \( V \) will be counted more than frames that has been explored with a less disfavoring bias potential. To learn more: Summary of theory
Biased sampling
We will make use as a toy-model of alanine dipeptide: we will see how we can use an iterative approach to build a constant bias to speed up the sampling.
Alanine dipeptide is characterized by multiple minima separated by relatively high free energy barriers. Here we will explore the conformational space of alanine dipeptide using a standard MD simulation, then instead of using the free energy as an external potential we will try to fit the potential using gnuplot and add a bias using an analytical function of a collective variable with CUSTOM and BIASVALUE .
As a first test lets run an MD and generate on-the-fly the free energy as a function of the phi and psi collective variables separately.
This is an example input file to calculate the phi and psi angles on the fly and accumulate two 1D histograms from which calculating the free energy.
#SETTINGS MOLFILE=user-doc/tutorials/lugano-2/diala.pdb # vim:ft=plumed MOLINFOSTRUCTURE=diala.pdb phi: TORSIONcompulsory keyword a file in pdb format containing a reference structure.ATOMS=@phi-2 psi: TORSIONthe four atoms involved in the torsional angleATOMS=@psi-2 hhphi: HISTOGRAMthe four atoms involved in the torsional angleARG=phithe input for this action is the scalar output from one or more other actions.STRIDE=50compulsory keyword ( default=1 ) the frequency with which the data should be collected and added to the quantity being averagedGRID_MIN=-picompulsory keyword the lower bounds for the gridGRID_MAX=picompulsory keyword the upper bounds for the gridGRID_BIN=600the number of bins for the gridBANDWIDTH=0.1 hhpsi: HISTOGRAMcompulsory keyword the bandwidths for kernel density estimationARG=psithe input for this action is the scalar output from one or more other actions.STRIDE=50compulsory keyword ( default=1 ) the frequency with which the data should be collected and added to the quantity being averagedGRID_MIN=-picompulsory keyword the lower bounds for the gridGRID_MAX=picompulsory keyword the upper bounds for the gridGRID_BIN=600the number of bins for the gridBANDWIDTH=0.1 ffphi: CONVERT_TO_FEScompulsory keyword the bandwidths for kernel density estimationGRID=hhphi ffpsi: CONVERT_TO_FEScompulsory keyword the action that creates the input grid you would like to useGRID=hhpsi DUMPGRIDcompulsory keyword the action that creates the input grid you would like to useGRID=ffphicompulsory keyword the action that creates the grid you would like to outputFILE=fes_phicompulsory keyword ( default=density ) the file on which to write the grid.STRIDE=100000 DUMPGRIDcompulsory keyword ( default=0 ) the frequency with which the grid should be output to the file.GRID=ffpsicompulsory keyword the action that creates the grid you would like to outputFILE=fes_psicompulsory keyword ( default=density ) the file on which to write the grid.STRIDE=100000 PRINTcompulsory keyword ( default=0 ) the frequency with which the grid should be output to the file.ARG=phi,psithe input for this action is the scalar output from one or more other actions.FILE=colvar.datthe name of the file on which to output these quantitiesSTRIDE=50compulsory keyword ( default=1 ) the frequency with which the quantities of interest should be output
run it with gromacs as
gmx mdrun -s topol -plumed plumed.dat -nb cpu -v
from the colvar file it is clear that we can quickly explore two minima but that the region for positive phi is not accessible. Ideally we would like to speed up the sampling of regions that are not visited spontaneously by MD. We have multiple possibilities. One option could be to use as a bias the opposite of the accumulated free-energy using EXTERNAL . Another option can be to fit the FES and use the fit. This is what we will do, but first of all take a look at the fes accumulated in time.
>gnuplot plot for [i=0:9] 'analysis.'.i.'.fes_phi' u 1:2 w l t''.i rep 'fes_phi' u 1:2 w l t'final' plot for [i=0:9] 'analysis.'.i.'.fes_psi' u 1:2 w l t''.i rep 'fes_psi' u 1:2 w l t'final'
So first we need to fit the opposite of the free energy as a function of phi in the region explored with a periodic function, because of the gaussian like look of the minima we can fit it using the von Mises distribution. In gnuplot
>gnuplot gnuplot>plot 'fes_phi' u 1:(-$2) w l
Now find a value such as the fes is always positive, e.g. ~38
gnuplot>plot 'fes_phi' u 1:(-$2+38) w l gnuplot>f(x)=exp(k1*cos(x-a1))+exp(k2*cos(x-a2)) gnuplot>k1=2 gnuplot>k2=2 gnuplot>fit [-2.9:-0.7] f(x) 'fes_phi' u 1:(-$2+38) via k1,a1,k2,a2 gnuplot>rep f(x)
The function and the resulting parameters can be used to run a new biased simulation:
To the above file we add a few lines to define using CUSTOM a function of the angle phi.
#SETTINGS MOLFILE=user-doc/tutorials/lugano-2/diala.pdb # vim:ft=plumed MOLINFOSTRUCTURE=diala.pdb phi: TORSIONcompulsory keyword a file in pdb format containing a reference structure.ATOMS=@phi-2 psi: TORSIONthe four atoms involved in the torsional angleATOMS=@psi-2 doubleg: CUSTOM ...the four atoms involved in the torsional angleARG=phithe input for this action is the scalar output from one or more other actions.FUNC=exp(__FILL__*cos(x-__FILL__))+exp(__FILL__*cos(x-__FILL__))compulsory keyword the function you wish to evaluatePERIODIC=NO ... b: BIASVALUEcompulsory keyword if the output of your function is periodic then you should specify the periodicity of the function.ARG=doubleg hhphi: HISTOGRAMthe input for this action is the scalar output from one or more other actions.ARG=phithe input for this action is the scalar output from one or more other actions.STRIDE=50compulsory keyword ( default=1 ) the frequency with which the data should be collected and added to the quantity being averagedGRID_MIN=-picompulsory keyword the lower bounds for the gridGRID_MAX=picompulsory keyword the upper bounds for the gridGRID_BIN=600the number of bins for the gridBANDWIDTH=0.1 hhpsi: HISTOGRAMcompulsory keyword the bandwidths for kernel density estimationARG=psithe input for this action is the scalar output from one or more other actions.STRIDE=50compulsory keyword ( default=1 ) the frequency with which the data should be collected and added to the quantity being averagedGRID_MIN=-picompulsory keyword the lower bounds for the gridGRID_MAX=picompulsory keyword the upper bounds for the gridGRID_BIN=600the number of bins for the gridBANDWIDTH=0.1 ffphi: CONVERT_TO_FEScompulsory keyword the bandwidths for kernel density estimationGRID=hhphi ffpsi: CONVERT_TO_FEScompulsory keyword the action that creates the input grid you would like to useGRID=hhpsi DUMPGRIDcompulsory keyword the action that creates the input grid you would like to useGRID=ffphicompulsory keyword the action that creates the grid you would like to outputFILE=fes_phicompulsory keyword ( default=density ) the file on which to write the grid.STRIDE=100000 DUMPGRIDcompulsory keyword ( default=0 ) the frequency with which the grid should be output to the file.GRID=ffpsicompulsory keyword the action that creates the grid you would like to outputFILE=fes_psicompulsory keyword ( default=density ) the file on which to write the grid.STRIDE=100000 PRINTcompulsory keyword ( default=0 ) the frequency with which the grid should be output to the file.ARG=phi,psi,b.biasthe input for this action is the scalar output from one or more other actions.FILE=colvar.datthe name of the file on which to output these quantitiesSTRIDE=50compulsory keyword ( default=1 ) the frequency with which the quantities of interest should be output
It is now possible to run a second simulation and observe the new behavior. The system quickly explores a new minimum. While a quantitative estimate of the free energy difference of the old and new regions is out of the scope of the current exercise what we can do is to add a new von Mises function centered in the new minimum with a comparable height, in this way we can hope to facilitate a back and forth transition along the phi collective variable. Look at the old and new free energy and add a third exponential function to CUSTOM centered in the new minimum.
gnuplot> plot 'fes_phi' u 1:(-$2+38) w l gnuplot> f(x)=exp(k3*cos(x-a3)) gnuplot>k3=2 gnuplot> fit [0.3:1.8] f(x) 'fes_phi' u 1:(-$2+38) via k3,a3
We can now run a third simulation where both regions are biased.
#SETTINGS MOLFILE=user-doc/tutorials/lugano-2/diala.pdb MOLINFOSTRUCTURE=diala.pdb phi: TORSIONcompulsory keyword a file in pdb format containing a reference structure.ATOMS=@phi-2 psi: TORSIONthe four atoms involved in the torsional angleATOMS=@psi-2 tripleg: CUSTOM ...the four atoms involved in the torsional angleARG=phithe input for this action is the scalar output from one or more other actions.FUNC=exp(__FILL__*cos(x-__FILL__))+exp(__FILL__*cos(x-__FILL__))+exp(__FILL__*cos(x-__FILL__))compulsory keyword the function you wish to evaluatePERIODIC=NO ... b: BIASVALUEcompulsory keyword if the output of your function is periodic then you should specify the periodicity of the function.ARG=tripleg hhphi: HISTOGRAMthe input for this action is the scalar output from one or more other actions.ARG=phithe input for this action is the scalar output from one or more other actions.STRIDE=50compulsory keyword ( default=1 ) the frequency with which the data should be collected and added to the quantity being averagedGRID_MIN=-picompulsory keyword the lower bounds for the gridGRID_MAX=picompulsory keyword the upper bounds for the gridGRID_BIN=600the number of bins for the gridBANDWIDTH=0.1 hhpsi: HISTOGRAMcompulsory keyword the bandwidths for kernel density estimationARG=psithe input for this action is the scalar output from one or more other actions.STRIDE=50compulsory keyword ( default=1 ) the frequency with which the data should be collected and added to the quantity being averagedGRID_MIN=-picompulsory keyword the lower bounds for the gridGRID_MAX=picompulsory keyword the upper bounds for the gridGRID_BIN=600the number of bins for the gridBANDWIDTH=0.1 ffphi: CONVERT_TO_FEScompulsory keyword the bandwidths for kernel density estimationGRID=hhphi ffpsi: CONVERT_TO_FEScompulsory keyword the action that creates the input grid you would like to useGRID=hhpsi DUMPGRIDcompulsory keyword the action that creates the input grid you would like to useGRID=ffphicompulsory keyword the action that creates the grid you would like to outputFILE=fes_phicompulsory keyword ( default=density ) the file on which to write the grid.STRIDE=100000 DUMPGRIDcompulsory keyword ( default=0 ) the frequency with which the grid should be output to the file.GRID=ffpsicompulsory keyword the action that creates the grid you would like to outputFILE=fes_psicompulsory keyword ( default=density ) the file on which to write the grid.STRIDE=100000 PRINTcompulsory keyword ( default=0 ) the frequency with which the grid should be output to the file.ARG=phi,psi,b.biasthe input for this action is the scalar output from one or more other actions.FILE=colvar.datthe name of the file on which to output these quantitiesSTRIDE=50compulsory keyword ( default=1 ) the frequency with which the quantities of interest should be output
With this third simulation it should be possible to visit both regions as a function on the phi torsion. The resulting free energy is now reporting about the biased simulation is flatter than the former even if not flat everywhere. Now it is possible to reweight the sampling and obtain a better free energy estimate along phi.
#SETTINGS MOLFILE=user-doc/tutorials/lugano-2/diala.pdb # vim:ft=plumed MOLINFOSTRUCTURE=diala.pdb phi: TORSIONcompulsory keyword a file in pdb format containing a reference structure.ATOMS=@phi-2 psi: TORSIONthe four atoms involved in the torsional angleATOMS=@psi-2 tripleg: MATHEVAL ...the four atoms involved in the torsional angleARG=phithe input for this action is the scalar output from one or more other actions.FUNC=__FILL__compulsory keyword the function you wish to evaluatePERIODIC=NO ... b: BIASVALUEcompulsory keyword if the output of your function is periodic then you should specify the periodicity of the function.ARG=tripleg as: REWEIGHT_BIASthe input for this action is the scalar output from one or more other actions.ARG=b.bias hhphi: HISTOGRAMcompulsory keyword ( default=*.bias ) the biases that must be taken into account when reweightingARG=phithe input for this action is the scalar output from one or more other actions.STRIDE=50compulsory keyword ( default=1 ) the frequency with which the data should be collected and added to the quantity being averagedGRID_MIN=-picompulsory keyword the lower bounds for the gridGRID_MAX=picompulsory keyword the upper bounds for the gridGRID_BIN=600the number of bins for the gridBANDWIDTH=0.1compulsory keyword the bandwidths for kernel density estimationLOGWEIGHTS=as hhpsi: HISTOGRAMlist of actions that calculates log weights that should be used to weight configurations when calculating averagesARG=psithe input for this action is the scalar output from one or more other actions.STRIDE=50compulsory keyword ( default=1 ) the frequency with which the data should be collected and added to the quantity being averagedGRID_MIN=-picompulsory keyword the lower bounds for the gridGRID_MAX=picompulsory keyword the upper bounds for the gridGRID_BIN=600the number of bins for the gridBANDWIDTH=0.1compulsory keyword the bandwidths for kernel density estimationLOGWEIGHTS=as ffphi: CONVERT_TO_FESlist of actions that calculates log weights that should be used to weight configurations when calculating averagesGRID=hhphicompulsory keyword the action that creates the input grid you would like to useSTRIDE=100000 ffpsi: CONVERT_TO_FEScould not find this keywordGRID=hhpsicompulsory keyword the action that creates the input grid you would like to useSTRIDE=100000 DUMPGRIDcould not find this keywordGRID=ffphicompulsory keyword the action that creates the grid you would like to outputFILE=ffphi.dat DUMPGRIDcompulsory keyword ( default=density ) the file on which to write the grid.GRID=ffpsicompulsory keyword the action that creates the grid you would like to outputFILE=ffpsi.dat PRINTcompulsory keyword ( default=density ) the file on which to write the grid.ARG=phi,psi,b.biasthe input for this action is the scalar output from one or more other actions.FILE=colvar.datthe name of the file on which to output these quantitiesSTRIDE=50compulsory keyword ( default=1 ) the frequency with which the quantities of interest should be output
Of notice that the reweighting is also applied to the psi collective variable. If you have performed your simulations in different folder you can compare the effect of the bias on phi on the free energy of psi. For a single simulation with a constant bias the reweighting is simple, the weight of each frame is exp(+bias(cv(t))/kt). So it is possible to perform the reweighting by hand at any time.
Now you have performed an original Umbrella Sampling calculation. This is not particularly easy to setup nor robust, even if from a modern perspective it is a very rough implementation of METAD
In the next exercise we will perform a WHAM Umbrella Sampling simulation.
In this case we will run many simulations with a strong harmonic restraint centered around specific values of phi in such a way to cover all possible values, keep each simulation close to its specific value, allow for overlap between neighbor simulations, i.e. simulations centered around consecutive phi values. The simulation can be either performed in parallel by preparing starting configurations close to each value or sequentially, extracting a good starting conformation from the former simulations. In the specific case of alanine dipeptide we can even just start always from the same configuration and let the bias quickly move it close to the target values.
To run the simulation in scalar you can make use of the provided bash script that is:
for AT in -3.00 -2.75 -2.50 -2.25 -2.00 -1.75 -1.50 -1.25 -1.00 -0.75 -0.50 -0.25 0.00 0.25 0.50 0.75 1.00 1.25 1.50 1.75 2.00 2.25 2.50 2.75 3.00 do cat >plumed.dat << EOF # vim:ft=plumed MOLINFO STRUCTURE=diala.pdb phi: TORSION ATOMS=@phi-2 psi: TORSION ATOMS=@psi-2 # # Impose an umbrella potential on CV 1 # with a spring constant of 250 kjoule/mol # at fixed points along phi # restraint-phi: RESTRAINT ARG=phi KAPPA=250.0 AT=$AT # monitor the two variables and the bias potential from the two restraints PRINT STRIDE=20 ARG=phi,psi,restraint-phi.bias FILE=COLVAR$AT EOF gmx mdrun -plumed plumed.dat -nsteps 100000 -x traj$AT.xtc -c cout$AT.gro -nb cpu done
you can run it using
./run_us.sh
Plotting the phi collective variable for all replica you will see that each simulation has explored a well defined region of the conformation space as defined by phi. To perform the WHAM merging of the windows we need to 1) collect all the frames
gmx trjcat -f traj*.xtc -cat -o concatenated.xtc
2) calculate the values for all employed biases applied on each frame for this we can write a plumed-wham.dat file including all the biases used in the former simulations:
#SETTINGS MOLFILE=user-doc/tutorials/lugano-2/diala.pdb # vim:ft=plumed MOLINFOSTRUCTURE=diala.pdb phi: TORSIONcompulsory keyword a file in pdb format containing a reference structure.ATOMS=@phi-2 RESTRAINTthe four atoms involved in the torsional angleARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=-3.00 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=-2.75 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=-2.50 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=-2.25 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=-2.00 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=-1.75 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=-1.50 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=-1.25 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=-1.00 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=-0.75 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=-0.50 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=-0.25 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=0.00 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=0.25 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=0.50 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=0.75 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=1.00 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=1.25 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=1.50 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=1.75 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=2.00 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=2.25 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=2.50 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=2.75 RESTRAINTcompulsory keyword the position of the restraintARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=3.00 PRINTcompulsory keyword the position of the restraintARG=*.biasthe input for this action is the scalar output from one or more other actions.FILE=biases.datthe name of the file on which to output these quantitiesSTRIDE=10 PRINTcompulsory keyword ( default=1 ) the frequency with which the quantities of interest should be outputARG=phithe input for this action is the scalar output from one or more other actions.FILE=allphi.datthe name of the file on which to output these quantitiesSTRIDE=10compulsory keyword ( default=1 ) the frequency with which the quantities of interest should be output
plumed driver --mf_xtc concatenated.xtc --plumed plumed-wham.dat
3) run the iterative WHAM optimization and get a weight per frame
python wham.py biases.dat 25 2.49
where 25 is the number of windows and 2.49 is the temperature in energy unit. After some time the result is a file weight.dat with one weight per frame that can be used to calculate any possible property of the system. For example the free energy profile along phi.
To do so edit the weight.dat file to add 3 blank lines and then
paste allphi.dat weights.dat | grep -v \# > allphi-w.dat python do_fes.py allphi-w.dat 1 -3.1415 3.1415 50 2.49 fes.dat
the resulting profile will be disappointing, error estimate and convergence will be discussed in the following tutorials, but clearly simulations are too short. A more advanced approach would be to use the configurations obtained from the former simulations to generate multiple replicas and then perform the US again for longer time and possible in parallel. The syntax is presented in the following but the exercise is possible only if plumed is compiled with mpi
Here we use the "replica" syntax of plumed to write a single plumed input file for all the windows:
#SETTINGS FILENAME=plumed.dat MOLFILE=user-doc/tutorials/lugano-2/diala.pdb # this is plumed.dat # vim:ft=plumed MOLINFOSTRUCTURE=diala.pdb phi: TORSIONcompulsory keyword a file in pdb format containing a reference structure.ATOMS=@phi-2 psi: TORSIONthe four atoms involved in the torsional angleATOMS=@psi-2 # # Impose an umbrella potential on CV 1 # with a spring constant of 250 kjoule/mol # at fixed points along phi # restraint-phi: RESTRAINT ...the four atoms involved in the torsional angleARG=phithe input for this action is the scalar output from one or more other actions.KAPPA=250.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables areAT=@replicas:{ -3.00 -2.75 -2.50 -2.25 -2.00 -1.75 -1.50 -1.25 -1.00 -0.75 -0.50 -0.25 0.00 0.25 0.50 0.75 1.00 1.25 1.50 1.75 2.00 2.25 2.50 2.75 3.00 } ... # monitor the two variables and the bias potential from the restraint PRINTcompulsory keyword the position of the restraintSTRIDE=20compulsory keyword ( default=1 ) the frequency with which the quantities of interest should be outputARG=phi,psi,restraint-phi.biasthe input for this action is the scalar output from one or more other actions.FILE=COLVARthe name of the file on which to output these quantities
The @replicas syntax allow to define different values for a variable for the different replicas.
mpiexec -np 25 gmx_mpi -s topol -plumed plumed.dat -multi 25 -replex 100 -nb cpu -nsteps 100000
In this case we run 25 parallel simulations and we also try to perform replica-exchange between neighbor replicas.
Once the simulation is finished the trajectories can be concatenated and analyzed with WHAM making use of the plumed native implementation:
gmx_mpi trjcat -f traj*.xtc -o concatenated.xtc -cat
Write a new plumed-wham.dat
And again use the driver in parallel:
mpiexec -np 25 plumed driver --mf_xtc concatenated.xtc --plumed plumed-wham.dat --multi 25
1.8.17