Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000276Rosetta[All Projects] Crashpublic2013-05-22 12:262013-05-22 12:26
Assigned To 
PlatformOSOS Version
Product Version 
Fixed in Version 
Summary0000276: DockingProtocol does not correctly reset input pose on sequence changes
DescriptionIf you call the protocols::docking::DockingProtocol mover with the low resolution stage twice, with a modification to the sequence in between, the ReturnSidechainMover in the centroid->fullatom transition will error out, as the cached input_pose_ will have a different sequence from the now mutated pose.
Steps To ReproduceSomething like the following (untested) XML file should trigger it

        <DockingProtocol name=dock docking_local_refine=0 dock_min=0 partners="A_B" />
        <PackRotamersMover name=redesign />
        <Add mover=dock/>
        <Add mover=redesign/>
        <Add mover=dock/> -- Will complain about the changed sequence
Additional InformationThanks to Jarod from the RosettaCommons forum for finding this: [^]
TagsNo tags attached.
Application(s) Affectedrosetta_scripts
Command Line Usedrosetta_scripts -parser:protocol dockdesigndock.xml
Developer Options
Fixed in SVN Version
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2013-05-22 12:26 rmoretti New Issue

Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker