Back to Mover page. Page last updated 9 April 2018.
Autogenerated Tag Syntax Documentation:
Given a symmetry definition file that describes configuration and scoring of a symmetric system, this mover 'symmetrizes' an asymmetric pose.
References and author information for the SetupForSymmetry mover:
SetupForSymmetry Mover's citation(s): DiMaio F, Leaver-Fay A, Bradley P, Baker D, and André I. (2011). Modeling symmetric macromolecular structures in Rosetta3. PLoS One 6(6):e20450. doi: 10.1371/journal.pone.0020450.
<SetupForSymmetry name="(&string;)" definition="(&string;)" preserve_datacache="(0 &bool;)" keep_pdb_info_labels="(0 &bool;)" symmetry_resource="(&string;)" set_global_symmetry_at_parsetime="(true &bool;)" />
For historical reasons, many protocols require symmetry to be set as a global option during script parsing. This is potentially dangerous, because symmetry is set throughout the protocol regardless of when
SetupForSymmetry mover is applied.
If your protocol is producing unexpected results or symmetry-related error messages, try setting
set_global_symmetry_at_parsetime=0, which disables setting the global option. If you have set
set_global_symmetry_at_parsetime=0 and Rosetta complains that you are dealing with an asymmetric pose or similar error, try setting
set_global_symmetry_at_parsetime=1 to enable setting the global option.
For backwards compatibility,
set_global_symmetry_at_parsetime=1 is currently the default.
A best practice could be to
set_global_symmetry_at_parsetime=0 and see if your protocols runs as expected without errors. If so, great. If not,
set_global_symmetry_at_parsetime=1 and see if that fixes it (in which case something is relying on the global setting).
Given the symmetry definition file 'C2.symm':
<SetupForSymmetry name="setup_symm" definition="C2.symm" preserve_datacache="0" />