|
libSBML C# API
5.18.0
|
|
libSBML C# API
5.18.0
|
An integral component in a complete description of a steady-state model is the so-called objective function, which generally consists of a linear combination of model variables (fluxes) and a sense (direction). In the SBML Level 3 Flux Balance Constraints (“fbc”) package, this concept is succinctly captured in the Objective class.
The Objective class is derived from the normal SBML SBase class and inherits the 'metaid' and 'sboTerm' attributes, as well as the subcomponents for Annotation and Notes. To these, the Objective class adds an optional attribute named 'type'. The type attribute can take one of two literal values: 'maximize' or 'minimize'. The values represent the sense of the optimality constraint for the FBC model.
The “fbc” package allows for the definition of multiple model objectives, with one being designated as active. The active objective is indicated using the attribute 'activeObjective' on the ListOfObjectives object. Here is an example of the XML encoding of a model with a list of objective functions:
<fbc:listOfObjectives fbc:activeObjective='obj1'> <fbc:objective fbc:id='obj1' fbc:type='maximize'> <fbc:listOfFluxObjectives> <fbc:fluxObjective fbc:reaction='R101' fbc:coefficient='1'/> </fbc:listOfFluxObjectives> </fbc:objective> <fbc:objective fbc:id='obj2' fbc:type='minimize'> <fbc:listOfFluxObjectives> <fbc:fluxObjective fbc:reaction='R102' fbc:coefficient='-2.5'/> <fbc:fluxObjective fbc:reaction='R103' fbc:coefficient='1'/> </fbc:listOfFluxObjectives> </fbc:objective> </fbc:listOfObjectives>
Public Member Functions | |
| int | addCVTerm (CVTerm term, bool newBag) |
| Adds a copy of the given CVTerm object to this SBML object. More... | |
| int | addCVTerm (CVTerm term) |
| Adds a copy of the given CVTerm object to this SBML object. More... | |
| int | addFluxObjective (FluxObjective fo) |
| Adds a copy the given FluxObjective to this Objective. More... | |
| new int | appendAnnotation (XMLNode annotation) |
Appends the given annotation to the 'annotation' subelement of this object. More... | |
| new int | appendAnnotation (string annotation) |
Appends the given annotation to the 'annotation' subelement of this object. More... | |
| int | appendNotes (XMLNode notes) |
Appends the given notes to the 'notes' subelement of this object. More... | |
| int | appendNotes (string notes) |
Appends the given notes to the 'notes' subelement of this object. More... | |
| int | checkCompatibility (SBase arg0) |
| string | checkMathMLNamespace (XMLToken elem) |
| new Objective | clone () |
| Creates and returns a deep copy of this Objective object. More... | |
| FluxObjective | createFluxObjective () |
| Creates a new FluxObjective object. More... | |
| void | deleteDisabledPlugins (bool recursive) |
| Deletes all information stored in disabled plugins. More... | |
| void | deleteDisabledPlugins () |
| Deletes all information stored in disabled plugins. More... | |
| int | disablePackage (string pkgURI, string pkgPrefix) |
| Disables the given SBML Level 3 package on this object. More... | |
| override void | Dispose () |
| int | enablePackage (string pkgURI, string pkgPrefix, bool flag) |
| Enables or disables the given SBML Level 3 package on this object. More... | |
| override bool | Equals (Object sb) |
| SBase | getAncestorOfType (int type, string pkgName) |
| Returns the first ancestor object that has the given SBML type code from the given package. More... | |
| SBase | getAncestorOfType (int type) |
| Returns the first ancestor object that has the given SBML type code from the given package. More... | |
| XMLNode | getAnnotation () |
| Returns the content of the 'annotation' subelement of this object as a tree of XMLNode objects. More... | |
| string | getAnnotationString () |
| Returns the content of the 'annotation' subelement of this object as a character string. More... | |
| long | getColumn () |
| Returns the column number where this object first appears in the XML representation of the SBML document. More... | |
| CVTerm | getCVTerm (long n) |
| Returns the nth CVTerm in the list of CVTerms of this SBML object. More... | |
| CVTermList | getCVTerms () |
| Returns a list of CVTerm objects in the annotations of this SBML object. More... | |
| SBasePlugin | getDisabledPlugin (long n) |
| Returns the nth disabled plug-in object (extension interface) for an SBML Level 3 package extension. More... | |
| new SBase | getElementByMetaId (string metaid) |
Returns the first child element it can find with a specific 'metaid' attribute value, or null if no such object is found. More... | |
| new SBase | getElementBySId (string id) |
Returns the first child element found that has the given id in the model-wide SId namespace, or null if no such object is found. More... | |
| new string | getElementName () |
| Returns the XML element name of this object. More... | |
| FluxObjective | getFluxObjective (long n) |
| Get a FluxObjective from the ListOfFluxObjectives. More... | |
| FluxObjective | getFluxObjective (string sid) |
| Get a FluxObjective from the ListOfFluxObjectives based on its identifier. More... | |
| override int | GetHashCode () |
| new string | getId () |
| Returns the value of the 'id' attribute of this Objective. More... | |
| string | getIdAttribute () |
| Returns the value of the 'id' attribute of this SBML object. More... | |
| bool | getIsSetListOfFluxObjectives () |
| long | getLevel () |
| Returns the SBML Level of the SBMLDocument object containing this object. More... | |
| long | getLine () |
| Returns the line number where this object first appears in the XML representation of the SBML document. More... | |
| SBaseList | getListOfAllElements (ElementFilter filter) |
| SBaseList | getListOfAllElements () |
| SBaseList | getListOfAllElementsFromPlugins (ElementFilter filter) |
| SBaseList | getListOfAllElementsFromPlugins () |
| ListOfFluxObjectives | getListOfFluxObjectives () |
| Returns the ListOfFluxObjectives in this Objective object. More... | |
| string | getMetaId () |
| Returns the value of the 'metaid' attribute of this SBML object. More... | |
| Model | getModel () |
| Returns the Model object for the SBML Document in which the current object is located. More... | |
| ModelHistory | getModelHistory () |
| Returns the ModelHistory object, if any, attached to this object. More... | |
| new string | getName () |
| Returns the value of the 'name' attribute of this Objective object. More... | |
| new XMLNamespaces | getNamespaces () |
| Returns a list of the XML Namespaces declared on the SBML document owning this object. More... | |
| XMLNode | getNotes () |
| Returns the content of the 'notes' subelement of this object as a tree of XMLNode objects. More... | |
| string | getNotesString () |
| Returns the content of the 'notes' subelement of this object as a string. More... | |
| long | getNumCVTerms () |
| Returns the number of CVTerm objects in the annotations of this SBML object. More... | |
| long | getNumDisabledPlugins () |
| Returns the number of disabled plug-in objects (extension interfaces) for SBML Level 3 package extensions known. More... | |
| long | getNumFluxObjectives () |
| Get the number of FluxObjective objects in this Objective. More... | |
| long | getNumPlugins () |
| Returns the number of plug-in objects (extenstion interfaces) for SBML Level 3 package extensions known. More... | |
| new int | getObjectiveType () |
| Returns the enumeration value of the 'type' attribute of this Objective. More... | |
| long | getPackageCoreVersion () |
| Returns the SBML Core Version within the SBML Level of the actual object. More... | |
| string | getPackageName () |
| Returns the name of the SBML Level 3 package in which this element is defined. More... | |
| long | getPackageVersion () |
| Returns the Version of the SBML Level 3 package to which this element belongs to. More... | |
| SBase | getParentSBMLObject () |
| Returns the parent SBML object containing this object. More... | |
| SBasePlugin | getPlugin (string package) |
| Returns a plug-in object (extension interface) for an SBML Level 3 package extension with the given package name or URI. More... | |
| SBasePlugin | getPlugin (long n) |
| Returns the nth plug-in object (extension interface) for an SBML Level 3 package extension. More... | |
| string | getPrefix () |
| Returns the XML namespace prefix of this element. More... | |
| int | getResourceBiologicalQualifier (string resource) |
| Returns the MIRIAM biological qualifier associated with the given resource. More... | |
| int | getResourceModelQualifier (string resource) |
| Returns the MIRIAM model qualifier associated with the given resource. More... | |
| SBMLDocument | getSBMLDocument () |
| Returns the SBMLDocument object containing this object instance. More... | |
| int | getSBOTerm () |
| Returns the integer portion of the value of the 'sboTerm' attribute of this object. More... | |
| string | getSBOTermAsURL () |
| Returns the URL representation of the 'sboTerm' attribute of this object. More... | |
| string | getSBOTermID () |
| Returns the string representation of the 'sboTerm' attribute of this object. More... | |
| string | getType () |
| Returns the string of the 'type' attribute of this Objective. More... | |
| new int | getTypeCode () |
| Returns the libSBML type code for this SBML object. More... | |
| string | getURI () |
| Gets the namespace URI to which this element belongs to. More... | |
| long | getVersion () |
| Returns the Version within the SBML Level of the SBMLDocument object containing this object. More... | |
| new bool | hasRequiredAttributes () |
Predicate returning true if all the required attributes for this Objective object have been set. More... | |
| new bool | hasRequiredElements () |
Predicate returning true if all the required elements for this Objective object have been set. More... | |
| bool | hasValidLevelVersionNamespaceCombination () |
Predicate returning true if this object's level/version and namespace values correspond to a valid SBML specification. More... | |
| bool | isPackageEnabled (string pkgName) |
Predicate returning true if the given SBML Level 3 package is enabled with this object. More... | |
| bool | isPackageURIEnabled (string pkgURI) |
Predicate returning true if an SBML Level 3 package with the given URI is enabled with this object. More... | |
| bool | isPkgEnabled (string pkgName) |
Predicate returning true if the given SBML Level 3 package is enabled with this object. More... | |
| bool | isPkgURIEnabled (string pkgURI) |
Predicate returning true if an SBML Level 3 package with the given URI is enabled with this object. More... | |
| bool | isSetAnnotation () |
Predicate returning true if this object's 'annotation' subelement exists and has content. More... | |
| new bool | isSetId () |
Predicate returning true if this Objective's 'id' attribute is set. More... | |
| bool | isSetIdAttribute () |
Predicate returning true if this object's 'id' attribute is set. More... | |
| bool | isSetMetaId () |
Predicate returning true if this object's 'metaid' attribute is set. More... | |
| bool | isSetModelHistory () |
Predicate returning true if this object has a ModelHistory object attached to it. More... | |
| new bool | isSetName () |
Predicate returning true if this Objective's 'name' attribute is set. More... | |
| bool | isSetNotes () |
Predicate returning true if this object's 'notes' subelement exists and has content. More... | |
| bool | isSetSBOTerm () |
Predicate returning true if this object's 'sboTerm' attribute is set. More... | |
| new bool | isSetType () |
Predicate returning true if this Objective's 'type' attribute is set. More... | |
| bool | isSetUserData () |
| Predicate returning true or false depending on whether the user data of this element has been set. More... | |
| bool | matchesRequiredSBMLNamespacesForAddition (SBase sb) |
Returns true if this object's set of XML namespaces are a subset of the given object's XML namespaces. More... | |
| bool | matchesSBMLNamespaces (SBase sb) |
Returns true if this object's set of XML namespaces are the same as the given object's XML namespaces. More... | |
| Objective (long level, long version, long pkgVersion) | |
| Creates a new Objective with the given SBML Level, Version, and “fbc”package version. More... | |
| Objective (long level, long version) | |
| Creates a new Objective with the given SBML Level, Version, and “fbc”package version. More... | |
| Objective (long level) | |
| Creates a new Objective with the given SBML Level, Version, and “fbc”package version. More... | |
| Objective () | |
| Creates a new Objective with the given SBML Level, Version, and “fbc”package version. More... | |
| Objective (FbcPkgNamespaces fbcns) | |
| Creates a new Objective with the given FbcPkgNamespaces object. More... | |
| Objective (Objective orig) | |
| Copy constructor for Objective. More... | |
| FluxObjective | removeFluxObjective (long n) |
| Removes the nth FluxObjective from the ListOfFluxObjectives. More... | |
| FluxObjective | removeFluxObjective (string sid) |
| Removes the FluxObjective with the given identifier from the ListOfFluxObjectives. More... | |
| new int | removeFromParentAndDelete () |
| Removes this object from its parent. More... | |
| int | removeTopLevelAnnotationElement (string elementName, string elementURI, bool removeEmpty) |
| Removes the top-level element within the 'annotation' subelement of this SBML object with the given name and optional URI. More... | |
| int | removeTopLevelAnnotationElement (string elementName, string elementURI) |
| Removes the top-level element within the 'annotation' subelement of this SBML object with the given name and optional URI. More... | |
| int | removeTopLevelAnnotationElement (string elementName) |
| Removes the top-level element within the 'annotation' subelement of this SBML object with the given name and optional URI. More... | |
| new void | renameMetaIdRefs (string oldid, string newid) |
| Replaces all uses of a given meta identifier attribute value with another value. More... | |
| new void | renameSIdRefs (string oldid, string newid) |
Replaces all uses of a given SIdRef type attribute value with another value. More... | |
| new void | renameUnitSIdRefs (string oldid, string newid) |
Replaces all uses of a given UnitSIdRef type attribute value with another value. More... | |
| int | replaceTopLevelAnnotationElement (XMLNode annotation) |
| Replaces the given top-level element within the 'annotation' subelement of this SBML object and with the annotation element supplied. More... | |
| int | replaceTopLevelAnnotationElement (string annotation) |
| Replaces the given top-level element within the 'annotation' subelement of this SBML object and with the annotation element supplied. More... | |
| new int | setAnnotation (XMLNode annotation) |
| Sets the value of the 'annotation' subelement of this SBML object. More... | |
| new int | setAnnotation (string annotation) |
| Sets the value of the 'annotation' subelement of this SBML object. More... | |
| new int | setId (string sid) |
| Sets the value of the 'id' attribute of this Objective. More... | |
| new int | setIdAttribute (string sid) |
| Sets the value of the 'id' attribute of this SBML object. More... | |
| int | setMetaId (string metaid) |
| Sets the value of the meta-identifier attribute of this SBML object. More... | |
| int | setModelHistory (ModelHistory history) |
| Sets the ModelHistory of this object. More... | |
| new int | setName (string name) |
| Sets the value of the 'name' attribute of this Objective. More... | |
| int | setNamespaces (XMLNamespaces xmlns) |
| Sets the namespaces relevant of this SBML object. More... | |
| int | setNotes (XMLNode notes) |
| Sets the value of the 'notes' subelement of this SBML object. More... | |
| int | setNotes (string notes, bool addXHTMLMarkup) |
Sets the value of the 'notes' subelement of this SBML object to a copy of the string notes. More... | |
| int | setNotes (string notes) |
Sets the value of the 'notes' subelement of this SBML object to a copy of the string notes. More... | |
| void | setSBMLNamespacesAndOwn (SBMLNamespaces disownedNs) |
| new int | setSBOTerm (int value) |
| Sets the value of the 'sboTerm' attribute. More... | |
| new int | setSBOTerm (string sboid) |
| Sets the value of the 'sboTerm' attribute by string. More... | |
| int | setType (int type) |
| Sets the value of the 'type' attribute of this Objective. More... | |
| new int | setType (string type) |
| Sets the value of the 'type' attribute of this Objective. More... | |
| string | toSBML () |
| Returns a string consisting of a partial SBML corresponding to just this object. More... | |
| XMLNode | toXMLNode () |
| Returns this element as an XMLNode. More... | |
| int | unsetAnnotation () |
| Unsets the value of the 'annotation' subelement of this SBML object. More... | |
| int | unsetCVTerms () |
| Clears the list of CVTerm objects attached to this SBML object. More... | |
| new int | unsetId () |
| Unsets the value of the 'id' attribute of this Objective. More... | |
| int | unsetIdAttribute () |
| Unsets the value of the 'id' attribute of this SBML object. More... | |
| int | unsetMetaId () |
| Unsets the value of the 'metaid' attribute of this SBML object. More... | |
| int | unsetModelHistory () |
| Unsets the ModelHistory object attached to this object. More... | |
| new int | unsetName () |
| Unsets the value of the 'name' attribute of this Objective. More... | |
| int | unsetNotes () |
| Unsets the value of the 'notes' subelement of this SBML object. More... | |
| int | unsetSBOTerm () |
| Unsets the value of the 'sboTerm' attribute of this SBML object. More... | |
| new int | unsetType () |
| Unsets the value of the 'type' attribute of this Objective. More... | |
| int | unsetUserData () |
| Unsets the user data of this element. More... | |
Static Public Member Functions | |
| static bool | operator!= (SBase lhs, SBase rhs) |
| static bool | operator== (SBase lhs, SBase rhs) |
Protected Attributes | |
| bool | swigCMemOwn |
| libsbmlcs.Objective.Objective | ( | long | level, |
| long | version, | ||
| long | pkgVersion | ||
| ) |
Creates a new Objective with the given SBML Level, Version, and “fbc”package version.
| level | a long integer, the SBML Level to assign to this Objective. |
| version | a long integer, the SBML Version to assign to this Objective. |
| pkgVersion | a long integer, the SBML Fbc Version to assign to this Objective. |
| libsbmlcs.Objective.Objective | ( | long | level, |
| long | version | ||
| ) |
Creates a new Objective with the given SBML Level, Version, and “fbc”package version.
| level | a long integer, the SBML Level to assign to this Objective. |
| version | a long integer, the SBML Version to assign to this Objective. |
| pkgVersion | a long integer, the SBML Fbc Version to assign to this Objective. |
| libsbmlcs.Objective.Objective | ( | long | level | ) |
Creates a new Objective with the given SBML Level, Version, and “fbc”package version.
| level | a long integer, the SBML Level to assign to this Objective. |
| version | a long integer, the SBML Version to assign to this Objective. |
| pkgVersion | a long integer, the SBML Fbc Version to assign to this Objective. |
| libsbmlcs.Objective.Objective | ( | ) |
Creates a new Objective with the given SBML Level, Version, and “fbc”package version.
| level | a long integer, the SBML Level to assign to this Objective. |
| version | a long integer, the SBML Version to assign to this Objective. |
| pkgVersion | a long integer, the SBML Fbc Version to assign to this Objective. |
| libsbmlcs.Objective.Objective | ( | FbcPkgNamespaces | fbcns | ) |
Creates a new Objective with the given FbcPkgNamespaces object.
The package namespaces object used in this constructor is derived from a SBMLNamespaces object, which encapsulates SBML Level/Version/namespaces information. It is used to communicate the SBML Level, Version, and package version and name information used in addition to SBML Level 3 Core. A common approach to using libSBML's SBMLNamespaces facilities is to create an package namespace object somewhere in a program once, then hand that object as needed to object constructors of that package that accept it as and argument, such as this one.
| fbcns | the FbcPkgNamespaces object. |
| libsbmlcs.Objective.Objective | ( | Objective | orig | ) |
|
inherited |
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. |
create) for alternatives that do not lead to these issues.
|
inherited |
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. |
create) for alternatives that do not lead to these issues.| int libsbmlcs.Objective.addFluxObjective | ( | FluxObjective | fo | ) |
Adds a copy the given FluxObjective to this Objective.
| fo | the FluxObjective object to add. |
|
inherited |
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(XMLNode annotation) or SBase::setAnnotation(string annotation), 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. |
|
inherited |
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(XMLNode annotation) or SBase::setAnnotation(string annotation), 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 |
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. |
|
inherited |
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. |
|
inherited |
|
inherited |
| new Objective libsbmlcs.Objective.clone | ( | ) |
| FluxObjective libsbmlcs.Objective.createFluxObjective | ( | ) |
Creates a new FluxObjective object.
This method creates the FluxObjective object, adds it to this Objective object's ListOfFluxObjectives, and returns the FluxObjective object created.
|
inherited |
Deletes all information stored in disabled plugins.
If the plugin is re-enabled later, it will then not have any previously-stored information.
SBML Level 3 consists of a Core definition that can be extended via optional SBML Level 3 packages. A given model may indicate that it uses one or more SBML packages, and likewise, a software tool may be able to support one or more packages. LibSBML does not come preconfigured with all possible packages included and enabled, in part because not all package specifications have been finalized. To support the ability for software systems to enable support for the Level 3 packages they choose, libSBML features a plug-in mechanism. Each SBML Level 3 package is implemented in a separate code plug-in that can be enabled by the application to support working with that SBML package. A given SBML model may thus contain not only objects defined by SBML Level 3 Core, but also objects created by libSBML plug-ins supporting additional Level 3 packages.
If a plugin is disabled, the package information it contains is no longer considered to be part of the SBML document for the purposes of searching the document or writing out the document. However, the information is still retained, so if the plugin is enabled again, the same information will once again be available, and will be written out to the final model.
| recursive | if true, the disabled information will be deleted also from all child elements, otherwise only from this SBase element. |
|
inherited |
Deletes all information stored in disabled plugins.
If the plugin is re-enabled later, it will then not have any previously-stored information.
SBML Level 3 consists of a Core definition that can be extended via optional SBML Level 3 packages. A given model may indicate that it uses one or more SBML packages, and likewise, a software tool may be able to support one or more packages. LibSBML does not come preconfigured with all possible packages included and enabled, in part because not all package specifications have been finalized. To support the ability for software systems to enable support for the Level 3 packages they choose, libSBML features a plug-in mechanism. Each SBML Level 3 package is implemented in a separate code plug-in that can be enabled by the application to support working with that SBML package. A given SBML model may thus contain not only objects defined by SBML Level 3 Core, but also objects created by libSBML plug-ins supporting additional Level 3 packages.
If a plugin is disabled, the package information it contains is no longer considered to be part of the SBML document for the purposes of searching the document or writing out the document. However, the information is still retained, so if the plugin is enabled again, the same information will once again be available, and will be written out to the final model.
| recursive | if true, the disabled information will be deleted also from all child elements, otherwise only from this SBase element. |
|
inherited |
Disables the given SBML Level 3 package on this object.
This method disables the specified package on this object and other objects connected by child-parent links in the same SBMLDocument object.
An example of when this may be useful is during construction of model components when mixing existing and new models. Suppose your application read an SBML document containing a model that used the SBML Hierarchical Model Composition (“comp”) package, and extracted parts of that model in order to construct a new model in memory. The new, in-memory model will not accept a component drawn from an other SBMLDocument with different package namespace declarations. You could reconstruct the same namespaces in the in-memory model first, but as a shortcut, you could also disable the package namespace on the object being added. Here is a code example to help clarify this:
| pkgURI | the URI of the package. |
| pkgPrefix | the XML prefix of the package. |
|
virtual |
Reimplemented from libsbmlcs.SBase.
|
inherited |
Enables or disables the given SBML Level 3 package on this object.
This method enables the specified package on this object and other objects connected by child-parent links in the same SBMLDocument object. This method is the converse of SBase::disablePackage(string pkgURI, string pkgPrefix).
| pkgURI | the URI of the package. |
| pkgPrefix | the XML prefix of the package. |
| flag | whether to enable (true) or disable (false) the package. |
|
inherited |
|
inherited |
Returns the first ancestor object that has the given SBML type code from the given package.
LibSBML attaches an identifying code to every kind of SBML object. These are known as SBML type codes. In the C# 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 from the given pkgName.
| 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. |
null if no ancestor exists.pkgName must be used for all type codes from SBML Level 3 packages. Otherwise, the function will search the 'core' namespace alone, not find any corresponding elements, and return null.
|
inherited |
Returns the first ancestor object that has the given SBML type code from the given package.
LibSBML attaches an identifying code to every kind of SBML object. These are known as SBML type codes. In the C# 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 from the given pkgName.
| 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. |
null if no ancestor exists.pkgName must be used for all type codes from SBML Level 3 packages. Otherwise, the function will search the 'core' namespace alone, not find any corresponding elements, and return null.
|
inherited |
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 |
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. See the method getAnnotation() for a version that returns annotations in XML form.
|
inherited |
Returns the column number where this object first appears in the XML representation of the SBML document.
0.
|
inherited |
|
inherited |
Returns a list of CVTerm objects in the annotations of this SBML object.
|
inherited |
Returns the nth disabled plug-in object (extension interface) for an SBML Level 3 package extension.
If no such plugin exists, null is returned.
SBML Level 3 consists of a Core definition that can be extended via optional SBML Level 3 packages. A given model may indicate that it uses one or more SBML packages, and likewise, a software tool may be able to support one or more packages. LibSBML does not come preconfigured with all possible packages included and enabled, in part because not all package specifications have been finalized. To support the ability for software systems to enable support for the Level 3 packages they choose, libSBML features a plug-in mechanism. Each SBML Level 3 package is implemented in a separate code plug-in that can be enabled by the application to support working with that SBML package. A given SBML model may thus contain not only objects defined by SBML Level 3 Core, but also objects created by libSBML plug-ins supporting additional Level 3 packages.
If a plugin is disabled, the package information it contains is no longer considered to be part of the SBML document for the purposes of searching the document or writing out the document. However, the information is still retained, so if the plugin is enabled again, the same information will once again be available, and will be written out to the final model.
| n | the index of the disabled plug-in to return. |
n is invalid, null is returned.
|
inherited |
Returns the first child element it can find with a specific 'metaid' attribute value, or null if no such object is found.
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. The latter point is important, because the uniqueness criterion applies across any attribute with type ID anywhere in the file, 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 the XML ID type. Although SBML itself specifies the use of XML ID only for the 'metaid' attribute, SBML-compatible applications 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. Finally, note that LibSBML does not provide an explicit XML ID data type; it uses ordinary character strings, which is easier for applications to support.
| metaid | string representing the 'metaid' attribute value of the object to find. |
|
inherited |
Returns the first child element found that has the given id in the model-wide SId namespace, or null if no such object is found.
| id | string representing the 'id' attribute value of the object to find. |
| new string libsbmlcs.Objective.getElementName | ( | ) |
Returns the XML element name of this object.
For Objective, the XML element name is always 'objective'.
'objective'. | FluxObjective libsbmlcs.Objective.getFluxObjective | ( | long | n | ) |
Get a FluxObjective from the ListOfFluxObjectives.
| n | the index number of the FluxObjective to get. |
n is invalid, null is returned.| FluxObjective libsbmlcs.Objective.getFluxObjective | ( | string | sid | ) |
Get a FluxObjective from the ListOfFluxObjectives based on its identifier.
| sid | a string representing the identifier of the FluxObjective to get. |
null if no such FluxObjective exists.
|
inherited |
| new string libsbmlcs.Objective.getId | ( | ) |
Returns the value of the 'id' attribute of this Objective.
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 SId or a type derived from that, such as UnitSId, depending on the object in question. All data types are defined as follows:
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. This applies to all uses of SId, SIdRef, and derived types.
Users need to be aware of some important API issues that are the result of the history of SBML and libSBML. Prior to SBML Level 3 Version 2, SBML defined 'id' and 'name' attributes on only a subset of SBML objects. To simplify the work of programmers, libSBML's API provided get, set, check, and unset on the SBase object class itself instead of on individual subobject classes. This made the get/set/etc. methods uniformly available on all objects in the libSBML API. LibSBML simply returned empty strings or otherwise did not act when the methods were applied to SBML objects that were not defined by the SBML specification to have 'id' or 'name' attributes. Additional complications arose with the rule and assignment objects: InitialAssignment, EventAssignment, AssignmentRule, and RateRule. In early versions of SBML, the rule object hierarchy was different, and in addition, then as now, they possess different attributes: 'variable' (for the rules and event assignments), 'symbol' (for initial assignments), or neither (for algebraic rules). Prior to SBML Level 3 Version 2, getId() would always return an empty string, and isSetId() would always return false for objects of these classes.
With the addition of 'id' and 'name' attributes on SBase in Level 3 Version 2, it became necessary to introduce a new way to interact with the attributes more consistently in libSBML to avoid breaking backward compatibility in the behavior of the original 'id' methods. For this reason, libSBML provides four functions (getIdAttribute(), setIdAttribute(), isSetIdAttribute(), and unsetIdAttribute()) that always act on the actual 'id' attribute inherited from SBase, regardless of the object's type. These new methods should be used instead of the older getId()/setId()/etc. methods unless the old behavior is somehow necessary. Regardless of the Level and Version of the SBML, these functions allow client applications to use more generalized code in some situations (for instance, when manipulating objects that are all known to have identifiers). If the object in question does not posess an 'id' attribute according to the SBML specification for the Level and Version in use, libSBML will not allow the identifier to be set, nor will it read or write 'id' attributes for those objects.
|
inherited |
Returns the value of the 'id' attribute of this SBML object.
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 SId or a type derived from that, such as UnitSId, depending on the object in question. All data types are defined as follows:
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. This applies to all uses of SId, SIdRef, and derived types.
Users need to be aware of some important API issues that are the result of the history of SBML and libSBML. Prior to SBML Level 3 Version 2, SBML defined 'id' and 'name' attributes on only a subset of SBML objects. To simplify the work of programmers, libSBML's API provided get, set, check, and unset on the SBase object class itself instead of on individual subobject classes. This made the get/set/etc. methods uniformly available on all objects in the libSBML API. LibSBML simply returned empty strings or otherwise did not act when the methods were applied to SBML objects that were not defined by the SBML specification to have 'id' or 'name' attributes. Additional complications arose with the rule and assignment objects: InitialAssignment, EventAssignment, AssignmentRule, and RateRule. In early versions of SBML, the rule object hierarchy was different, and in addition, then as now, they possess different attributes: 'variable' (for the rules and event assignments), 'symbol' (for initial assignments), or neither (for algebraic rules). Prior to SBML Level 3 Version 2, getId() would always return an empty string, and isSetId() would always return false for objects of these classes.
With the addition of 'id' and 'name' attributes on SBase in Level 3 Version 2, it became necessary to introduce a new way to interact with the attributes more consistently in libSBML to avoid breaking backward compatibility in the behavior of the original 'id' methods. For this reason, libSBML provides four functions (getIdAttribute(), setIdAttribute(), isSetIdAttribute(), and unsetIdAttribute()) that always act on the actual 'id' attribute inherited from SBase, regardless of the object's type. These new methods should be used instead of the older getId()/setId()/etc. methods unless the old behavior is somehow necessary. Regardless of the Level and Version of the SBML, these functions allow client applications to use more generalized code in some situations (for instance, when manipulating objects that are all known to have identifiers). If the object in question does not posess an 'id' attribute according to the SBML specification for the Level and Version in use, libSBML will not allow the identifier to be set, nor will it read or write 'id' attributes for those objects.
| bool libsbmlcs.Objective.getIsSetListOfFluxObjectives | ( | ) |
|
inherited |
Returns the SBML Level of the SBMLDocument object containing this 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 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.)
|
inherited |
Returns the line number where this object first appears in the XML representation of the SBML document.
0.
|
inherited |
|
inherited |
|
inherited |
|
inherited |
| ListOfFluxObjectives libsbmlcs.Objective.getListOfFluxObjectives | ( | ) |
Returns the ListOfFluxObjectives in this Objective object.
|
inherited |
Returns 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. The latter point is important, because the uniqueness criterion applies across any attribute with type ID anywhere in the file, 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 the XML ID type. Although SBML itself specifies the use of XML ID only for the 'metaid' attribute, SBML-compatible applications 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. Finally, note that LibSBML does not provide an explicit XML ID data type; it uses ordinary character strings, which is easier for applications to support.
|
inherited |
|
inherited |
Returns the ModelHistory object, if any, attached to this object.
null if none exist.| new string libsbmlcs.Objective.getName | ( | ) |
Returns the value of the 'name' attribute of this Objective object.
In SBML Level 3 Version 2, the 'id' and 'name' attributes were moved to SBase directly, instead of being defined individually for many (but not all) objects. LibSBML has for a long time provided functions defined on SBase itself to get, set, and unset those attributes, which would fail or otherwise return empty strings if executed on any object for which those attributes were not defined. Now that all SBase objects define those attributes, those functions now succeed for any object with the appropriate level and version.
The 'name' attribute is optional and is not intended to be used for cross-referencing purposes within a model. Its purpose instead is to provide a human-readable label for the component. The data type of 'name' is the type string defined in XML Schema. SBML imposes no restrictions as to the content of 'name' attributes beyond those restrictions defined by the string type in XML Schema.
The recommended practice for handling 'name' is as follows. If a software tool has the capability for displaying the content of 'name' attributes, it should display this content to the user as a component's label instead of the component's 'id'. If the user interface does not have this capability (e.g., because it cannot display or use special characters in symbol names), or if the 'name' attribute is missing on a given component, then the user interface should display the value of the 'id' attribute instead. (Script language interpreters are especially likely to display 'id' instead of 'name'.)
As a consequence of the above, authors of systems that automatically generate the values of 'id' attributes should be aware some systems may display the 'id''s to the user. Authors therefore may wish to take some care to have their software create 'id' values that are: (a) reasonably easy for humans to type and read; and (b) likely to be meaningful, for example by making the 'id' attribute be an abbreviated form of the name attribute value.
An additional point worth mentioning is although there are restrictions on the uniqueness of 'id' values, there are no restrictions on the uniqueness of 'name' values in a model. This allows software applications leeway in assigning component identifiers.
Regardless of the level and version of the SBML, these functions allow client applications to use more generalized code in some situations (for instance, when manipulating objects that are all known to have names). If the object in question does not posess a 'name' attribute according to the SBML specification for the Level and Version in use, libSBML will not allow the name to be set, nor will it read or write 'name' attributes for those objects.
|
inherited |
Returns a list of the XML Namespaces declared on the SBML document owning this object.
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.
null in certain very usual circumstances where a namespace is not set.
|
inherited |
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 (and in SBML Level 3, the 'message' subelement of Constraint), 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 conform to the definition of XHTML 1.0. However, the content cannot be entirely free-form; it must satisfy certain requirements defined in the SBML specifications for specific SBML Levels. To help verify the formatting of 'notes' content, libSBML provides the static utility method SyntaxChecker::hasExpectedXHTMLSyntax(); this method implements a verification process that lets callers check whether the content of a given XMLNode object conforms to the SBML requirements for 'notes' and 'message' structure. Developers are urged to consult the appropriate SBML specification document for the Level and Version of their model for more in-depth explanations of using 'notes' in SBML. 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 |
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 (and in SBML Level 3, the 'message' subelement of Constraint), 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 conform to the definition of XHTML 1.0. However, the content cannot be entirely free-form; it must satisfy certain requirements defined in the SBML specifications for specific SBML Levels. To help verify the formatting of 'notes' content, libSBML provides the static utility method SyntaxChecker::hasExpectedXHTMLSyntax(); this method implements a verification process that lets callers check whether the content of a given XMLNode object conforms to the SBML requirements for 'notes' and 'message' structure. Developers are urged to consult the appropriate SBML specification document for the Level and Version of their model for more in-depth explanations of using 'notes' in SBML. 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 |
Returns the number of CVTerm objects in the annotations of this SBML object.
|
inherited |
Returns the number of disabled plug-in objects (extension interfaces) for SBML Level 3 package extensions known.
SBML Level 3 consists of a Core definition that can be extended via optional SBML Level 3 packages. A given model may indicate that it uses one or more SBML packages, and likewise, a software tool may be able to support one or more packages. LibSBML does not come preconfigured with all possible packages included and enabled, in part because not all package specifications have been finalized. To support the ability for software systems to enable support for the Level 3 packages they choose, libSBML features a plug-in mechanism. Each SBML Level 3 package is implemented in a separate code plug-in that can be enabled by the application to support working with that SBML package. A given SBML model may thus contain not only objects defined by SBML Level 3 Core, but also objects created by libSBML plug-ins supporting additional Level 3 packages.
If a plugin is disabled, the package information it contains is no longer considered to be part of the SBML document for the purposes of searching the document or writing out the document. However, the information is still retained, so if the plugin is enabled again, the same information will once again be available, and will be written out to the final model.
| long libsbmlcs.Objective.getNumFluxObjectives | ( | ) |
Get the number of FluxObjective objects in this Objective.
|
inherited |
Returns the number of plug-in objects (extenstion interfaces) for SBML Level 3 package extensions known.
SBML Level 3 consists of a Core definition that can be extended via optional SBML Level 3 packages. A given model may indicate that it uses one or more SBML packages, and likewise, a software tool may be able to support one or more packages. LibSBML does not come preconfigured with all possible packages included and enabled, in part because not all package specifications have been finalized. To support the ability for software systems to enable support for the Level 3 packages they choose, libSBML features a plug-in mechanism. Each SBML Level 3 package is implemented in a separate code plug-in that can be enabled by the application to support working with that SBML package. A given SBML model may thus contain not only objects defined by SBML Level 3 Core, but also objects created by libSBML plug-ins supporting additional Level 3 packages.
| new int libsbmlcs.Objective.getObjectiveType | ( | ) |
|
inherited |
Returns the SBML Core Version within the SBML Level of the actual 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 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.)
|
inherited |
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 |
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 |
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 |
Returns a plug-in object (extension interface) for an SBML Level 3 package extension with the given package name or URI.
The returned plug-in will be the appropriate type of plugin requested: calling Model::getPlugin('fbc') will return an FbcModelPlugin; calling Parameter::getPlugin('comp') will return CompSBasePlugin, etc.
If no such plugin exists, null is returned.
SBML Level 3 consists of a Core definition that can be extended via optional SBML Level 3 packages. A given model may indicate that it uses one or more SBML packages, and likewise, a software tool may be able to support one or more packages. LibSBML does not come preconfigured with all possible packages included and enabled, in part because not all package specifications have been finalized. To support the ability for software systems to enable support for the Level 3 packages they choose, libSBML features a plug-in mechanism. Each SBML Level 3 package is implemented in a separate code plug-in that can be enabled by the application to support working with that SBML package. A given SBML model may thus contain not only objects defined by SBML Level 3 Core, but also objects created by libSBML plug-ins supporting additional Level 3 packages.
| package | the name or URI of the package. |
|
inherited |
Returns the nth plug-in object (extension interface) for an SBML Level 3 package extension.
The returned plug-in will be the appropriate type of plugin requested: calling Model::getPlugin('fbc') will return an FbcModelPlugin; calling Parameter::getPlugin('comp') will return CompSBasePlugin, etc.
If no such plugin exists, null is returned.
SBML Level 3 consists of a Core definition that can be extended via optional SBML Level 3 packages. A given model may indicate that it uses one or more SBML packages, and likewise, a software tool may be able to support one or more packages. LibSBML does not come preconfigured with all possible packages included and enabled, in part because not all package specifications have been finalized. To support the ability for software systems to enable support for the Level 3 packages they choose, libSBML features a plug-in mechanism. Each SBML Level 3 package is implemented in a separate code plug-in that can be enabled by the application to support working with that SBML package. A given SBML model may thus contain not only objects defined by SBML Level 3 Core, but also objects created by libSBML plug-ins supporting additional Level 3 packages.
| n | the index of the plug-in to return. |
n is invalid, null is returned.
|
inherited |
Returns the XML namespace prefix of this element.
This reports the XML namespace prefix chosen for this class of object in the current SBML document. This may be an empty string if the component has no explicit prefix (for instance, if it is a core SBML object placed in the default SBML namespace of the document). If it is not empty, then it corresponds to the XML namespace prefix used set the object, whatever that may be in a given SBML document.
|
inherited |
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 names begin with BQB_ in 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 |
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 BQB_ 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 names begin with BQB_ in the interface class libsbml.
| resource | string representing the resource; e.g., 'http://www.geneontology.org/#GO:0005892'. |
BQM_ constants defined in libsbml may be expanded in later libSBML releases, to match the values defined by MIRIAM at that later time.
|
inherited |
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 |
Returns the integer portion of the value of the 'sboTerm' attribute of this object.
Beginning with SBML Level 2 Version 2, 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'. More details can be found in SBML specifications for Level 2 Version 2 and above.
-1 if the value is not set.
|
inherited |
Returns the 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'. More details can be found in SBML specifications for Level 2 Version 2 and above.
|
inherited |
Returns the string representation of the 'sboTerm' attribute of this object.
Beginning with SBML Level 2 Version 2, 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'. More details can be found in SBML specifications for Level 2 Version 2 and above.
| string libsbmlcs.Objective.getType | ( | ) |
| new int libsbmlcs.Objective.getTypeCode | ( | ) |
Returns the libSBML type code for this SBML object.
LibSBML attaches an identifying code to every kind of SBML object. These are integer constants known as SBML type codes. The names of all the codes begin with the characters SBML_. In the C# language interface for libSBML, the type codes are defined as static integer constants in the interface class libsbmlcs.libsbml.Note that different Level 3 package plug-ins may use overlapping type codes; to identify the package to which a given object belongs, call the SBase::getPackageName() method on the object.
The exception to this is lists: all SBML-style list elements have the type SBML_LIST_OF, regardless of what package they are from.
|
inherited |
Gets the namespace URI to which this element belongs to.
For example, all elements that belong to SBML Level 3 Version 1 Core must would have the URI 'http://www.sbml.org/sbml/level3/version1/core'; all elements that belong to Layout Extension Version 1 for SBML Level 3 Version 1 Core must would have the URI 'http://www.sbml.org/sbml/level3/version1/layout/version1'.
This function first returns the URI for this element by looking into the SBMLNamespaces object of the document with the its package name. If not found, it will then look for the namespace associated with the element itself.
|
inherited |
Returns the Version within the SBML Level of the SBMLDocument object containing this 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 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.)
| new bool libsbmlcs.Objective.hasRequiredAttributes | ( | ) |
| new bool libsbmlcs.Objective.hasRequiredElements | ( | ) |
Predicate returning true if all the required elements for this Objective object have been set.
|
inherited |
Predicate returning true if 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:
http://www.sbml.org/sbml/level1" http://www.sbml.org/sbml/level2" http://www.sbml.org/sbml/level2/version2" http://www.sbml.org/sbml/level2/version3" http://www.sbml.org/sbml/level2/version4" http://www.sbml.org/sbml/level2/version5" http://www.sbml.org/sbml/level3/version1/core" http://www.sbml.org/sbml/level3/version2/core" true if the level, version and namespace values of this SBML object correspond to a valid set of values, false otherwise.
|
inherited |
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 |
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 |
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 |
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 |
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.| new bool libsbmlcs.Objective.isSetId | ( | ) |
Predicate returning true if this Objective's 'id' attribute is set.
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 SId or a type derived from that, such as UnitSId, depending on the object in question. All data types are defined as follows:
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. This applies to all uses of SId, SIdRef, and derived types.
Users need to be aware of some important API issues that are the result of the history of SBML and libSBML. Prior to SBML Level 3 Version 2, SBML defined 'id' and 'name' attributes on only a subset of SBML objects. To simplify the work of programmers, libSBML's API provided get, set, check, and unset on the SBase object class itself instead of on individual subobject classes. This made the get/set/etc. methods uniformly available on all objects in the libSBML API. LibSBML simply returned empty strings or otherwise did not act when the methods were applied to SBML objects that were not defined by the SBML specification to have 'id' or 'name' attributes. Additional complications arose with the rule and assignment objects: InitialAssignment, EventAssignment, AssignmentRule, and RateRule. In early versions of SBML, the rule object hierarchy was different, and in addition, then as now, they possess different attributes: 'variable' (for the rules and event assignments), 'symbol' (for initial assignments), or neither (for algebraic rules). Prior to SBML Level 3 Version 2, getId() would always return an empty string, and isSetId() would always return false for objects of these classes.
With the addition of 'id' and 'name' attributes on SBase in Level 3 Version 2, it became necessary to introduce a new way to interact with the attributes more consistently in libSBML to avoid breaking backward compatibility in the behavior of the original 'id' methods. For this reason, libSBML provides four functions (getIdAttribute(), setIdAttribute(), isSetIdAttribute(), and unsetIdAttribute()) that always act on the actual 'id' attribute inherited from SBase, regardless of the object's type. These new methods should be used instead of the older getId()/setId()/etc. methods unless the old behavior is somehow necessary. Regardless of the Level and Version of the SBML, these functions allow client applications to use more generalized code in some situations (for instance, when manipulating objects that are all known to have identifiers). If the object in question does not posess an 'id' attribute according to the SBML specification for the Level and Version in use, libSBML will not allow the identifier to be set, nor will it read or write 'id' attributes for those objects.
true if the 'id' attribute of this SBML object is set, false otherwise.
|
inherited |
Predicate returning true if this object's 'id' attribute is set.
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 SId or a type derived from that, such as UnitSId, depending on the object in question. All data types are defined as follows:
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. This applies to all uses of SId, SIdRef, and derived types.
Users need to be aware of some important API issues that are the result of the history of SBML and libSBML. Prior to SBML Level 3 Version 2, SBML defined 'id' and 'name' attributes on only a subset of SBML objects. To simplify the work of programmers, libSBML's API provided get, set, check, and unset on the SBase object class itself instead of on individual subobject classes. This made the get/set/etc. methods uniformly available on all objects in the libSBML API. LibSBML simply returned empty strings or otherwise did not act when the methods were applied to SBML objects that were not defined by the SBML specification to have 'id' or 'name' attributes. Additional complications arose with the rule and assignment objects: InitialAssignment, EventAssignment, AssignmentRule, and RateRule. In early versions of SBML, the rule object hierarchy was different, and in addition, then as now, they possess different attributes: 'variable' (for the rules and event assignments), 'symbol' (for initial assignments), or neither (for algebraic rules). Prior to SBML Level 3 Version 2, getId() would always return an empty string, and isSetId() would always return false for objects of these classes.
With the addition of 'id' and 'name' attributes on SBase in Level 3 Version 2, it became necessary to introduce a new way to interact with the attributes more consistently in libSBML to avoid breaking backward compatibility in the behavior of the original 'id' methods. For this reason, libSBML provides four functions (getIdAttribute(), setIdAttribute(), isSetIdAttribute(), and unsetIdAttribute()) that always act on the actual 'id' attribute inherited from SBase, regardless of the object's type. These new methods should be used instead of the older getId()/setId()/etc. methods unless the old behavior is somehow necessary. Regardless of the Level and Version of the SBML, these functions allow client applications to use more generalized code in some situations (for instance, when manipulating objects that are all known to have identifiers). If the object in question does not posess an 'id' attribute according to the SBML specification for the Level and Version in use, libSBML will not allow the identifier to be set, nor will it read or write 'id' attributes for those objects.
true if the 'id' attribute of this SBML object is set, false otherwise.
|
inherited |
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. The latter point is important, because the uniqueness criterion applies across any attribute with type ID anywhere in the file, 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 the XML ID type. Although SBML itself specifies the use of XML ID only for the 'metaid' attribute, SBML-compatible applications 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. Finally, note that LibSBML does not provide an explicit XML ID data type; it uses ordinary character strings, which is easier for applications to support.
true if the 'metaid' attribute of this SBML object is set, false otherwise.
|
inherited |
Predicate returning true if this object has a ModelHistory object attached to it.
true if the ModelHistory of this object is set, false otherwise.| new bool libsbmlcs.Objective.isSetName | ( | ) |
Predicate returning true if this Objective's 'name' attribute is set.
In SBML Level 3 Version 2, the 'id' and 'name' attributes were moved to SBase directly, instead of being defined individually for many (but not all) objects. LibSBML has for a long time provided functions defined on SBase itself to get, set, and unset those attributes, which would fail or otherwise return empty strings if executed on any object for which those attributes were not defined. Now that all SBase objects define those attributes, those functions now succeed for any object with the appropriate level and version.
The 'name' attribute is optional and is not intended to be used for cross-referencing purposes within a model. Its purpose instead is to provide a human-readable label for the component. The data type of 'name' is the type string defined in XML Schema. SBML imposes no restrictions as to the content of 'name' attributes beyond those restrictions defined by the string type in XML Schema.
The recommended practice for handling 'name' is as follows. If a software tool has the capability for displaying the content of 'name' attributes, it should display this content to the user as a component's label instead of the component's 'id'. If the user interface does not have this capability (e.g., because it cannot display or use special characters in symbol names), or if the 'name' attribute is missing on a given component, then the user interface should display the value of the 'id' attribute instead. (Script language interpreters are especially likely to display 'id' instead of 'name'.)
As a consequence of the above, authors of systems that automatically generate the values of 'id' attributes should be aware some systems may display the 'id''s to the user. Authors therefore may wish to take some care to have their software create 'id' values that are: (a) reasonably easy for humans to type and read; and (b) likely to be meaningful, for example by making the 'id' attribute be an abbreviated form of the name attribute value.
An additional point worth mentioning is although there are restrictions on the uniqueness of 'id' values, there are no restrictions on the uniqueness of 'name' values in a model. This allows software applications leeway in assigning component identifiers.
Regardless of the level and version of the SBML, these functions allow client applications to use more generalized code in some situations (for instance, when manipulating objects that are all known to have names). If the object in question does not posess a 'name' attribute according to the SBML specification for the Level and Version in use, libSBML will not allow the name to be set, nor will it read or write 'name' attributes for those objects.
true if the 'name' attribute of this SBML object is set, false otherwise.
|
inherited |
Predicate returning true if this object's 'notes' subelement exists and has content.
The optional SBML element named 'notes', present on every major SBML component type, is intended as a place for storing optional information intended to be seen by humans. An example use of the 'notes' element would be to contain formatted user comments about the model element in which the 'notes' element is enclosed. Every object derived directly or indirectly from type SBase can have a separate value for 'notes', allowing users considerable freedom when adding comments to their models.
The format of 'notes' elements must be XHTML 1.0. To help verify the formatting of 'notes' content, libSBML provides the static utility method SyntaxChecker::hasExpectedXHTMLSyntax(); however, readers are urged to consult the appropriate SBML specification document for the Level and Version of their model for more in-depth explanations. The SBML Level 2 and 3 specifications have considerable detail about how 'notes' element content must be structured.
true if a 'notes' subelement exists, false otherwise.
|
inherited |
Predicate returning true if this object's 'sboTerm' attribute is set.
true if the 'sboTerm' attribute of this SBML object is set, false otherwise. | new bool libsbmlcs.Objective.isSetType | ( | ) |
|
inherited |
Predicate returning true or false depending on whether the user data of this element has been set.
The user data associated with an SBML object can be used by an application developer to attach custom information to that object in the model. In case of a deep copy, this data will passed as-is. The data attribute will never be interpreted by libSBML.
true if this object's user data has been set, false otherwise.
|
inherited |
Returns true if this object's set of XML namespaces are a subset of the given object's XML namespaces.
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. A common approach to using libSBML's SBMLNamespaces facilities is to create an SBMLNamespaces object somewhere in a program once, then hand that object as needed to object constructors that accept SBMLNamespaces as arguments.
| 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 |
Returns true if this object's set of XML namespaces are the same as the given object's XML namespaces.
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. A common approach to using libSBML's SBMLNamespaces facilities is to create an SBMLNamespaces object somewhere in a program once, then hand that object as needed to object constructors that accept SBMLNamespaces as arguments.
| 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. | FluxObjective libsbmlcs.Objective.removeFluxObjective | ( | long | n | ) |
Removes the nth FluxObjective from the ListOfFluxObjectives.
The caller owns the returned item and is responsible for deleting it.
| n | the index of the FluxObjective to remove. |
| FluxObjective libsbmlcs.Objective.removeFluxObjective | ( | string | sid | ) |
Removes the FluxObjective with the given identifier from the ListOfFluxObjectives.
The caller owns the returned item and is responsible for deleting it. If none of the items in this list have the identifier sid, then null is returned.
| sid | the identifier of the FluxObjective to remove. |
|
inherited |
Removes this object from its parent.
If the parent was storing this object as a pointer, it is deleted. If not, it is simply cleared (as in ListOf objects). This is a pure virtual method, 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.
|
inherited |
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. |
| removeEmpty | if after removing of the element, the annotation is empty, and the removeEmpty argument is true, the annotation node will be deleted (default). |
|
inherited |
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. |
| removeEmpty | if after removing of the element, the annotation is empty, and the removeEmpty argument is true, the annotation node will be deleted (default). |
|
inherited |
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. |
| removeEmpty | if after removing of the element, the annotation is empty, and the removeEmpty argument is true, the annotation node will be deleted (default). |
|
inherited |
Replaces all uses of a given meta identifier attribute value with another value.
In SBML, object 'meta' identifiers are of the XML data type ID; the SBML object attribute itself is typically named metaid. All attributes that hold values referring to values of type ID are of the XML data type IDREF. They are also sometimes informally referred to as 'metaid refs', in analogy to the SBML-defined type SIdRef.
This method works by looking at all meta-identifier attribute values, comparing the identifiers to the value of oldid. If any matches are found, the matching identifiers are replaced with newid. The method does not descend into child elements.
| oldid | the old identifier. |
| newid | the new identifier. |
|
inherited |
Replaces all uses of a given SIdRef type attribute value with another value.
In SBML, object identifiers are of a data type called SId. In SBML Level 3, an explicit data type called SIdRef was introduced for attribute values that refer to SId values; in previous Levels of SBML, this data type did not exist and attributes were simply described to as 'referring to an identifier', but the effective data type was the same as SIdRef in Level 3. These and other methods of libSBML refer to the type SIdRef for all Levels of SBML, even if the corresponding SBML specification did not explicitly name the data type.
This method works by looking at all attributes and (if appropriate) mathematical formulas in MathML content, comparing the referenced identifiers to the value of oldid. If any matches are found, the matching values are replaced with newid. The method does not descend into child elements.
| oldid | the old identifier. |
| newid | the new identifier. |
|
inherited |
Replaces all uses of a given UnitSIdRef type attribute value with another value.
In SBML, unit definitions have identifiers of type UnitSId. In SBML Level 3, an explicit data type called UnitSIdRef was introduced for attribute values that refer to UnitSId values; in previous Levels of SBML, this data type did not exist and attributes were simply described to as 'referring to a unit identifier', but the effective data type was the same as UnitSIdRef in Level 3. These and other methods of libSBML refer to the type UnitSIdRef for all Levels of SBML, even if the corresponding SBML specification did not explicitly name the data type.
This method works by looking at all unit identifier attribute values (including, if appropriate, inside mathematical formulas), comparing the referenced unit identifiers to the value of oldid. If any matches are found, the matching values are replaced with newid. The method does not descend into child elements.
| oldid | the old identifier. |
| newid | the new identifier. |
|
inherited |
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) followed by calling 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. |
|
inherited |
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) followed by calling 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 |
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(XMLNode annotation) or SBase::appendAnnotation(string annotation).
| annotation | an XML structure that is to be used as the new content of the 'annotation' subelement of this object. |
|
inherited |
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(XMLNode annotation) or SBase::appendAnnotation(string annotation).
| annotation | an XML string that is to be used as the content of the 'annotation' subelement of this object. |
| new int libsbmlcs.Objective.setId | ( | string | sid | ) |
Sets the value of the 'id' attribute of this Objective.
The string sid is copied.
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 SId or a type derived from that, such as UnitSId, depending on the object in question. All data types are defined as follows:
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. This applies to all uses of SId, SIdRef, and derived types.
Users need to be aware of some important API issues that are the result of the history of SBML and libSBML. Prior to SBML Level 3 Version 2, SBML defined 'id' and 'name' attributes on only a subset of SBML objects. To simplify the work of programmers, libSBML's API provided get, set, check, and unset on the SBase object class itself instead of on individual subobject classes. This made the get/set/etc. methods uniformly available on all objects in the libSBML API. LibSBML simply returned empty strings or otherwise did not act when the methods were applied to SBML objects that were not defined by the SBML specification to have 'id' or 'name' attributes. Additional complications arose with the rule and assignment objects: InitialAssignment, EventAssignment, AssignmentRule, and RateRule. In early versions of SBML, the rule object hierarchy was different, and in addition, then as now, they possess different attributes: 'variable' (for the rules and event assignments), 'symbol' (for initial assignments), or neither (for algebraic rules). Prior to SBML Level 3 Version 2, getId() would always return an empty string, and isSetId() would always return false for objects of these classes.
With the addition of 'id' and 'name' attributes on SBase in Level 3 Version 2, it became necessary to introduce a new way to interact with the attributes more consistently in libSBML to avoid breaking backward compatibility in the behavior of the original 'id' methods. For this reason, libSBML provides four functions (getIdAttribute(), setIdAttribute(), isSetIdAttribute(), and unsetIdAttribute()) that always act on the actual 'id' attribute inherited from SBase, regardless of the object's type. These new methods should be used instead of the older getId()/setId()/etc. methods unless the old behavior is somehow necessary. Regardless of the Level and Version of the SBML, these functions allow client applications to use more generalized code in some situations (for instance, when manipulating objects that are all known to have identifiers). If the object in question does not posess an 'id' attribute according to the SBML specification for the Level and Version in use, libSBML will not allow the identifier to be set, nor will it read or write 'id' attributes for those objects.
| sid | the string to use as the identifier of this object. |
|
inherited |
Sets the value of the 'id' attribute of this SBML object.
The string sid is copied.
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 SId or a type derived from that, such as UnitSId, depending on the object in question. All data types are defined as follows:
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. This applies to all uses of SId, SIdRef, and derived types.
Users need to be aware of some important API issues that are the result of the history of SBML and libSBML. Prior to SBML Level 3 Version 2, SBML defined 'id' and 'name' attributes on only a subset of SBML objects. To simplify the work of programmers, libSBML's API provided get, set, check, and unset on the SBase object class itself instead of on individual subobject classes. This made the get/set/etc. methods uniformly available on all objects in the libSBML API. LibSBML simply returned empty strings or otherwise did not act when the methods were applied to SBML objects that were not defined by the SBML specification to have 'id' or 'name' attributes. Additional complications arose with the rule and assignment objects: InitialAssignment, EventAssignment, AssignmentRule, and RateRule. In early versions of SBML, the rule object hierarchy was different, and in addition, then as now, they possess different attributes: 'variable' (for the rules and event assignments), 'symbol' (for initial assignments), or neither (for algebraic rules). Prior to SBML Level 3 Version 2, getId() would always return an empty string, and isSetId() would always return false for objects of these classes.
With the addition of 'id' and 'name' attributes on SBase in Level 3 Version 2, it became necessary to introduce a new way to interact with the attributes more consistently in libSBML to avoid breaking backward compatibility in the behavior of the original 'id' methods. For this reason, libSBML provides four functions (getIdAttribute(), setIdAttribute(), isSetIdAttribute(), and unsetIdAttribute()) that always act on the actual 'id' attribute inherited from SBase, regardless of the object's type. These new methods should be used instead of the older getId()/setId()/etc. methods unless the old behavior is somehow necessary. Regardless of the Level and Version of the SBML, these functions allow client applications to use more generalized code in some situations (for instance, when manipulating objects that are all known to have identifiers). If the object in question does not posess an 'id' attribute according to the SBML specification for the Level and Version in use, libSBML will not allow the identifier to be set, nor will it read or write 'id' attributes for those objects.
| sid | the string to use as the identifier of this object. |
|
inherited |
Sets the value of the meta-identifier 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. The latter point is important, because the uniqueness criterion applies across any attribute with type ID anywhere in the file, 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 the XML ID type. Although SBML itself specifies the use of XML ID only for the 'metaid' attribute, SBML-compatible applications 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. Finally, note that LibSBML does not provide an explicit XML ID data type; it uses ordinary character strings, which is easier for applications to support.
The string metaid is copied.
| metaid | the identifier string to use as the value of the 'metaid' attribute. |
|
inherited |
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. |
| new int libsbmlcs.Objective.setName | ( | string | name | ) |
Sets the value of the 'name' attribute of this Objective.
The string in name is copied.
| name | the new name for the SBML object. |
|
inherited |
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 |
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. |
|
inherited |
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. |
|
inherited |
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. |
|
inherited |
|
inherited |
Sets the value of the 'sboTerm' attribute.
Beginning with SBML Level 2 Version 2, 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'. More details can be found in SBML specifications for Level 2 Version 2 and above.
| value | the NNNNNNN integer portion of the SBO identifier. |
|
inherited |
Sets the value of the 'sboTerm' attribute by string.
Beginning with SBML Level 2 Version 2, 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'. More details can be found in SBML specifications for Level 2 Version 2 and above.
| int libsbmlcs.Objective.setType | ( | int | type | ) |
Sets the value of the 'type' attribute of this Objective.
The type must be a value from one of the constants whose names begin with OBJECTIVE_TYPE_.
| type | string value of the 'type' attribute to be set. Valid values include: |
| new int libsbmlcs.Objective.setType | ( | string | type | ) |
Sets the value of the 'type' attribute of this Objective.
| type | string value of the 'type' attribute to be set. Valid values include:
|
|
inherited |
Returns a string consisting of a partial SBML corresponding to just this object.
|
inherited |
|
inherited |
Unsets the value of the 'annotation' subelement of this SBML object.
Whereas the SBase 'notes' subelement is a container for content to be shown directly to humans, the 'annotation' element is a container for optional software-generated content not meant to be shown to humans. Every object derived from SBase can have its own value for 'annotation'. The element's content type is XML type 'any', allowing essentially arbitrary well-formed XML data content.
SBML places a few restrictions on the organization of the content of annotations; these are intended to help software tools read and write the data as well as help reduce conflicts between annotations added by different tools. Please see the SBML specifications for more details.
|
inherited |
Clears the list of CVTerm objects attached to this SBML object.
| new int libsbmlcs.Objective.unsetId | ( | ) |
Unsets the value of the 'id' attribute of this Objective.
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 SId or a type derived from that, such as UnitSId, depending on the object in question. All data types are defined as follows:
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. This applies to all uses of SId, SIdRef, and derived types.
Users need to be aware of some important API issues that are the result of the history of SBML and libSBML. Prior to SBML Level 3 Version 2, SBML defined 'id' and 'name' attributes on only a subset of SBML objects. To simplify the work of programmers, libSBML's API provided get, set, check, and unset on the SBase object class itself instead of on individual subobject classes. This made the get/set/etc. methods uniformly available on all objects in the libSBML API. LibSBML simply returned empty strings or otherwise did not act when the methods were applied to SBML objects that were not defined by the SBML specification to have 'id' or 'name' attributes. Additional complications arose with the rule and assignment objects: InitialAssignment, EventAssignment, AssignmentRule, and RateRule. In early versions of SBML, the rule object hierarchy was different, and in addition, then as now, they possess different attributes: 'variable' (for the rules and event assignments), 'symbol' (for initial assignments), or neither (for algebraic rules). Prior to SBML Level 3 Version 2, getId() would always return an empty string, and isSetId() would always return false for objects of these classes.
With the addition of 'id' and 'name' attributes on SBase in Level 3 Version 2, it became necessary to introduce a new way to interact with the attributes more consistently in libSBML to avoid breaking backward compatibility in the behavior of the original 'id' methods. For this reason, libSBML provides four functions (getIdAttribute(), setIdAttribute(), isSetIdAttribute(), and unsetIdAttribute()) that always act on the actual 'id' attribute inherited from SBase, regardless of the object's type. These new methods should be used instead of the older getId()/setId()/etc. methods unless the old behavior is somehow necessary. Regardless of the Level and Version of the SBML, these functions allow client applications to use more generalized code in some situations (for instance, when manipulating objects that are all known to have identifiers). If the object in question does not posess an 'id' attribute according to the SBML specification for the Level and Version in use, libSBML will not allow the identifier to be set, nor will it read or write 'id' attributes for those objects.
|
inherited |
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.
|
inherited |
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. The latter point is important, because the uniqueness criterion applies across any attribute with type ID anywhere in the file, 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 the XML ID type. Although SBML itself specifies the use of XML ID only for the 'metaid' attribute, SBML-compatible applications 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. Finally, note that LibSBML does not provide an explicit XML ID data type; it uses ordinary character strings, which is easier for applications to support.
|
inherited |
Unsets the ModelHistory object attached to this object.
| new int libsbmlcs.Objective.unsetName | ( | ) |
Unsets the value of the 'name' attribute of this Objective.
In SBML Level 3 Version 2, the 'id' and 'name' attributes were moved to SBase directly, instead of being defined individually for many (but not all) objects. LibSBML has for a long time provided functions defined on SBase itself to get, set, and unset those attributes, which would fail or otherwise return empty strings if executed on any object for which those attributes were not defined. Now that all SBase objects define those attributes, those functions now succeed for any object with the appropriate level and version.
The 'name' attribute is optional and is not intended to be used for cross-referencing purposes within a model. Its purpose instead is to provide a human-readable label for the component. The data type of 'name' is the type string defined in XML Schema. SBML imposes no restrictions as to the content of 'name' attributes beyond those restrictions defined by the string type in XML Schema.
The recommended practice for handling 'name' is as follows. If a software tool has the capability for displaying the content of 'name' attributes, it should display this content to the user as a component's label instead of the component's 'id'. If the user interface does not have this capability (e.g., because it cannot display or use special characters in symbol names), or if the 'name' attribute is missing on a given component, then the user interface should display the value of the 'id' attribute instead. (Script language interpreters are especially likely to display 'id' instead of 'name'.)
As a consequence of the above, authors of systems that automatically generate the values of 'id' attributes should be aware some systems may display the 'id''s to the user. Authors therefore may wish to take some care to have their software create 'id' values that are: (a) reasonably easy for humans to type and read; and (b) likely to be meaningful, for example by making the 'id' attribute be an abbreviated form of the name attribute value.
An additional point worth mentioning is although there are restrictions on the uniqueness of 'id' values, there are no restrictions on the uniqueness of 'name' values in a model. This allows software applications leeway in assigning component identifiers.
Regardless of the level and version of the SBML, these functions allow client applications to use more generalized code in some situations (for instance, when manipulating objects that are all known to have names). If the object in question does not posess a 'name' attribute according to the SBML specification for the Level and Version in use, libSBML will not allow the name to be set, nor will it read or write 'name' attributes for those objects.
|
inherited |
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 |
Unsets the value of the 'sboTerm' attribute of this SBML object.
| new int libsbmlcs.Objective.unsetType | ( | ) |
Unsets the value of the 'type' attribute of this Objective.
|
inherited |
Unsets the user data of this element.
The user data associated with an SBML object can be used by an application developer to attach custom information to that object in the model. In case of a deep copy, this data will passed as-is. The data attribute will never be interpreted by libSBML.
|
protectedinherited |