libsbml.Compartment Class Reference

Inheritance diagram for libsbml.Compartment:

[legend]

List of all members.

---

Detailed Description

LibSBML implementation of SBML's Compartment construct.

A compartment in SBML represents a bounded space in which species are located. Compartments do not necessarily have to correspond to actual structures inside or outside of a biological cell.

It is important to note that although compartments are optional in the overall definition of Model, every species in an SBML model must be located in a compartment. This in turn means that if a model defines any species, the model must also define at least one compartment. The reason is simply that species represent physical things, and therefore must exist somewhere. Compartments represent the somewhere.

Compartment has one required attribute, 'id', to give the compartment a unique identifier by which other parts of an SBML model definition can refer to it. A compartment can also have an optional 'name' attribute of type string. Identifiers and names must be used according to the guidelines described in the SBML specification (e.g., Section 3.3 in the Level 2 Version 4 specification).

Each compartment in a model may optionally be designated as belonging to a particular compartment type. The optional attribute 'compartmentType' is used identify the compartment type represented by the Compartment structure. The 'compartmentType' attribute's value must be the identifier of a CompartmentType instance defined in the model. If the 'compartmentType' attribute is not present on a particular compartment definition, a unique virtual compartment type is assumed for that compartment, and no other compartment can belong to that compartment type. The values of 'compartmentType' attributes on compartments have no effect on the numerical interpretation of a model. Simulators and other numerical analysis software may ignore 'compartmentType' attributes.

Compartment also has an optional attribute 'spatialDimensions', whose value must be a positive integer indicating the number of spatial dimensions possessed by the compartment. The maximum value is 3, meaning a three-dimensional structure (a volume). Other permissible values are 2 (for a two-dimensional area), 1 (for a one-dimensional curve), and 0 (for a point). The default value of 'spatialDimensions' is 3.

Compartment has another optional attribute named 'size', representing the initial total size of the compartment. The 'size' attribute must be a floating-point value and may represent a volume (if the compartment is a three-dimensional one), or an area (if the compartment is two-dimensional), or a length (if the compartment is one-dimensional). There is no default value of compartment size in SBML Level 2. In particular, a missing 'size' value does not imply that the compartment size is 1. (This is unlike the definition of compartment 'volume' in SBML Level 1.) When the compartment's 'spatialDimensions' attribute does not have a value of 0, a missing value of 'size' for a given compartment signifies that the value either is unknown, or to be obtained from an external source, or determined by an InitialAssignment, AssignmentRule, AlgebraicRule or RateRule elsewhere in the model. The 'size' attribute must not be present if the 'spatialDimensions' attribute has a value of 0; otherwise, a logical inconsistency would exist because a zero-dimensional object cannot have a physical size.

The units associated with a compartment's 'size' attribute value may be set using the optional Compartment attribute 'units'. The default units, and the kinds of units allowed as values of the attribute 'units', interact with the number of spatial dimensions of the compartment. The value of the 'units' attribute of a Compartment object must be one of the base units (see Unit), or the predefined unit identifiers volume, area, length or dimensionless, or a new unit defined by a UnitDefinition object in the enclosing Model, subject to the restrictions detailed in the following table:

Restrictions on values permitted for compartment size and units attributes.

Value of spatialDimensions	size allowed?	units allowed?	Allowable kinds of units	Default value of attribute units
"3"	yes	yes	units of volume, or dimensionless	"volume"
"2"	yes	yes	units of area, or dimensionless	"area"
"1"	yes	yes	units of length, or dimensionless	"length"
"0"	no	no	(no units allowed)

In SBML Level 2, the units of the compartment size, as defined by the 'units' attribute or (if 'units' is not set) the default value listed in the table above, are used in the following ways when the compartment has a 'spatialDimensions' value greater than 0:

• The value of the 'units' attribute is used as the units of the compartment identifier when the identifier appears as a numerical quantity in a mathematical formula expressed in MathML.

• The math element of an AssignmentRule or InitialAssignment referring to this compartment must have identical units.

• In RateRule objects that set the rate of change of the compartment's size, the units of the rule's math element must be identical to the compartment's 'units' attribute divided by the default time units. (In other words, the units for the rate of change of compartment size are compartment size/time units.

• When a Species is to be treated in terms of concentrations or density, the units of the spatial size portion of the concentration value (i.e., the denominator in the units formula substance/size) are those indicated by the value of the 'units' attribute on the compartment in which the species is located.

Compartments with 'spatialDimensions'=0 require special treatment in this framework. If a compartment has no size or dimensional units, how should such a compartment's identifier be interpreted when it appears in mathematical formulas? The answer is that such a compartment's identifier should not appear in mathematical formulas in the first place—it has no value, and its value cannot change. Note also that a zero-dimensional compartment is a point, and species located at points can only be described in terms of amounts, not spatially-dependent measures such as concentration. Since SBML KineticLaw formulas are already in terms of substance/time and not (say) concentration/time, volume or other factors in principle are not needed for species located in zero-dimensional compartments.

Compartment has another optional attribute named 'constant'. This takes a boolean value indicating whether the compartment's size stays constant or can vary during a simulation. A value of false indicates the compartment's 'size' can be changed by other constructs in SBML. A value of true indicates the compartment's 'size' cannot be changed by any other construct except InitialAssignment. In the special case of 'spatialDimensions'=0, the value cannot be changed by InitialAssignment either. The default value for the 'constant' attribute is true because in the most common modeling scenarios at the time of this writing, compartment sizes remain constant. The 'constant' attribute must default to or be set to true if the value of the 'spatialDimensions' attribute is 0, because a zero-dimensional compartment cannot ever have a size.

Finally, Compartment has an optional attribute named 'outside', whose value can be the identifier of another Compartment object defined in the enclosing Model object. Doing so means that the other compartment contains it or is outside of it. This enables the representation of simple topological relationships between compartments, for those simulation systems that can make use of the information (e.g., for drawing simple diagrams of compartments). There are two restrictions on the containment relationships in SBML. First, because a compartment with 'spatialDimensions' of 0 has no size, such a compartment cannot act as the container of any other compartment except compartments that also have 'spatialDimensions' values of 0. Second, the directed graph formed by representing Compartment structures as vertexes and the 'outside' attribute values as edges must be acyclic. The latter condition is imposed to prevent a compartment from being contained inside itself. In the absence of a value for 'outside', compartment definitions in SBML Level 2 do not have any implied spatial relationships between each other.

It is worth noting that in SBML, there is no relationship between compartment sizes when compartment positioning is expressed using the 'outside' attribute. The size of a given compartment does not in any sense include the sizes of other compartments having it as the value of their 'outside' attributes. In other words, if a compartment B has the identifier of compartment A as its 'outside' attribute value, the size of A does not include the size of B. The compartment sizes are separate.

Note:

the 'size' attribute on a compartment must be defined as optional; however, it is extremely good practice to specify values for compartment sizes when such values are available. There are three major technical reasons for this. First, if the model contains any species whose initial amounts are given in terms of concentrations, and there is at least one reaction in the model referencing such a species, then the model is numerically incomplete if it lacks a value for the size of the compartment in which the species is located. The reason is simply that SBML Reaction objects defined in units of substance/time, not concentration per time, and thus the compartment size must at some point be used to convert from species concentration to substance units. Second, models ideally should be instantiable in a variety of simulation frameworks. A commonly-used one is the discrete stochastic framework in which species are represented as item counts (e.g., molecule counts). If species' initial quantities are given in terms of concentrations or densities, it is impossible to convert the values to item counts without knowing compartment sizes. Third, if a model contains multiple compartments whose sizes are not all identical to each other, it is impossible to quantify the reaction rate expressions without knowing the compartment volumes. The reason for the latter is again that reaction rates in SBML are defined in terms of substance/time, and when species quantities are given in terms of concentrations or densities, the compartment sizes become factors in the reaction rate expressions.

Definition at line 11824 of file libsbml.py.

Public Member Functions
def	__eq__
def	__init__
def	__init__
def	__ne__
def	addCVTerm
def	appendAnnotation
def	appendNotes
def	clone
def	getAncestorOfType
def	getAnnotation
def	getAnnotationString
def	getColumn
def	getCompartmentType
def	getConstant
def	getCVTerm
def	getCVTerms
def	getDerivedUnitDefinition
def	getElementName
def	getId
def	getLevel
def	getLine
def	getMetaId
def	getModel
def	getName
def	getNamespaces
def	getNotes
def	getNotesString
def	getNumCVTerms
def	getOutside
def	getParentSBMLObject
def	getResourceBiologicalQualifier
def	getResourceModelQualifier
def	getSBMLDocument
def	getSBOTerm
def	getSBOTermID
def	getSize
def	getSpatialDimensions
def	getTypeCode
def	getUnits
def	getVersion
def	getVolume
def	hasRequiredAttributes
def	hasRequiredElements
def	hasValidLevelVersionNamespaceCombination
def	initDefaults
def	isSetAnnotation
def	isSetCompartmentType
def	isSetId
def	isSetMetaId
def	isSetName
def	isSetNotes
def	isSetOutside
def	isSetSBOTerm
def	isSetSize
def	isSetUnits
def	isSetVolume
def	setAnnotation
def	setCompartmentType
def	setConstant
def	setId
def	setMetaId
def	setName
def	setNamespaces
def	setNotes
def	setOutside
def	setSBOTerm
def	setSize
def	setSpatialDimensions
def	setUnits
def	setVolume
def	toSBML
def	unsetAnnotation
def	unsetCompartmentType
def	unsetCVTerms
def	unsetMetaId
def	unsetName
def	unsetNotes
def	unsetOutside
def	unsetSBOTerm
def	unsetSize
def	unsetUnits
def	unsetVolume
Public Attributes
	this

---

Member Function Documentation

def libsbml.SBase.__eq__	(		self,
			rhs
	)			[inherited]

Definition at line 3296 of file libsbml.py.

def libsbml.SBase.__init__	(		self,
			args,
			kwargs
	)			[inherited]

Reimplemented in libsbml.SimpleSpeciesReference.

Definition at line 1771 of file libsbml.py.

def libsbml.Compartment.__init__	(		self,
			args
	)

Python method signature(s):

__init__(self, unsigned int level, unsigned int version)    Compartment
__init__(self, SBMLNamespaces sbmlns)    Compartment
__init__(self, Compartment orig)    Compartment

Predicate returning true or false depending on whether all the required attributes for this Compartment object have been set.

Note:

The required attributes for a Compartment object are: id (name in L1)

Returns:

a boolean value indicating whether all the required attributes for this object have been defined.

Deprecated:

libSBML internal

Definition at line 12014 of file libsbml.py.

def libsbml.SBase.__ne__	(		self,
			rhs
	)			[inherited]

Definition at line 3303 of file libsbml.py.

def libsbml.SBase.addCVTerm	(		self,
			args
	)			[inherited]

Python method signature(s):

addCVTerm(self, CVTerm term)    int

Adds a copy of the given CVTerm to this SBML object.

Parameters:

term

the CVTerm to assign

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_OPERATION_FAILED
• LIBSBML_UNEXPECTED_ATTRIBUTE
• LIBSBML_INVALID_OBJECT

Note:

Since the CV Term uses the metaid of the object as a reference, if the object has no metaid set the CVTerm will not be added.

Warning:

The fact that this method copies the object passed to it means that the caller will be left holding a physically different object instance than the one contained in this object. Changes made to the original object instance (such as resetting attribute values) will not affect the instance added here. In addition, the caller should make sure to free the original object if it is no longer being used, or else a memory leak will result.

Definition at line 2974 of file libsbml.py.

def libsbml.SBase.appendAnnotation	(		self,
			args
	)			[inherited]

Python method signature(s):

appendAnnotation(self, XMLNode annotation)    int
appendAnnotation(self, string annotation)    int

Appends the annotation content given by annotation to any existing content in the 'annotation' subelement of this object.

Whereas the SBase 'notes' subelement is a container for content to be shown directly to humans, the 'annotation' element is a container for optional software-generated content not meant to be shown to humans. Every object derived from SBase can have its own value for 'annotation'. The element's content type is XML type any, allowing essentially arbitrary well-formed XML data content.

SBML places a few restrictions on the organization of the content of annotations; these are intended to help software tools read and write the data as well as help reduce conflicts between annotations added by different tools. Please see the SBML specifications for more details.

Unlike SBase.setAnnotation(const XMLNode* annotation) or SBase.setAnnotation(const std.string& annotation), this method allows other annotations to be preserved when an application adds its own data.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Parameters:

annotation

an XML string that is to be copied and appended to the content of the 'annotation' subelement of this object

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_OPERATION_FAILED

See also:

getAnnotationString()

isSetAnnotation()

setAnnotation(const XMLNode* annotation)

setAnnotation(const std.string& annotation)

appendAnnotation(const XMLNode* annotation)

unsetAnnotation()

Reimplemented in libsbml.Model, and libsbml.SpeciesReference.

Definition at line 2624 of file libsbml.py.

def libsbml.SBase.appendNotes	(		self,
			args
	)			[inherited]

Python method signature(s):

appendNotes(self, XMLNode notes)    int
appendNotes(self, string notes)    int

Appends notes content to the 'notes' element attached to this object.

The content in notes is copied.

The optional element named 'notes', present on every major SBML component type, is intended as a place for storing optional information intended to be seen by humans. An example use of the 'notes' element would be to contain formatted user comments about the model element in which the 'notes' element is enclosed. Every object derived directly or indirectly from type SBase can have a separate value for 'notes', allowing users considerable freedom when adding comments to their models. The format of 'notes' elements must be XHTML 1.0. The SBML Level 2 specification has considerable detail about how 'notes' element content must be handled; please refer to the specifications.

Parameters:

notes

an XML string that is to appended to the content of the 'notes' subelement of this object

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_INVALID_OBJECT
• LIBSBML_OPERATION_FAILED

See also:

getNotesString()

isSetNotes()

setNotes(const XMLNode* notes)

setNotes(const std.string& notes)

appendNotes(const XMLNode* notes)

unsetNotes()

Definition at line 2726 of file libsbml.py.

def libsbml.Compartment.clone

(

self

)

Python method signature(s):

clone(self)    Compartment

Creates and returns a deep copy of this Compartment.

Returns:

a (deep) copy of this Compartment.

Reimplemented from libsbml.SBase.

Definition at line 12039 of file libsbml.py.

def libsbml.SBase.getAncestorOfType	(		self,
			args
	)			[inherited]

Python method signature(s):

getAncestorOfType(self, SBMLTypeCode_t type)    SBase

Returns the ancestor SBML object that corresponds to the given SBMLTypeCode_t.

This function allows any object to determine its exact location/function within a model. For example a StoichiometryMath object has ancestors of type SpeciesReference, ListOfProducts/ListOfReactants/ListOfModifiers, Reaction, ListOfReactions and Model; any of which can be accessed via this function.

Parameters:

type

the SBMLTypeCode_t of the ancestor to be returned.

Returns:

the ancestor SBML object of this SBML object, that corresponds to the given SBMLTypeCode_t, NULL if none exists.

Definition at line 2115 of file libsbml.py.

def libsbml.SBase.getAnnotation

(

self

)

[inherited]

Python method signature(s):

getAnnotation(self)    XMLNode

Returns the content of the 'annotation' subelement of this object as an XML node tree.

Whereas the SBase 'notes' subelement is a container for content to be shown directly to humans, the 'annotation' element is a container for optional software-generated content not meant to be shown to humans. Every object derived from SBase can have its own value for 'annotation'. The element's content type is XML type any, allowing essentially arbitrary well-formed XML data content.

SBML places a few restrictions on the organization of the content of annotations; these are intended to help software tools read and write the data as well as help reduce conflicts between annotations added by different tools. Please see the SBML specifications for more details.

The annotations returned by this method will be in XML form. LibSBML provides an object model and related interfaces for certain specific kinds of annotations, namely model history information and RDF content. See the ModelHistory, CVTerm and RDFAnnotationParser classes for more information about the facilities available.

Returns:

the annotation of this SBML object as an XMLNode

See also:

getAnnotationString()

isSetAnnotation()

setAnnotation(const XMLNode* annotation)

setAnnotation(const std.string& annotation)

appendAnnotation(const XMLNode* annotation)

appendAnnotation(const std.string& annotation)

unsetAnnotation()

Definition at line 1971 of file libsbml.py.

def libsbml.SBase.getAnnotationString

(

self

)

[inherited]

Python method signature(s):

getAnnotationString(self)    string

Returns the content of the 'annotation' subelement of this object as a character string.

Whereas the SBase 'notes' subelement is a container for content to be shown directly to humans, the 'annotation' element is a container for optional software-generated content not meant to be shown to humans. Every object derived from SBase can have its own value for 'annotation'. The element's content type is XML type any, allowing essentially arbitrary well-formed XML data content.

SBML places a few restrictions on the organization of the content of annotations; these are intended to help software tools read and write the data as well as help reduce conflicts between annotations added by different tools. Please see the SBML specifications for more details.

The annotations returned by this method will be in string form.

Returns:

the annotation string of this SBML object.

See also:

getAnnotation()

isSetAnnotation()

setAnnotation(const XMLNode* annotation)

setAnnotation(const std.string& annotation)

appendAnnotation(const XMLNode* annotation)

appendAnnotation(const std.string& annotation)

unsetAnnotation()

Definition at line 2014 of file libsbml.py.

def libsbml.SBase.getColumn

(

self

)

[inherited]

Python method signature(s):

getColumn(self)    unsigned int

Returns the column number on which this object first appears in the XML representation of the SBML document.

Returns:

the column number of this SBML object.

See also:

getLine()

Definition at line 2217 of file libsbml.py.

def libsbml.Compartment.getCompartmentType

(

self

)

Python method signature(s):

getCompartmentType(self)    string

Get the compartment type of this Compartment, as indicated by the Compartment object's 'compartmentType' attribute value.

Returns:

the value of the 'compartmentType' attribute of this Compartment as a string.

Definition at line 12103 of file libsbml.py.

def libsbml.Compartment.getConstant

(

self

)

Python method signature(s):

getConstant(self)    bool

Get the value of the 'constant' attribute of this Compartment.

Returns:

true if this Compartment's size is flagged as being constant, false otherwise.

Definition at line 12217 of file libsbml.py.

def libsbml.SBase.getCVTerm	(		self,
			args
	)			[inherited]

Python method signature(s):

getCVTerm(self, unsigned int n)    CVTerm

Returns the nth CVTerm in the list of CVTerms of this SBML object.

Parameters:

n

unsigned int the index of the CVTerm to retrieve

Returns:

the nth CVTerm in the list of CVTerms for this SBML object.

Definition at line 3042 of file libsbml.py.

def libsbml.SBase.getCVTerms

(

self

)

[inherited]

Python method signature(s):

getCVTerms(self)    CVTermList

Get the CVTermList of CVTerm objects in this SBase.

Returns:

the CVTermList for this SBase.

Definition at line 3010 of file libsbml.py.

def libsbml.Compartment.getDerivedUnitDefinition	(		self,
			args
	)

Python method signature(s):

getDerivedUnitDefinition(self)    UnitDefinition
getDerivedUnitDefinition(self)    UnitDefinition

Constructs and returns a UnitDefinition that corresponds to the units of this Compartment's designated size.

Compartments in SBML have an attribute ('units') for declaring the units of measurement intended for the value of the compartment's size. In the absence of a value given for this attribute, the units are taken from the model's definition of 'volume', 'area', 'length' units, depending on the value given to this Compartment's 'size' attribute, or (if the Model does not redefine them) the corresponding SBML default units for those quantities. Following that procedure, the method getDerivedUnitDefinition() returns a UnitDefinition based on the interpreted units of this compartment's size.

Note that the functionality that facilitates unit analysis depends on the model as a whole. Thus, in cases where the object has not been added to a model or the model itself is incomplete, unit analysis is not possible and this method will return NULL.

Note also that unit declarations for Compartment are in terms of the identifier of a unit, but this method returns a UnitDefinition object, not a unit identifier. It does this by constructing an appropriate UnitDefinition. Callers may find this particularly useful when used in conjunction with the helper methods on UnitDefinition for comparing different UnitDefinition objects.

Returns:

a UnitDefinition that expresses the units of this Compartment.

See also:

getUnits()

Definition at line 12778 of file libsbml.py.

def libsbml.Compartment.getElementName

(

self

)

Python method signature(s):

getElementName(self)    string

Returns the XML element name of this object, which for Compartment, is always 'compartment'.

Returns:

the name of this element, i.e., 'compartment'.

Reimplemented from libsbml.SBase.

Definition at line 12850 of file libsbml.py.

def libsbml.Compartment.getId

(

self

)

Python method signature(s):

getId(self)    string

Returns the value of the 'id' attribute of this Compartment.

Returns:

the id of this Compartment.

Reimplemented from libsbml.SBase.

Definition at line 12073 of file libsbml.py.

def libsbml.SBase.getLevel

(

self

)

[inherited]

Python method signature(s):

getLevel(self)    unsigned int

Returns the SBML Level of the overall SBML document.

Returns:

the SBML level of this SBML object.

See also:

getVersion()

Definition at line 3134 of file libsbml.py.

def libsbml.SBase.getLine

(

self

)

[inherited]

Python method signature(s):

getLine(self)    unsigned int

Returns the line number on which this object first appears in the XML representation of the SBML document.

Returns:

the line number of this SBML object.

See also:

getColumn()

Definition at line 2199 of file libsbml.py.

def libsbml.SBase.getMetaId

(

self

)

[inherited]

Python method signature(s):

getMetaId(self)    string

Returns the value of the 'metaid' attribute of this object.

The optional attribute named 'metaid', present on every major SBML component type, is for supporting metadata annotations using RDF (Resource Description Format). The attribute value has the data type XML ID, the XML identifier type, which means each 'metaid' value must be globally unique within an SBML file. (Importantly, this uniqueness criterion applies across any attribute with type XML ID, not just the 'metaid' attribute used by SBML—something to be aware of if your application-specific XML content inside the 'annotation' subelement happens to use XML ID.) The 'metaid' value serves to identify a model component for purposes such as referencing that component from metadata placed within 'annotation' subelements.

Returns:

the metaid of this SBML object.

See also:

isSetMetaId()

setMetaId(const std.string& metaid)

Definition at line 1790 of file libsbml.py.

def libsbml.SBase.getModel

(

self

)

[inherited]

Python method signature(s):

getModel(self)    Model

Returns the Model object in which the current object is located.

Returns:

the parent Model of this SBML object.

Definition at line 3119 of file libsbml.py.

def libsbml.Compartment.getName

(

self

)

Python method signature(s):

getName(self)    string

Returns the value of the 'name' attribute of this Compartment.

Returns:

the name of this Compartment.

Reimplemented from libsbml.SBase.

Definition at line 12088 of file libsbml.py.

def libsbml.SBase.getNamespaces

(

self

)

[inherited]

Python method signature(s):

getNamespaces(self)    XMLNamespaces

Returns a list of the XML Namespaces declared on this SBML document.

Returns:

the XML Namespaces associated with this SBML object

Reimplemented in libsbml.SBMLDocument.

Definition at line 2053 of file libsbml.py.

def libsbml.SBase.getNotes

(

self

)

[inherited]

Python method signature(s):

getNotes(self)    XMLNode

Returns the content of the 'notes' subelement of this object as a tree of XML nodes.

The optional element named 'notes', present on every major SBML component type, is intended as a place for storing optional information intended to be seen by humans. An example use of the 'notes' element would be to contain formatted user comments about the model element in which the 'notes' element is enclosed. Every object derived directly or indirectly from type SBase can have a separate value for 'notes', allowing users considerable freedom when adding comments to their models. The format of 'notes' elements must be XHTML 1.0. The SBML Level 2 specification has considerable detail about how 'notes' element content must be handled; please refer to the specifications.

The 'notes' element content returned by this method will be in XML form, but libSBML does not provide an object model specifically for the content of notes. Callers will need to traverse the XML tree structure using the facilities available on XMLNode and related objects.

Returns:

the content of the 'notes' subelement of this SBML object.

See also:

getNotesString()

isSetNotes()

setNotes(const XMLNode* notes)

setNotes(const std.string& notes)

appendNotes(const XMLNode* notes)

appendNotes(const std.string& notes)

unsetNotes()

Definition at line 1891 of file libsbml.py.

def libsbml.SBase.getNotesString

(

self

)

[inherited]

Python method signature(s):

getNotesString(self)    string

Returns the content of the 'notes' subelement of this object as a string.

The optional element named 'notes', present on every major SBML component type, is intended as a place for storing optional information intended to be seen by humans. An example use of the 'notes' element would be to contain formatted user comments about the model element in which the 'notes' element is enclosed. Every object derived directly or indirectly from type SBase can have a separate value for 'notes', allowing users considerable freedom when adding comments to their models. The format of 'notes' elements must be XHTML 1.0. The SBML Level 2 specification has considerable detail about how 'notes' element content must be handled; please refer to the specifications.

Returns:

the content of the 'notes' subelement of this SBML object.

See also:

getNotes()

isSetNotes()

setNotes(const XMLNode* notes)

setNotes(const std.string& notes)

appendNotes(const XMLNode* notes)

appendNotes(const std.string& notes)

unsetNotes()

Definition at line 1934 of file libsbml.py.

def libsbml.SBase.getNumCVTerms

(

self

)

[inherited]

Python method signature(s):

getNumCVTerms(self)    unsigned int

Returns the number of CVTerm objects in the annotations of this SBML object.

Returns:

the number of CVTerms for this SBML object.

Definition at line 3026 of file libsbml.py.

def libsbml.Compartment.getOutside

(

self

)

Python method signature(s):

getOutside(self)    string

Get the identifier, if any, of the compartment that is designated as being outside of this one.

Returns:

the value of the 'outside' attribute of this Compartment.

Definition at line 12201 of file libsbml.py.

def libsbml.SBase.getParentSBMLObject

(

self

)

[inherited]

Python method signature(s):

getParentSBMLObject(self)    SBase

Returns the parent SBML object.

This method is convenient when holding an object nested inside other objects in an SBML model. It allows direct access to the <model> element containing it.

Returns:

the parent SBML object of this SBML object.

Definition at line 2096 of file libsbml.py.

def libsbml.SBase.getResourceBiologicalQualifier	(		self,
			args
	)			[inherited]

Python method signature(s):

getResourceBiologicalQualifier(self, string resource)    BiolQualifierType_t

Returns the BiologicalQualifier associated with this resource, or BQB_UNKNOWN if the resource does not exist.

Parameters:

resource

string representing the resource; e.g., 'http://www.geneontology.org/GO:0005892'

Returns:

the BiolQualifierType_t value associated with the resource

Definition at line 3081 of file libsbml.py.

def libsbml.SBase.getResourceModelQualifier	(		self,
			args
	)			[inherited]

Python method signature(s):

getResourceModelQualifier(self, string resource)    ModelQualifierType_t

Returns the ModelQualifier associated with this resource, or BQM_UNKNOWN if the resource does not exist.

Parameters:

resource

string representing the resource; e.g., 'http://www.geneontology.org/GO:0005892'

Returns:

the ModelQualifierType_t value associated with the resource

Definition at line 3100 of file libsbml.py.

def libsbml.SBase.getSBMLDocument	(		self,
			args
	)			[inherited]

Python method signature(s):

getSBMLDocument(self)    SBMLDocument
getSBMLDocument(self)    SBMLDocument

Returns the parent SBMLDocument object.

LibSBML uses the class SBMLDocument as a top-level container for storing SBML content and data associated with it (such as warnings and error messages). An SBML model in libSBML is contained inside an SBMLDocument object. SBMLDocument corresponds roughly to the class Sbml defined in the SBML Level 2 specification, but it does not have a direct correspondence in SBML Level 1. (But, it is created by libSBML no matter whether the model is Level 1 or Level 2.)

This method allows the SBMLDocument for the current object to be retrieved.

Returns:

the parent SBMLDocument object of this SBML object.

Definition at line 2068 of file libsbml.py.

def libsbml.SBase.getSBOTerm

(

self

)

[inherited]

Python method signature(s):

getSBOTerm(self)    int

Returns the integer portion of the value of the 'sboTerm' attribute of this object.

In SBML Level 2 Versions 2, 3 and 4, the data type of the attribute is a string of the form SBO:NNNNNNN, where NNNNNNN is a seven digit integer number; libSBML simplifies the representation by only storing the NNNNNNN integer portion. Thus, in libSBML, the 'sboTerm' attribute on SBase has data type int, and SBO identifiers are stored simply as integers. SBO terms are a type of optional annotation, and each different class of SBML object derived from SBase imposes its own requirements about the values permitted for 'sboTerm'. Please consult the SBML Level 2 Version 4 specification for more information about the use of SBO and the 'sboTerm' attribute.

Returns:

the value of the 'sboTerm' attribute as an integer, or -1 if the value is not set.

Definition at line 2141 of file libsbml.py.

def libsbml.SBase.getSBOTermID

(

self

)

[inherited]

Python method signature(s):

getSBOTermID(self)    string

Returns the string representation of the 'sboTerm' attribute of this object.

In SBML Level 2 Versions 2, 3 and 4, the data type of the attribute is a string of the form SBO:NNNNNNN, where NNNNNNN is a seven digit integer number; libSBML simplifies the representation by only storing the NNNNNNN integer portion. Thus, in libSBML, the 'sboTerm' attribute on SBase has data type int, and SBO identifiers are stored simply as integers. This function recreates the string representation from the stored value. SBO terms are a type of optional annotation, and each different class of SBML object derived from SBase imposes its own requirements about the values permitted for 'sboTerm'. Please consult the SBML Level 2 Version 4 specification for more information about the use of SBO and the 'sboTerm' attribute.

Returns:

the value of the 'sboTerm' attribute as a string of the form SBO:NNNNNNN, or an empty string if the value is not set.

Definition at line 2169 of file libsbml.py.

def libsbml.Compartment.getSize

(

self

)

Python method signature(s):

getSize(self)    float

Get the size of this Compartment

This method is identical to getVolume(). In SBML Level 1, compartments are always three-dimensional constructs and only have volumes, whereas in SBML Level 2, compartments may be other than three-dimensional and therefore the 'volume' attribute is named 'size' in Level 2. LibSBML provides both getSize() and getVolume() for easier compatibility between SBML Levels.

Returns:

the value of the 'size' attribute ('volume' in Level 1) of this Compartment as a float-point number.

See also:

isSetSize()

Definition at line 12136 of file libsbml.py.

def libsbml.Compartment.getSpatialDimensions

(

self

)

Python method signature(s):

getSpatialDimensions(self)    unsigned int

Get the number of spatial dimensions of this Compartment object.

Returns:

the value of the 'spatialDimensions' attribute of this Compartment as an unsigned integer

Definition at line 12120 of file libsbml.py.

def libsbml.Compartment.getTypeCode

(

self

)

Python method signature(s):

getTypeCode(self)    SBMLTypeCode_t

Returns the libSBML type code for this SBML object.

Returns:

the SBML type code for this object, or SBML_UNKNOWN (default).

See also:

getElementName()

Reimplemented from libsbml.SBase.

Definition at line 12821 of file libsbml.py.

def libsbml.Compartment.getUnits

(

self

)

Python method signature(s):

getUnits(self)    string

Get the units of this compartment's size or volume.

Returns:

the value of the 'units' attribute of this Compartment.

Definition at line 12186 of file libsbml.py.

def libsbml.SBase.getVersion

(

self

)

[inherited]

Python method signature(s):

getVersion(self)    unsigned int

Returns the Version within the SBML Level of the overall SBML document.

Returns:

the SBML version of this SBML object.

See also:

getLevel()

Definition at line 3151 of file libsbml.py.

def libsbml.Compartment.getVolume

(

self

)

Python method signature(s):

getVolume(self)    float

(For SBML Level 1) Get the volume of this Compartment

This method is identical to getSize(). In SBML Level 1, compartments are always three-dimensional constructs and only have volumes, whereas in SBML Level 2, compartments may be other than three-dimensional and therefore the 'volume' attribute is named 'size' in Level 2. LibSBML provides both getSize() and getVolume() for easier compatibility between SBML Levels.

Returns:

the value of the 'volume' attribute ('size' in Level 2) of this Compartment, as a floating-point number.

See also:

isSetVolume()

Definition at line 12161 of file libsbml.py.

def libsbml.Compartment.hasRequiredAttributes

(

self

)

Python method signature(s):

hasRequiredAttributes(self)    bool

Predicate returning true or false depending on whether all the required attributes for this Compartment object have been set.

Note:

The required attributes for a Compartment object are: id (name in L1)

Returns:

a boolean value indicating whether all the required attributes for this object have been defined.

Reimplemented from libsbml.SBase.

Definition at line 12866 of file libsbml.py.

def libsbml.SBase.hasRequiredElements

(

self

)

[inherited]

Python method signature(s):

hasRequiredElements(self)    bool

Subclasses should override this method to write out their contained SBML objects as XML elements. Be sure to call your parents implementation of this method as well. For example:

SBase.writeElements(stream); mReactans.write(stream); mProducts.write(stream); ...

Deprecated:

libSBML internal

Reimplemented in libsbml.Model, libsbml.FunctionDefinition, libsbml.UnitDefinition, libsbml.InitialAssignment, libsbml.Rule, libsbml.Constraint, libsbml.KineticLaw, libsbml.Event, libsbml.EventAssignment, libsbml.Trigger, libsbml.Delay, and libsbml.StoichiometryMath.

Definition at line 3275 of file libsbml.py.

def libsbml.SBase.hasValidLevelVersionNamespaceCombination

(

self

)

[inherited]

Python method signature(s):

hasValidLevelVersionNamespaceCombination(self)    bool

Predicate returning true or false depending on whether this object's level/version and namespace values correspond to a valid SBML specification.

The valid combinations of SBML Level, Version and Namespace as of this release of libSBML are the following:

• Level 1 Version 2 'http://www.sbml.org/sbml/level1'
• Level 2 Version 1 'http://www.sbml.org/sbml/level2'
• Level 2 Version 2 'http://www.sbml.org/sbml/level2/version2'
• Level 2 Version 3 'http://www.sbml.org/sbml/level2/version3'
• Level 2 Version 4 'http://www.sbml.org/sbml/level2/version4'

Returns:

true if the level, version and namespace values of this SBML object correspond to a valid set of values, false otherwise.

Definition at line 3192 of file libsbml.py.

def libsbml.Compartment.initDefaults

(

self

)

Python method signature(s):

initDefaults(self)

Initializes the fields of this Compartment to the defaults defined in the specification of the relevant Level/Version of SBML.

• (SBML Level 1 only) sets attribute 'volume' to 1.0
• (SBML Level 2 only) sets attribute 'spatialDimensions' to 3
• (SBML Level 2 only) sets attribute 'constant' to 1 (true)

Definition at line 12054 of file libsbml.py.

def libsbml.SBase.isSetAnnotation

(

self

)

[inherited]

Python method signature(s):

isSetAnnotation(self)    bool

Predicate returning true or false depending on whether this object's 'annotation' subelement exists and has content.

Whereas the SBase 'notes' subelement is a container for content to be shown directly to humans, the 'annotation' element is a container for optional software-generated content not meant to be shown to humans. Every object derived from SBase can have its own value for 'annotation'. The element's content type is XML type any, allowing essentially arbitrary well-formed XML data content.

SBML places a few restrictions on the organization of the content of annotations; these are intended to help software tools read and write the data as well as help reduce conflicts between annotations added by different tools. Please see the SBML specifications for more details.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Returns:

true if a 'annotation' subelement exists, false otherwise.

See also:

getAnnotation()

getAnnotationString()

setAnnotation(const XMLNode* annotation)

setAnnotation(const std.string& annotation)

appendAnnotation(const XMLNode* annotation)

appendAnnotation(const std.string& annotation)

unsetAnnotation()

Definition at line 2387 of file libsbml.py.

def libsbml.Compartment.isSetCompartmentType

(

self

)

Python method signature(s):

isSetCompartmentType(self)    bool

Predicate returning true or false depending on whether this Compartment's 'compartmentType' attribute has been set.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Returns:

true if the 'compartmentType' attribute of this Compartment has been set, false otherwise.

Definition at line 12271 of file libsbml.py.

def libsbml.Compartment.isSetId

(

self

)

Python method signature(s):

isSetId(self)    bool

Predicate returning true or false depending on whether this Compartment's 'id' attribute has been set.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Returns:

true if the 'id' attribute of this Compartment has been set, false otherwise.

Reimplemented from libsbml.SBase.

Definition at line 12233 of file libsbml.py.

def libsbml.SBase.isSetMetaId

(

self

)

[inherited]

Python method signature(s):

isSetMetaId(self)    bool

Predicate returning true or false depending on whether this object's 'metaid' attribute has been set.

The optional attribute named 'metaid', present on every major SBML component type, is for supporting metadata annotations using RDF (Resource Description Format). The attribute value has the data type XML ID, the XML identifier type, which means each 'metaid' value must be globally unique within an SBML file. (Importantly, this uniqueness criterion applies across any attribute with type XML ID, not just the 'metaid' attribute used by SBML—something to be aware of if your application-specific XML content inside the 'annotation' subelement happens to use XML ID.) The 'metaid' value serves to identify a model component for purposes such as referencing that component from metadata placed within 'annotation' subelements.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Returns:

true if the 'metaid' attribute of this SBML object has been set, false otherwise.

See also:

getMetaId()

setMetaId(const std.string& metaid)

Definition at line 2235 of file libsbml.py.

def libsbml.Compartment.isSetName

(

self

)

Python method signature(s):

isSetName(self)    bool

Predicate returning true or false depending on whether this Compartment's 'name' attribute has been set.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Returns:

true if the 'name' attribute of this Compartment has been set, false otherwise.

Reimplemented from libsbml.SBase.

Definition at line 12252 of file libsbml.py.

def libsbml.SBase.isSetNotes

(

self

)

[inherited]

Python method signature(s):

isSetNotes(self)    bool

Predicate returning true or false depending on whether this object's 'notes' subelement exists and has content.

The optional element named 'notes', present on every major SBML component type, is intended as a place for storing optional information intended to be seen by humans. An example use of the 'notes' element would be to contain formatted user comments about the model element in which the 'notes' element is enclosed. Every object derived directly or indirectly from type SBase can have a separate value for 'notes', allowing users considerable freedom when adding comments to their models. The format of 'notes' elements must be XHTML 1.0. The SBML Level 2 specification has considerable detail about how 'notes' element content must be handled; please refer to the specifications.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Returns:

true if a 'notes' subelement exists, false otherwise.

See also:

getNotes()

getNotesString()

setNotes(const XMLNode* notes)

setNotes(const std.string& notes)

appendNotes(const XMLNode* notes)

appendNotes(const std.string& notes)

unsetNotes()

Definition at line 2348 of file libsbml.py.

def libsbml.Compartment.isSetOutside

(

self

)

Python method signature(s):

isSetOutside(self)    bool

Predicate returning true or false depending on whether this Compartment's 'outside' attribute has been set.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Returns:

true if the 'outside' attribute of this Compartment has been set, false otherwise.

Definition at line 12370 of file libsbml.py.

def libsbml.SBase.isSetSBOTerm

(

self

)

[inherited]

Python method signature(s):

isSetSBOTerm(self)    bool

Predicate returning true or false depending on whether this object's 'sboTerm' attribute has been set.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Returns:

true if the 'sboTerm' attribute of this SBML object has been set, false otherwise.

Definition at line 2427 of file libsbml.py.

def libsbml.Compartment.isSetSize

(

self

)

Python method signature(s):

isSetSize(self)    bool

Predicate returning true or false depending on whether this Compartment's 'size' attribute has been set.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

This method is similar but not identical to isSetVolume(). The latter should be used in the context of SBML Level 1 models instead of isSetSize() because isSetVolume() performs extra processing to take into account the difference in default values between SBML Levels 1 and 2.

Returns:

true if the 'size' attribute ('volume' in Level) of this Compartment has been set, false otherwise.

See also:

isSetVolume()

setSize (float value)

Definition at line 12290 of file libsbml.py.

def libsbml.Compartment.isSetUnits

(

self

)

Python method signature(s):

isSetUnits(self)    bool

Predicate returning true or false depending on whether this Compartment's 'units' attribute has been set.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Returns:

true if the 'units' attribute of this Compartment has been set, false otherwise.

Definition at line 12351 of file libsbml.py.

def libsbml.Compartment.isSetVolume

(

self

)

Python method signature(s):

isSetVolume(self)    bool

(For SBML Level 1) Predicate returning true or false depending on whether this Compartment's 'volume' attribute has been set.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

This method is similar but not identical to isSetSize(). The latter should not be used in the context of SBML Level 1 models because this method (isSetVolume()) performs extra processing to take into account the difference in default values between SBML Levels 1 and 2.

Returns:

true if the 'volume' attribute ('size' in L2) of this Compartment has been set, false otherwise.

See also:

isSetSize()

setVolume (float value)

Note:

In SBML Level 1, a compartment's volume has a default value (1.0) and therefore this method will always return true. In Level 2, a compartment's size (the equivalent of SBML Level 1's 'volume') is optional and has no default value, and therefore may or may not be set.

Definition at line 12318 of file libsbml.py.

def libsbml.SBase.setAnnotation	(		self,
			args
	)			[inherited]

Python method signature(s):

setAnnotation(self, XMLNode annotation)    int
setAnnotation(self, string annotation)    int

Sets the value of the 'annotation' subelement of this SBML object to a copy of annotation given as a character string.

Whereas the SBase 'notes' subelement is a container for content to be shown directly to humans, the 'annotation' element is a container for optional software-generated content not meant to be shown to humans. Every object derived from SBase can have its own value for 'annotation'. The element's content type is XML type any, allowing essentially arbitrary well-formed XML data content.

SBML places a few restrictions on the organization of the content of annotations; these are intended to help software tools read and write the data as well as help reduce conflicts between annotations added by different tools. Please see the SBML specifications for more details.

Call this method will result in any existing content of the 'annotation' subelement to be discarded. Unless you have taken steps to first copy and reconstitute any existing annotations into the annotation that is about to be assigned, it is likely that performing such wholesale replacement is unfriendly towards other software applications whose annotations are discarded. An alternative may be to use SBase.appendAnnotation(const XMLNode* annotation) or SBase.appendAnnotation(const std.string& annotation).

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Parameters:

annotation

an XML string that is to be used as the content of the 'annotation' subelement of this object

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_OPERATION_FAILED

See also:

getAnnotationString()

isSetAnnotation()

setAnnotation(const XMLNode* annotation)

appendAnnotation(const XMLNode* annotation)

appendAnnotation(const std.string& annotation)

unsetAnnotation()

Reimplemented in libsbml.Model, and libsbml.SpeciesReference.

Definition at line 2568 of file libsbml.py.

def libsbml.Compartment.setCompartmentType	(		self,
			args
	)

Python method signature(s):

setCompartmentType(self, string sid)    int

Sets the 'compartmentType' attribute of this Compartment.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Parameters:

sid

the identifier of a CompartmentType object defined elsewhere in this Model.

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_INVALID_ATTRIBUTE_VALUE
• LIBSBML_UNEXPECTED_ATTRIBUTE

Definition at line 12455 of file libsbml.py.

def libsbml.Compartment.setConstant	(		self,
			args
	)

Python method signature(s):

setConstant(self, bool value)    int

Sets the value of the 'constant' attribute of this Compartment.

Parameters:

value

a boolean indicating whether the size/volume of this compartment should be considered constant (true) or variable (false)

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_UNEXPECTED_ATTRIBUTE

Definition at line 12615 of file libsbml.py.

def libsbml.Compartment.setId	(		self,
			args
	)

Python method signature(s):

setId(self, string sid)    int

Sets the value of the 'id' attribute of this Compartment.

The string sid is copied. Note that SBML has strict requirements for the syntax of identifiers. The following is summary of the definition of the SBML identifier type SId (here expressed in an extended form of BNF notation):

  letter ::= 'a'..'z','A'..'Z'
  digit  ::= '0'..'9'
  idChar ::= letter | digit | '_'
  SId    ::= ( letter | '_' ) idChar*

The equality of SBML identifiers is determined by an exact character sequence match; i.e., comparisons must be performed in a case-sensitive manner. In addition, there are a few conditions for the uniqueness of identifiers in an SBML model. Please consult the SBML specifications for the exact formulations.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Parameters:

sid

the string to use as the identifier of this Compartment

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_INVALID_ATTRIBUTE_VALUE

Reimplemented from libsbml.SBase.

Definition at line 12389 of file libsbml.py.

def libsbml.SBase.setMetaId	(		self,
			args
	)			[inherited]

Python method signature(s):

setMetaId(self, string metaid)    int

Sets the value of the 'metaid' attribute of this object.

The string metaid is copied. The value of metaid must be an identifier conforming to the syntax defined by the XML 1.0 data type ID. Among other things, this type requires that a value is unique among all the values of type XML ID in an SBMLDocument. Although SBML only uses XML ID for the 'metaid' attribute, callers should be careful if they use XML ID's in XML portions of a model that are not defined by SBML, such as in the application-specific content of the 'annotation' subelement.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Parameters:

metaid

the identifier string to use as the value of the 'metaid' attribute

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_INVALID_ATTRIBUTE_VALUE
• LIBSBML_UNEXPECTED_ATTRIBUTE

See also:

getMetaId()

isSetMetaId()

Definition at line 2446 of file libsbml.py.

def libsbml.Compartment.setName	(		self,
			args
	)

Python method signature(s):

setName(self, string name)    int

Sets the value of the 'name' attribute of this Compartment.

The string in name is copied.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Parameters:

name

the new name for the Compartment

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_INVALID_ATTRIBUTE_VALUE

Reimplemented from libsbml.SBase.

Definition at line 12429 of file libsbml.py.

def libsbml.SBase.setNamespaces	(		self,
			args
	)			[inherited]

Python method signature(s):

setNamespaces(self, XMLNamespaces xmlns)    int

Sets the namespaces relevant of this SBML object.

Parameters:

xmlns

the namespaces to set

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS

Definition at line 2811 of file libsbml.py.

def libsbml.SBase.setNotes	(		self,
			args
	)			[inherited]

Python method signature(s):

setNotes(self, XMLNode notes)    int
setNotes(self, string notes)    int

Sets the value of the 'notes' subelement of this SBML object to a copy of the string notes.

Any existing content of the 'notes' subelement is discarded.

The optional element named 'notes', present on every major SBML component type, is intended as a place for storing optional information intended to be seen by humans. An example use of the 'notes' element would be to contain formatted user comments about the model element in which the 'notes' element is enclosed. Every object derived directly or indirectly from type SBase can have a separate value for 'notes', allowing users considerable freedom when adding comments to their models. The format of 'notes' elements must be XHTML 1.0. The SBML Level 2 specification has considerable detail about how 'notes' element content must be handled; please refer to the specifications.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Parameters:

notes

an XML string that is to be used as the content of the 'notes' subelement of this object

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_INVALID_OBJECT
• LIBSBML_OPERATION_FAILED

See also:

getNotesString()

isSetNotes()

setNotes(const XMLNode* notes)

appendNotes(const XMLNode* notes)

appendNotes(const std.string& notes)

unsetNotes()

Definition at line 2676 of file libsbml.py.

def libsbml.Compartment.setOutside	(		self,
			args
	)

Python method signature(s):

setOutside(self, string sid)    int

Sets the 'outside' attribute of this Compartment.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Parameters:

sid

the identifier of a compartment that encloses this one.

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_INVALID_ATTRIBUTE_VALUE

Definition at line 12591 of file libsbml.py.

def libsbml.SBase.setSBOTerm	(		self,
			args
	)			[inherited]

Python method signature(s):

setSBOTerm(self, int value)    int
setSBOTerm(self, string sboid)    int

Sets the value of the 'sboTerm' attribute.

In SBML Level 2 Versions 2, 3 and 4, the data type of the SBML 'sboTerm' attribute is a string of the form SBO:NNNNNNN, where NNNNNNN is a seven digit integer number; libSBML simplifies the representation by only storing the NNNNNNN integer portion. Thus, in libSBML, the 'sboTerm' attribute on SBase has data type int, and SBO identifiers are stored simply as integers. SBO terms are a type of optional annotation, and each different class of SBML object derived from SBase imposes its own requirements about the values permitted for 'sboTerm'. Please consult the SBML Level 2 Version 4 specification for more information about the use of SBO and the 'sboTerm' attribute.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Parameters:

value

the NNNNNNN integer portion of the SBO identifier

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_INVALID_ATTRIBUTE_VALUE
• LIBSBML_UNEXPECTED_ATTRIBUTE

Definition at line 2774 of file libsbml.py.

def libsbml.Compartment.setSize	(		self,
			args
	)

Python method signature(s):

setSize(self, float value)    int

Sets the 'size' attribute (or 'volume' in SBML Level 1) of this Compartment.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

This method is identical to setVolume() and is provided for compatibility between SBML Level 1 and Level 2.

Parameters:

value

a float representing the size of this compartment instance in whatever units are in effect for the compartment.

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS

Definition at line 12511 of file libsbml.py.

def libsbml.Compartment.setSpatialDimensions	(		self,
			args
	)

Python method signature(s):

setSpatialDimensions(self, unsigned int value)    int

Sets the 'spatialDimensions' attribute of this Compartment.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

If value is not one of 0, 1, 2, or 3, this method will have no effect (i.e., the 'spatialDimensions' attribute will not be set).

Parameters:

value

an unsigned integer indicating the number of dimensions of this compartment.

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_INVALID_ATTRIBUTE_VALUE
• LIBSBML_UNEXPECTED_ATTRIBUTE

Definition at line 12481 of file libsbml.py.

def libsbml.Compartment.setUnits	(		self,
			args
	)

Python method signature(s):

setUnits(self, string sid)    int

Sets the 'units' attribute of this Compartment.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Parameters:

sid

the identifier of the defined units to use.

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_INVALID_ATTRIBUTE_VALUE

Definition at line 12567 of file libsbml.py.

def libsbml.Compartment.setVolume	(		self,
			args
	)

Python method signature(s):

setVolume(self, float value)    int

Sets the 'volume' attribute (or 'size' in SBML Level 2) of this Compartment.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

This method is identical to setVolume() and is provided for compatibility between SBML Level 1 and Level 2.

Parameters:

value

a float representing the volume of this compartment instance in whatever units are in effect for the compartment.

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS

Definition at line 12539 of file libsbml.py.

def libsbml.SBase.toSBML

(

self

)

[inherited]

Python method signature(s):

toSBML(self)    char

Returns a string that consists of the partial SBML describing this object. This is primarily provided for testing and debugging purposes. It may be removed in a future version of libSBML.

Returns:

the partial SBML that describes this SBML object.

Definition at line 3237 of file libsbml.py.

def libsbml.SBase.unsetAnnotation

(

self

)

[inherited]

Python method signature(s):

unsetAnnotation(self)    int

Unsets the value of the 'annotation' subelement of this SBML object.

Whereas the SBase 'notes' subelement is a container for content to be shown directly to humans, the 'annotation' element is a container for optional software-generated content not meant to be shown to humans. Every object derived from SBase can have its own value for 'annotation'. The element's content type is XML type any, allowing essentially arbitrary well-formed XML data content.

SBML places a few restrictions on the organization of the content of annotations; these are intended to help software tools read and write the data as well as help reduce conflicts between annotations added by different tools. Please see the SBML specifications for more details.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS

See also:

getAnnotation()

getAnnotationString()

isSetAnnotation()

setAnnotation(const XMLNode* annotation)

setAnnotation(const std.string& annotation)

appendAnnotation(const XMLNode* annotation)

appendAnnotation(const std.string& annotation)

Definition at line 2910 of file libsbml.py.

def libsbml.Compartment.unsetCompartmentType

(

self

)

Python method signature(s):

unsetCompartmentType(self)    int

Unsets the value of the 'compartmentType' attribute of this Compartment.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

See also:

setCompartmentType(const std.string& sid)

isSetCompartmentType()

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_OPERATION_FAILED

Definition at line 12661 of file libsbml.py.

def libsbml.SBase.unsetCVTerms

(

self

)

[inherited]

Python method signature(s):

unsetCVTerms(self)    int

Clears the list of CVTerms of this SBML object.

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_OPERATION_FAILED

Definition at line 3060 of file libsbml.py.

def libsbml.SBase.unsetMetaId

(

self

)

[inherited]

Python method signature(s):

unsetMetaId(self)    int

Unsets the value of the 'metaid' attribute of this SBML object.

The optional attribute named 'metaid', present on every major SBML component type, is for supporting metadata annotations using RDF (Resource Description Format). The attribute value has the data type XML ID, the XML identifier type, which means each 'metaid' value must be globally unique within an SBML file. (Importantly, this uniqueness criterion applies across any attribute with type XML ID, not just the 'metaid' attribute used by SBML—something to be aware of if your application-specific XML content inside the 'annotation' subelement happens to use XML ID.) The 'metaid' value serves to identify a model component for purposes such as referencing that component from metadata placed within 'annotation' subelements.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_OPERATION_FAILED

Definition at line 2832 of file libsbml.py.

def libsbml.Compartment.unsetName

(

self

)

Python method signature(s):

unsetName(self)    int

Unsets the value of the 'name' attribute of this Compartment.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_OPERATION_FAILED

Definition at line 12639 of file libsbml.py.

def libsbml.SBase.unsetNotes

(

self

)

[inherited]

Python method signature(s):

unsetNotes(self)    int

Unsets the value of the 'notes' subelement of this SBML object.

The optional element named 'notes', present on every major SBML component type, is intended as a place for storing optional information intended to be seen by humans. An example use of the 'notes' element would be to contain formatted user comments about the model element in which the 'notes' element is enclosed. Every object derived directly or indirectly from type SBase can have a separate value for 'notes', allowing users considerable freedom when adding comments to their models. The format of 'notes' elements must be XHTML 1.0. The SBML Level 2 specification has considerable detail about how 'notes' element content must be handled; please refer to the specifications.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS

See also:

getNotesString()

isSetNotes()

setNotes(const XMLNode* notes)

setNotes(const std.string& notes)

appendNotes(const XMLNode* notes)

appendNotes(const std.string& notes)

Definition at line 2869 of file libsbml.py.

def libsbml.Compartment.unsetOutside

(

self

)

Python method signature(s):

unsetOutside(self)    int

Unsets the value of the 'outside' attribute of this Compartment.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_OPERATION_FAILED

Definition at line 12756 of file libsbml.py.

def libsbml.SBase.unsetSBOTerm

(

self

)

[inherited]

Python method signature(s):

unsetSBOTerm(self)    int

Unsets the value of the 'sboTerm' attribute of this SBML object.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_UNEXPECTED_ATTRIBUTE

Definition at line 2952 of file libsbml.py.

def libsbml.Compartment.unsetSize

(

self

)

Python method signature(s):

unsetSize(self)    int

Unsets the value of the 'size' attribute of this Compartment.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS

Definition at line 12687 of file libsbml.py.

def libsbml.Compartment.unsetUnits

(

self

)

Python method signature(s):

unsetUnits(self)    int

Unsets the value of the 'units' attribute of this Compartment.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_OPERATION_FAILED

Definition at line 12734 of file libsbml.py.

def libsbml.Compartment.unsetVolume

(

self

)

Python method signature(s):

unsetVolume(self)    int

(For SBML Level 1) Unsets the value of the 'volume' attribute of this Compartment.

Some words of explanation about the set/unset/isSet methods: SBML Levels 1 and 2 define certain attributes on some classes of objects as optional. This requires an application to be careful about the distinction between two cases: (1) a given attribute has never been set to a value, and therefore should be assumed to have the SBML-defined default value, and (2) a given attribute has been set to a value, but the value happens to be an empty string. LibSBML supports these distinctions by providing methods to set, unset, and query the status of attributes that are optional. The methods have names of the form setAttribute(...), unsetAttribute(), and isSetAttribute(), where Attribute is the the name of the optional attribute in question.

In SBML Level 1, a Compartment volume has a default value (1.0) and therefore should always be set. In Level 2, 'size' is optional with no default value and as such may or may not be set.

Returns:

integer value indicating success/failure of the function. The possible values returned by this function are:

• LIBSBML_OPERATION_SUCCESS

Definition at line 12708 of file libsbml.py.

---

Member Data Documentation

libsbml.Compartment.this

Reimplemented from libsbml.SBase.

Definition at line 12038 of file libsbml.py.