Rosetta
|
packing mover that makes extensive reuse of rotamer pair energies class declaration More...
#include <protocols/minimization_packing/GreenPacker.fwd.hh>
#include <protocols/moves/Mover.hh>
#include <core/chemical/AA.hh>
#include <core/chemical/ResidueType.fwd.hh>
#include <core/conformation/Residue.fwd.hh>
#include <utility/graph/Graph.fwd.hh>
#include <core/pack/interaction_graph/PrecomputedPairEnergiesInteractionGraph.fwd.hh>
#include <core/pack/task/TaskFactory.fwd.hh>
#include <core/pack/task/PackerTask.fwd.hh>
#include <core/pose/Pose.fwd.hh>
#include <core/scoring/EnergyMap.fwd.hh>
#include <core/scoring/methods/LongRangeTwoBodyEnergy.fwd.hh>
#include <core/scoring/ScoreFunction.fwd.hh>
#include <core/scoring/ScoreType.hh>
#include <core/types.hh>
#include <utility/vector1.hh>
#include <utility/VirtualBase.hh>
#include <core/scoring/annealing/RotamerSets.fwd.hh>
Classes | |
class | protocols::minimization_packing::MinimalRotamer |
class | protocols::minimization_packing::GroupDiscriminator |
Interface class used to break a pose down into a set of component "groups" where intra-group rotamer-pair energies are preserved between calls to the GreenPacker. E.g. in rigid-body docking between two proteins, chains 1 and 2 define groups 1 and 2. In rigid-body docking between two domains of the same chain, those residues upstream of jump 1 define group 1, and those downstream of jump 1 define group 2. In loop modelling, the static background is group 1, and the loop itself is group 0, since loop residues will have their bb dofs change regularly between repackings. More... | |
class | protocols::minimization_packing::UserDefinedGroupDiscriminator |
class | protocols::minimization_packing::ChainGroupDiscriminator |
class | protocols::minimization_packing::GreenPacker |
Namespaces | |
protocols | |
The instance of Loops contained by AbrelaxApplication should be replaced by a LoopsOP. | |
protocols::minimization_packing | |
packing mover that makes extensive reuse of rotamer pair energies class declaration