AUTO suggests that a packer can/should reconsider the design setting at a/each residue. More...

#include <ResfileReader.hh>

Inheritance diagram for core::pack::task::AUTO:

Collaboration diagram for core::pack::task::AUTO:

Public Member Functions
virtual ResfileCommandOP	clone () const

virtual void	initialize_from_tokens (utility::vector1< std::string > const &tokens, Size &which_token, Size resid)
	AUTO. More...

virtual void	residue_action (PackerTask &, Size resid) const
	Modify the packer task with the command that was read in. More...

Public Member Functions inherited from core::pack::task::ResfileCommand
virtual	~ResfileCommand ()
	Automatically generated virtual destructor for class deriving directly from ReferenceCount. More...

Static Public Member Functions
static std::string	name ()

Detailed Description

AUTO suggests that a packer can/should reconsider the design setting at a/each residue.

This is a protocol-level flag to be used in non-vanilla packers. For example, one may want an ALLAA tag to be effective only if the residue is in an automatically-determined region of interest, without knowing which residues qualify a-priori