Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000272Rosetta[All Projects] Incorrect Resultspublic2013-05-13 16:232013-05-13 16:23
Assigned To 
PlatformAll platformsOSAnyOS VersionAny
Product VersionTrunk 
Fixed in Version 
Summary0000272: Potentially incorrect logic in protocols::motifs::add_motif_sc_constraints
Descriptionprotocols::motifs::add_motif_sc_constraints makes constraints involving a current residue and the first protein residue.Usually the residue is a protein residue, but if it's not, the variable first_protein_resi is set to have the value of the first protein residue. The problem is that this value is not properly used when constructing the constraint. In other words, this code:

        new CoordinateConstraint(
            core::id::AtomID( index2, this_pos ),
            core::id::AtomID( pose.residue( first_protein_resi ).atom_index( "CA" ), 1 ),
   index2 ),
            new HarmonicFunc( 0.0, 1.0 ) ) );

should instead read

        new CoordinateConstraint(
            core::id::AtomID( index2, this_pos ),
            core::id::AtomID( pose.residue( first_protein_resi ).atom_index( "CA" ), first_protein_resi ),
   index2 ),
            new HarmonicFunc( 0.0, 1.0 ) ) );

Is this correct? I found this while refactoring and it's in code i'm not familiar with.
TagsNo tags attached.
Application(s) Affectedall
Command Line Usedall
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-13 16:23 delucasl New Issue

Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker