Rosetta  2020.50
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Friends Macros Pages
Classes | Namespaces
RigidChunkClaimer.hh File Reference
#include <protocols/topology_broker/RigidChunkClaimer.fwd.hh>
#include <protocols/topology_broker/claims/DofClaim.fwd.hh>
#include <protocols/topology_broker/TopologyClaimer.hh>
#include <core/pose/Pose.hh>
#include <protocols/loops/Loops.hh>
#include <utility/VirtualBase.hh>
#include <protocols/topology_broker/ClaimerMessage.hh>
#include <utility/vector1.hh>

Classes

class  protocols::topology_broker::RigidChunkClaimer
 defines a rigid part of structure... imagine a loop-relax application core structure is fixed via jumps and loops can move the rigid chunk takes a definition of rigid regions in form of an instance of Loops (just taken as bunch of start-end residue numbers — here defining the rigid residues and not the loops). the rigid chunk to keep its integrity will need jumps, the claimer will reuse jumps if somebody else claims them, or submit in finalize_claims his own jumps, if not enough jumps are present. in "bExclusive_ mode" the RigidChunk will reclaim any jump claim that is useful and wihin the rigid region. (i.e., foreign claim is dissallowed but own claim with same residues is issued — in this way the claimer uses e.g., beta-sheet jumps, where they are suggested the input pose is used to initialize the rigid region ( via copying of internal coordinates ) e.g., a hole in the structure shouldn't pose a problem, since we basically copy the atom-tree. More...
 
class  protocols::topology_broker::RigidChunkClaimer::CM_SuggestFixResidue
 
class  protocols::topology_broker::RigidChunkClaimer::JumpCalculator
 helper class – computes if we have all jupms needed to rigidify the chosen chunk and generate more jumps if needed. More...
 

Namespaces

 protocols
 The instance of Loops contained by AbrelaxApplication should be replaced by a LoopsOP.
 
 protocols::topology_broker