If, for some reason, you want to spread your PLUMED input over a number of files you can use INCLUDE as shown below:
INCLUDEFILE=filenamecompulsory keyword file to be included
So, for example, a single "plumed.dat" file:
dist: DISTANCEATOMS=1,2 RESTRAINTthe pair of atom that we are calculating the distance between.ARG=distthe input for this action is the scalar output from one or more other actions.AT=2.0compulsory keyword the position of the restraintKAPPA=1.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables are
could be split up into two files as shown below:
dist: DISTANCEATOMS=1,2 INCLUDEthe pair of atom that we are calculating the distance between.FILE=toBeIncluded.inccompulsory keyword file to be included
plus a "toBeIncluded.inc" file
#SETTINGS FILENAME=toBeIncluded.inc # this is toBeIncluded.inc RESTRAINTARG=distthe input for this action is the scalar output from one or more other actions.AT=2.0compulsory keyword the position of the restraintKAPPA=1.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables are
However, when you do this it is important to recognize that INCLUDE is a real directive that is only resolved after all the Comments have been stripped and the Continuation lines have been unrolled. This means it is not possible to do things like:
# this is wrong: DISTANCEINCLUDEcould not find this keywordFILE=options.dat RESTRAINTcould not find this keywordARG=distthe input for this action is the scalar output from one or more other actions.AT=2.0compulsory keyword the position of the restraintKAPPA=1.0compulsory keyword ( default=0.0 ) specifies that the restraint is harmonic and what the values of the force constants on each of the variables are