As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Use IMP::rmf instead when interfacing with Chimera.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Use get_contents_version() instead as that is safer.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. With the advent of the ScoringFunction, this should not be needed.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. With the advent of the ScoringFunction, this should not be needed.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. No longer needed, just destroy the ScoreState itself.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. You should act directly on the ModelObjects instead.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. You should act directly on the ModelObjects instead.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. You should act directly on the ModelObjects instead.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. You should act directly on the ModelObjects instead.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. You should act directly on the ModelObjects instead.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. You should use a ScoringFunction or a RestraintSet.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. You should use a ScoringFunction or a RestraintSet.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. This is slow and dependent on the order of elements in the tuple.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. This is slow and dependent on the order of elements in the tuple.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. This is slow and dependent on the order of elements in the tuple.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. This is slow and dependent on the order of elements in the tuple.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Declare the methods directly and use IMP_PAIR_CONTAINER_METHODS
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Declare the methods directly and use IMP_QUAD_CONTAINER_METHODS
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Declare the methods directly and use IMP_SINGLETON_CONTAINER_METHODS
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Declare the methods directly and use IMP_TRIPLET_CONTAINER_METHODS
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. As of IMP 2.1. Use IMPMODULE_DEPRECATED_CLASS_DEF() instead
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. As of IMP 2.1. Use IMPMODULE_DEPRECATED_FUNCTION_DEF() instead
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Deprecated as of IMP 2.1. Use IMPMODULE_DEPRECATED_CLASS_DEF().
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. As of IMP 2.1. Use IMPMODULE_DEPRECATED_FUNCTION_DEF() instead.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Declare methods yourself and use IMP_PAIR_MODIFIER_METHODS to fill in the rest.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Declare methods yourself and use IMP_PAIR_PREDICATE_METHODS to fill in the rest.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Declare methods yourself and use IMP_QUAD_MODIFIER_METHODS to fill in the rest.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Declare methods yourself and use IMP_QUAD_PREDICATE_METHODS to fill in the rest.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Declare methods yourself and use IMP_SINGLETON_MODIFIER_METHODS to fill in the rest.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Declare methods yourself and use IMP_SINGLETON_PREDICATE_METHODS to fill in the rest.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Declare methods yourself and use IMP_TRIPLET_MODIFIER_METHODS to fill in the rest.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Declare methods yourself and use IMP_TRIPLET_PREDICATE_METHODS to fill in the rest.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Declare the methods directly and use IMP_PAIR_CONTAINER_METHODS
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Declare methods yourself and use IMP_PAIR_MODIFIER_METHODS to fill in the rest.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Use IMP_PAIR_PREDICATE_METHODS instead and declare the methods you implement.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Declare the methods directly and use IMP_QUAD_CONTAINER_METHODS
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Declare methods yourself and use IMP_QUAD_MODIFIER_METHODS to fill in the rest.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Use IMP_QUAD_PREDICATE_METHODS instead and declare the methods you implement.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Declare the methods directly and use IMP_SINGLETON_CONTAINER_METHODS
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Declare methods yourself and use IMP_SINGLETON_MODIFIER_METHODS to fill in the rest.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Use IMP_SINGLETON_PREDICATE_METHODS instead and declare the methods you implement.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Declare the methods directly and use IMP_TRIPLET_CONTAINER_METHODS
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Declare methods yourself and use IMP_TRIPLET_MODIFIER_METHODS to fill in the rest.
As of IMP release 2.1. See the IMP Deprecation Policy for more information about deprecation in IMP. Use IMP_TRIPLET_PREDICATE_METHODS instead and declare the methods you implement.