This is part of the setup module |
Loads a library, possibly defining new actions.
It is available only on systems allowing for dynamic loading. It can also be fed with a cpp file, in which case the file is compiled first.
If you have a shared object named extensions.so and want to use the functions implemented within it within PLUMED you can load it with the following syntax
LOADFILE=extensions.socompulsory keyword file to be loaded
As a more practical example, imagine that you want to make a small change to one collective variable that is already implemented in PLUMED, say DISTANCE . Copy the file src/colvar/Distance.cpp
into your work directory, rename it as Distance2.cpp
and edit it as you wish. It might be better to also replace any occurrence of the string DISTANCE within the file with DISTANCE2, so that both old and new implementation will be available with different names. Then you can compile it into a shared object using
> plumed mklib Distance2.cpp
This will generate a file Distance2.so
(or Distance2.dylib
on a mac) that can be loaded. Now you can use your new implementation with the following input
# load the new library LOADFILE=Distance2.so # compute standard distance d: DISTANCEcompulsory keyword file to be loadedATOMS=1,10 # compute modified distance d2: DISTANCE2the pair of atom that we are calculating the distance between.ATOMS=1,10 # print them on a file PRINTcould not find this keywordARG=d,d2compulsory keyword the labels of the values that you would like to print to the fileFILE=compare-themthe name of the file on which to output these quantities
You can even skip the initial step and directly feed PLUMED with the Distance2.cpp
file: it will be compiled on the fly.
# load the new definition # this is a cpp file so it will be compiled LOADFILE=Distance2.cpp # compute standard distance d: DISTANCEcompulsory keyword file to be loadedATOMS=1,10 # compute modified distance d2: DISTANCE2the pair of atom that we are calculating the distance between.ATOMS=1,10 # print them on a file PRINTcould not find this keywordARG=d,d2compulsory keyword the labels of the values that you would like to print to the fileFILE=compare-themthe name of the file on which to output these quantities
This will allow to make quick tests while developing your own variables. Of course, after your implementation is ready you might want to add it to the PLUMED source tree and recompile the whole PLUMED.
Starting with PLUMED 2.10, the LOAD action can be placed in any point of the input file, and will only affect commands that are placed after the LOAD action. In other words, you can create a file named Distance.cpp
and that reimplement the DISTANCE action and use it like this:
# compute standard distance d: DISTANCEATOMS=1,10 # load the new definition LOADthe pair of atom that we are calculating the distance between.FILE=Distance.so # compute modified distance d2: DISTANCEcompulsory keyword file to be loadedATOMS=1,10 # print them on a file PRINTthe pair of atom that we are calculating the distance between.ARG=d,d2compulsory keyword the labels of the values that you would like to print to the fileFILE=compare-themthe name of the file on which to output these quantities
In addition, starting with PLUMED 2.10 the LOAD action can be used in contexts where multiple Plumed objects exist. A possible example is multithreading: loading an action from a Plumed object used in one thread will not affect other threads. Another example is if multiple Plumed objects are created in the C/C++ or Python interface. If a LOAD command is used in one of these objects, the loaded action will not affect the other objects.
FILE | file to be loaded |