Skip to content
Snippets Groups Projects
Commit 42327b53 authored by Giovanni Bussi's avatar Giovanni Bussi
Browse files

Typos

parent 35e7dde6
No related branches found
No related tags found
No related merge requests found
...@@ -7,13 +7,19 @@ Version 2.0.0 (Sep 27, 2013) ...@@ -7,13 +7,19 @@ Version 2.0.0 (Sep 27, 2013)
Version 2.0 is a complete rewrite, so there is no way to write a complete set of difference Version 2.0 is a complete rewrite, so there is no way to write a complete set of difference
with respect to plumed 1.3. Here is a possibly incomplete summary of the difference: with respect to plumed 1.3. Here is a possibly incomplete summary of the difference:
- The input is simpler, more flexible, and more error proof. Many checks are now performed and in this way common errors are avoided. - The input is simpler, more flexible, and more error proof.
- The units are now the same for all MD codes. If you want to use a different unit than the default you set it in the input file. Many checks are now performed and in this way common errors are avoided.
- The analysis tools are now much more flexible. As an example of this it is now possible to write different collective variables with different frequencies - The units are now the same for all MD codes.
- Many complex collective variables are considerably faster than they were in plumed1. In particular, all variables based on RMSD distances. If you want to use a different unit than the default you set it in the input file.
- Centers of mass can be used as if they were atoms. Hence, unlike plumed 1.3, you can use center of mass positions in ALL collective variables. - The analysis tools are now much more flexible.
- The virial contribution is now computed and passed to the MD code. Plumed can thus now be used to perform biased NPT simulations As an example of this it is now possible to write different collective variables with different frequencies.
- Variables can be dumped on different files and with different files, and are - Many complex collective variables are considerably faster than they were in plumed1.
In particular, all variables based on RMSD distances.
- Centers of mass can be used as if they were atoms.
Hence, unlike plumed 1.3, you can use center of mass positions in ALL collective variables.
- The virial contribution is now computed and passed to the MD code.
Plumed can thus now be used to perform biased NPT simulations.
- Variables can be dumped on different files, and are
computed only when this is necessary. computed only when this is necessary.
- PLUMED is now compiled as a separate library. This simplifies the patching - PLUMED is now compiled as a separate library. This simplifies the patching
procedure, but might require some extra work to configure PLUMED properly. procedure, but might require some extra work to configure PLUMED properly.
...@@ -22,16 +28,16 @@ with respect to plumed 1.3. Here is a possibly incomplete summary of the differe ...@@ -22,16 +28,16 @@ with respect to plumed 1.3. Here is a possibly incomplete summary of the differe
other. other.
In addition, it is now much easier to contribute new functionality to the code because: In addition, it is now much easier to contribute new functionality to the code because:
- There is a much simpler interface between plumed and the base MD codes. This makes it much easier to add plumed to a new MD code. - There is a much simpler interface between plumed and the base MD codes.
- There is C++ object oriented programming and full compatibility with the C++ standard library This makes it much easier to add plumed to a new MD code. Hopefully, in the future,
- A modular structure interfaces with MD codes will be maintained by the developers of the MD codes
- New collective variables and methods can be released independently
- There is an extensive developer documentation
- User documentation is provided together inside the implementation files
- Interfacing with MD codes is simpler. Hopefully, in the future, these
interface will be maitained by the developers of the MD codes
independently from PLUMED developers. This will allow more MD codes independently from PLUMED developers. This will allow more MD codes
to be compatible with PLUMED. to be compatible with PLUMED.
- There is C++ object oriented programming and full compatibility with the C++ standard library
- A modular structure.
- New collective variables and methods can be released independently.
- There is an extensive developer documentation.
- User documentation is provided together inside the implementation files.
Caveats: Caveats:
- PLUMED 2 input file (plumed.dat) has a syntax which is not - PLUMED 2 input file (plumed.dat) has a syntax which is not
......
...@@ -48,7 +48,7 @@ equivalent. You should read the documentation for the Plumed 2 Action. ...@@ -48,7 +48,7 @@ equivalent. You should read the documentation for the Plumed 2 Action.
</TR> </TR>
<TR> <TR>
<TD> INTERVAL </TD> <TD> INTERVAL </TD>
<TD> <b> \ref METAD with INTERVAL </b> </TD> <TD> \ref METAD with INTERVAL </TD>
</TR> </TR>
<TR> <TR>
<TD> INVERT </TD> <TD> INVERT </TD>
...@@ -109,7 +109,7 @@ equivalent. You should read the documentation for the Plumed 2 Action. ...@@ -109,7 +109,7 @@ equivalent. You should read the documentation for the Plumed 2 Action.
</TR> </TR>
<TR> <TR>
<TD> POSITION </TD> <TD> POSITION </TD>
<TD> <b> currently missing</b> </TD> <TD> <b> currently missing </b> </TD>
</TR> </TR>
<TR> <TR>
<TD> MINDIST </TD> <TD> MINDIST </TD>
...@@ -176,7 +176,7 @@ equivalent. You should read the documentation for the Plumed 2 Action. ...@@ -176,7 +176,7 @@ equivalent. You should read the documentation for the Plumed 2 Action.
<TD> \ref PATHMSD, s component </TD> <TD> \ref PATHMSD, s component </TD>
</TR> </TR>
<TR> <TR>
<TD> S_PATH </TD> <TD> Z_PATH </TD>
<TD> \ref PATHMSD, z component </TD> <TD> \ref PATHMSD, z component </TD>
</TR> </TR>
<TR> <TR>
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment