Inheritance diagram for LigandRepackMinimizeProtocol:

Public Member Functions
	LigandRepackMinimizeProtocol ()

void	apply (core::pose::Pose &pose) override
	Creates a new hierarchy of Movers for each Pose passed in. More...

	LigandRepackMinimizeProtocol ()

void	apply (core::pose::Pose &pose) override

Constructor & Destructor Documentation

◆ LigandRepackMinimizeProtocol() [1/2]

LigandRepackMinimizeProtocol::LigandRepackMinimizeProtocol ( )

inline

◆ LigandRepackMinimizeProtocol() [2/2]

LigandRepackMinimizeProtocol::LigandRepackMinimizeProtocol ( )

inline

Member Function Documentation

◆ apply() [1/2]

void LigandRepackMinimizeProtocol::apply ( core::pose::Pose & pose )

override

Creates a new hierarchy of Movers for each Pose passed in.

Some Movers (e.g. repack) require knowledge of the Pose to create, and are only valid for that Pose and other conformations of it (i.e. poses with the same number of residues, jumps, etc). In general, we expect each Pose coming in here to be from a different PDB file. The cost of creating these objects anew should be minimal compared to the processing work they do.

References create_a3b_hbs::i, basic::options::OptionKeys::in::file::movemap, beta_nonlocal::pose, oop_conformations::scorefxn, vancomycin::task, and basic::options::OptionKeys::packing::unboundrot.

Referenced by pyrosetta.distributed.tasks.rosetta_scripts.BaseRosettaScriptsTask::execute().

◆ apply() [2/2]