Getting Started

Build Documentation

Rosetta Basics

Application Documentation

Scripting Interfaces

Development Documentation

Internal Documentation

How to Write Documentation

FAQ

Glossary

Options list

Back to Mover page.

SaveAndRetrieveSidechains

To be used after an ala pose was built (and the design moves are done) to retrieve the sidechains from the input pose that were set to Ala by build_Ala_pose. OR, to be used inside mini to recover sidechains after switching residue typesets. By default, sidechains that are different than Ala will not be changed, unless allsc is true. Please note that naming your mover "SARS" is almost certainly bad luck and strongly discouraged.

Autogenerated Tag Syntax Documentation:

XRW TO DO

<SaveAndRetrieveSidechains name="(&string;)" allsc="(0 &bool;)"
        multi_use="(false &bool;)" two_step="(false &bool;)"
        jumpid="(1 &non_negative_integer;)" reference_name="(&string;)" />
  • allsc: Save and retrieve all sidechains
  • multi_use: Set up so that we can use this multiple times
  • two_step: Save and retrieve in two steps
  • jumpid: Jump ID to keep track of
  • reference_name: If two_step is false, what structure to get the sidechains from.
  • task_operations: see RepackMinimize
  • two_step: the first call to SARS only saves the sidechains, second call retrieves them. If this is false, the sidechains are saved at parse time.
  • multi_use: If SaveAndRetrieveSidechains is used multiple times with two_steps enabled throughout the xml protocol, multi_use should be enabled. If not, the side chains saved the first time SaveAndRetrieveSidechains is called, will be retrieved for all the proceeding calls.

See Also