Rosetta  2020.37
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Friends Macros Pages
Public Types | Public Member Functions | Private Attributes | List of all members
protocols::match::upstream::OriginalBackboneBuildPoint Class Reference

#include <OriginalScaffoldBuildPoint.hh>

Inheritance diagram for protocols::match::upstream::OriginalBackboneBuildPoint:
Inheritance graph
[legend]

Public Types

typedef ProteinBackboneBuildPoint parent
 
- Public Types inherited from protocols::match::upstream::ProteinBackboneBuildPoint
typedef core::Real Real
 
typedef core::Vector Vector
 
typedef ScaffoldBuildPoint parent
 
- Public Types inherited from protocols::match::upstream::ScaffoldBuildPoint
typedef core::Size Size
 

Public Member Functions

 OriginalBackboneBuildPoint (core::Size index)
 
 ~OriginalBackboneBuildPoint () override
 
 OriginalBackboneBuildPoint (core::conformation::Residue const &res)
 
 OriginalBackboneBuildPoint (core::conformation::Residue const &res, core::Size index)
 
void initialize_from_residue (core::conformation::Residue const &res)
 
bool compatible (ScaffoldBuildPoint const &other, bool first_dispatch=true) const override
 
bool compatible (OriginalBackboneBuildPoint const &other, bool first_dispatch=true) const override
 
core::Size original_insertion_point () const override
 Inform the calling function where in the original scaffold this build point should be inserted. If the output pose from a matching has a different number of residues than the original scaffold, then the calling function must determine where the hit from this build point should be inserted. More...
 
void insert (core::Size seqpos_to_insert_at, Hit const &hit, UpstreamBuilderCOP builder, core::pose::Pose &pose) const override
 
core::Size original_resid () const
 
core::conformation::Residue const & input_conformation () const
 
- Public Member Functions inherited from protocols::match::upstream::ProteinBackboneBuildPoint
 ProteinBackboneBuildPoint ()
 
 ProteinBackboneBuildPoint (core::Size index)
 
 ~ProteinBackboneBuildPoint () override
 
Real phi () const
 
Real psi () const
 
Vector N_pos () const
 
Vector CA_pos () const
 
Vector C_pos () const
 
Vector O_pos () const
 
Vector H_pos () const
 
Vector HA_pos () const
 
void phi (Real setting)
 Setters. More...
 
void psi (Real setting)
 
void N_pos (Vector const &setting)
 
void CA_pos (Vector const &setting)
 
void C_pos (Vector const &setting)
 
void O_pos (Vector const &setting)
 
void H_pos (Vector const &setting)
 
void HA_pos (Vector const &setting)
 
- Public Member Functions inherited from protocols::match::upstream::ScaffoldBuildPoint
 ScaffoldBuildPoint ()
 
 ScaffoldBuildPoint (core::Size index)
 
 ~ScaffoldBuildPoint () override
 
core::Size index () const
 
void index (core::Size setting)
 

Private Attributes

core::Size original_resid_
 
core::conformation::ResidueOP input_conformation_
 

Member Typedef Documentation

Constructor & Destructor Documentation

protocols::match::upstream::OriginalBackboneBuildPoint::OriginalBackboneBuildPoint ( core::Size  index)
protocols::match::upstream::OriginalBackboneBuildPoint::~OriginalBackboneBuildPoint ( )
overridedefault
protocols::match::upstream::OriginalBackboneBuildPoint::OriginalBackboneBuildPoint ( core::conformation::Residue const &  res)
protocols::match::upstream::OriginalBackboneBuildPoint::OriginalBackboneBuildPoint ( core::conformation::Residue const &  res,
core::Size  index 
)

Member Function Documentation

bool protocols::match::upstream::OriginalBackboneBuildPoint::compatible ( ScaffoldBuildPoint const &  other,
bool  first_dispatch = true 
) const
overridevirtual
bool protocols::match::upstream::OriginalBackboneBuildPoint::compatible ( OriginalBackboneBuildPoint const &  other,
bool  first_dispatch = true 
) const
overridevirtual

It's ok for a single backbone build point to be used by multiple geometric constraints at least from the perspective of the build point. If two different side chain conformations are needed for a single build point, then clearly that's impossible; however, if one of the geometric constraints requires a particular sidechain conformation, and the other is using the backbone of the original build point, then we're fine. Therefore, this method always returns true.

Reimplemented from protocols::match::upstream::ScaffoldBuildPoint.

void protocols::match::upstream::OriginalBackboneBuildPoint::initialize_from_residue ( core::conformation::Residue const &  res)
core::conformation::Residue const& protocols::match::upstream::OriginalBackboneBuildPoint::input_conformation ( ) const
inline

References input_conformation_.

void protocols::match::upstream::OriginalBackboneBuildPoint::insert ( core::Size  seqpos_to_insert_at,
Hit const &  hit,
UpstreamBuilderCOP  builder,
core::pose::Pose pose 
) const
overridevirtual
OriginalBackboneBuildPoint::Size protocols::match::upstream::OriginalBackboneBuildPoint::original_insertion_point ( ) const
overridevirtual

Inform the calling function where in the original scaffold this build point should be inserted. If the output pose from a matching has a different number of residues than the original scaffold, then the calling function must determine where the hit from this build point should be inserted.

Implements protocols::match::upstream::ScaffoldBuildPoint.

References original_resid_.

core::Size protocols::match::upstream::OriginalBackboneBuildPoint::original_resid ( ) const
inline

References original_resid_.

Member Data Documentation

core::conformation::ResidueOP protocols::match::upstream::OriginalBackboneBuildPoint::input_conformation_
private
core::Size protocols::match::upstream::OriginalBackboneBuildPoint::original_resid_
private

The documentation for this class was generated from the following files: