Rosetta 3.4
Public Member Functions
protocols::simple_filters::ContactMapEvaluator Class Reference

#include <ContactMapEvaluator.hh>

Inheritance diagram for protocols::simple_filters::ContactMapEvaluator:
Inheritance graph
[legend]
Collaboration diagram for protocols::simple_filters::ContactMapEvaluator:
Collaboration graph
[legend]

List of all members.

Public Member Functions

 ContactMapEvaluator (core::pose::Pose const &native_pose, core::Real const max_dist, core::Size const min_seqsep)
 ~ContactMapEvaluator ()
virtual void apply (core::pose::Pose &pose, std::string tag, core::io::silent::SilentStruct &ss) const
 evaluate pose and store values in Silent_Struct why is this specific to a specific type of SilentStruct? that seems needlessly pointless and overly constraining.
virtual core::Real apply (core::pose::Pose &) const
 evaluate pose

Constructor & Destructor Documentation

protocols::simple_filters::ContactMapEvaluator::ContactMapEvaluator ( core::pose::Pose const &  native_pose,
core::Real const  max_dist,
core::Size const  min_seqsep 
)
protocols::simple_filters::ContactMapEvaluator::~ContactMapEvaluator ( ) [inline]

Member Function Documentation

void protocols::simple_filters::ContactMapEvaluator::apply ( core::pose::Pose ,
std::string  tag,
core::io::silent::SilentStruct pss 
) const [virtual]

evaluate pose and store values in Silent_Struct why is this specific to a specific type of SilentStruct? that seems needlessly pointless and overly constraining.

Reimplemented from protocols::evaluation::SingleValuePoseEvaluator< core::Real >.

References core::io::silent::SilentStruct::add_energy(), protocols::simple_filters::get_contact_features(), and protocols::simple_filters::pct_features_in_common().

virtual core::Real protocols::simple_filters::ContactMapEvaluator::apply ( core::pose::Pose ) const [inline, virtual]

The documentation for this class was generated from the following files:
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Friends Defines