Package org.biopax.paxtools.impl.level3
Class ComplexImpl
- All Implemented Interfaces:
Serializable,Cloneable,BioPAXElement,Complex,Controller,Entity,Level3Element,Named,Observable,PhysicalEntity,XReferrable
- See Also:
-
Field Summary
Fields inherited from interface org.biopax.paxtools.model.BioPAXElement
UNKNOWN_DOUBLE, UNKNOWN_FLOAT, UNKNOWN_INT -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionvoidaddComponent(PhysicalEntity component) Defines the PhysicalEntity subunits of this complex.voidaddComponentStoichiometry(Stoichiometry stoichiometry) The stoichiometry of components in a complex.protected voidDefines the PhysicalEntity subunits of this complex.The stoichiometry of components in a complex.Gets theEntityReferences of the member simple physical entities.Overridden to provide better downcastingGets the member physical entities which are not complex.protected Set<SimplePhysicalEntity> voidremoveComponent(PhysicalEntity component) Defines the PhysicalEntity subunits of this complex.voidremoveComponentStoichiometry(Stoichiometry stoichiometry) The stoichiometry of components in a complex.protected booleansemanticallyEquivalent(BioPAXElement element) protected voidsetComponent(Set<PhysicalEntity> component) protected voidsetComponentStoichiometry(Set<Stoichiometry> stoichiometry) Methods inherited from class org.biopax.paxtools.impl.level3.PhysicalEntityImpl
addFeature, addMemberPhysicalEntity, addNotFeature, equivalenceCode, getCellularLocation, getComponentOf, getControllerOf, getFeature, getMemberPhysicalEntity, getMemberPhysicalEntityOf, getNotFeature, hasEquivalentCellularLocation, hasEquivalentFeatures, locationAndFeatureCode, removeFeature, removeMemberPhysicalEntity, removeNotFeature, setCellularLocationMethods inherited from class org.biopax.paxtools.impl.level3.EntityImpl
addAvailability, addDataSource, addEvidence, getAvailability, getDataSource, getEvidence, getParticipantOf, removeAvailability, removeDataSource, removeEvidence, setDataSourceMethods inherited from class org.biopax.paxtools.impl.level3.NamedImpl
addName, getDisplayName, getName, getStandardName, removeName, setDisplayName, setName, setStandardNameMethods inherited from class org.biopax.paxtools.impl.level3.XReferrableImpl
addXref, getXref, removeXref, setXrefMethods inherited from class org.biopax.paxtools.impl.level3.L3ElementImpl
addComment, getComment, removeComment, setCommentMethods inherited from class org.biopax.paxtools.impl.BioPAXElementImpl
equals, getAnnotations, getUri, hashCode, isEquivalent, toStringMethods inherited from class java.lang.Object
clone, finalize, getClass, notify, notifyAll, wait, wait, waitMethods inherited from interface org.biopax.paxtools.model.BioPAXElement
equivalenceCode, getAnnotations, getUri, isEquivalentMethods inherited from interface org.biopax.paxtools.model.level3.Controller
getControllerOfMethods inherited from interface org.biopax.paxtools.model.level3.Entity
addAvailability, addDataSource, getAvailability, getDataSource, getParticipantOf, removeAvailability, removeDataSourceMethods inherited from interface org.biopax.paxtools.model.level3.Level3Element
addComment, getComment, removeCommentMethods inherited from interface org.biopax.paxtools.model.level3.Named
addName, getDisplayName, getName, getStandardName, removeName, setDisplayName, setName, setStandardNameMethods inherited from interface org.biopax.paxtools.model.level3.Observable
addEvidence, getEvidence, removeEvidenceMethods inherited from interface org.biopax.paxtools.model.level3.PhysicalEntity
addFeature, addMemberPhysicalEntity, addNotFeature, getCellularLocation, getComponentOf, getFeature, getMemberPhysicalEntity, getMemberPhysicalEntityOf, getNotFeature, hasEquivalentCellularLocation, hasEquivalentFeatures, removeFeature, removeMemberPhysicalEntity, removeNotFeature, setCellularLocationMethods inherited from interface org.biopax.paxtools.model.level3.XReferrable
addXref, getXref, removeXref
-
Constructor Details
-
ComplexImpl
public ComplexImpl()
-
-
Method Details
-
getModelInterface
Description copied from interface:PhysicalEntityOverridden to provide better downcasting- Specified by:
getModelInterfacein interfaceBioPAXElement- Specified by:
getModelInterfacein interfacePhysicalEntity- Overrides:
getModelInterfacein classPhysicalEntityImpl- Returns:
- an interface from
org.biopax.paxtools.modelpackage corresponding to a BioPAX class.
-
getComponent
Description copied from interface:ComplexDefines the PhysicalEntity subunits of this complex. This property should not contain other complexes, i.e. it should always be a flat representation of the complex. For example, if two protein complexes join to form a single larger complex via a complex assembly interaction, the component of the new complex should be the individual proteins of the smaller complexes, not the two smaller complexes themselves. Exceptions are black-box complexes (i.e. complexes in which the component property is empty), which may be used as component of other complexes because their constituent parts are unknown / unspecified. The reason for keeping complexes flat is to signify that there is no information stored in the way complexes are nested, such as assembly order. Otherwise, the complex assembly order may be implicitly encoded and interpreted by some users, while others created hierarchical complexes randomly, which could lead to data loss. Additionally, the physicalEntityParticipants used in the component property are in the context of the complex, thus should not be reused between complexes. For instance, a protein may participate in two different complexes, but have different conformation in each.- Specified by:
getComponentin interfaceComplex- Returns:
- components of this complex
-
addComponent
Description copied from interface:ComplexDefines the PhysicalEntity subunits of this complex. This property should not contain other complexes, i.e. it should always be a flat representation of the complex. For example, if two protein complexes join to form a single larger complex via a complex assembly interaction, the component of the new complex should be the individual proteins of the smaller complexes, not the two smaller complexes themselves. Exceptions are black-box complexes (i.e. complexes in which the component property is empty), which may be used as component of other complexes because their constituent parts are unknown / unspecified. The reason for keeping complexes flat is to signify that there is no information stored in the way complexes are nested, such as assembly order. Otherwise, the complex assembly order may be implicitly encoded and interpreted by some users, while others created hierarchical complexes randomly, which could lead to data loss. Additionally, the physicalEntityParticipants used in the component property are in the context of the complex, thus should not be reused between complexes. For instance, a protein may participate in two different complexes, but have different conformation in each.- Specified by:
addComponentin interfaceComplex- Parameters:
component- to be added as a new member
-
removeComponent
Description copied from interface:ComplexDefines the PhysicalEntity subunits of this complex. This property should not contain other complexes, i.e. it should always be a flat representation of the complex. For example, if two protein complexes join to form a single larger complex via a complex assembly interaction, the component of the new complex should be the individual proteins of the smaller complexes, not the two smaller complexes themselves. Exceptions are black-box complexes (i.e. complexes in which the component property is empty), which may be used as component of other complexes because their constituent parts are unknown / unspecified. The reason for keeping complexes flat is to signify that there is no information stored in the way complexes are nested, such as assembly order. Otherwise, the complex assembly order may be implicitly encoded and interpreted by some users, while others created hierarchical complexes randomly, which could lead to data loss. Additionally, the physicalEntityParticipants used in the component property are in the context of the complex, thus should not be reused between complexes. For instance, a protein may participate in two different complexes, but have different conformation in each.- Specified by:
removeComponentin interfaceComplex- Parameters:
component- to be removed from members.
-
setComponent
-
getComponentStoichiometry
Description copied from interface:ComplexThe stoichiometry of components in a complex.- Specified by:
getComponentStoichiometryin interfaceComplex- Returns:
- the stoichiometry of components in a complex.
-
addComponentStoichiometry
Description copied from interface:ComplexThe stoichiometry of components in a complex.- Specified by:
addComponentStoichiometryin interfaceComplex- Parameters:
stoichiometry- add a stoichiometry for the member.
-
removeComponentStoichiometry
Description copied from interface:ComplexThe stoichiometry of components in a complex.- Specified by:
removeComponentStoichiometryin interfaceComplex- Parameters:
stoichiometry- remove a stoichiometry for the member.
-
setComponentStoichiometry
-
getSimpleMembers
Description copied from interface:ComplexGets the member physical entities which are not complex. When the complex is nested, members of inner complexes are added to the returned set recursively.- Specified by:
getSimpleMembersin interfaceComplex- Returns:
- non-complex member physical entities
-
getSimpleMembers
-
collectSimpleMembersRecursive
-
getMemberReferences
Description copied from interface:ComplexGets theEntityReferences of the member simple physical entities. When the complex is nested, contents of the member complexes are retrieved recursively.- Specified by:
getMemberReferencesin interfaceComplex- Returns:
- non-complex members' entity references
-
semanticallyEquivalent
- Overrides:
semanticallyEquivalentin classPhysicalEntityImpl
-