Package org.biopax.paxtools.model.level3
Interface PhysicalEntity
- All Superinterfaces:
BioPAXElement,Cloneable,Controller,Entity,Level3Element,Named,Observable,Serializable,XReferrable
- All Known Subinterfaces:
Complex,Dna,DnaRegion,NucleicAcid,Protein,Rna,RnaRegion,SequenceEntity,SimplePhysicalEntity,SmallMolecule
- All Known Implementing Classes:
ComplexImpl,DnaImpl,DnaRegionImpl,NucleicAcidImpl,PhysicalEntityImpl,ProteinImpl,RnaImpl,RnaRegionImpl,SimplePhysicalEntityImpl,SmallMoleculeImpl
-
Field Summary
Fields inherited from interface org.biopax.paxtools.model.BioPAXElement
UNKNOWN_DOUBLE, UNKNOWN_FLOAT, UNKNOWN_INT -
Method Summary
Modifier and TypeMethodDescriptionvoidaddFeature(EntityFeature feature) voidaddMemberPhysicalEntity(PhysicalEntity memberPhysicalEntity) voidaddNotFeature(EntityFeature feature) A cellular location, e.g.Please avoid using this property in your BioPAX L3 models unless absolutely sure/required, for there is an alternative way (using PhysicalEntity/entityReference/memberEntityReference), and this will probably be deprecated in the future BioPAX releases.Class<? extends PhysicalEntity> Overridden to provide better downcastingbooleanbooleanvoidremoveFeature(EntityFeature feature) voidremoveMemberPhysicalEntity(PhysicalEntity memberPhysicalEntity) voidremoveNotFeature(EntityFeature feature) voidsetCellularLocation(CellularLocationVocabulary newCellularLocation) A cellular location, e.g.Methods 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.XReferrable
addXref, getXref, removeXref
-
Method Details
-
getComponentOf
-
getCellularLocation
CellularLocationVocabulary getCellularLocation()A cellular location, e.g. 'cytoplasm'. This should reference a term in the Gene Ontology Cellular Component ontology. The location referred to by this property should be as specific as is known. If an interaction is known to occur in multiple locations, separate interactions (and physicalEntities) must be created for each different location. If the location of a participant in a complex is unspecified, it may be assumed to be the same location as that of the complex. A molecule in two different cellular locations are considered two different physical entities.- Returns:
- cellular location of this physical entity
-
setCellularLocation
A cellular location, e.g. 'cytoplasm'. This should reference a term in the Gene Ontology Cellular Component ontology. The location referred to by this property should be as specific as is known. If an interaction is known to occur in multiple locations, separate interactions (and physicalEntities) must be created for each different location. If the location of a participant in a complex is unspecified, it may be assumed to be the same location as that of the complex. A molecule in two different cellular locations are considered two different physical entities.- Parameters:
newCellularLocation- for this physical entity
-
hasEquivalentFeatures
-
hasEquivalentCellularLocation
-
getFeature
Set<EntityFeature> getFeature() -
addFeature
-
removeFeature
-
getNotFeature
Set<EntityFeature> getNotFeature() -
addNotFeature
-
removeNotFeature
-
getMemberPhysicalEntity
Set<PhysicalEntity> getMemberPhysicalEntity()Please avoid using this property in your BioPAX L3 models unless absolutely sure/required, for there is an alternative way (using PhysicalEntity/entityReference/memberEntityReference), and this will probably be deprecated in the future BioPAX releases. It's usually hard to say what this relationship (grouping) means...- Returns:
- member physical entities
-
addMemberPhysicalEntity
-
removeMemberPhysicalEntity
-
getMemberPhysicalEntityOf
Set<PhysicalEntity> getMemberPhysicalEntityOf() -
getModelInterface
Class<? extends PhysicalEntity> getModelInterface()Overridden to provide better downcasting- Specified by:
getModelInterfacein interfaceBioPAXElement- Returns:
- an interface from
org.biopax.paxtools.modelpackage corresponding to a BioPAX class.
-