libsbml.Reaction Class Reference

Inheritance diagram for libsbml.Reaction:

[legend]

List of all members.

---

Detailed Description

LibSBML 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. These various parts of a reaction are recorded in the Reaction object and its supporting object classes: KineticLaw, SpeciesReference, ModifierSpeciesReference, ListOfSpeciesReferences, ListOfModifierSpeciesReferences, and StoichiometryMath. It also uses Parameter and ListOfParameters.

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. 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 (e.g., Section 3.3 in the Level 2 Version 4 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 definition can contain an empty list of reactants or an empty list of products, but it must have at least one reactant or product; in other words, a reaction without any reactant or product species is not permitted. (This restriction does not apply to modifier species, which remain optional in all cases.)

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 an optional boolean attribute named 'reversible' for indicating whether the reaction is reversible. The default is true. 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.

Finally, Reaction has another optional boolean attribute called 'fast'. 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, 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. 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'.

Readers are urged to read the SBML specification for more details about the proper use of Reaction.

Definition at line 18046 of file libsbml.py.

Public Member Functions
def	__eq__
def	__init__
def	__init__
def	__ne__
def	addCVTerm
def	addModifier
def	addProduct
def	addReactant
def	appendAnnotation
def	appendNotes
def	clone
def	createKineticLaw
def	createModifier
def	createProduct
def	createReactant
def	getAncestorOfType
def	getAnnotation
def	getAnnotationString
def	getColumn
def	getCVTerm
def	getCVTerms
def	getElementName
def	getFast
def	getId
def	getKineticLaw
def	getLevel
def	getLine
def	getListOfModifiers
def	getListOfProducts
def	getListOfReactants
def	getMetaId
def	getModel
def	getModifier
def	getName
def	getNamespaces
def	getNotes
def	getNotesString
def	getNumCVTerms
def	getNumModifiers
def	getNumProducts
def	getNumReactants
def	getParentSBMLObject
def	getProduct
def	getReactant
def	getResourceBiologicalQualifier
def	getResourceModelQualifier
def	getReversible
def	getSBMLDocument
def	getSBOTerm
def	getSBOTermID
def	getTypeCode
def	getVersion
def	hasRequiredAttributes
def	hasRequiredElements
def	hasValidLevelVersionNamespaceCombination
def	initDefaults
def	isSetAnnotation
def	isSetFast
def	isSetId
def	isSetKineticLaw
def	isSetMetaId
def	isSetName
def	isSetNotes
def	isSetSBOTerm
def	removeModifier
def	removeProduct
def	removeReactant
def	setAnnotation
def	setFast
def	setId
def	setKineticLaw
def	setMetaId
def	setName
def	setNamespaces
def	setNotes
def	setReversible
def	setSBOTerm
def	toSBML
def	unsetAnnotation
def	unsetCVTerms
def	unsetFast
def	unsetKineticLaw
def	unsetMetaId
def	unsetName
def	unsetNotes
def	unsetSBOTerm
Public Attributes
	this

---

Member Function Documentation

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

Definition at line 3296 of file libsbml.py.

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

Reimplemented in libsbml.SimpleSpeciesReference.

Definition at line 1771 of file libsbml.py.

def libsbml.Reaction.__init__	(		self,
			args
	)

Python method signature(s):

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

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

Note:

The required attributes for a Reaction object are: id

Returns:

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

Deprecated:

libSBML internal

Definition at line 18162 of file libsbml.py.

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

Definition at line 3303 of file libsbml.py.

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

Python method signature(s):

addCVTerm(self, CVTerm term)    int

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

Parameters:

term

the CVTerm to assign

Returns:

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

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_OPERATION_FAILED
• LIBSBML_UNEXPECTED_ATTRIBUTE
• LIBSBML_INVALID_OBJECT

Note:

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

Warning:

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

Definition at line 2974 of file libsbml.py.

def libsbml.Reaction.addModifier	(		self,
			args
	)

Python method signature(s):

addModifier(self, ModifierSpeciesReference msr)    int

Adds a given ModifierSpeciesReference object as a product in this Reaction.

The ModifierSpeciesReference instance in msr is copied.

Parameters:

msr

a ModifierSpeciesReference object referring to a Species in the enclosing Model

Returns:

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

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_UNEXPECTED_ATTRIBUTE
• LIBSBML_LEVEL_MISMATCH
• LIBSBML_VERSION_MISMATCH
• LIBSBML_OPERATION_FAILED

Note:

This method should be used with some caution. The fact that this method copies the object passed to it means that the caller will be left holding a physically different object instance than the one contained in this Reaction. Changes made to the original object instance (such as resetting attribute values) will not affect the instance in the Reaction. In addition, the caller should make sure to free the original object if it is no longer being used, or else a memory leak will result. Please see Reaction.createModifier() for a method that does not lead to these issues.

See also:

createModifier()

Definition at line 18720 of file libsbml.py.

def libsbml.Reaction.addProduct	(		self,
			args
	)

Python method signature(s):

addProduct(self, SpeciesReference sr)    int

Adds a given SpeciesReference object as a product in this Reaction.

The SpeciesReference instance in sr is copied.

Parameters:

sr

a SpeciesReference object referring to a Species in the enclosing Model

Returns:

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

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_LEVEL_MISMATCH
• LIBSBML_VERSION_MISMATCH
• LIBSBML_OPERATION_FAILED

Note:

This method should be used with some caution. The fact that this method copies the object passed to it means that the caller will be left holding a physically different object instance than the one contained in this Reaction. Changes made to the original object instance (such as resetting attribute values) will not affect the instance in the Reaction. In addition, the caller should make sure to free the original object if it is no longer being used, or else a memory leak will result. Please see Reaction.createProduct() for a method that does not lead to these issues.

See also:

createProduct()

Definition at line 18681 of file libsbml.py.

def libsbml.Reaction.addReactant	(		self,
			args
	)

Python method signature(s):

addReactant(self, SpeciesReference sr)    int

Adds a given SpeciesReference object as a reactant in this Reaction.

The SpeciesReference instance in sr is copied.

Parameters:

sr

a SpeciesReference object referring to a Species in the enclosing Model

Returns:

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

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_LEVEL_MISMATCH
• LIBSBML_VERSION_MISMATCH
• LIBSBML_OPERATION_FAILED

Note:

This method should be used with some caution. The fact that this method copies the object passed to it means that the caller will be left holding a physically different object instance than the one contained in this Reaction. Changes made to the original object instance (such as resetting attribute values) will not affect the instance in the Reaction. In addition, the caller should make sure to free the original object if it is no longer being used, or else a memory leak will result. Please see Reaction.createReactant() for a method that does not lead to these issues.

See also:

createReactant()

Definition at line 18642 of file libsbml.py.

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

Python method signature(s):

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

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

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

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

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

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

Parameters:

annotation

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

Returns:

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

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_OPERATION_FAILED

See also:

getAnnotationString()

isSetAnnotation()

setAnnotation(const XMLNode* annotation)

setAnnotation(const std.string& annotation)

appendAnnotation(const XMLNode* annotation)

unsetAnnotation()

Reimplemented in libsbml.Model, and libsbml.SpeciesReference.

Definition at line 2624 of file libsbml.py.

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

Python method signature(s):

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

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

The content in notes is copied.

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

Parameters:

notes

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

Returns:

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

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_INVALID_OBJECT
• LIBSBML_OPERATION_FAILED

See also:

getNotesString()

isSetNotes()

setNotes(const XMLNode* notes)

setNotes(const std.string& notes)

appendNotes(const XMLNode* notes)

unsetNotes()

Definition at line 2726 of file libsbml.py.

def libsbml.Reaction.clone

(

self

)

Python method signature(s):

clone(self)    Reaction

Creates and returns a deep copy of this Reaction.

Returns:

a (deep) copy of this Reaction.

Reimplemented from libsbml.SBase.

Definition at line 18187 of file libsbml.py.

def libsbml.Reaction.createKineticLaw

(

self

)

Python method signature(s):

createKineticLaw(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.

Returns:

the new KineticLaw object

Definition at line 18809 of file libsbml.py.

def libsbml.Reaction.createModifier

(

self

)

Python method signature(s):

createModifier(self)    ModifierSpeciesReference

Creates a new ModifierSpeciesReference, adds it to this Reaction's list of modifiers and returns it.

Returns:

a new ModifierSpeciesReference object.

Definition at line 18793 of file libsbml.py.

def libsbml.Reaction.createProduct

(

self

)

Python method signature(s):

createProduct(self)    SpeciesReference

Creates a new SpeciesReference, adds it to this Reaction's list of products, and returns it.

Returns:

a new SpeciesReference object.

Definition at line 18777 of file libsbml.py.

def libsbml.Reaction.createReactant

(

self

)

Python method signature(s):

createReactant(self)    SpeciesReference

Creates a new SpeciesReference, adds it to this Reaction's list of reactants, and returns it.

Returns:

a new SpeciesReference object.

Definition at line 18761 of file libsbml.py.

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

Python method signature(s):

getAncestorOfType(self, SBMLTypeCode_t type)    SBase

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

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

Parameters:

type

the SBMLTypeCode_t of the ancestor to be returned.

Returns:

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

Definition at line 2115 of file libsbml.py.

def libsbml.SBase.getAnnotation

(

self

)

[inherited]

Python method signature(s):

getAnnotation(self)    XMLNode

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

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

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

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

Returns:

the annotation of this SBML object as an XMLNode

See also:

getAnnotationString()

isSetAnnotation()

setAnnotation(const XMLNode* annotation)

setAnnotation(const std.string& annotation)

appendAnnotation(const XMLNode* annotation)

appendAnnotation(const std.string& annotation)

unsetAnnotation()

Definition at line 1971 of file libsbml.py.

def libsbml.SBase.getAnnotationString

(

self

)

[inherited]

Python method signature(s):

getAnnotationString(self)    string

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

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

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

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

Returns:

the annotation string of this SBML object.

See also:

getAnnotation()

isSetAnnotation()

setAnnotation(const XMLNode* annotation)

setAnnotation(const std.string& annotation)

appendAnnotation(const XMLNode* annotation)

appendAnnotation(const std.string& annotation)

unsetAnnotation()

Definition at line 2014 of file libsbml.py.

def libsbml.SBase.getColumn

(

self

)

[inherited]

Python method signature(s):

getColumn(self)    unsigned int

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

Returns:

the column number of this SBML object.

See also:

getLine()

Definition at line 2217 of file libsbml.py.

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

Python method signature(s):

getCVTerm(self, unsigned int n)    CVTerm

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

Parameters:

n

unsigned int the index of the CVTerm to retrieve

Returns:

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

Definition at line 3042 of file libsbml.py.

def libsbml.SBase.getCVTerms

(

self

)

[inherited]

Python method signature(s):

getCVTerms(self)    CVTermList

Get the CVTermList of CVTerm objects in this SBase.

Returns:

the CVTermList for this SBase.

Definition at line 3010 of file libsbml.py.

def libsbml.Reaction.getElementName

(

self

)

Python method signature(s):

getElementName(self)    string

Returns the XML element name of this object, which for Reaction, is always 'reaction'.

Returns:

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

Reimplemented from libsbml.SBase.

Definition at line 19094 of file libsbml.py.

def libsbml.Reaction.getFast

(

self

)

Python method signature(s):

getFast(self)    bool

Returns the value of the 'fast' attribute of this Reaction.

Returns:

the 'fast' status of this Reaction.

Warning:

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.

Definition at line 18295 of file libsbml.py.

def libsbml.Reaction.getId

(

self

)

Python method signature(s):

getId(self)    string

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

Returns:

the id of this Reaction.

Reimplemented from libsbml.SBase.

Definition at line 18233 of file libsbml.py.

def libsbml.Reaction.getKineticLaw	(		self,
			args
	)

Python method signature(s):

getKineticLaw(self)    KineticLaw
getKineticLaw(self)    KineticLaw

Returns the KineticLaw object contained in this Reaction.

Returns:

the KineticLaw instance.

Definition at line 18263 of file libsbml.py.

def libsbml.SBase.getLevel

(

self

)

[inherited]

Python method signature(s):

getLevel(self)    unsigned int

Returns the SBML Level of the overall SBML document.

Returns:

the SBML level of this SBML object.

See also:

getVersion()

Definition at line 3134 of file libsbml.py.

def libsbml.SBase.getLine

(

self

)

[inherited]

Python method signature(s):

getLine(self)    unsigned int

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

Returns:

the line number of this SBML object.

See also:

getColumn()

Definition at line 2199 of file libsbml.py.

def libsbml.Reaction.getListOfModifiers	(		self,
			args
	)

Python method signature(s):

getListOfModifiers(self)    ListOfSpeciesReferences
getListOfModifiers(self)    ListOfSpeciesReferences

Returns the list of modifiers in this Reaction object.

Returns:

the ListOfSpeciesReferences containing the references to the species acting as modifiers in this reaction

Definition at line 18861 of file libsbml.py.

def libsbml.Reaction.getListOfProducts	(		self,
			args
	)

Python method signature(s):

getListOfProducts(self)    ListOfSpeciesReferences
getListOfProducts(self)    ListOfSpeciesReferences

Returns the list of products in this Reaction object.

Returns:

the ListOfSpeciesReferences containing the references to the species acting as products in this reaction

Definition at line 18844 of file libsbml.py.

def libsbml.Reaction.getListOfReactants	(		self,
			args
	)

Python method signature(s):

getListOfReactants(self)    ListOfSpeciesReferences
getListOfReactants(self)    ListOfSpeciesReferences

Returns the list of reactants in this Reaction object.

Returns:

the ListOfSpeciesReferences containing the references to the species acting as reactants in this reaction

Definition at line 18827 of file libsbml.py.

def libsbml.SBase.getMetaId

(

self

)

[inherited]

Python method signature(s):

getMetaId(self)    string

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

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

Returns:

the metaid of this SBML object.

See also:

isSetMetaId()

setMetaId(const std.string& metaid)

Definition at line 1790 of file libsbml.py.

def libsbml.SBase.getModel

(

self

)

[inherited]

Python method signature(s):

getModel(self)    Model

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

Returns:

the parent Model of this SBML object.

Definition at line 3119 of file libsbml.py.

def libsbml.Reaction.getModifier	(		self,
			args
	)

Python method signature(s):

getModifier(self, unsigned int n)    ModifierSpeciesReference
getModifier(self, unsigned int n)    ModifierSpeciesReference
getModifier(self, string species)    ModifierSpeciesReference
getModifier(self, string species)    ModifierSpeciesReference

Returns the modifier species (as a ModifierSpeciesReference object) having a specific identifier in this Reaction.

Parameters:

species

the identifier of the modifier Species ('species' attribute of the ModifierSpeciesReference object)

Returns:

a ModifierSpeciesReference object, or NULL if no species with the given identifier species appears as a modifier in this Reaction.

Definition at line 18924 of file libsbml.py.

def libsbml.Reaction.getName

(

self

)

Python method signature(s):

getName(self)    string

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

Returns:

the name of this Reaction.

Reimplemented from libsbml.SBase.

Definition at line 18248 of file libsbml.py.

def libsbml.SBase.getNamespaces

(

self

)

[inherited]

Python method signature(s):

getNamespaces(self)    XMLNamespaces

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

Returns:

the XML Namespaces associated with this SBML object

Reimplemented in libsbml.SBMLDocument.

Definition at line 2053 of file libsbml.py.

def libsbml.SBase.getNotes

(

self

)

[inherited]

Python method signature(s):

getNotes(self)    XMLNode

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

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

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

Returns:

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

See also:

getNotesString()

isSetNotes()

setNotes(const XMLNode* notes)

setNotes(const std.string& notes)

appendNotes(const XMLNode* notes)

appendNotes(const std.string& notes)

unsetNotes()

Definition at line 1891 of file libsbml.py.

def libsbml.SBase.getNotesString

(

self

)

[inherited]

Python method signature(s):

getNotesString(self)    string

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

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

Returns:

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

See also:

getNotes()

isSetNotes()

setNotes(const XMLNode* notes)

setNotes(const std.string& notes)

appendNotes(const XMLNode* notes)

appendNotes(const std.string& notes)

unsetNotes()

Definition at line 1934 of file libsbml.py.

def libsbml.SBase.getNumCVTerms

(

self

)

[inherited]

Python method signature(s):

getNumCVTerms(self)    unsigned int

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

Returns:

the number of CVTerms for this SBML object.

Definition at line 3026 of file libsbml.py.

def libsbml.Reaction.getNumModifiers

(

self

)

Python method signature(s):

getNumModifiers(self)    unsigned int

Returns the number of modifier species in this Reaction.

Returns:

the number of modifiers in this Reaction.

Definition at line 18978 of file libsbml.py.

def libsbml.Reaction.getNumProducts

(

self

)

Python method signature(s):

getNumProducts(self)    unsigned int

Returns the number of product species in this Reaction.

Returns:

the number of products in this Reaction.

Definition at line 18963 of file libsbml.py.

def libsbml.Reaction.getNumReactants

(

self

)

Python method signature(s):

getNumReactants(self)    unsigned int

Returns the number of reactant species in this Reaction.

Returns:

the number of reactants in this Reaction.

Definition at line 18948 of file libsbml.py.

def libsbml.SBase.getParentSBMLObject

(

self

)

[inherited]

Python method signature(s):

getParentSBMLObject(self)    SBase

Returns the parent SBML object.

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

Returns:

the parent SBML object of this SBML object.

Definition at line 2096 of file libsbml.py.

def libsbml.Reaction.getProduct	(		self,
			args
	)

Python method signature(s):

getProduct(self, unsigned int n)    SpeciesReference
getProduct(self, unsigned int n)    SpeciesReference
getProduct(self, string species)    SpeciesReference
getProduct(self, string species)    SpeciesReference

Returns the product species (as a SpeciesReference object) having a specific identifier in this Reaction.

Parameters:

species

the identifier of the product Species ('species' attribute of the product SpeciesReference object)

Returns:

a SpeciesReference object, or NULL if no species with the given identifier species appears as a product in this Reaction.

Definition at line 18901 of file libsbml.py.

def libsbml.Reaction.getReactant	(		self,
			args
	)

Python method signature(s):

getReactant(self, unsigned int n)    SpeciesReference
getReactant(self, unsigned int n)    SpeciesReference
getReactant(self, string species)    SpeciesReference
getReactant(self, string species)    SpeciesReference

Returns the reactant species (as a SpeciesReference object) having a specific identifier in this Reaction.

Parameters:

species

the identifier of the reactant Species ('species' attribute of the reactant SpeciesReference object)

Returns:

a SpeciesReference object, or NULL if no species with the given identifier species appears as a reactant in this Reaction.

Definition at line 18878 of file libsbml.py.

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

Python method signature(s):

getResourceBiologicalQualifier(self, string resource)    BiolQualifierType_t

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

Parameters:

resource

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

Returns:

the BiolQualifierType_t value associated with the resource

Definition at line 3081 of file libsbml.py.

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

Python method signature(s):

getResourceModelQualifier(self, string resource)    ModelQualifierType_t

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

Parameters:

resource

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

Returns:

the ModelQualifierType_t value associated with the resource

Definition at line 3100 of file libsbml.py.

def libsbml.Reaction.getReversible

(

self

)

Python method signature(s):

getReversible(self)    bool

Returns the value of the 'reversible' attribute on the Reaction as a boolean value.

Returns:

the reversibility status of this Reaction.

Definition at line 18279 of file libsbml.py.

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

Python method signature(s):

getSBMLDocument(self)    SBMLDocument
getSBMLDocument(self)    SBMLDocument

Returns the parent SBMLDocument object.

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

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

Returns:

the parent SBMLDocument object of this SBML object.

Definition at line 2068 of file libsbml.py.

def libsbml.SBase.getSBOTerm

(

self

)

[inherited]

Python method signature(s):

getSBOTerm(self)    int

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

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

Returns:

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

Definition at line 2141 of file libsbml.py.

def libsbml.SBase.getSBOTermID

(

self

)

[inherited]

Python method signature(s):

getSBOTermID(self)    string

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

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

Returns:

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

Definition at line 2169 of file libsbml.py.

def libsbml.Reaction.getTypeCode

(

self

)

Python method signature(s):

getTypeCode(self)    SBMLTypeCode_t

Returns the libSBML type code for this SBML object.

Returns:

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

See also:

getElementName()

Reimplemented from libsbml.SBase.

Definition at line 19065 of file libsbml.py.

def libsbml.SBase.getVersion

(

self

)

[inherited]

Python method signature(s):

getVersion(self)    unsigned int

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

Returns:

the SBML version of this SBML object.

See also:

getLevel()

Definition at line 3151 of file libsbml.py.

def libsbml.Reaction.hasRequiredAttributes

(

self

)

Python method signature(s):

hasRequiredAttributes(self)    bool

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

Note:

The required attributes for a Reaction object are: id

Returns:

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

Reimplemented from libsbml.SBase.

Definition at line 19110 of file libsbml.py.

def libsbml.SBase.hasRequiredElements

(

self

)

[inherited]

Python method signature(s):

hasRequiredElements(self)    bool

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

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

Deprecated:

libSBML internal

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

Definition at line 3275 of file libsbml.py.

def libsbml.SBase.hasValidLevelVersionNamespaceCombination

(

self

)

[inherited]

Python method signature(s):

hasValidLevelVersionNamespaceCombination(self)    bool

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

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

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

Returns:

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

Definition at line 3192 of file libsbml.py.

def libsbml.Reaction.initDefaults

(

self

)

Python method signature(s):

initDefaults(self)

Initializes certain attributes of this Reaction object to default values.

• Sets the 'reversible' attribute to true
• (SBML Level 1 only) Sets the 'fast' attribute to false

Warning:

The 'fast' attribute must be used with care. 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.

Definition at line 18202 of file libsbml.py.

def libsbml.SBase.isSetAnnotation

(

self

)

[inherited]

Python method signature(s):

isSetAnnotation(self)    bool

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

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

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

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

Returns:

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

See also:

getAnnotation()

getAnnotationString()

setAnnotation(const XMLNode* annotation)

setAnnotation(const std.string& annotation)

appendAnnotation(const XMLNode* annotation)

appendAnnotation(const std.string& annotation)

unsetAnnotation()

Definition at line 2387 of file libsbml.py.

def libsbml.Reaction.isSetFast

(

self

)

Python method signature(s):

isSetFast(self)    bool

Predicate returning true or false depending on the value of the 'fast' attribute on this Reaction.

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

Returns:

true if the 'fast' attribute is true, false otherwise.

Warning:

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. Note also that in SBML Level 1, 'fast' is defined as optional with a default of false, which means it is effectively always set.

Definition at line 18379 of file libsbml.py.

def libsbml.Reaction.isSetId

(

self

)

Python method signature(s):

isSetId(self)    bool

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

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

Returns:

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

Reimplemented from libsbml.SBase.

Definition at line 18322 of file libsbml.py.

def libsbml.Reaction.isSetKineticLaw

(

self

)

Python method signature(s):

isSetKineticLaw(self)    bool

Predicate returning true or false depending on whether this Reaction contains a kinetic law object.

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

Returns:

true if a KineticLaw is present in this Reaction,, false otherwise.

Definition at line 18360 of file libsbml.py.

def libsbml.SBase.isSetMetaId

(

self

)

[inherited]

Python method signature(s):

isSetMetaId(self)    bool

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

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

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

Returns:

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

See also:

getMetaId()

setMetaId(const std.string& metaid)

Definition at line 2235 of file libsbml.py.

def libsbml.Reaction.isSetName

(

self

)

Python method signature(s):

isSetName(self)    bool

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

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

Returns:

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

Reimplemented from libsbml.SBase.

Definition at line 18341 of file libsbml.py.

def libsbml.SBase.isSetNotes

(

self

)

[inherited]

Python method signature(s):

isSetNotes(self)    bool

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

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

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

Returns:

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

See also:

getNotes()

getNotesString()

setNotes(const XMLNode* notes)

setNotes(const std.string& notes)

appendNotes(const XMLNode* notes)

appendNotes(const std.string& notes)

unsetNotes()

Definition at line 2348 of file libsbml.py.

def libsbml.SBase.isSetSBOTerm

(

self

)

[inherited]

Python method signature(s):

isSetSBOTerm(self)    bool

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

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

Returns:

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

Definition at line 2427 of file libsbml.py.

def libsbml.Reaction.removeModifier	(		self,
			args
	)

Python method signature(s):

removeModifier(self, unsigned int n)    ModifierSpeciesReference
removeModifier(self, string species)    ModifierSpeciesReference

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.

Parameters:

species

the 'species' attribute of the ModifierSpeciesReference object

Returns:

the removed ModifierSpeciesReference object, or NULL if no ModifierSpeciesReference object with the given 'species' attribute species exists in this Reaction.

Definition at line 19041 of file libsbml.py.

def libsbml.Reaction.removeProduct	(		self,
			args
	)

Python method signature(s):

removeProduct(self, unsigned int n)    SpeciesReference
removeProduct(self, string species)    SpeciesReference

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.

Parameters:

species

the 'species' attribute of the product SpeciesReference object

Returns:

the removed product SpeciesReference object, or NULL if no product SpeciesReference object with the given 'species' attribute species exists in this Reaction.

Definition at line 19017 of file libsbml.py.

def libsbml.Reaction.removeReactant	(		self,
			args
	)

Python method signature(s):

removeReactant(self, unsigned int n)    SpeciesReference
removeReactant(self, string species)    SpeciesReference

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.

Parameters:

species

the 'species' attribute of the reactant SpeciesReference object

Returns:

the removed reactant SpeciesReference object, or NULL if no reactant SpeciesReference object with the given 'species' attribute species exists in this Reaction.

Definition at line 18993 of file libsbml.py.

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

Python method signature(s):

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

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

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

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

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

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

Parameters:

annotation

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

Returns:

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

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_OPERATION_FAILED

See also:

getAnnotationString()

isSetAnnotation()

setAnnotation(const XMLNode* annotation)

appendAnnotation(const XMLNode* annotation)

appendAnnotation(const std.string& annotation)

unsetAnnotation()

Reimplemented in libsbml.Model, and libsbml.SpeciesReference.

Definition at line 2568 of file libsbml.py.

def libsbml.Reaction.setFast	(		self,
			args
	)

Python method signature(s):

setFast(self, bool value)    int

Sets the value of the 'fast' attribute of this Reaction.

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

Parameters:

value

the value of the 'fast' attribute.

Returns:

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

• LIBSBML_OPERATION_SUCCESS

Warning:

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.

Definition at line 18526 of file libsbml.py.

def libsbml.Reaction.setId	(		self,
			args
	)

Python method signature(s):

setId(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 summary of the definition of the SBML identifier type SId (here expressed in an extended form of BNF notation):

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

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

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

Parameters:

sid

the string to use as the identifier of this Reaction

Returns:

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

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_INVALID_ATTRIBUTE_VALUE

Reimplemented from libsbml.SBase.

Definition at line 18411 of file libsbml.py.

def libsbml.Reaction.setKineticLaw	(		self,
			args
	)

Python method signature(s):

setKineticLaw(self, KineticLaw kl)    int

Sets the 'kineticLaw' subelement of this Reaction to a copy of the given KineticLaw object.

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

Parameters:

kl

the KineticLaw object to use.

Returns:

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

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_LEVEL_MISMATCH
• LIBSBML_VERSION_MISMATCH

Definition at line 18477 of file libsbml.py.

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

Python method signature(s):

setMetaId(self, string metaid)    int

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

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

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

Parameters:

metaid

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

Returns:

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

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_INVALID_ATTRIBUTE_VALUE
• LIBSBML_UNEXPECTED_ATTRIBUTE

See also:

getMetaId()

isSetMetaId()

Definition at line 2446 of file libsbml.py.

def libsbml.Reaction.setName	(		self,
			args
	)

Python method signature(s):

setName(self, string name)    int

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

The string in name is copied.

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

Parameters:

name

the new name for the Reaction

Returns:

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

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_INVALID_ATTRIBUTE_VALUE

Reimplemented from libsbml.SBase.

Definition at line 18451 of file libsbml.py.

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

Python method signature(s):

setNamespaces(self, XMLNamespaces xmlns)    int

Sets the namespaces relevant of this SBML object.

Parameters:

xmlns

the namespaces to set

Returns:

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

• LIBSBML_OPERATION_SUCCESS

Definition at line 2811 of file libsbml.py.

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

Python method signature(s):

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

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

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

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

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

Parameters:

notes

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

Returns:

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

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_INVALID_OBJECT
• LIBSBML_OPERATION_FAILED

See also:

getNotesString()

isSetNotes()

setNotes(const XMLNode* notes)

appendNotes(const XMLNode* notes)

appendNotes(const std.string& notes)

unsetNotes()

Definition at line 2676 of file libsbml.py.

def libsbml.Reaction.setReversible	(		self,
			args
	)

Python method signature(s):

setReversible(self, bool value)    int

Sets the value of the 'reversible' attribute of this Reaction.

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

Parameters:

value

the value of the 'reversible' attribute.

Returns:

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

• LIBSBML_OPERATION_SUCCESS

Definition at line 18503 of file libsbml.py.

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

Python method signature(s):

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

Sets the value of the 'sboTerm' attribute.

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

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

Parameters:

value

the NNNNNNN integer portion of the SBO identifier

Returns:

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

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_INVALID_ATTRIBUTE_VALUE
• LIBSBML_UNEXPECTED_ATTRIBUTE

Definition at line 2774 of file libsbml.py.

def libsbml.SBase.toSBML

(

self

)

[inherited]

Python method signature(s):

toSBML(self)    char

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

Returns:

the partial SBML that describes this SBML object.

Definition at line 3237 of file libsbml.py.

def libsbml.SBase.unsetAnnotation

(

self

)

[inherited]

Python method signature(s):

unsetAnnotation(self)    int

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

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

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

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

Returns:

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

• LIBSBML_OPERATION_SUCCESS

See also:

getAnnotation()

getAnnotationString()

isSetAnnotation()

setAnnotation(const XMLNode* annotation)

setAnnotation(const std.string& annotation)

appendAnnotation(const XMLNode* annotation)

appendAnnotation(const std.string& annotation)

Definition at line 2910 of file libsbml.py.

def libsbml.SBase.unsetCVTerms

(

self

)

[inherited]

Python method signature(s):

unsetCVTerms(self)    int

Clears the list of CVTerms of this SBML object.

Returns:

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

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_OPERATION_FAILED

Definition at line 3060 of file libsbml.py.

def libsbml.Reaction.unsetFast

(

self

)

Python method signature(s):

unsetFast(self)    int

Unsets the value of the 'fast' attribute of this Reaction.

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

Returns:

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

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_OPERATION_FAILED

Warning:

In SBML Level 1, 'fast' is optional with a default of 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.

Definition at line 18605 of file libsbml.py.

def libsbml.Reaction.unsetKineticLaw

(

self

)

Python method signature(s):

unsetKineticLaw(self)    int

Unsets the 'kineticLaw' subelement of this Reaction.

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

Returns:

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

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_OPERATION_FAILED

Definition at line 18583 of file libsbml.py.

def libsbml.SBase.unsetMetaId

(

self

)

[inherited]

Python method signature(s):

unsetMetaId(self)    int

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

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

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

Returns:

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

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_OPERATION_FAILED

Definition at line 2832 of file libsbml.py.

def libsbml.Reaction.unsetName

(

self

)

Python method signature(s):

unsetName(self)    int

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

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

Returns:

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

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_OPERATION_FAILED

Definition at line 18561 of file libsbml.py.

def libsbml.SBase.unsetNotes

(

self

)

[inherited]

Python method signature(s):

unsetNotes(self)    int

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

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

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

Returns:

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

• LIBSBML_OPERATION_SUCCESS

See also:

getNotesString()

isSetNotes()

setNotes(const XMLNode* notes)

setNotes(const std.string& notes)

appendNotes(const XMLNode* notes)

appendNotes(const std.string& notes)

Definition at line 2869 of file libsbml.py.

def libsbml.SBase.unsetSBOTerm

(

self

)

[inherited]

Python method signature(s):

unsetSBOTerm(self)    int

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

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

Returns:

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

• LIBSBML_OPERATION_SUCCESS
• LIBSBML_UNEXPECTED_ATTRIBUTE

Definition at line 2952 of file libsbml.py.

---

Member Data Documentation

libsbml.Reaction.this

Reimplemented from libsbml.SBase.

Definition at line 18186 of file libsbml.py.