libSBML Python API
5.8.0
|
Implementation of SBML's Reaction construct.
A reaction represents any transformation, transport or binding process, typically a chemical reaction, that can change the quantity of one or more species. In SBML, a reaction is defined primarily in terms of the participating reactants and products (and their corresponding stoichiometries), along with optional modifier species, an optional rate at which the reaction takes place, and optional parameters.
As with other major object in SBML, Reaction has a mandatory attribute, 'id', used to give the compartment type an identifier. The identifier must be a text string conforming to the identifer syntax permitted in SBML. In SBML Level 2 and Level 3, the reaction 'id' identifier can be used in mathematical formulas elsewhere in an SBML model to represent the rate of that reaction; this usage is explained below. Reaction also has an optional 'name' attribute, of type string
. The 'id' and 'name' must be used according to the guidelines described in the SBML specification.
The species participating as reactants, products, and/or modifiers in a reaction are declared using lists of SpeciesReference and/or ModifierSpeciesReference instances stored in subelements 'listOfReactants', 'listOfProducts' and 'listOfModifiers'. Certain restrictions are placed on the appearance of species in reaction definitions:
The ability of a species to appear as a reactant or product of any reaction in a model is governed by certain flags in that species' definition; see the definition of Species for more information.
Any species appearing in the mathematical formula of the subelement 'kineticLaw' (described below) of a Reaction must be declared in at least one of that Reaction's lists of reactants, products, and/or modifiers. Put another way, it is an error for a reaction's kinetic law formula to refer to species that have not been declared for that reaction.
A reaction can contain up to one KineticLaw object in a subelement named 'kineticLaw'. It defines the speed at which the process defined by the reaction takes place. The description of KineticLaw provides more details about its use. Note that although the inclusion of a KineticLaw object in an instance of a Reaction component is optional, there is no useful default that can be substituted in place of a missing rate expression in a reaction. Moreover, a reaction's rate cannot be defined in any other way in SBML—InitialAssignment, AssignmentRule, RateRule, AlgebraicRule, Event, and other constructs in SBML cannot be used to set the reaction rate separately. Nevertheless, for some modeling applications, reactions without any defined rate can be perfectly acceptable.
Reaction also has a boolean attribute named 'reversible' for indicating whether the reaction is reversible. This attribute is optional in SBML Level 2, with a default of True
; it is mandatory in SBML Level 3 (with no default value). To say that a reaction is reversible is to say it can proceed in either the forward or the reverse direction. Although the reversibility of a reaction can sometimes be deduced by inspecting its rate expression, this is not always the case, especially for complicated expressions. Moreover, the need in SBML to allow rate expressions (i.e., KineticLaw) to be optional leads to the need for a separate flag indicating reversibility. Note that labeling a reaction as irreversible is an assertion that the reaction always proceeds in the given forward direction. (Why else would it be flagged as irreversible?) This implies the rate expression in the KineticLaw always has a non-negative value during simulations. Software tools could provide a means of optionally testing that this condition holds. The presence of reversibility information in two places (i.e., the rate expression and the 'reversible' attribute on Reaction) leaves open the possibility that a model could contain contradictory information, but the creation of such a model would be an error on the part of the software generating it.
The Reaction object class has another boolean attribute called 'fast'. This attribute is optional in SBML Level 2, with a default of false
; it is mandatory in SBML Level 3 (with no default value). It is used to indicate that a reaction occurs on a vastly faster time scale than others in a system. Readers are directed to the SBML Level 2 Version 4 specification, which provides more detail about the conditions under which a reaction can be considered to be fast in this sense. The attribute's default value is False
. SBML Level 1 and Level 2 Version 1 incorrectly claimed that software tools could ignore this attribute if they did not implement support for the corresponding concept; however, further research in SBML has revealed that this is not true, and 'fast' cannot be ignored if it is set to True
. SBML Level 2 Versions 2–4 therefore stipulate that if a model has any reactions with 'fast' set to True
, a software tool must be able to respect the attribute or else indicate to the user that it does not have the capacity to do so. Analysis software cannot ignore the value of the 'fast' attribute because doing so may lead to different results as compared to a software system that does make use of 'fast'.
In SBML Level 3 Version 1, the Reaction object has an additional optional attribute named 'compartment', whose value must be the identifier of a compartment defined in the enclosing Model object. The 'compartment' attribute can be used to indicate the compartment in which the reaction is assumed to take place. If the attribute is present, its value must be the identifier of a Compartment object defined in the enclosing Model object. Similar to the 'reversible' attribute, the value of the 'compartment' attribute has no direct impact on the construction of mathematical equations for the SBML model. When a kinetic law is given for a reaction, the compartment location may already be implicit in the kinetic law (although this cannot always be guaranteed). Nevertheless, software tools may find the 'compartment' attribute value useful for such purposes as analyzing the structure of the model, guiding the modeler in constructing correct rate formulas, and visualization purposes.
Readers are urged to read the SBML specification for more details about the proper use of Reaction.
|
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. |
def libsbml.Reaction.addModifier | ( | self, | |
args | |||
) |
Python method signature(s):
addModifier(Reaction self, ModifierSpeciesReference msr)int
Adds a given ModifierSpeciesReference object as a product in this Reaction.
The ModifierSpeciesReference instance in msr
is copied.
msr | a ModifierSpeciesReference object referring to a Species in the enclosing Model |
def libsbml.Reaction.addProduct | ( | self, | |
args | |||
) |
Python method signature(s):
addProduct(Reaction self, SpeciesReference sr)int
Adds a given SpeciesReference object as a product in this Reaction.
The SpeciesReference instance in sr
is copied.
sr | a SpeciesReference object referring to a Species in the enclosing Model |
def libsbml.Reaction.addReactant | ( | self, | |
args | |||
) |
Python method signature(s):
addReactant(Reaction self, SpeciesReference sr)int
Adds a given SpeciesReference object as a reactant in this Reaction.
The SpeciesReference instance in sr
is copied.
sr | a SpeciesReference object referring to a Species in the enclosing Model |
|
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.Reaction.clone | ( | self | ) |
Implementation of SBML's Reaction construct.
A reaction represents any transformation, transport or binding process, typically a chemical reaction, that can change the quantity of one or more species. In SBML, a reaction is defined primarily in terms of the participating reactants and products (and their corresponding stoichiometries), along with optional modifier species, an optional rate at which the reaction takes place, and optional parameters.
As with other major object in SBML, Reaction has a mandatory attribute, 'id', used to give the compartment type an identifier. The identifier must be a text string conforming to the identifer syntax permitted in SBML. In SBML Level 2 and Level 3, the reaction 'id' identifier can be used in mathematical formulas elsewhere in an SBML model to represent the rate of that reaction; this usage is explained below. Reaction also has an optional 'name' attribute, of type string
. The 'id' and 'name' must be used according to the guidelines described in the SBML specification.
The species participating as reactants, products, and/or modifiers in a reaction are declared using lists of SpeciesReference and/or ModifierSpeciesReference instances stored in subelements 'listOfReactants', 'listOfProducts' and 'listOfModifiers'. Certain restrictions are placed on the appearance of species in reaction definitions:
The ability of a species to appear as a reactant or product of any reaction in a model is governed by certain flags in that species' definition; see the definition of Species for more information.
Any species appearing in the mathematical formula of the subelement 'kineticLaw' (described below) of a Reaction must be declared in at least one of that Reaction's lists of reactants, products, and/or modifiers. Put another way, it is an error for a reaction's kinetic law formula to refer to species that have not been declared for that reaction.
A reaction can contain up to one KineticLaw object in a subelement named 'kineticLaw'. It defines the speed at which the process defined by the reaction takes place. The description of KineticLaw provides more details about its use. Note that although the inclusion of a KineticLaw object in an instance of a Reaction component is optional, there is no useful default that can be substituted in place of a missing rate expression in a reaction. Moreover, a reaction's rate cannot be defined in any other way in SBML—InitialAssignment, AssignmentRule, RateRule, AlgebraicRule, Event, and other constructs in SBML cannot be used to set the reaction rate separately. Nevertheless, for some modeling applications, reactions without any defined rate can be perfectly acceptable.
Reaction also has a boolean attribute named 'reversible' for indicating whether the reaction is reversible. This attribute is optional in SBML Level 2, with a default of True
; it is mandatory in SBML Level 3 (with no default value). To say that a reaction is reversible is to say it can proceed in either the forward or the reverse direction. Although the reversibility of a reaction can sometimes be deduced by inspecting its rate expression, this is not always the case, especially for complicated expressions. Moreover, the need in SBML to allow rate expressions (i.e., KineticLaw) to be optional leads to the need for a separate flag indicating reversibility. Note that labeling a reaction as irreversible is an assertion that the reaction always proceeds in the given forward direction. (Why else would it be flagged as irreversible?) This implies the rate expression in the KineticLaw always has a non-negative value during simulations. Software tools could provide a means of optionally testing that this condition holds. The presence of reversibility information in two places (i.e., the rate expression and the 'reversible' attribute on Reaction) leaves open the possibility that a model could contain contradictory information, but the creation of such a model would be an error on the part of the software generating it.
The Reaction object class has another boolean attribute called 'fast'. This attribute is optional in SBML Level 2, with a default of false
; it is mandatory in SBML Level 3 (with no default value). It is used to indicate that a reaction occurs on a vastly faster time scale than others in a system. Readers are directed to the SBML Level 2 Version 4 specification, which provides more detail about the conditions under which a reaction can be considered to be fast in this sense. The attribute's default value is False
. SBML Level 1 and Level 2 Version 1 incorrectly claimed that software tools could ignore this attribute if they did not implement support for the corresponding concept; however, further research in SBML has revealed that this is not true, and 'fast' cannot be ignored if it is set to True
. SBML Level 2 Versions 2–4 therefore stipulate that if a model has any reactions with 'fast' set to True
, a software tool must be able to respect the attribute or else indicate to the user that it does not have the capacity to do so. Analysis software cannot ignore the value of the 'fast' attribute because doing so may lead to different results as compared to a software system that does make use of 'fast'.
In SBML Level 3 Version 1, the Reaction object has an additional optional attribute named 'compartment', whose value must be the identifier of a compartment defined in the enclosing Model object. The 'compartment' attribute can be used to indicate the compartment in which the reaction is assumed to take place. If the attribute is present, its value must be the identifier of a Compartment object defined in the enclosing Model object. Similar to the 'reversible' attribute, the value of the 'compartment' attribute has no direct impact on the construction of mathematical equations for the SBML model. When a kinetic law is given for a reaction, the compartment location may already be implicit in the kinetic law (although this cannot always be guaranteed). Nevertheless, software tools may find the 'compartment' attribute value useful for such purposes as analyzing the structure of the model, guiding the modeler in constructing correct rate formulas, and visualization purposes.
Readers are urged to read the SBML specification for more details about the proper use of Reaction. Python method signature(s):
clone(Reaction self)Reaction
Creates and returns a deep copy of this Reaction.
def libsbml.Reaction.createKineticLaw | ( | self | ) |
Python method signature(s):
createKineticLaw(Reaction self)KineticLaw
Creates a new KineticLaw object, installs it as this Reaction's 'kineticLaw' subelement, and returns it.
If this Reaction had a previous KineticLaw, it will be destroyed.
def libsbml.Reaction.createModifier | ( | self | ) |
Python method signature(s):
createModifier(Reaction self)ModifierSpeciesReference
Creates a new ModifierSpeciesReference, adds it to this Reaction's list of modifiers and returns it.
def libsbml.Reaction.createProduct | ( | self | ) |
Python method signature(s):
createProduct(Reaction self)SpeciesReference
Creates a new SpeciesReference, adds it to this Reaction's list of products, and returns it.
def libsbml.Reaction.createReactant | ( | self | ) |
Python method signature(s):
createReactant(Reaction self)SpeciesReference
Creates a new SpeciesReference, adds it to this Reaction's list of reactants, and returns it.
|
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.
def libsbml.Reaction.getCompartment | ( | self | ) |
Python method signature(s):
getCompartment(Reaction self)string
(SBML Level 3 only) Returns the value of the 'compartment' attribute on the Reaction.
|
inherited |
|
inherited |
Python method signature(s):
getCVTerms()CVTermList
Get the CVTermList of CVTerm objects in this SBase.
Returns the CVTermList for this SBase.
def libsbml.Reaction.getElementByMetaId | ( | self, | |
args | |||
) |
Python method signature(s):
getElementByMetaId(Reaction self, string metaid)SBase
Returns the first child element it can find with the given metaid
, or None
if no such object is found.
metaid | string representing the metaid of objects to find |
metaid
. def libsbml.Reaction.getElementBySId | ( | self, | |
args | |||
) |
Python method signature(s):
getElementBySId(Reaction 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 of objects to find. |
id
. def libsbml.Reaction.getElementName | ( | self | ) |
def libsbml.Reaction.getFast | ( | self | ) |
Python method signature(s):
getFast(Reaction self)bool
Returns the value of the 'fast' attribute of this Reaction.
True
. SBML Level 2 Versions 2, 3 and 4 therefore stipulate that if a model has any reactions with 'fast' set to True
, a software tool must be able to respect the attribute or else indicate to the user that it does not have the capacity to do so. Readers are directed to the SBML Level 2 Version 4 specification, which provides more detail about the conditions under which a reaction can be considered to be fast in this sense. def libsbml.Reaction.getId | ( | self | ) |
def libsbml.Reaction.getKineticLaw | ( | self, | |
args | |||
) |
Python method signature(s):
getKineticLaw(Reaction self)KineticLaw getKineticLaw(Reaction self)
KineticLaw
Returns the KineticLaw object contained in this Reaction.
|
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 |
def libsbml.Reaction.getListOfModifiers | ( | self, | |
args | |||
) |
Python method signature(s):
getListOfModifiers(Reaction self)ListOfSpeciesReferences getListOfModifiers(Reaction self)
ListOfSpeciesReferences
Returns the list of modifiers in this Reaction object.
def libsbml.Reaction.getListOfProducts | ( | self, | |
args | |||
) |
Python method signature(s):
getListOfProducts(Reaction self)ListOfSpeciesReferences getListOfProducts(Reaction self)
ListOfSpeciesReferences
Returns the list of products in this Reaction object.
def libsbml.Reaction.getListOfReactants | ( | self, | |
args | |||
) |
Python method signature(s):
getListOfReactants(Reaction self)ListOfSpeciesReferences getListOfReactants(Reaction self)
ListOfSpeciesReferences
Returns the list of reactants in this Reaction object.
|
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.Reaction.getModifier | ( | self, | |
args | |||
) |
Python method signature(s):
getModifier(Reaction self, long n)ModifierSpeciesReference getModifier(Reaction self, long n)
ModifierSpeciesReference getModifier(Reaction self, string species)
ModifierSpeciesReference getModifier(Reaction self, string species)
ModifierSpeciesReference
This method has multiple variants that differ in the arguments they accept. Each is described separately below.
Method variant with the following signature:
getModifier(string species)
Returns the modifier species (as a ModifierSpeciesReference object) having a specific identifier in this Reaction.
species | the identifier of the modifier Species ('species' attribute of the ModifierSpeciesReference object) |
None
if no species with the given identifier species
appears as a modifier in this Reaction.Method variant with the following signature:
getModifier(long n)
Returns the nth modifier species (as a ModifierSpeciesReference object) in the list of modifiers of this Reaction.
Callers should first call getNumModifiers() to find out how many modifiers there are, to avoid using an invalid index number.
n | the index of the modifier species sought |
def libsbml.Reaction.getName | ( | 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 |
def libsbml.Reaction.getNumModifiers | ( | self | ) |
|
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.Reaction.getNumProducts | ( | self | ) |
def libsbml.Reaction.getNumReactants | ( | self | ) |
|
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 |
def libsbml.Reaction.getProduct | ( | self, | |
args | |||
) |
Python method signature(s):
getProduct(Reaction self, long n)SpeciesReference getProduct(Reaction self, long n)
SpeciesReference getProduct(Reaction self, string species)
SpeciesReference getProduct(Reaction self, string species)
SpeciesReference
This method has multiple variants that differ in the arguments they accept. Each is described separately below.
Method variant with the following signature:
getProduct(string species)
Returns the product species (as a SpeciesReference object) having a specific identifier in this Reaction.
species | the identifier of the product Species ('species' attribute of the product SpeciesReference object) |
None
if no species with the given identifier species
appears as a product in this Reaction.Method variant with the following signature:
getProduct(long n)
Returns the nth product species (as a SpeciesReference object) in the list of products in this Reaction.
Callers should first call getNumProducts() to find out how many products there are, to avoid using an invalid index number.
n | the index of the product sought. |
def libsbml.Reaction.getReactant | ( | self, | |
args | |||
) |
Python method signature(s):
getReactant(Reaction self, long n)SpeciesReference getReactant(Reaction self, long n)
SpeciesReference getReactant(Reaction self, string species)
SpeciesReference getReactant(Reaction self, string species)
SpeciesReference
This method has multiple variants that differ in the arguments they accept. Each is described separately below.
Method variant with the following signature:
getReactant(string species)
Returns the reactant species (as a SpeciesReference object) having a specific identifier in this Reaction.
species | the identifier of the reactant Species ('species' attribute of the reactant SpeciesReference object) |
None
if no species with the given identifier species
appears as a reactant in this Reaction.Method variant with the following signature:
getReactant(long n)
Returns the nth reactant species (as a SpeciesReference object) in the list of reactants in this Reaction.
Callers should first call getNumReactants() to find out how many reactants there are, to avoid using an invalid index number.
n | the index of the reactant sought. |
|
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. def libsbml.Reaction.getReversible | ( | self | ) |
|
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.Reaction.getTypeCode | ( | self | ) |
Python method signature(s):
getTypeCode(Reaction self)int
Returns the libSBML type code for this SBML object.
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.Reaction.hasRequiredAttributes | ( | self | ) |
Python method signature(s):
hasRequiredAttributes(Reaction self)bool
Predicate returning True
if all the required attributes for this Reaction object have been set.
|
inherited |
Python method signature(s):
hasValidLevelVersionNamespaceCombination(SBase self)bool
def libsbml.Reaction.initDefaults | ( | self | ) |
Python method signature(s):
initDefaults(Reaction self)
Initializes the fields of this Reaction object to 'typical' default values.
The SBML Reaction 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:
True
False
True
. Beginning with SBML Level 2 Versions 2, the SBML specifications therefore stipulate that if a model has any reactions with 'fast' set to true
, a software tool must be able to respect the attribute or else indicate to the user that it does not have the capacity to do so. Readers are directed to the SBML specifications, which provides more detail about the conditions under which a reaction can be considered to be fast in this sense.
|
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.
|
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.
|
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.Reaction.isSetCompartment | ( | self | ) |
Python method signature(s):
isSetCompartment(Reaction self)bool
Predicate returning True
if this Reaction's 'compartment' attribute is set.
True
if the 'compartment' attribute of this Reaction is set, False
otherwise.def libsbml.Reaction.isSetFast | ( | self | ) |
Python method signature(s):
isSetFast(Reaction self)bool
Predicate returning True
if the value of the 'fast' attribute on this Reaction.
True
if the 'fast' attribute is true, False
otherwise.True
. SBML Level 2 Versions 2, 3 and 4 therefore stipulate that if a model has any reactions with 'fast' set to True
, a software tool must be able to respect the attribute or else indicate to the user that it does not have the capacity to do so. Readers are directed to the SBML Level 2 Version 4 specification, which provides more detail about the conditions under which a reaction can be considered to be fast in this sense. Note also that in SBML Level 1, 'fast' is defined as optional with a default of False
, which means it is effectively always set. def libsbml.Reaction.isSetId | ( | self | ) |
def libsbml.Reaction.isSetKineticLaw | ( | self | ) |
Python method signature(s):
isSetKineticLaw(Reaction self)bool
Predicate returning True
if this Reaction contains a kinetic law object.
True
if a KineticLaw is present in this Reaction,, False
otherwise.
|
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.Reaction.isSetName | ( | 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.def libsbml.Reaction.isSetReversible | ( | self | ) |
|
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.
|
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.
|
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.Reaction.removeModifier | ( | self, | |
args | |||
) |
Python method signature(s):
removeModifier(Reaction self, long n)ModifierSpeciesReference removeModifier(Reaction self, string species)
ModifierSpeciesReference
This method has multiple variants that differ in the arguments they accept. Each is described separately below.
Method variant with the following signature:
removeModifier(string species)
Removes the modifier species (ModifierSpeciesReference object) having the given 'species' attribute in this Reaction and returns a pointer to it.
The caller owns the returned object and is responsible for deleting it.
species | the 'species' attribute of the ModifierSpeciesReference object |
None
if no ModifierSpeciesReference object with the given 'species' attribute species
exists in this Reaction.Method variant with the following signature:
removeModifier(long n)
Removes the nth modifier species (ModifierSpeciesReference object) in the list of modifiers in this Reaction and returns a pointer to it.
The caller owns the returned object and is responsible for deleting it. The caller should first call getNumModifiers() to find out how many modifiers there are, to avoid using an invalid index number.
n | the index of the ModifierSpeciesReference object to remove |
None
if the given index is out of range. def libsbml.Reaction.removeProduct | ( | self, | |
args | |||
) |
Python method signature(s):
removeProduct(Reaction self, long n)SpeciesReference removeProduct(Reaction self, string species)
SpeciesReference
This method has multiple variants that differ in the arguments they accept. Each is described separately below.
Method variant with the following signature:
removeProduct(string species)
Removes the product species (SpeciesReference object) having the given 'species' attribute in this Reaction and returns a pointer to it.
The caller owns the returned object and is responsible for deleting it.
species | the 'species' attribute of the product SpeciesReference object |
None
if no product SpeciesReference object with the given 'species' attribute species
exists in this Reaction.Method variant with the following signature:
removeProduct(long n)
Removes the nth product species (SpeciesReference object) in the list of products in this Reaction and returns a pointer to it.
The caller owns the returned object and is responsible for deleting it. The caller should first call getNumProducts() to find out how many products there are, to avoid using an invalid index number.
n | the index of the product SpeciesReference object to remove |
None
if the given index is out of range. def libsbml.Reaction.removeReactant | ( | self, | |
args | |||
) |
Python method signature(s):
removeReactant(Reaction self, long n)SpeciesReference removeReactant(Reaction self, string species)
SpeciesReference
This method has multiple variants that differ in the arguments they accept. Each is described separately below.
Method variant with the following signature:
removeReactant(string species)
Removes the reactant species (SpeciesReference object) having the given 'species' attribute in this Reaction and returns a pointer to it.
The caller owns the returned object and is responsible for deleting it.
species | the 'species' attribute of the reactant SpeciesReference object |
None
if no reactant SpeciesReference object with the given 'species' attribute species
exists in this Reaction.Method variant with the following signature:
removeReactant(long n)
Removes the nth reactant species (SpeciesReference object) in the list of reactants in this Reaction and returns a pointer to it.
The caller owns the returned object and is responsible for deleting it. The caller should first call getNumReactants() to find out how many reactants there are, to avoid using an invalid index number.
n | the index of the reactant SpeciesReference object to remove |
None
if the given index is out of range.
|
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 |
def libsbml.Reaction.renameSIdRefs | ( | self, | |
args | |||
) |
Python method signature(s):
renameSIdRefs(Reaction self, string oldid, string newid)
Renames all the SIdRef attributes on this element, including any found in MathML
|
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.Reaction.setCompartment | ( | self, | |
args | |||
) |
Python method signature(s):
setCompartment(Reaction self, string sid)int
Sets the value of the 'compartment' attribute of this Reaction.
The string sid
is copied.
sid | the string to use as the compartment of this Reaction |
def libsbml.Reaction.setFast | ( | self, | |
args | |||
) |
Python method signature(s):
setFast(Reaction self, bool value)int
Sets the value of the 'fast' attribute of this Reaction.
value | the value of the 'fast' attribute. |
True
. SBML Level 2 Versions 2, 3 and 4 therefore stipulate that if a model has any reactions with 'fast' set to True
, a software tool must be able to respect the attribute or else indicate to the user that it does not have the capacity to do so. Readers are directed to the SBML Level 2 Version 4 specification, which provides more detail about the conditions under which a reaction can be considered to be fast in this sense. def libsbml.Reaction.setId | ( | self, | |
args | |||
) |
Python method signature(s):
setId(Reaction self, string sid)int
Sets the value of the 'id' attribute of this Reaction.
The string sid
is copied. Note that SBML has strict requirements for the syntax of identifiers. The following is a summary of the definition of the SBML identifier type
SId
, which defines the permitted syntax of identifiers. We
express the syntax using an extended form of BNF notation:
letter ::= 'a'..'z','A'..'Z' digit ::= '0'..'9' idChar ::= letter | digit | '_' SId ::= ( letter | '_' ) idChar*The characters
(
and )
are used for grouping, the
character *
"zero or more times", and the character
|
indicates logical "or". 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.
sid | the string to use as the identifier of this Reaction |
def libsbml.Reaction.setKineticLaw | ( | self, | |
args | |||
) |
Python method signature(s):
setKineticLaw(Reaction self, KineticLaw kl)int
Sets the 'kineticLaw' subelement of this Reaction to a copy of the given KineticLaw object.
kl | the KineticLaw object to use. |
|
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.Reaction.setName | ( | self, | |
args | |||
) |
Python method signature(s):
setName(Reaction self, string name)int
Sets the value of the 'name' attribute of this Reaction.
The string in name
is copied.
name | the new name for the Reaction |
|
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.Reaction.setReversible | ( | self, | |
args | |||
) |
Python method signature(s):
setReversible(Reaction self, bool value)int
Sets the value of the 'reversible' attribute of this Reaction.
value | the value of the 'reversible' attribute. |
|
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.
|
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.
def libsbml.Reaction.unsetCompartment | ( | self | ) |
Python method signature(s):
unsetCompartment(Reaction self)int
Unsets the value of the 'compartment' attribute of this Reaction.
|
inherited |
def libsbml.Reaction.unsetFast | ( | self | ) |
Python method signature(s):
unsetFast(Reaction self)int
Unsets the value of the 'fast' attribute of this Reaction.
false
, which means it is effectively always set (and reset to False
if this method is called). Further, SBML definitions before SBML Level 2 Version 2 incorrectly indicated that software tools could ignore this attribute if they did not implement support for the corresponding concept; however, further research in SBML has revealed that this is not true, and 'fast' cannot be ignored if it is set to True
. SBML Level 2 Versions 2, 3 and 4 therefore stipulate that if a model has any reactions with 'fast' set to True
, a software tool must be able to respect the attribute or else indicate to the user that it does not have the capacity to do so. Readers are directed to the SBML Level 2 Version 4 specification, which provides more detail about the conditions under which a reaction can be considered to be fast in this sense.
|
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
.
def libsbml.Reaction.unsetKineticLaw | ( | self | ) |
|
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.
def libsbml.Reaction.unsetName | ( | self | ) |
|
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.