libSBML Python API
5.8.0
|
Implementation of SBML's Unit construct.
The SBML unit definition facility uses two classes of objects, UnitDefinition and Unit. The approach to defining units in SBML is compositional; for example, meter second –2 is constructed by combining a Unit object representing meter with another Unit object representing second –2. The combination is wrapped inside a UnitDefinition, which provides for assigning an identifier and optional name to the combination. The identifier can then be referenced from elsewhere in a model. Thus, the UnitDefinition class is the container, and Unit instances are placed inside UnitDefinition instances.
A Unit structure has four attributes named 'kind', 'exponent', 'scale' and 'multiplier'. It represents a (possibly transformed) reference to a base unit. The attribute 'kind' on Unit indicates the chosen base unit. Its value must be one of the text strings listed below; this list corresponds to SBML Level 3 Version 1 Core:
ampere | farad | joule | lux | radian | volt |
avogadro | gram | katal | metre | second | watt |
becquerel | gray | kelvin | mole | siemens | weber |
candela | henry | kilogram | newton | sievert | |
coulomb | hertz | litre | ohm | steradian | |
dimensionless | item | lumen | pascal | tesla |
A few small differences exist between the Level 3 list of base units and the list defined in other Level/Version combinations of SBML. Specifically, Levels of SBML before Level 3 do not define avogadro
; conversely, Level 2 Version 1 defines Celsius
, and Level 1 defines celsius
, meter
, and liter
, none of which are available in Level 3. In libSBML, each of the predefined base unit names is represented by an enumeration value whose name begins with the characters UNIT_KIND_
, discussed in a separate section below.
The attribute named 'exponent' on Unit represents an exponent on the unit. In SBML Level 2, the attribute is optional and has a default value of 1
(one); in SBML Level 3, the attribute is mandatory and there is no default value. A Unit structure also has an attribute called 'scale'; its value must be an integer exponent for a power-of-ten multiplier used to set the scale of the unit. For example, a unit having a 'kind' value of gram
and a 'scale' value of -3
signifies 10 –3 * gram, or milligrams. In SBML Level 2, the attribute is optional and has a default value of 0
(zero), because 10 0 = 1; in SBML Level 3, the attribute is mandatory and has no default value. Lastly, the attribute named 'multiplier' can be used to multiply the unit by a real-numbered factor; this enables the definition of units that are not power-of-ten multiples of SI units. For instance, a multiplier of 0.3048 could be used to define foot
as a measure of length in terms of a metre
. The 'multiplier' attribute is optional in SBML Level 2, where it has a default value of 1
(one); in SBML Level 3, the attribute is mandatory and has not default value.
As discussed above, SBML defines a set of base units which serves as the starting point for new unit definitions. This set of base units consists of the SI units and a small number of additional convenience units.
In SBML Level 2 Versions before Version 3, there existed an enumeration of units called UnitKind
. In Version 3, this enumeration was removed and the identifier class UnitSId
redefined to include the previous UnitKind
values as reserved symbols. This change has no net effect on permissible models, their representation or their syntax. The purpose of the change in the SBML specification was simply to clean up an inconsistency about the contexts in which these values were usable. However, libSBML maintains UnitKind in the form of of a set of static integer constants whose names begin with the characters UNIT_KIND_
. These constants are defined in the class libsbml.
As a consequence of the fact that libSBML supports models in all Levels and Versions of SBML, libSBML's set of UNIT_KIND_
values is a union of all the possible base unit names defined in the different SBML specifications. However, not every base unit is allowed in every Level+Version combination of SBML. Note in particular the following exceptions:
The alternate spelling 'meter'
is included in addition to the official SI spelling 'metre'
. This spelling is only permitted in SBML Level 1 models.
The alternate spelling 'liter'
is included in addition to the official SI spelling 'litre'
. This spelling is only permitted in SBML Level 1 models.
The unit 'Celsius'
is included because of its presence in specifications of SBML prior to SBML Level 2 Version 3.
avogadro
was introduced in SBML Level 3, and is only permitted for use in SBML Level 3 models. The table below lists the unit constants defined in libSBML, and their meanings.
Enumerator | Meaning |
---|---|
UNIT_KIND_AMPERE | The ampere unit. |
UNIT_KIND_AVOGADRO | The unit
dimensionless multiplied by the numerical value of Avogadro's
constant. (Only usable in SBML Level 3 models.) |
UNIT_KIND_BECQUEREL | The becquerel unit. |
UNIT_KIND_CANDELA | The candela unit. |
UNIT_KIND_CELSIUS | The Celsius unit. (Only usable in SBML Level 1 and SBML Level 2 Version 1 models.) |
UNIT_KIND_COULOMB | The coulomb unit. |
UNIT_KIND_DIMENSIONLESS | A pseudo-unit indicating a dimensionless quantity. |
UNIT_KIND_FARAD | The farad unit. |
UNIT_KIND_GRAM | The gram unit. |
UNIT_KIND_GRAY | The gray unit. |
UNIT_KIND_HENRY | The henry unit. |
UNIT_KIND_HERTZ | The hertz unit. |
UNIT_KIND_ITEM | A pseudo-unit representing a single "thing". |
UNIT_KIND_JOULE | The joule unit. |
UNIT_KIND_KATAL | The katal unit. |
UNIT_KIND_KELVIN | The kelvin unit. |
UNIT_KIND_KILOGRAM | The kilogram unit. |
UNIT_KIND_LITER | Alternate spelling of litre. |
UNIT_KIND_LITRE | The litre unit. |
UNIT_KIND_LUMEN | The lumen unit. |
UNIT_KIND_LUX | The lux unit. |
UNIT_KIND_METER | Alternate spelling of metre. |
UNIT_KIND_METRE | The metre unit. |
UNIT_KIND_MOLE | The mole unit. |
UNIT_KIND_NEWTON | The newton unit. |
UNIT_KIND_OHM | The ohm unit. |
UNIT_KIND_PASCAL | The pascal unit. |
UNIT_KIND_RADIAN | The radian unit. |
UNIT_KIND_SECOND | The second unit. |
UNIT_KIND_SIEMENS | The siemens unit. |
UNIT_KIND_SIEVERT | The sievert unit. |
UNIT_KIND_STERADIAN | The steradian unit. |
UNIT_KIND_TESLA | The tesla unit. |
UNIT_KIND_VOLT | The volt unit. |
UNIT_KIND_WATT | The watt unit. |
UNIT_KIND_WEBER | The weber unit. |
UNIT_KIND_INVALID | Marker used by libSBML to indicate an invalid or unset unit. |
|
inherited |
Python method signature(s):
addCVTerm(SBase self, CVTerm term, bool newBag=False)int addCVTerm(SBase self, CVTerm term)
int
Adds a copy of the given CVTerm object to this SBML object.
term | the CVTerm to assign. |
newBag | if True , creates a new RDF bag with the same identifier as a previous bag, and if False , adds the term to an existing RDF bag with the same type of qualifier as the term being added. |
|
inherited |
Python method signature(s):
appendAnnotation(SBase self, XMLNode annotation)int appendAnnotation(SBase self, string annotation)
int
This method has multiple variants that differ in the arguments they accept. Each is described separately below.
Method variant with the following signature:
appendAnnotation(XMLNode annotation)
Appends the given annotation
to 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() or SBase.setAnnotation(), this method allows other annotations to be preserved when an application adds its own data.
annotation | an XML structure that is to be copied and appended to the content of the 'annotation' subelement of this object |
Method variant with the following signature:
appendAnnotation(string annotation)
Appends the given annotation
to 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() or SBase.setAnnotation(), this method allows other annotations to be preserved when an application adds its own data.
annotation | an XML string that is to be copied and appended to the content of the 'annotation' subelement of this object |
|
inherited |
Python method signature(s):
appendNotes(SBase self, XMLNode notes)int appendNotes(SBase self, string notes)
int
This method has multiple variants that differ in the arguments they accept. Each is described separately below.
Method variant with the following signature:
appendNotes(string notes)
Appends the given notes
to the 'notes' subelement of this object.
The content of the parameter notes
is copied.
The optional SBML 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. To help verify the formatting of 'notes' content, libSBML provides the static utility method SyntaxChecker.hasExpectedXHTMLSyntax(); however, readers are urged to consult the appropriate SBML specification document for the Level and Version of their model for more in-depth explanations. The SBML Level 2 and 3 specifications have considerable detail about how 'notes' element content must be structured.
notes | an XML string that is to appended to the content of the 'notes' subelement of this object |
Method variant with the following signature:
appendNotes(XMLNode notes)
Appends the given notes
to the 'notes' subelement of this object.
The content of notes
is copied.
The optional SBML 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. To help verify the formatting of 'notes' content, libSBML provides the static utility method SyntaxChecker.hasExpectedXHTMLSyntax(); however, readers are urged to consult the appropriate SBML specification document for the Level and Version of their model for more in-depth explanations. The SBML Level 2 and 3 specifications have considerable detail about how 'notes' element content must be structured.
notes | an XML node structure that is to appended to the content of the 'notes' subelement of this object |
def libsbml.Unit.areEquivalent | ( | args | ) |
Python method signature(s):
areEquivalent(Unit unit1, Unit unit2)bool
Predicate returning True
if Unit objects are equivalent.
Two Unit objects are considered to be equivalent either if (1) both have a 'kind' attribute value of dimensionless
, or (2) their 'kind', 'exponent' and (for SBML Level 2 Version 1) 'offset' attribute values are equal. (Contrast this to the method areIdentical(), which compares Unit objects with respect to all attributes, not just the 'kind' and 'exponent'.)
True
if the 'kind' and 'exponent' attributes of unit1 are identical to the kind and exponent attributes of unit2, False
otherwise.def libsbml.Unit.areIdentical | ( | args | ) |
Python method signature(s):
areIdentical(Unit unit1, Unit unit2)bool
Predicate returning True
if two Unit objects are identical.
Two Unit objects are considered to be identical if they match in all attributes. (Contrast this to the method areEquivalent(), which compares Unit objects only with respect to certain attributes.)
True
if all the attributes of unit1 are identical to the attributes of unit2, False
otherwise.def libsbml.Unit.clone | ( | self | ) |
Implementation of SBML's Unit construct.
The SBML unit definition facility uses two classes of objects, UnitDefinition and Unit. The approach to defining units in SBML is compositional; for example, meter second –2 is constructed by combining a Unit object representing meter with another Unit object representing second –2. The combination is wrapped inside a UnitDefinition, which provides for assigning an identifier and optional name to the combination. The identifier can then be referenced from elsewhere in a model. Thus, the UnitDefinition class is the container, and Unit instances are placed inside UnitDefinition instances.
A Unit structure has four attributes named 'kind', 'exponent', 'scale' and 'multiplier'. It represents a (possibly transformed) reference to a base unit. The attribute 'kind' on Unit indicates the chosen base unit. Its value must be one of the text strings listed below; this list corresponds to SBML Level 3 Version 1 Core:
ampere | farad | joule | lux | radian | volt |
avogadro | gram | katal | metre | second | watt |
becquerel | gray | kelvin | mole | siemens | weber |
candela | henry | kilogram | newton | sievert | |
coulomb | hertz | litre | ohm | steradian | |
dimensionless | item | lumen | pascal | tesla |
A few small differences exist between the Level 3 list of base units and the list defined in other Level/Version combinations of SBML. Specifically, Levels of SBML before Level 3 do not define avogadro
; conversely, Level 2 Version 1 defines Celsius
, and Level 1 defines celsius
, meter
, and liter
, none of which are available in Level 3. In libSBML, each of the predefined base unit names is represented by an enumeration value whose name begins with the characters UNIT_KIND_
, discussed in a separate section below.
The attribute named 'exponent' on Unit represents an exponent on the unit. In SBML Level 2, the attribute is optional and has a default value of 1
(one); in SBML Level 3, the attribute is mandatory and there is no default value. A Unit structure also has an attribute called 'scale'; its value must be an integer exponent for a power-of-ten multiplier used to set the scale of the unit. For example, a unit having a 'kind' value of gram
and a 'scale' value of -3
signifies 10 –3 * gram, or milligrams. In SBML Level 2, the attribute is optional and has a default value of 0
(zero), because 10 0 = 1; in SBML Level 3, the attribute is mandatory and has no default value. Lastly, the attribute named 'multiplier' can be used to multiply the unit by a real-numbered factor; this enables the definition of units that are not power-of-ten multiples of SI units. For instance, a multiplier of 0.3048 could be used to define foot
as a measure of length in terms of a metre
. The 'multiplier' attribute is optional in SBML Level 2, where it has a default value of 1
(one); in SBML Level 3, the attribute is mandatory and has not default value.
As discussed above, SBML defines a set of base units which serves as the starting point for new unit definitions. This set of base units consists of the SI units and a small number of additional convenience units.
In SBML Level 2 Versions before Version 3, there existed an enumeration of units called UnitKind
. In Version 3, this enumeration was removed and the identifier class UnitSId
redefined to include the previous UnitKind
values as reserved symbols. This change has no net effect on permissible models, their representation or their syntax. The purpose of the change in the SBML specification was simply to clean up an inconsistency about the contexts in which these values were usable. However, libSBML maintains UnitKind in the form of of a set of static integer constants whose names begin with the characters UNIT_KIND_
. These constants are defined in the class libsbml.
As a consequence of the fact that libSBML supports models in all Levels and Versions of SBML, libSBML's set of UNIT_KIND_
values is a union of all the possible base unit names defined in the different SBML specifications. However, not every base unit is allowed in every Level+Version combination of SBML. Note in particular the following exceptions:
The alternate spelling 'meter'
is included in addition to the official SI spelling 'metre'
. This spelling is only permitted in SBML Level 1 models.
The alternate spelling 'liter'
is included in addition to the official SI spelling 'litre'
. This spelling is only permitted in SBML Level 1 models.
The unit 'Celsius'
is included because of its presence in specifications of SBML prior to SBML Level 2 Version 3.
avogadro
was introduced in SBML Level 3, and is only permitted for use in SBML Level 3 models. The table below lists the unit constants defined in libSBML, and their meanings.
Enumerator | Meaning |
---|---|
UNIT_KIND_AMPERE | The ampere unit. |
UNIT_KIND_AVOGADRO | The unit
dimensionless multiplied by the numerical value of Avogadro's
constant. (Only usable in SBML Level 3 models.) |
UNIT_KIND_BECQUEREL | The becquerel unit. |
UNIT_KIND_CANDELA | The candela unit. |
UNIT_KIND_CELSIUS | The Celsius unit. (Only usable in SBML Level 1 and SBML Level 2 Version 1 models.) |
UNIT_KIND_COULOMB | The coulomb unit. |
UNIT_KIND_DIMENSIONLESS | A pseudo-unit indicating a dimensionless quantity. |
UNIT_KIND_FARAD | The farad unit. |
UNIT_KIND_GRAM | The gram unit. |
UNIT_KIND_GRAY | The gray unit. |
UNIT_KIND_HENRY | The henry unit. |
UNIT_KIND_HERTZ | The hertz unit. |
UNIT_KIND_ITEM | A pseudo-unit representing a single "thing". |
UNIT_KIND_JOULE | The joule unit. |
UNIT_KIND_KATAL | The katal unit. |
UNIT_KIND_KELVIN | The kelvin unit. |
UNIT_KIND_KILOGRAM | The kilogram unit. |
UNIT_KIND_LITER | Alternate spelling of litre. |
UNIT_KIND_LITRE | The litre unit. |
UNIT_KIND_LUMEN | The lumen unit. |
UNIT_KIND_LUX | The lux unit. |
UNIT_KIND_METER | Alternate spelling of metre. |
UNIT_KIND_METRE | The metre unit. |
UNIT_KIND_MOLE | The mole unit. |
UNIT_KIND_NEWTON | The newton unit. |
UNIT_KIND_OHM | The ohm unit. |
UNIT_KIND_PASCAL | The pascal unit. |
UNIT_KIND_RADIAN | The radian unit. |
UNIT_KIND_SECOND | The second unit. |
UNIT_KIND_SIEMENS | The siemens unit. |
UNIT_KIND_SIEVERT | The sievert unit. |
UNIT_KIND_STERADIAN | The steradian unit. |
UNIT_KIND_TESLA | The tesla unit. |
UNIT_KIND_VOLT | The volt unit. |
UNIT_KIND_WATT | The watt unit. |
UNIT_KIND_WEBER | The weber unit. |
UNIT_KIND_INVALID | Marker used by libSBML to indicate an invalid or unset unit. |
clone(Unit self)Unit
Creates and returns a deep copy of this Unit.
def libsbml.Unit.convertToSI | ( | args | ) |
Python method signature(s):
convertToSI(Unit unit)UnitDefinition
Returns a UnitDefinition object containing the given unit
converted to the appropriate SI unit.
This method exists because some units can be expressed in terms of others when the same physical dimension is involved. For example, one hertz is identical to 1 sec-1, one litre is equivalent to 1 cubic decametre, and so on.
unit | the Unit object to convert to SI |
|
inherited |
Python method signature(s):
disablePackage(SBase self, string pkgURI, string pkgPrefix)int
Disables the given SBML Level 3 package
This method enables or disables the specified package on this object and other objects connected by child-parent links in the same SBMLDocument object.
pkgURI | the URI of the package |
pkgPrefix | the XML prefix of the package |
|
inherited |
Python method signature(s):
enablePackage(SBase self, string pkgURI, string pkgPrefix, bool flag)int
Enables or disables the given SBML Level 3 package
This method enables or disables the specified package on this object and other objects connected by child-parent links in the same SBMLDocument object.
pkgURI | the URI of the package |
pkgPrefix | the XML prefix of the package |
flag | whether to enable (True ) or disable (False ) the package |
|
inherited |
Python method signature(s):
getAncestorOfType(SBase self, int type, string pkgName="core")SBase getAncestorOfType(SBase self, int type)
SBase getAncestorOfType(SBase self, int type, string pkgName="core")
SBase getAncestorOfType(SBase self, int type)
SBase
Returns the first ancestor object that has the given SBML type code.
LibSBML attaches an identifying code to every kind of SBML object. These are known as SBML type codes. In the Python language interface for libSBML, the type codes are defined as static integer constants in the interface class libsbml. The names of the type codes all begin with the characters SBML_
.
This method searches the tree of objects that are parents of this object, and returns the first one that has the given SBML type code. If the optional argument pkgName
is given, it will cause the search to be limited to the SBML Level 3 package given.
type | the SBML type code of the object sought |
pkgName | (optional) the short name of an SBML Level 3 package to which the sought-after object must belong |
None
if no ancestor exists.
|
inherited |
Python method signature(s):
getAnnotation(SBase self)XMLNode getAnnotation(SBase self)
XMLNode
Returns the content of the 'annotation' subelement of this object as a tree of XMLNode objects.
Whereas the SBML '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.
|
inherited |
Python method signature(s):
getAnnotationString(SBase self)string getAnnotationString(SBase self)
string
Returns the content of the 'annotation' subelement of this object as a character string.
Whereas the SBML '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.
|
inherited |
Python method signature(s):
getColumn(SBase self)long
Returns the column number on which this object first appears in the XML representation of the SBML document.
|
inherited |
|
inherited |
Python method signature(s):
getCVTerms()CVTermList
Get the CVTermList of CVTerm objects in this SBase.
Returns the CVTermList for this SBase.
|
inherited |
Python method signature(s):
getElementByMetaId(SBase self, string metaid)SBase
Returns the first child element it can find with a specific 'metaid' attribute value, or None
if no such object is found.
metaid | string representing the 'metaid' attribute value of the object to find. |
|
inherited |
Python method signature(s):
getElementBySId(SBase self, string id)SBase
Returns the first child element found that has the given id
in the model-wide SId
namespace, or None
if no such object is found.
id | string representing the 'id' attribute value of the object to find. |
def libsbml.Unit.getElementName | ( | self | ) |
def libsbml.Unit.getExponent | ( | self | ) |
def libsbml.Unit.getExponentAsDouble | ( | self | ) |
def libsbml.Unit.getKind | ( | self | ) |
|
inherited |
Python method signature(s):
getLevel(SBase self)long
Returns the SBML Level of the SBMLDocument object containing this object.
|
inherited |
Python method signature(s):
getLine(SBase self)long
Returns the line number on which this object first appears in the XML representation of the SBML document.
|
inherited |
|
inherited |
|
inherited |
Python method signature(s):
getMetaId(SBase 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.
|
inherited |
|
inherited |
Python method signature(s):
getModelHistory(SBase self)ModelHistory getModelHistory(SBase self)
ModelHistory
Returns the ModelHistory object, if any, attached to this object.
None
if none exist.def libsbml.Unit.getMultiplier | ( | self | ) |
|
inherited |
Python method signature(s):
getNamespaces(SBase self)XMLNamespaces
Returns a list of the XML Namespaces declared on this SBML document.
The SBMLNamespaces object encapsulates SBML Level/Version/namespaces information. It is used to communicate the SBML Level, Version, and (in SBML Level 3) packages used in addition to SBML Level 3 Core.
|
inherited |
Python method signature(s):
getNotes(SBase self)XMLNode getNotes(SBase self)
XMLNode
Returns the content of the 'notes' subelement of this object as a tree of XMLNode objects.
The optional SBML 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. To help verify the formatting of 'notes' content, libSBML provides the static utility method SyntaxChecker.hasExpectedXHTMLSyntax(); however, readers are urged to consult the appropriate SBML specification document for the Level and Version of their model for more in-depth explanations. The SBML Level 2 and 3 specifications have considerable detail about how 'notes' element content must be structured.
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. For an alternative method of accessing the notes, see getNotesString().
|
inherited |
Python method signature(s):
getNotesString(SBase self)string getNotesString(SBase self)
string
Returns the content of the 'notes' subelement of this object as a string.
The optional SBML 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. To help verify the formatting of 'notes' content, libSBML provides the static utility method SyntaxChecker.hasExpectedXHTMLSyntax(); however, readers are urged to consult the appropriate SBML specification document for the Level and Version of their model for more in-depth explanations. The SBML Level 2 and 3 specifications have considerable detail about how 'notes' element content must be structured.
For an alternative method of accessing the notes, see getNotes(), which returns the content as an XMLNode tree structure. Depending on an application's needs, one or the other method may be more convenient.
|
inherited |
|
inherited |
Python method signature(s):
getNumPlugins(SBase self)long
Returns the number of plug-in objects (extenstion interfaces) for SBML Level 3 package extensions known.
def libsbml.Unit.getOffset | ( | self | ) |
Python method signature(s):
getOffset(Unit self)float
Returns the value of the 'offset' attribute of this Unit.
|
inherited |
Python method signature(s):
getPackageName(SBase self)string
Returns the name of the SBML Level 3 package in which this element is defined.
"core"
will be returned if this element is defined in SBML Level 3 Core. The string "unknown"
will be returned if this element is not defined in any SBML package.
|
inherited |
Python method signature(s):
getPackageVersion(SBase self)long
Returns the Version of the SBML Level 3 package to which this element belongs to.
0
will be returned if this element belongs to the SBML Level 3 Core package.
|
inherited |
Python method signature(s):
getParentSBMLObject(SBase self)SBase getParentSBMLObject(SBase self)
SBase
Returns the parent SBML object containing this object.
This returns the immediately-containing object. This method is convenient when holding an object nested inside other objects in an SBML model.
|
inherited |
Python method signature(s):
getPlugin(SBase self, string package)SBasePlugin getPlugin(SBase self, string package)
SBasePlugin getPlugin(SBase self, long n)
SBasePlugin getPlugin(SBase self, long n)
SBasePlugin
This method has multiple variants that differ in the arguments they accept. Each is described separately below.
Method variant with the following signature:
getPlugin(long n)
Returns the nth plug-in object (extension interface) for an SBML Level 3 package extension.
n | the index of the plug-in to return |
Method variant with the following signature:
getPlugin(string package)
Returns a plug-in object (extension interface) for an SBML Level 3 package extension with the given package name or URI.
package | the name or URI of the package |
|
inherited |
Python method signature(s):
getResourceBiologicalQualifier(SBase self, string resource)long
Returns the MIRIAM biological qualifier associated with the given resource.
In MIRIAM, qualifiers are an optional means of indicating the relationship between a model component and its annotations. There are two broad kinds of annotations: model and biological. The latter kind is used to qualify the relationship between a model component and a biological entity which it represents. Examples of relationships include 'is' and 'has part', but many others are possible. MIRIAM defines numerous relationship qualifiers to enable different software tools to qualify biological annotations in the same standardized way. In libSBML, the MIRIAM controlled-vocabulary annotations on an SBML model element are represented using lists of CVTerm objects, and the the MIRIAM biological qualifiers are represented using valueswhose names begin with BQB_
in the interface class libsbml.
This method searches the controlled-vocabulary annotations (i.e., the list of CVTerm objects) on the present object, then out of those that have biological qualifiers, looks for an annotation to the given resource
. If such an annotation is found, it returns the type of biological qualifier associated with that resource as a valuewhose name begins with BQB_
from the interface class libsbml.
resource | string representing the resource; e.g., 'http://www.geneontology.org/#GO:0005892' . |
BQB_
constants defined in libsbml may be expanded in later libSBML releases, to match the values defined by MIRIAM at that later time.
|
inherited |
Python method signature(s):
getResourceModelQualifier(SBase self, string resource)long
Returns the MIRIAM model qualifier associated with the given resource.
In MIRIAM, qualifiers are an optional means of indicating the relationship between a model component and its annotations. There are two broad kinds of annotations: model and biological. The former kind is used to qualify the relationship between a model component and another modeling object. An example qualifier is 'isDerivedFrom', to indicate that a given component of the model is derived from the modeling object represented by the referenced resource. MIRIAM defines numerous relationship qualifiers to enable different software tools to qualify model annotations in the same standardized way. In libSBML, the MIRIAM controlled-vocabulary annotations on an SBML model element are represented using lists of CVTerm objects, and the the MIRIAM model qualifiers are represented using valueswhose names begin with BQM_
in the interface class libsbml.
This method method searches the controlled-vocabulary annotations (i.e., the list of CVTerm objects) on the present object, then out of those that have model qualifiers, looks for an annotation to the given resource
. If such an annotation is found, it returns the type of type of model qualifier associated with that resource as a valuewhose name begins with BQM_
from the interface class libsbml.
resource | string representing the resource; e.g., 'http://www.geneontology.org/#GO:0005892' . |
BQM_
constants defined in libsbml may be expanded in later libSBML releases, to match the values defined by MIRIAM at that later time.
|
inherited |
Python method signature(s):
getSBMLDocument(SBase self)SBMLDocument getSBMLDocument(SBase self)
SBMLDocument
Returns the SBMLDocument object containing this object instance.
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 3 and Level 2 specifications, 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, Level 2 or Level 3.)
This method allows the caller to obtain the SBMLDocument for the current object.
|
inherited |
Python method signature(s):
getSBOTerm(SBase self)int
Returns the integer portion of the value of the 'sboTerm' attribute of this object.
Beginning with SBML Level 2 Version 3, objects derived from SBase have an optional attribute named 'sboTerm' for supporting the use of the Systems Biology Ontology. In SBML proper, 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. (For convenience, libSBML offers methods for returning both the integer form and a text-string form of the SBO identifier.)
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.
-1
if the value is not set.
|
inherited |
Python method signature(s):
getSBOTermAsURL(SBase self)string
Returns the identifiers.org URL representation of the 'sboTerm' attribute of this object.
This method returns the entire SBO identifier as a text string in the form 'http://identifiers.org/biomodels.sbo/SBO:NNNNNNN'.
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.
|
inherited |
Python method signature(s):
getSBOTermID(SBase self)string
Returns the string representation of the 'sboTerm' attribute of this object.
Beginning with SBML Level 2 Version 3, objects derived from SBase have an optional attribute named 'sboTerm' for supporting the use of the Systems Biology Ontology. In SBML proper, 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 method returns the entire SBO identifier as a text string in the form 'SBO:NNNNNNN'.
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.
def libsbml.Unit.getScale | ( | self | ) |
def libsbml.Unit.getTypeCode | ( | self | ) |
Python method signature(s):
getTypeCode(Unit self)int
Returns the libSBML type code of this object instance.
LibSBML attaches an identifying code to every kind of SBML object. These are known as SBML type codes. In the Python language interface for libSBML, the type codes are defined as static integer constants in the interface class libsbml. The names of the type codes all begin with the characters SBML_
.
|
inherited |
Python method signature(s):
getVersion(SBase self)long
Returns the Version within the SBML Level of the SBMLDocument object containing this object.
def libsbml.Unit.hasRequiredAttributes | ( | self | ) |
Python method signature(s):
hasRequiredAttributes(Unit self)bool
Predicate returning True
if all the required attributes for this Unit object have been set.
|
inherited |
Python method signature(s):
hasValidLevelVersionNamespaceCombination(SBase self)bool
def libsbml.Unit.initDefaults | ( | self | ) |
Python method signature(s):
initDefaults(Unit self)
Initializes the fields of this Unit object to 'typical' default values.
The SBML Unit component has slightly different aspects and default attribute values in different SBML Levels and Versions. This method sets the values to certain common defaults, based mostly on what they are in SBML Level 2. Specifically:
1
0
1.0
The 'kind' attribute is left unchanged.
def libsbml.Unit.isAmpere | ( | self | ) |
def libsbml.Unit.isAvogadro | ( | self | ) |
def libsbml.Unit.isBecquerel | ( | self | ) |
def libsbml.Unit.isBuiltIn | ( | args | ) |
Python method signature(s):
isBuiltIn(string name, long level)bool
Predicate to test whether a given string is the name of a predefined SBML unit.
name | a string to be tested against the predefined unit names |
level | the Level of SBML for which the determination should be made. This is necessary because there are a few small differences in allowed units between SBML Level 1 and Level 2. |
True
if name
is one of the five SBML predefined unit identifiers ('substance'
, 'volume'
, 'area'
, 'length'
or 'time'
), False
otherwise.'length'
and 'area'
were added in Level 2 Version 1.def libsbml.Unit.isCandela | ( | self | ) |
def libsbml.Unit.isCelsius | ( | self | ) |
Python method signature(s):
isCelsius(Unit self)bool
Predicate for testing whether this Unit is of the kind Celsius
True
if the kind of this Unit is Celsius
, False
otherwise.Celsius
was removed from the list of predefined units in SBML Level 2 Version 2 at the same time that the 'offset' attribute was removed from Unit definitions. LibSBML methods such as this one related to Celsius
are retained in order to support SBML Level 2 Version 1, but their use is strongly discouraged. def libsbml.Unit.isCoulomb | ( | self | ) |
def libsbml.Unit.isDimensionless | ( | self | ) |
def libsbml.Unit.isFarad | ( | self | ) |
def libsbml.Unit.isGram | ( | self | ) |
def libsbml.Unit.isGray | ( | self | ) |
def libsbml.Unit.isHenry | ( | self | ) |
def libsbml.Unit.isHertz | ( | self | ) |
def libsbml.Unit.isItem | ( | self | ) |
def libsbml.Unit.isJoule | ( | self | ) |
def libsbml.Unit.isKatal | ( | self | ) |
def libsbml.Unit.isKelvin | ( | self | ) |
def libsbml.Unit.isKilogram | ( | self | ) |
def libsbml.Unit.isLitre | ( | self | ) |
def libsbml.Unit.isLumen | ( | self | ) |
def libsbml.Unit.isLux | ( | self | ) |
def libsbml.Unit.isMetre | ( | self | ) |
def libsbml.Unit.isMole | ( | self | ) |
def libsbml.Unit.isNewton | ( | self | ) |
def libsbml.Unit.isOhm | ( | self | ) |
|
inherited |
Python method signature(s):
isPackageEnabled(SBase self, string pkgName)bool
Predicate returning True
if the given SBML Level 3 package is enabled with this object.
The search ignores the package version.
pkgName | the name of the package |
True
if the given package is enabled within this object, false
otherwise.
|
inherited |
Python method signature(s):
isPackageURIEnabled(SBase self, string pkgURI)bool
Predicate returning True
if an SBML Level 3 package with the given URI is enabled with this object.
pkgURI | the URI of the package |
True
if the given package is enabled within this object, false
otherwise.def libsbml.Unit.isPascal | ( | self | ) |
|
inherited |
Python method signature(s):
isPkgEnabled(SBase self, string pkgName)bool
Predicate returning True
if the given SBML Level 3 package is enabled with this object.
The search ignores the package version.
pkgName | the name of the package |
True
if the given package is enabled within this object, false
otherwise.
|
inherited |
Python method signature(s):
isPkgURIEnabled(SBase self, string pkgURI)bool
Predicate returning True
if an SBML Level 3 package with the given URI is enabled with this object.
pkgURI | the URI of the package |
True
if the given package is enabled within this object, false
otherwise.def libsbml.Unit.isRadian | ( | self | ) |
def libsbml.Unit.isSecond | ( | self | ) |
|
inherited |
Python method signature(s):
isSetAnnotation(SBase self)bool
Predicate returning True
if 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.
True
if a 'annotation' subelement exists, False
otherwise.def libsbml.Unit.isSetExponent | ( | self | ) |
def libsbml.Unit.isSetKind | ( | self | ) |
|
inherited |
Python method signature(s):
isSetMetaId(SBase self)bool
Predicate returning True
if this object's 'metaid' attribute is 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.
True
if the 'metaid' attribute of this SBML object is set, False
otherwise.
|
inherited |
Python method signature(s):
isSetModelHistory(SBase self)bool
Predicate returning True
if this object has a ModelHistory object attached to it.
True
if the ModelHistory of this object is set, false
otherwise.def libsbml.Unit.isSetMultiplier | ( | self | ) |
|
inherited |
Python method signature(s):
isSetNotes(SBase self)bool
Predicate returning True
if this object's 'notes' subelement exists and has content.
The optional SBML 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. To help verify the formatting of 'notes' content, libSBML provides the static utility method SyntaxChecker.hasExpectedXHTMLSyntax(); however, readers are urged to consult the appropriate SBML specification document for the Level and Version of their model for more in-depth explanations. The SBML Level 2 and 3 specifications have considerable detail about how 'notes' element content must be structured.
True
if a 'notes' subelement exists, False
otherwise.
|
inherited |
Python method signature(s):
isSetSBOTerm(SBase self)bool
Predicate returning True
if this object's 'sboTerm' attribute is set.
True
if the 'sboTerm' attribute of this SBML object is set, False
otherwise. def libsbml.Unit.isSetScale | ( | self | ) |
def libsbml.Unit.isSiemens | ( | self | ) |
def libsbml.Unit.isSievert | ( | self | ) |
def libsbml.Unit.isSteradian | ( | self | ) |
def libsbml.Unit.isTesla | ( | self | ) |
def libsbml.Unit.isUnitKind | ( | args | ) |
Python method signature(s):
isUnitKind(string name, long level, long version)bool
Predicate to test whether a given string is the name of a valid base unit in SBML (such as 'gram'
or 'mole'
).
This method exists because prior to SBML Level 2 Version 3, an enumeration called UnitKind
was defined by SBML. This enumeration was removed in SBML Level 2 Version 3 and its values were folded into the space of values of a type called UnitSId
. This method therefore has less significance in SBML Level 2 Version 3 and Level 2 Version 4, but remains for backward compatibility and support for reading models in older Versions of Level 2.
name | a string to be tested |
level | a long integer representing the SBML specification Level |
version | a long integer representing the SBML specification Version |
True
if name is a valid SBML UnitKind, False
otherwisedef libsbml.Unit.isVolt | ( | self | ) |
def libsbml.Unit.isWatt | ( | self | ) |
def libsbml.Unit.isWeber | ( | self | ) |
|
inherited |
Python method signature(s):
matchesRequiredSBMLNamespacesForAddition(SBase self, SBase sb)bool matchesRequiredSBMLNamespacesForAddition(SBase self, SBase sb)
bool
Returns True
if this object's set of XML namespaces are a subset of the given object's XML namespaces.
sb | an object to compare with respect to namespaces |
True
if this object's collection of namespaces is a subset of sb's
, False
otherwise.
|
inherited |
Python method signature(s):
matchesSBMLNamespaces(SBase self, SBase sb)bool matchesSBMLNamespaces(SBase self, SBase sb)
bool
Returns True
if this object's set of XML namespaces are the same as the given object's XML namespaces.
sb | an object to compare with respect to namespaces |
True
if this object's collection of namespaces is the same as sb's
, False
otherwise. def libsbml.Unit.merge | ( | args | ) |
Python method signature(s):
merge(Unit unit1, Unit unit2)
Merges two Unit objects with the same 'kind' attribute value into a single Unit.
For example, the following,
<unit kind='metre' exponent='2'/> <unit kind='metre' exponent='1'/>
would be merged to become
<unit kind='metre' exponent='3'/>
unit1 | the first Unit object; the result of the operation is left as a new version of this unit, modified in-place. |
unit2 | the second Unit object to merge with the first |
|
inherited |
Python method signature(s):
removeFromParentAndDelete(SBase self)int
Removes itself from its parent. If the parent was storing it as a pointer, it is deleted. If not, it is simply cleared (as in ListOf objects). Pure virutal, as every SBase element has different parents, and therefore different methods of removing itself. Will fail (and not delete itself) if it has no parent object. This function is designed to be overridden, but for all objects whose parent is of the class ListOf, the default implementation will work.
def libsbml.Unit.removeScale | ( | args | ) |
Python method signature(s):
removeScale(Unit unit)int
Manipulates the attributes of the Unit to express the unit with the value of the scale attribute reduced to zero.
For example, 1 millimetre can be expressed as a Unit with kind='metre'
multiplier='1'
scale='-3'
exponent='1'
. It can also be expressed as a Unit with kind='metre'
multiplier='0.001'
scale='0'
exponent='1'
.
unit | the Unit object to manipulate. |
|
inherited |
Python method signature(s):
removeTopLevelAnnotationElement(SBase self, string elementName, string elementURI="")int removeTopLevelAnnotationElement(SBase self, string elementName)
int
Removes the top-level element within the 'annotation' subelement of this SBML object with the given name and optional URI.
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.
Calling this method allows a particular annotation element to be removed whilst the remaining annotations remain intact.
elementName | a string representing the name of the top level annotation element that is to be removed |
elementURI | an optional string that is used to check both the name and URI of the top level element to be removed |
|
inherited |
Python method signature(s):
renameMetaIdRefs(SBase self, string oldid, string newid)
Renames all the MetaIdRef
attributes on this element.
This method works by looking at all meta-attribute values, comparing the identifiers to the value of oldid
. If any matches are found, the matching identifiers are replaced with newid
. The method does not descend into child elements.
oldid | the old identifier |
newid | the new identifier |
|
inherited |
Python method signature(s):
renameSIdRefs(SBase self, string oldid, string newid)
Renames all the SIdRef
attributes on this element, including any found in MathML content (if such exists).
This method works by looking at all attributes and (if appropriate) mathematical formulas, comparing the identifiers to the value of oldid
. If any matches are found, the matching identifiers are replaced with newid
. The method does not descend into child elements.
oldid | the old identifier |
newid | the new identifier |
|
inherited |
Python method signature(s):
renameUnitSIdRefs(SBase self, string oldid, string newid)
Renames all the UnitSIdRef
attributes on this element.
This method works by looking at all unit identifier attribute values (including, if appropriate, inside mathematical formulas), comparing the unit identifiers to the value of oldid
. If any matches are found, the matching identifiers are replaced with newid
. The method does not descend into child elements.
oldid | the old identifier |
newid | the new identifier |
|
inherited |
Python method signature(s):
replaceTopLevelAnnotationElement(SBase self, XMLNode annotation)int replaceTopLevelAnnotationElement(SBase self, string annotation)
int
This method has multiple variants that differ in the arguments they accept. Each is described separately below.
Method variant with the following signature:
replaceTopLevelAnnotationElement(XMLNode annotation)
Replaces the given top-level element within the 'annotation' subelement of this SBML object and with the annotation element supplied.
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.
This method determines the name of the element to be replaced from the annotation argument. Functionally it is equivalent to calling removeTopLevelAnnotationElement(name); appendAnnotation(annotation_with_name);
with the exception that the placement of the annotation element remains the same.
annotation | XMLNode representing the replacement top level annotation |
Method variant with the following signature:
replaceTopLevelAnnotationElement(string annotation)
Replaces the given top-level element within the 'annotation' subelement of this SBML object and with the annotation element supplied.
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.
This method determines the name of the element to be replaced from the annotation argument. Functionally it is equivalent to calling removeTopLevelAnnotationElement(name); appendAnnotation(annotation_with_name);
with the exception that the placement of the annotation element remains the same.
annotation | string representing the replacement top level annotation |
|
inherited |
Python method signature(s):
setAnnotation(SBase self, XMLNode annotation)int setAnnotation(SBase self, string annotation)
int
This method has multiple variants that differ in the arguments they accept. Each is described separately below.
Method variant with the following signature:
setAnnotation(XMLNode annotation)
Sets the value of the 'annotation' subelement of this SBML object.
The content of annotation
is copied, and any previous content of this object's 'annotation' subelement is deleted.
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() or SBase.appendAnnotation().
annotation | an XML structure that is to be used as the new content of the 'annotation' subelement of this object |
Method variant with the following signature:
setAnnotation(string annotation)
Sets the value of the 'annotation' subelement of this SBML object.
The content of annotation
is copied, and any previous content of this object's 'annotation' subelement is deleted.
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() or SBase.appendAnnotation().
annotation | an XML string that is to be used as the content of the 'annotation' subelement of this object |
def libsbml.Unit.setExponent | ( | self, | |
args | |||
) |
Python method signature(s):
setExponent(Unit self, int value)int setExponent(Unit self, float value)
int
This method has multiple variants that differ in the arguments they accept. Each is described separately below.
Method variant with the following signature:
setExponent(int value)
Sets the 'exponent' attribute value of this Unit.
value | the integer to which the attribute 'exponent' should be set |
setExponent (float value)
Sets the 'exponent' attribute value of this Unit.
value | the float to which the attribute 'exponent' should be set |
def libsbml.Unit.setKind | ( | self, | |
args | |||
) |
Python method signature(s):
setKind(Unit self, long kind)int
Sets the 'kind' attribute value of this Unit.
kind | a unit identifier chosen from the set of constants whose names begin with UNIT_KIND_ in libsbml. |
|
inherited |
Python method signature(s):
setMetaId(SBase 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.
metaid | the identifier string to use as the value of the 'metaid' attribute |
|
inherited |
Python method signature(s):
setModelHistory(SBase self, ModelHistory history)int
Sets the ModelHistory of this object.
The content of history
is copied, and this object's existing model history content is deleted.
history | ModelHistory of this object. |
def libsbml.Unit.setMultiplier | ( | self, | |
args | |||
) |
Python method signature(s):
setMultiplier(Unit self, float value)int
Sets the 'multipler' attribute value of this Unit.
value | the floating-point value to which the attribute 'multiplier' should be set |
|
inherited |
Python method signature(s):
setNamespaces(SBase self, XMLNamespaces xmlns)int
Sets the namespaces relevant of this SBML object.
The content of xmlns
is copied, and this object's existing namespace content is deleted.
The SBMLNamespaces object encapsulates SBML Level/Version/namespaces information. It is used to communicate the SBML Level, Version, and (in Level 3) packages used in addition to SBML Level 3 Core.
xmlns | the namespaces to set |
|
inherited |
Python method signature(s):
setNotes(SBase self, XMLNode notes)int setNotes(SBase self, string notes, bool addXHTMLMarkup=False)
int setNotes(SBase self, string notes)
int
This method has multiple variants that differ in the arguments they accept. Each is described separately below.
Method variant with the following signature:
setNotes(string notes, bool addXHTMLMarkup = false)
Sets the value of the 'notes' subelement of this SBML object to a copy of the string notes
.
The content of notes
is copied, and any existing content of this object's 'notes' subelement is deleted.
The optional SBML 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. To help verify the formatting of 'notes' content, libSBML provides the static utility method SyntaxChecker.hasExpectedXHTMLSyntax(); however, readers are urged to consult the appropriate SBML specification document for the Level and Version of their model for more in-depth explanations. The SBML Level 2 and 3 specifications have considerable detail about how 'notes' element content must be structured.
The following code illustrates a very simple way of setting the notes using this method. Here, the object being annotated is the whole SBML document, but that is for illustration purposes only; you could of course use this same approach to annotate any other SBML component.
notes | an XML string that is to be used as the content of the 'notes' subelement of this object |
addXHTMLMarkup | a boolean indicating whether to wrap the contents of the notes argument with XHTML paragraph (<p> ) tags. This is appropriate when the string in notes does not already containg the appropriate XHTML markup. |
Method variant with the following signature:
setNotes(XMLNode notes)
Sets the value of the 'notes' subelement of this SBML object.
The content of notes
is copied, and any existing content of this object's 'notes' subelement is deleted.
The optional SBML 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. To help verify the formatting of 'notes' content, libSBML provides the static utility method SyntaxChecker.hasExpectedXHTMLSyntax(); however, readers are urged to consult the appropriate SBML specification document for the Level and Version of their model for more in-depth explanations. The SBML Level 2 and 3 specifications have considerable detail about how 'notes' element content must be structured.
notes | an XML structure that is to be used as the content of the 'notes' subelement of this object |
def libsbml.Unit.setOffset | ( | self, | |
args | |||
) |
Python method signature(s):
setOffset(Unit self, float value)int
Sets the 'offset' attribute value of this Unit.
value | the float-point value to which the attribute 'offset' should set |
|
inherited |
Python method signature(s):
setSBOTerm(SBase self, int value)int setSBOTerm(SBase self, string sboid)
int
This method has multiple variants that differ in the arguments they accept. Each is described separately below.
Method variant with the following signature:
setSBOTerm(int value)
Sets the value of the 'sboTerm' attribute.
Beginning with SBML Level 2 Version 3, objects derived from SBase have an optional attribute named 'sboTerm' for supporting the use of the Systems Biology Ontology. In SBML proper, 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.
value | the NNNNNNN integer portion of the SBO identifier |
Method variant with the following signature:
setSBOTerm(string &sboid)
Sets the value of the 'sboTerm' attribute by string.
Beginning with SBML Level 2 Version 3, objects derived from SBase have an optional attribute named 'sboTerm' for supporting the use of the Systems Biology Ontology. In SBML proper, 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 method lets you set the value of 'sboTerm' as a complete string of the form 'SBO:NNNNNNN', whereas setSBOTerm(int value) allows you to set it using the integer form.
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.
def libsbml.Unit.setScale | ( | self, | |
args | |||
) |
|
inherited |
toSBML(SBase self) string *
Returns a string consisting of a partial SBML corresponding to just this object.
|
inherited |
Python method signature(s):
unsetAnnotation(SBase 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.
|
inherited |
|
inherited |
Python method signature(s):
unsetId(SBase self)int
Unsets the value of the 'id' attribute of this SBML object.
Most (but not all) objects in SBML include two common attributes: 'id' and 'name'. The identifier given by an object's 'id' attribute value is used to identify the object within the SBML model definition. Other objects can refer to the component using this identifier. The data type of 'id' is always either Sid
or UnitSId
, depending on the object in question. Both data types are defined as follows:
letter ::= 'a'..'z','A'..'Z' digit ::= '0'..'9' idChar ::= letter | digit | '_' SId ::= ( letter | '_' ) idChar*
The equality of SId
and UnitSId
type values in SBML is determined by an exact character sequence match; i.e., comparisons of these identifiers must be performed in a case-sensitive manner. This applies to all uses of SId
and UnitSId
.
|
inherited |
Python method signature(s):
unsetMetaId(SBase 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.
|
inherited |
Python method signature(s):
unsetModelHistory(SBase self)int
Unsets the ModelHistory object attached to this object.
|
inherited |
Python method signature(s):
unsetName(SBase self)int
Unsets the value of the 'name' attribute of this SBML object.
Most (but not all) objects in SBML include two common attributes: 'id' and 'name'. In contrast to the 'id' attribute, the 'name' attribute is optional and is not intended to be used for cross-referencing purposes within a model. Its purpose instead is to provide a human-readable label for the component. The data type of 'name' is the type string
defined in XML Schema. SBML imposes no restrictions as to the content of 'name' attributes beyond those restrictions defined by the string
type in XML Schema.
The recommended practice for handling 'name' is as follows. If a software tool has the capability for displaying the content of 'name' attributes, it should display this content to the user as a component's label instead of the component's 'id'. If the user interface does not have this capability (e.g., because it cannot display or use special characters in symbol names), or if the 'name' attribute is missing on a given component, then the user interface should display the value of the 'id' attribute instead. (Script language interpreters are especially likely to display 'id' instead of 'name'.)
As a consequence of the above, authors of systems that automatically generate the values of 'id' attributes should be aware some systems may display the 'id''s to the user. Authors therefore may wish to take some care to have their software create 'id' values that are: (a) reasonably easy for humans to type and read; and (b) likely to be meaningful, for example by making the 'id' attribute be an abbreviated form of the name attribute value.
An additional point worth mentioning is although there are restrictions on the uniqueness of 'id' values, there are no restrictions on the uniqueness of 'name' values in a model. This allows software applications leeway in assigning component identifiers.
|
inherited |
Python method signature(s):
unsetNotes(SBase self)int
Unsets the value of the 'notes' subelement of this SBML object.
The optional SBML 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. To help verify the formatting of 'notes' content, libSBML provides the static utility method SyntaxChecker.hasExpectedXHTMLSyntax(); however, readers are urged to consult the appropriate SBML specification document for the Level and Version of their model for more in-depth explanations. The SBML Level 2 and 3 specifications have considerable detail about how 'notes' element content must be structured.
|
inherited |
Python method signature(s):
unsetSBOTerm(SBase self)int
Unsets the value of the 'sboTerm' attribute of this SBML object.