I want to use COMPASS forcefield with EMC. The sourceforge website mentions that EMC can be used to generate input structures for COMPASS forcefield, but I’m unable to find a method to do so. The COMPASS forcefield is not available in the fields directory as well.
When I attempt to set the field to COMPASS, I get:
COMPASS is a proprietary class 2 force, which is part of the Materials Studio package from Biovia (Dassault Systems). The force field uses the same syntactic input format as the PCFF force field. EMC can type COMPASS when the necessary input files are provided. However, due to the proprietary nature of COMPASS, the EMC does not include force field files for the COMPASS parameters and typing rules.
in the LAMMPS distribution as can be found at the LAMMPS web site. You actually would have to split the compass_published.frc file into two by moving the templates section into its own separate templates file, because this file is mandatory. As it turns out, a number of end_test keywords are missing in the templates section. After adding these, this results in
You can add these files either to your main force field collection by creating a compass directory in your EMC distribution,
$EMC_ROOT/field/compass
followed by copying the above two files here, or you can add them to the directory in which you are executing your EMC Setup script, or you can create a central depository somewhere else. In both latter cases you will have to let EMC Setup know where to find the force field files by setting the option field_location before you set field, which for a local copy would look like
ITEM OPTIONS
field_location .
field compass
ITEM END
You would leave out the field_location line, if you decide to add the compass files to your EMC distribution as described above. I successfully tested the validity of the above files. I will include this version of COMPASS in the next EMC release. Note that these files should also work with Materials Studio.
This paragraph was adapted and corrected after the questions and comments below.
I checked out the original and noticed some end_test keywords were missing in the original templates section. I corrected these mistakes and successfully tested the result. The updated the files can be found in my previous answer above.