libSBML C++ API  5.18.0
Event Class Reference
Inheritance diagram for Event:
[legend]

Detailed Description

A discontinuous SBML event.

An SBML Event object defines when the event can occur, the variables that are affected by it, how the variables are affected, and the event's relationship to other events. The effect of the event can optionally be delayed after the occurrence of the condition which invokes it.

The operation of Event is divided into two phases (even when the event is not delayed): one when the event is triggered, and the other when the event is executed. Trigger objects define the conditions for triggering an event, Delay objects define when the event is actually executed, EventAssignment objects define the effects of executing the event, and (in SBML Level 3) Priority objects influence the order of EventAssignment performance in cases of simultaneous events. Please consult the descriptions of Trigger, Delay, EventAssignment and Priority for more information.

SBML Level/Version differences

SBML Level 2

In SBML Level 2 versions before Version 4, the semantics of Event time delays were defined such that the expressions in the event's assignments were always evaluated at the time the event was triggered. This definition made it difficult to define an event whose assignment formulas were meant to be evaluated at the time the event was executed (i.e., after the time period defined by the value of the Delay element, or after any other simultaneous event may have been executed and changed the model state). In SBML Level 2 Version 4 and in Level 3, the attribute "useValuesFromTriggerTime" on Event was added to allow a model to indicate the time at which the event's assignments are to be calculated, whether at the moment the event is triggered (if the value of the attribute is true), or at the moment of execution (if "useValuesFromTriggerTime"=false). If the event has a delay, the "useValuesFromTriggerTime" is likely to make a significant difference in the values used in the assignment, but the possibility of simultaneous events mean that even zero-delay events can have different results depending on the value of this attribute.

The definition of Event in SBML Level 2 Versions 1 and 2 includes an additional attribute called "timeUnits", which allowed the time units of the Delay to be set explicitly. Later Versions of SBML Level 2 as well as SBML Level 3 do not define this attribute. LibSBML supports this attribute for compatibility with previous versions of SBML Level 2; however, if a model in SBML Level 3 or Level 2 Versions 3–4 format sets the attribute, the consistency-checking method SBMLDocument::checkConsistency() will report an error.

The attribute "useValuesFromTriggerTime" was introduced in SBML Level 2 Version 4. Models defined in prior Versions of SBML Level 2 cannot use this attribute, and SBMLDocument::checkConsistency() will report an error if they do.

SBML Level 3

SBML Level 3 introduces several changes to the structure and components of Events compared to SBML Level 2. These changes fall into two main categories: changes to what is optional or required, and additions of new attributes and elements.

  • The attribute "useValuesFromTriggerTime" on Event is mandatory (it was optional in Level 2 and had a default value of true);
  • Event's "listOfEventAssignments" element (of class ListOfEventAssignments) is optional (it was mandatory in Level 2);
  • Event's "priority" element (of class Priority) is new in Level 3; and
  • The Trigger object gains new mandatory attributes (described as part of the definition of Trigger).
  • In SBML Level 3 Version 2, the Trigger object became optional. An Event with no Trigger will simply not fire.

The changes to the attributes of Event are described below; the changes to Trigger and Priority are described in their respective sections.

Semantics of events in SBML Level 3 Version 1

The detailed semantics of events are described in the specification documents for each SBML Level/Version. Here we include the description from the SBML Level 1 Version 1. Any transition of a Trigger object's "math" formula from the value false to true will cause the enclosing Event object to trigger. Such a transition is not possible at the very start of a simulation (i.e., at time t = 0) unless the Trigger object's "initialValue" attribute has a value of false; this defines the value of the trigger formula to be false immediately prior to the start of simulation, thereby giving it the potential to change in value from false to true when the formula is evaluated at t = 0. If "initialValue"=true, then the trigger expression cannot transition from false to true at t = 0 but may do so at some time t > 0.

Consider an Event object definition E with delay d in which the Trigger object's "math" formula makes a transition in value from false to true at times t1 and t2. The EventAssignment within the Event object will have effect at t1 + d and t2 + d irrespective of the relative times of t1 and t2. For example, events can "overlap" so that t1 < t2 < t1 + d still causes an event assignments to occur at t1 + d and t2 + d.

It is entirely possible for two events to be executed simultaneously, and it is possible for events to trigger other events (i.e., an event assignment can cause an event to trigger). This leads to several points:

  • A software package should retest all event triggers after executing an event assignment in order to account for the possibility that the assignment causes another event trigger to transition from false to true. This check should be made after each individual Event object's execution, even when several events are to be executed simultaneously.

  • Any Event object whose Trigger "persistent" attribute has the value false must have its trigger expression reevaluated continuously between when the event is triggered and when it is executed. If its trigger expression ever evaluates to false, it must be removed from the queue of events pending execution and treated as any other event whose trigger expression evaluates to false.

  • Although the precise time at which events are executed is not resolved beyond the given execution point in simulated time, it is assumed that the order in which the events occur is resolved. This order can be significant in determining the overall outcome of a given simulation. When an event X triggers another event Y and event Y has zero delay, then event Y is added to the existing set of simultaneous events that are pending execution. Events X and Y form a cascade of events at the same point in simulation time. An event such as Y may have a special priority if it contains a Priority subobject.

  • All events in a model are open to being in a cascade. The position of an event in the event queue does not affect whether it can be in the cascade: event Y can be triggered whether it is before or after X in the queue of events pending execution. A cascade of events can be potentially infinite (never terminate); when this occurs a simulator should indicate this has occurred—it is incorrect for a simulator to break a cascade arbitrarily and continue the simulation without at least indicating that the infinite cascade occurred.

  • Simultaneous events having no defined priorities are executed in an undefined order. This does not mean that the behavior of the simulation is completely undefined; merely that the order of execution of these particular events is undefined. A given simulator may use any algorithm to choose an order as long as every event is executed exactly once.

  • Events with defined priorities are executed in the order implied by their Priority "math" formula values, with events having higher priorities being executed ahead of events with lower priorities, and events with identical priorities being executed in a random order with respect to one another (as determined at run-time by some random algorithm equivalent to coin-flipping). Newly-triggered events that are to be executed immediately (i.e., if they define no delays) should be inserted into the queue of events pending execution according to their priorities: events with higher priority values value must be inserted ahead of events with lower priority values and after any pending events with even higher priorities, and inserted randomly among pending events with the same priority values. Events without Priority objects must be inserted into the queue in some fashion, but the algorithm used to place it in the queue is undefined. Similarly, there is no restriction on the order of a newly-inserted event with a defined Priority with respect to any other pending Event without a defined Priority.

  • A model variable that is the target of one or more event assignments can change more than once when simultaneous events are processed at some time point t. The model's behavior (output) for such a variable is the value of the variable at the end of processing all the simultaneous events at time t.

Restrictions relaxed in SBML Level 3 Version 2

In SBML Level 3 Version 2, several restrictions were lifted that have the potential to affect the semantics of an Event:

  • The Trigger subobject of an Event is optional. If missing, an Event is never triggered, unless an alternate triggering scheme is introduced by an SBML Level 3 package.

  • The "math" subelements of an Event Trigger, Delay, Priority, and EventAssignment are all optional. If any of these elements lack a "math" subelement, and that information is not supplied in an SBML Level 3 package, it is mathematically equivalent to the Trigger, Delay, Priority, or EventAssignment not being present at all.

  • The ListOfEventAssignments may be empty, which is mathematically equivalent to the Event not having a ListOfEventAssignments at all.

  • Any "math" subelement may return a Boolean or a numeric value in any context. If a numeric value is used in a Boolean context, a "0" is interpreted as false, and all other values are interpreted as true. If a Boolean value is used in a numeric context, a true is interpreted as a 1, and a false is interpreted as a 0. This means (for example) that a Trigger value that changes from 0.0 to anything else is equivalent to changing from false to true.
See also
Trigger
Priority
Delay
EventAssignment
Examples:
printAnnotation.cpp, printMath.cpp, printNotes.cpp, printUnits.cpp, unsetAnnotation.cpp, and unsetNotes.cpp.

Public Member Functions

int addCVTerm (CVTerm *term, bool newBag=false)
 Adds a copy of the given CVTerm object to this SBML object. More...
 
int addEventAssignment (const EventAssignment *ea)
 Appends a copy of the given EventAssignment to this Event. More...
 
virtual int appendAnnotation (const XMLNode *annotation)
 Appends the given annotation to the "annotation" subelement of this object. More...
 
virtual int appendAnnotation (const std::string &annotation)
 Appends the given annotation to the "annotation" subelement of this object. More...
 
int appendNotes (const XMLNode *notes)
 Appends the given notes to the "notes" subelement of this object. More...
 
int appendNotes (const std::string &notes)
 Appends the given notes to the "notes" subelement of this object. More...
 
virtual Eventclone () const
 Creates and returns a deep copy of this Event object. More...
 
DelaycreateDelay ()
 Creates a new, empty Delay, adds it to this Event and returns the Delay. More...
 
EventAssignmentcreateEventAssignment ()
 Creates a new, empty EventAssignment, adds it to this Event's list of event assignments and returns the EventAssignment. More...
 
PrioritycreatePriority ()
 (SBML Level 3 only) Creates a new, empty Priority, adds it to this Event and returns the Priority. More...
 
TriggercreateTrigger ()
 Creates a new, empty Trigger, adds it to this Event and returns the Trigger. More...
 
void deleteDisabledPlugins (bool recursive=true)
 Deletes all information stored in disabled plugins. More...
 
int disablePackage (const std::string &pkgURI, const std::string &pkgPrefix)
 Disables the given SBML Level 3 package on this object. More...
 
int enablePackage (const std::string &pkgURI, const std::string &pkgPrefix, bool flag)
 Enables or disables the given SBML Level 3 package on this object. More...
 
 Event (unsigned int level, unsigned int version)
 Creates a new Event using the given SBML level and version values. More...
 
 Event (SBMLNamespaces *sbmlns)
 Creates a new Event using the given SBMLNamespaces object sbmlns. More...
 
 Event (const Event &orig)
 Copy constructor; creates a copy of this Event. More...
 
virtual ListgetAllElements (ElementFilter *filter=NULL)
 Returns a List of all child SBase objects, including those nested to an arbitrary depth. More...
 
virtual ListgetAllElementsFromPlugins (ElementFilter *filter=NULL)
 Returns a List of all child SBase objects contained in SBML package plug-ins. More...
 
SBasegetAncestorOfType (int type, const std::string &pkgName="core")
 Returns the first ancestor object that has the given SBML type code from the given package. More...
 
const SBasegetAncestorOfType (int type, const std::string pkgName="core") const
 Returns the first ancestor object that has the given SBML type code from the given package. More...
 
XMLNodegetAnnotation ()
 Returns the content of the "annotation" subelement of this object as a tree of XMLNode objects. More...
 
XMLNodegetAnnotation () const
 Returns the content of the "annotation" subelement of this object as a tree of XMLNode objects. More...
 
std::string getAnnotationString ()
 Returns the content of the "annotation" subelement of this object as a character string. More...
 
std::string getAnnotationString () const
 Returns the content of the "annotation" subelement of this object as a character string. More...
 
unsigned int getColumn () const
 Returns the column number where this object first appears in the XML representation of the SBML document. More...
 
CVTermgetCVTerm (unsigned int n)
 Returns the nth CVTerm in the list of CVTerms of this SBML object. More...
 
ListgetCVTerms ()
 Returns a list of CVTerm objects in the annotations of this SBML object. More...
 
ListgetCVTerms () const
 Returns a list of CVTerm objects in the annotations of this SBML object. More...
 
const DelaygetDelay () const
 Get the assignment delay portion of this Event, if there is one. More...
 
DelaygetDelay ()
 Get the assignment delay portion of this Event, if there is one. More...
 
SBasePlugingetDisabledPlugin (unsigned int n)
 Returns the nth disabled plug-in object (extension interface) for an SBML Level 3 package extension. More...
 
const SBasePlugingetDisabledPlugin (unsigned int n) const
 Returns the nth disabled plug-in object (extension interface) for an SBML Level 3 package extension. More...
 
const SBasegetElementByMetaId (const std::string &metaid) const
 Returns the first child element it can find with a specific "metaid" attribute value, or NULL if no such object is found. More...
 
virtual SBasegetElementByMetaId (const std::string &metaid)
 Returns the first child element it can find with the given metaid, or NULL if no such object is found. More...
 
const SBasegetElementBySId (const std::string &id) const
 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...
 
virtual SBasegetElementBySId (const std::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...
 
virtual const std::string & getElementName () const
 Returns the XML element name of this object, which for Event, is always "event". More...
 
const EventAssignmentgetEventAssignment (unsigned int n) const
 Return a specific EventAssignment object of this Event. More...
 
EventAssignmentgetEventAssignment (unsigned int n)
 Return a specific EventAssignment object of this Event. More...
 
const EventAssignmentgetEventAssignment (const std::string &variable) const
 Return the event assignment indicated by the given variable. More...
 
EventAssignmentgetEventAssignment (const std::string &variable)
 Return the event assignment indicated by the given variable. More...
 
virtual const std::string & getId () const
 Returns the value of the "id" attribute of this Event. More...
 
const std::string & getIdAttribute () const
 Returns the value of the "id" attribute of this SBML object. More...
 
unsigned int getLevel () const
 Returns the SBML Level of the SBMLDocument object containing this object. More...
 
unsigned int getLine () const
 Returns the line number where this object first appears in the XML representation of the SBML document. More...
 
const ListOfEventAssignmentsgetListOfEventAssignments () const
 Returns the list of event assignments for this Event. More...
 
ListOfEventAssignmentsgetListOfEventAssignments ()
 Returns the list of event assignments for this Event. More...
 
const std::string & getMetaId () const
 Returns the value of the "metaid" attribute of this SBML object. More...
 
std::string & getMetaId ()
 Returns the value of the "metaid" attribute of this SBML object. More...
 
const ModelgetModel () const
 Returns the Model object for the SBML Document in which the current object is located. More...
 
ModelHistorygetModelHistory () const
 Returns the ModelHistory object, if any, attached to this object. More...
 
ModelHistorygetModelHistory ()
 Returns the ModelHistory object, if any, attached to this object. More...
 
virtual const std::string & getName () const
 Returns the value of the "name" attribute of this Event. More...
 
virtual XMLNamespacesgetNamespaces () const
 Returns a list of the XML Namespaces declared on the SBML document owning this object. More...
 
XMLNodegetNotes ()
 Returns the content of the "notes" subelement of this object as a tree of XMLNode objects. More...
 
XMLNodegetNotes () const
 Returns the content of the "notes" subelement of this object as a tree of XMLNode objects. More...
 
std::string getNotesString ()
 Returns the content of the "notes" subelement of this object as a string. More...
 
std::string getNotesString () const
 Returns the content of the "notes" subelement of this object as a string. More...
 
unsigned int getNumCVTerms ()
 Returns the number of CVTerm objects in the annotations of this SBML object. More...
 
unsigned int getNumDisabledPlugins () const
 Returns the number of disabled plug-in objects (extension interfaces) for SBML Level 3 package extensions known. More...
 
unsigned int getNumEventAssignments () const
 Returns the number of EventAssignment objects attached to this Event. More...
 
unsigned int getNumPlugins () const
 Returns the number of plug-in objects (extenstion interfaces) for SBML Level 3 package extensions known. More...
 
unsigned int getPackageCoreVersion () const
 Returns the SBML Core Version within the SBML Level of the actual object. More...
 
const std::string & getPackageName () const
 Returns the name of the SBML Level 3 package in which this element is defined. More...
 
unsigned int getPackageVersion () const
 Returns the Version of the SBML Level 3 package to which this element belongs to. More...
 
SBasegetParentSBMLObject ()
 Returns the parent SBML object containing this object. More...
 
const SBasegetParentSBMLObject () const
 Returns the parent SBML object containing this object. More...
 
SBasePlugingetPlugin (const std::string &package)
 Returns a plug-in object (extension interface) for an SBML Level 3 package extension with the given package name or URI. More...
 
const SBasePlugingetPlugin (const std::string &package) const
 Returns a plug-in object (extension interface) for an SBML Level 3 package extension with the given package name or URI. More...
 
SBasePlugingetPlugin (unsigned int n)
 Returns the nth plug-in object (extension interface) for an SBML Level 3 package extension. More...
 
const SBasePlugingetPlugin (unsigned int n) const
 Returns the nth plug-in object (extension interface) for an SBML Level 3 package extension. More...
 
std::string getPrefix () const
 Returns the XML namespace prefix of this element. More...
 
const PrioritygetPriority () const
 (SBML Level 3 only) Get the event priority portion of this Event. More...
 
PrioritygetPriority ()
 (SBML Level 3 only) Get the event priority portion of this Event. More...
 
BiolQualifierType_t getResourceBiologicalQualifier (std::string resource)
 Returns the MIRIAM biological qualifier associated with the given resource. More...
 
ModelQualifierType_t getResourceModelQualifier (std::string resource)
 Returns the MIRIAM model qualifier associated with the given resource. More...
 
const SBMLDocumentgetSBMLDocument () const
 Returns the SBMLDocument object containing this object instance. More...
 
SBMLDocumentgetSBMLDocument ()
 Returns the SBMLDocument object containing this object instance. More...
 
int getSBOTerm () const
 Returns the integer portion of the value of the "sboTerm" attribute of this object. More...
 
std::string getSBOTermAsURL () const
 Returns the URL representation of the "sboTerm" attribute of this object. More...
 
std::string getSBOTermID () const
 Returns the string representation of the "sboTerm" attribute of this object. More...
 
const std::string & getTimeUnits () const
 Get the value of the "timeUnits" attribute of this Event, if it has one. More...
 
const TriggergetTrigger () const
 Get the event trigger portion of this Event. More...
 
TriggergetTrigger ()
 Get the event trigger portion of this Event. More...
 
virtual int getTypeCode () const
 Returns the libSBML type code of this object instance. More...
 
std::string getURI () const
 Gets the namespace URI to which this element belongs to. More...
 
void * getUserData () const
 Returns the user data that has been previously set via setUserData(). More...
 
bool getUseValuesFromTriggerTime () const
 Get the value of the "useValuesFromTriggerTime" attribute of this Event. More...
 
unsigned int getVersion () const
 Returns the Version within the SBML Level of the SBMLDocument object containing this object. More...
 
virtual bool hasRequiredAttributes () const
 Predicate returning true if all the required attributes for this Event object have been set. More...
 
virtual bool hasRequiredElements () const
 Predicate returning true if all the required elements for this Event 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...
 
void initDefaults ()
 Initializes the fields of this Event object to "typical" default values. More...
 
bool isPackageEnabled (const std::string &pkgName) const
 Predicate returning true if the given SBML Level 3 package is enabled with this object. More...
 
bool isPackageURIEnabled (const std::string &pkgURI) const
 Predicate returning true if an SBML Level 3 package with the given URI is enabled with this object. More...
 
bool isPkgEnabled (const std::string &pkgName) const
 Predicate returning true if the given SBML Level 3 package is enabled with this object. More...
 
bool isPkgURIEnabled (const std::string &pkgURI) const
 Predicate returning true if an SBML Level 3 package with the given URI is enabled with this object. More...
 
bool isSetAnnotation () const
 Predicate returning true if this object's "annotation" subelement exists and has content. More...
 
bool isSetDelay () const
 Predicate for testing whether the delay for this Event is set. More...
 
virtual bool isSetId () const
 Predicate returning true if this Event's "id" attribute is set. More...
 
bool isSetIdAttribute () const
 Predicate returning true if this object's "id" attribute is set. More...
 
bool isSetMetaId () const
 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...
 
virtual bool isSetName () const
 Predicate returning true if this Event's "name" attribute is set. More...
 
bool isSetNotes () const
 Predicate returning true if this object's "notes" subelement exists and has content. More...
 
bool isSetPriority () const
 (SBML Level 3 only) Predicate for testing whether the priority for this Event is set. More...
 
bool isSetSBOTerm () const
 Predicate returning true if this object's "sboTerm" attribute is set. More...
 
bool isSetTimeUnits () const
 Predicate for testing whether the "timeUnits" attribute of this Event is set. More...
 
bool isSetTrigger () const
 Predicate for testing whether the trigger for this Event is set. More...
 
bool isSetUserData () const
 Predicate returning true or false depending on whether the user data of this element has been set. More...
 
bool isSetUseValuesFromTriggerTime () const
 Predicate for testing whether the "useValuesFromTriggerTime" attribute of this Event is set. More...
 
bool matchesRequiredSBMLNamespacesForAddition (const SBase *sb)
 Returns true if this object's set of XML namespaces are a subset of the given object's XML namespaces. More...
 
bool matchesRequiredSBMLNamespacesForAddition (const SBase *sb) const
 Returns true if this object's set of XML namespaces are a subset of the given object's XML namespaces. More...
 
bool matchesSBMLNamespaces (const SBase *sb)
 Returns true if this object's set of XML namespaces are the same as the given object's XML namespaces. More...
 
bool matchesSBMLNamespaces (const SBase *sb) const
 Returns true if this object's set of XML namespaces are the same as the given object's XML namespaces. More...
 
Eventoperator= (const Event &rhs)
 Assignment operator for Event. More...
 
void read (XMLNode &node, XMLErrorSeverityOverride_t flag=LIBSBML_OVERRIDE_DISABLED)
 Reads (initializes) this SBML object by reading from the given XMLNode. More...
 
EventAssignmentremoveEventAssignment (unsigned int n)
 Removes the nth EventAssignment object from this Event object and returns a pointer to it. More...
 
EventAssignmentremoveEventAssignment (const std::string &variable)
 Removes the EventAssignment object with the given "variable" attribute from this Event object and returns a pointer to it. More...
 
virtual int removeFromParentAndDelete ()
 Removes this object from its parent. More...
 
int removeTopLevelAnnotationElement (const std::string &elementName, const std::string elementURI="", bool removeEmpty=true)
 Removes the top-level element within the "annotation" subelement of this SBML object with the given name and optional URI. More...
 
virtual void renameMetaIdRefs (const std::string &oldid, const std::string &newid)
 Replaces all uses of a given meta identifier attribute value with another value. More...
 
virtual void renameSIdRefs (const std::string &oldid, const std::string &newid)
 Replaces all uses of a given SIdRef type attribute value with another value. More...
 
virtual void renameUnitSIdRefs (const std::string &oldid, const std::string &newid)
 Replaces all uses of a given UnitSIdRef type attribute value with another value. More...
 
int replaceTopLevelAnnotationElement (const 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 (const std::string &annotation)
 Replaces the given top-level element within the "annotation" subelement of this SBML object and with the annotation element supplied. More...
 
virtual int setAnnotation (const XMLNode *annotation)
 Sets the value of the "annotation" subelement of this SBML object. More...
 
virtual int setAnnotation (const std::string &annotation)
 Sets the value of the "annotation" subelement of this SBML object. More...
 
int setDelay (const Delay *delay)
 Sets the delay definition of this Event to a copy of the given Delay object instance. More...
 
virtual int setId (const std::string &sid)
 Sets the value of the "id" attribute of this Event. More...
 
virtual int setIdAttribute (const std::string &sid)
 Sets the value of the "id" attribute of this SBML object. More...
 
int setMetaId (const std::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...
 
virtual int setName (const std::string &name)
 Sets the value of the "name" attribute of this Event. More...
 
int setNamespaces (XMLNamespaces *xmlns)
 Sets the namespaces relevant of this SBML object. More...
 
int setNotes (const XMLNode *notes)
 Sets the value of the "notes" subelement of this SBML object. More...
 
int setNotes (const std::string &notes, bool addXHTMLMarkup=false)
 Sets the value of the "notes" subelement of this SBML object to a copy of the string notes. More...
 
int setPriority (const Priority *priority)
 (SBML Level 3 only) Sets the priority definition of this Event to a copy of the given Priority object instance. More...
 
virtual int setSBOTerm (int value)
 Sets the value of the "sboTerm" attribute. More...
 
virtual int setSBOTerm (const std::string &sboid)
 Sets the value of the "sboTerm" attribute by string. More...
 
int setTimeUnits (const std::string &sid)
 Sets the "timeUnits" attribute of this Event to a copy of sid. More...
 
int setTrigger (const Trigger *trigger)
 Sets the trigger definition of this Event to a copy of the given Trigger object instance. More...
 
int setUserData (void *userData)
 Sets the user data of this element. More...
 
int setUseValuesFromTriggerTime (bool value)
 Sets the "useValuesFromTriggerTime" attribute of this Event to a value. More...
 
char * toSBML ()
 Returns a string consisting of a partial SBML corresponding to just this object. More...
 
XMLNodetoXMLNode ()
 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...
 
int unsetDelay ()
 Unsets the Delay of this Event. More...
 
virtual int unsetId ()
 Unsets the value of the "id" attribute of this Event. 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...
 
virtual int unsetName ()
 Unsets the value of the "name" attribute of this Event. More...
 
int unsetNotes ()
 Unsets the value of the "notes" subelement of this SBML object. More...
 
int unsetPriority ()
 (SBML Level 3 only) Unsets the Priority of this Event. More...
 
int unsetSBOTerm ()
 Unsets the value of the "sboTerm" attribute of this SBML object. More...
 
int unsetTimeUnits ()
 Unsets the "timeUnits" attribute of this Event. More...
 
int unsetTrigger ()
 Unsets the Trigger of this Event. More...
 
int unsetUserData ()
 Unsets the user data of this element. More...
 
int unsetUseValuesFromTriggerTime ()
 Unsets the value of the "useValuesFromTriggerTime" attribute of this Event. More...
 
virtual ~Event ()
 Destroys this Event. More...
 

Protected Member Functions

virtual void setElementText (const std::string &text)
 When overridden allows SBase elements to use the text included in between the elements tags. More...
 

Constructor & Destructor Documentation

Event::Event ( unsigned int  level,
unsigned int  version 
)

Creates a new Event using the given SBML level and version values.

Parameters
levelan unsigned int, the SBML Level to assign to this Event.
versionan unsigned int, the SBML Version to assign to this Event.
Exceptions
SBMLConstructorExceptionThrown if the given level and version combination are invalid or if this object is incompatible with the given level and version.
Note
Attempting to add an object to an SBMLDocument having a different combination of SBML Level, Version and XML namespaces than the object itself will result in an error at the time a caller attempts to make the addition. A parent object must have compatible Level, Version and XML namespaces. (Strictly speaking, a parent may also have more XML namespaces than a child, but the reverse is not permitted.) The restriction is necessary to ensure that an SBML model has a consistent overall structure. This requires callers to manage their objects carefully, but the benefit is increased flexibility in how models can be created by permitting callers to create objects bottom-up if desired. In situations where objects are not yet attached to parents (e.g., SBMLDocument), knowledge of the intented SBML Level and Version help libSBML determine such things as whether it is valid to assign a particular value to an attribute.
Event::Event ( SBMLNamespaces sbmlns)

Creates a new Event using the given SBMLNamespaces object sbmlns.

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.
Parameters
sbmlnsan SBMLNamespaces object.
Exceptions
SBMLConstructorExceptionThrown if the given sbmlns is inconsistent or incompatible with this object.
Note
Attempting to add an object to an SBMLDocument having a different combination of SBML Level, Version and XML namespaces than the object itself will result in an error at the time a caller attempts to make the addition. A parent object must have compatible Level, Version and XML namespaces. (Strictly speaking, a parent may also have more XML namespaces than a child, but the reverse is not permitted.) The restriction is necessary to ensure that an SBML model has a consistent overall structure. This requires callers to manage their objects carefully, but the benefit is increased flexibility in how models can be created by permitting callers to create objects bottom-up if desired. In situations where objects are not yet attached to parents (e.g., SBMLDocument), knowledge of the intented SBML Level and Version help libSBML determine such things as whether it is valid to assign a particular value to an attribute.
Event::~Event ( )
virtual

Destroys this Event.

Event::Event ( const Event orig)

Copy constructor; creates a copy of this Event.

Parameters
origthe object to copy.

Member Function Documentation

int SBase::addCVTerm ( CVTerm term,
bool  newBag = false 
)
inherited

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

Parameters
termthe CVTerm to assign.
newBagif 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.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
Note
Since the CV Term uses the "metaid" attribute of the object as a reference, if the object has no "metaid" attribute value set, then the CVTerm will not be added.
This method should be used with some caution. The fact that this method copies the object passed to it means that the caller will be left holding a physically different object instance than the one contained inside this object. Changes made to the original object instance (such as resetting attribute values) will not affect the instance in this object. In addition, the caller should make sure to free the original object if it is no longer being used, or else a memory leak will result. Please see other methods on this class (particularly a corresponding method whose name begins with the word create) for alternatives that do not lead to these issues.
Examples:
addCVTerms.cpp, addingEvidenceCodes_1.cpp, and addingEvidenceCodes_2.cpp.
int Event::addEventAssignment ( const EventAssignment ea)

Appends a copy of the given EventAssignment to this Event.

Parameters
eathe EventAssignment object to add.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
Note
This method should be used with some caution. The fact that this method copies the object passed to it means that the caller will be left holding a physically different object instance than the one contained inside this object. Changes made to the original object instance (such as resetting attribute values) will not affect the instance in this object. In addition, the caller should make sure to free the original object if it is no longer being used, or else a memory leak will result. Please see other methods on this class (particularly a corresponding method whose name begins with the word create) for alternatives that do not lead to these issues.
See also
createEventAssignment()
int SBase::appendAnnotation ( const XMLNode annotation)
virtualinherited

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(const XMLNode* annotation) or SBase::setAnnotation(const std::string& annotation), this method allows other annotations to be preserved when an application adds its own data.

Parameters
annotationan XML structure that is to be copied and appended to the content of the "annotation" subelement of this object.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
See also
getAnnotationString()
isSetAnnotation()
setAnnotation(const XMLNode* annotation)
setAnnotation(const std::string& annotation)
appendAnnotation(const std::string& annotation)
unsetAnnotation()

Reimplemented in Model, and SpeciesReference.

Examples:
addingEvidenceCodes_2.cpp, and appendAnnotation.cpp.
int SBase::appendAnnotation ( const std::string &  annotation)
virtualinherited

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(const XMLNode* annotation) or SBase::setAnnotation(const std::string& annotation), this method allows other annotations to be preserved when an application adds its own data.

Parameters
annotationan XML string that is to be copied and appended to the content of the "annotation" subelement of this object.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
See also
getAnnotationString()
isSetAnnotation()
setAnnotation(const XMLNode* annotation)
setAnnotation(const std::string& annotation)
appendAnnotation(const XMLNode* annotation)
unsetAnnotation()

Reimplemented in Model, and SpeciesReference.

int SBase::appendNotes ( const XMLNode notes)
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.

Parameters
notesan XML node structure that is to appended to the content of the "notes" subelement of this object.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
See also
getNotesString()
isSetNotes()
setNotes(const XMLNode* notes)
setNotes(const std::string& notes, bool addXHTMLMarkup)
appendNotes(const std::string& notes)
unsetNotes()
SyntaxChecker::hasExpectedXHTMLSyntax()
int SBase::appendNotes ( const std::string &  notes)
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.

Parameters
notesan XML string that is to appended to the content of the "notes" subelement of this object.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
See also
getNotesString()
isSetNotes()
setNotes(const XMLNode* notes)
setNotes(const std::string& notes, bool addXHTMLMarkup)
appendNotes(const XMLNode* notes)
unsetNotes()
SyntaxChecker::hasExpectedXHTMLSyntax()
Event * Event::clone ( ) const
virtual

Creates and returns a deep copy of this Event object.

Returns
the (deep) copy of this Event object.

Implements SBase.

Delay * Event::createDelay ( )

Creates a new, empty Delay, adds it to this Event and returns the Delay.

Returns
the newly created Delay object instance.
EventAssignment * Event::createEventAssignment ( )

Creates a new, empty EventAssignment, adds it to this Event's list of event assignments and returns the EventAssignment.

Returns
the newly created EventAssignment object instance.
See also
addEventAssignment(const EventAssignment* ea)
Priority * Event::createPriority ( )

(SBML Level 3 only) Creates a new, empty Priority, adds it to this Event and returns the Priority.

Returns
the newly created Priority object instance, or NULL if the SBML level and version used for this Event does not define Priority children.
Note
The element "priority" is available in SBML Level 3, but is not present in lower Levels of SBML.
Trigger * Event::createTrigger ( )

Creates a new, empty Trigger, adds it to this Event and returns the Trigger.

Returns
the newly created Trigger object instance.
void SBase::deleteDisabledPlugins ( bool  recursive = true)
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.
Parameters
recursiveif true, the disabled information will be deleted also from all child elements, otherwise only from this SBase element.
See also
getNumDisabledPlugins()
int SBase::disablePackage ( const std::string &  pkgURI,
const std::string &  pkgPrefix 
)
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:

// We read in an SBML L3V1 model that uses the 'comp'
// package namespace.
doc = readSBML("sbml-file-with-comp-elements.xml");
// We extract one of the species from the model.
Species* s1 = doc->getModel()->getSpecies(0);
// We construct a new model. This model does not use the
// 'comp' package.
Model * newModel = new Model(3,1);
// The following will fail with an error, because addSpecies()
// will first check that the parent of the given object has
// namespaces declared, and will discover that s1 does but
// newModel does not.
// newModel->addSpecies(s1);
// However, if we disable the 'comp' package on s1, then
// the call to addSpecies will work.
s1->disablePackage("http://www.sbml.org/sbml/level3/version1/comp/version1",
"comp");
newModel->addSpecies(s1);
Parameters
pkgURIthe URI of the package.
pkgPrefixthe XML prefix of the package.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
See also
enablePackage(const std::string& pkgURI, const std::string& pkgPrefix, bool flag)
int SBase::enablePackage ( const std::string &  pkgURI,
const std::string &  pkgPrefix,
bool  flag 
)
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(const std::string& pkgURI, const std::string& pkgPrefix).

Parameters
pkgURIthe URI of the package.
pkgPrefixthe XML prefix of the package.
flagwhether to enable (true) or disable (false) the package.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
See also
disablePackage(const std::string& pkgURI, const std::string& pkgPrefix)
Examples:
addLayout.cpp.
List * Event::getAllElements ( ElementFilter filter = NULL)
virtual

Returns a List of all child SBase objects, including those nested to an arbitrary depth.

Parameters
filtera pointer to an ElementFilter, which causes the function to return only elements that match a particular set of constraints. If NULL (the default), the function will return all child objects.
Returns
a List of pointers to all children objects.

Reimplemented from SBase.

List * SBase::getAllElementsFromPlugins ( ElementFilter filter = NULL)
virtualinherited

Returns a List of all child SBase objects contained in SBML package plug-ins.

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.

This method walks down the list of all SBML Level 3 packages used by this object and returns all child objects defined by those packages.

Parameters
filtera pointer to an ElementFilter, which causes the function to return only elements that match a particular set of constraints. If NULL (the default), the function will return all child objects.
Returns
a pointer to a List of pointers to all children objects from plug-ins.
SBase * SBase::getAncestorOfType ( int  type,
const std::string &  pkgName = "core" 
)
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. The set of possible type codes is defined in the enumeration SBMLTypeCode_t. 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.

Parameters
typethe 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.
Returns
the ancestor SBML object of this SBML object that corresponds to the given SBMLTypeCode_t value, or NULL if no ancestor exists.
Warning
The optional argument 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.
const SBase * SBase::getAncestorOfType ( int  type,
const std::string  pkgName = "core" 
) const
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. The set of possible type codes is defined in the enumeration SBMLTypeCode_t. 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.

Parameters
typethe 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.
Returns
the ancestor SBML object of this SBML object that corresponds to the given SBMLTypeCode_t value, or NULL if no ancestor exists.
Warning
The optional argument 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.
XMLNode * SBase::getAnnotation ( )
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.

Returns
the annotation of this SBML object as a tree of XMLNode objects.
See also
getAnnotationString()
isSetAnnotation()
setAnnotation(const XMLNode* annotation)
setAnnotation(const std::string& annotation)
appendAnnotation(const XMLNode* annotation)
appendAnnotation(const std::string& annotation)
unsetAnnotation()
XMLNode * SBase::getAnnotation ( ) const
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.

Returns
the annotation of this SBML object as a tree of XMLNode objects.
See also
getAnnotationString()
isSetAnnotation()
setAnnotation(const XMLNode* annotation)
setAnnotation(const std::string& annotation)
appendAnnotation(const XMLNode* annotation)
appendAnnotation(const std::string& annotation)
unsetAnnotation()
std::string SBase::getAnnotationString ( )
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.

Returns
the annotation of this SBML object as a character string.
See also
getAnnotation()
isSetAnnotation()
setAnnotation(const XMLNode* annotation)
setAnnotation(const std::string& annotation)
appendAnnotation(const XMLNode* annotation)
appendAnnotation(const std::string& annotation)
unsetAnnotation()
Examples:
printAnnotation.cpp.
std::string SBase::getAnnotationString ( ) const
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.

Returns
the annotation of this SBML object as a character string.
See also
getAnnotation()
isSetAnnotation()
setAnnotation(const XMLNode* annotation)
setAnnotation(const std::string& annotation)
appendAnnotation(const XMLNode* annotation)
appendAnnotation(const std::string& annotation)
unsetAnnotation()
unsigned int SBase::getColumn ( ) const
inherited

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

Returns
the column number of this SBML object. If this object was created programmatically and not read from a file, this method will return the value 0.
Note
The column number for each construct in an SBML model is set upon reading the model. The accuracy of the column number depends on the correctness of the XML representation of the model, and on the particular XML parser library being used. The former limitation relates to the following problem: if the model is actually invalid XML, then the parser may not be able to interpret the data correctly and consequently may not be able to establish the real column number. The latter limitation is simply that different parsers seem to have their own accuracy limitations, and out of all the parsers supported by libSBML, none have been 100% accurate in all situations. (At this time, libSBML supports the use of libxml2, Expat and Xerces.)
See also
getLine()
CVTerm * SBase::getCVTerm ( unsigned int  n)
inherited

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

Parameters
nunsigned int the index of the CVTerm to retrieve.
Returns
the nth CVTerm in the list of CVTerms for this SBML object. If the index n is invalid, NULL is returned.
List * SBase::getCVTerms ( )
inherited

Returns a list of CVTerm objects in the annotations of this SBML object.

Returns
the list of CVTerms for this SBML object.
List * SBase::getCVTerms ( ) const
inherited

Returns a list of CVTerm objects in the annotations of this SBML object.

Returns
the list of CVTerms for this SBML object.
const Delay * Event::getDelay ( ) const

Get the assignment delay portion of this Event, if there is one.

Returns
the delay of this Event if one is defined, or NULL if none is defined.
Examples:
printAnnotation.cpp, printMath.cpp, printNotes.cpp, and printUnits.cpp.
Delay * Event::getDelay ( )

Get the assignment delay portion of this Event, if there is one.

Returns
the delay of this Event if one is defined, or NULL if none is defined.
SBasePlugin * SBase::getDisabledPlugin ( unsigned int  n)
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.
Parameters
nthe index of the disabled plug-in to return.
Returns
the nth disabled plug-in object (the libSBML extension interface) of a package extension. If the index n is invalid, NULL is returned.
See also
getNumDisabledPlugins()
getPlugin(const std::string& package)
const SBasePlugin * SBase::getDisabledPlugin ( unsigned int  n) const
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.
Parameters
nthe index of the disabled plug-in to return.
Returns
the nth disabled plug-in object (the libSBML extension interface) of a package extension. If the index n is invalid, NULL is returned.
See also
getNumDisabledPlugins()
getPlugin(const std::string& package)
const SBase * SBase::getElementByMetaId ( const std::string &  metaid) const
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.
Parameters
metaidstring representing the "metaid" attribute value of the object to find.
Returns
pointer to the first element found with the given meta-identifier.
SBase * Event::getElementByMetaId ( const std::string &  metaid)
virtual

Returns the first child element it can find with the given metaid, or NULL if no such object is found.

Parameters
metaidstring representing the metaid of the object to find.
Returns
pointer to the first element found with the given metaid.

Reimplemented from SBase.

const SBase * SBase::getElementBySId ( const std::string &  id) const
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.

Parameters
idstring representing the "id" attribute value of the object to find.
Returns
pointer to the first element found with the given identifier.
SBase * Event::getElementBySId ( const std::string &  id)
virtual

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.

Parameters
idstring representing the id of the object to find.
Returns
pointer to the first element found with the given id.

Reimplemented from SBase.

const string & Event::getElementName ( ) const
virtual

Returns the XML element name of this object, which for Event, is always "event".

Returns
the name of this element, i.e., "event".

Reimplemented from SBase.

const EventAssignment * Event::getEventAssignment ( unsigned int  n) const

Return a specific EventAssignment object of this Event.

Parameters
nan integer, the index of the EventAssignment object to return.
Returns
the nth EventAssignment of this Event.
Examples:
printAnnotation.cpp, printMath.cpp, printNotes.cpp, printUnits.cpp, unsetAnnotation.cpp, and unsetNotes.cpp.
EventAssignment * Event::getEventAssignment ( unsigned int  n)

Return a specific EventAssignment object of this Event.

Parameters
nan integer, the index of the EventAssignment object to return.
Returns
the nth EventAssignment of this Event.
const EventAssignment * Event::getEventAssignment ( const std::string &  variable) const

Return the event assignment indicated by the given variable.

Parameters
variablea string, the identifier of the variable whose EventAssignment is being sought.
Returns
the EventAssignment for the given variable, or NULL if no such EventAssignment exists.
EventAssignment * Event::getEventAssignment ( const std::string &  variable)

Return the event assignment indicated by the given variable.

Parameters
variablea string, the identifier of the variable whose EventAssignment is being sought.
Returns
the EventAssignment for the given variable, or NULL if no such EventAssignment exists.
const string & Event::getId ( ) const
virtual

Returns the value of the "id" attribute of this Event.

Note
Because of the inconsistent behavior of this function with respect to assignments and rules, it is now recommended to use the getIdAttribute() function instead.
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.

Returns
the id of this Event.
See also
getIdAttribute()
setIdAttribute(const std::string& sid)
isSetIdAttribute()
unsetIdAttribute()

Reimplemented from SBase.

const string & SBase::getIdAttribute ( ) const
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.

Returns
the id of this SBML object, if set and valid for this level and version of SBML; an empty string otherwise.
Note
Because of the inconsistent behavior of this function with respect to assignments and rules, callers should use getIdAttribute() instead.
See also
setIdAttribute(const std::string& sid)
isSetIdAttribute()
unsetIdAttribute()
unsigned int SBase::getLevel ( ) const
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.)
Returns
the SBML level of this SBML object.
See also
getVersion()
getNamespaces()
getPackageVersion()
Examples:
addLayout.cpp, convertSBML.cpp, and printSBML.cpp.
unsigned int SBase::getLine ( ) const
inherited

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

Returns
the line number of this SBML object. If this object was created programmatically and not read from a file, this method will return the value 0.
Note
The line number for each construct in an SBML model is set upon reading the model. The accuracy of the line number depends on the correctness of the XML representation of the model, and on the particular XML parser library being used. The former limitation relates to the following problem: if the model is actually invalid XML, then the parser may not be able to interpret the data correctly and consequently may not be able to establish the real line number. The latter limitation is simply that different parsers seem to have their own accuracy limitations, and out of all the parsers supported by libSBML, none have been 100% accurate in all situations. (At this time, libSBML supports the use of libxml2, Expat and Xerces.)
See also
getColumn()
const ListOfEventAssignments * Event::getListOfEventAssignments ( ) const

Returns the list of event assignments for this Event.

Returns
the list of EventAssignments for this Event.
ListOfEventAssignments * Event::getListOfEventAssignments ( )

Returns the list of event assignments for this Event.

Returns
the list of EventAssignments for this Event.
const string & SBase::getMetaId ( ) const
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.
Returns
the meta-identifier of this SBML object.
See also
isSetMetaId()
setMetaId(const std::string& metaid)
Examples:
addingEvidenceCodes_2.cpp.
string & SBase::getMetaId ( )
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.
Returns
the meta-identifier of this SBML object, as a string.
See also
isSetMetaId()
setMetaId(const std::string& metaid)
const Model * SBase::getModel ( ) const
inherited

Returns the Model object for the SBML Document in which the current object is located.

Returns
the Model object for the SBML Document of this SBML object.
See also
getParentSBMLObject()
getSBMLDocument()
ModelHistory * SBase::getModelHistory ( ) const
inherited

Returns the ModelHistory object, if any, attached to this object.

Returns
the ModelHistory object attached to this object, or NULL if none exist.
Note
In SBML Level 2, model history annotations were only permitted on the Model element. In SBML Level 3, they are permitted on all SBML components derived from SBase.
ModelHistory * SBase::getModelHistory ( )
inherited

Returns the ModelHistory object, if any, attached to this object.

Returns
the ModelHistory object attached to this object, or NULL if none exist.
Note
In SBML Level 2, model history annotations were only permitted on the Model element. In SBML Level 3, they are permitted on all SBML components derived from SBase.
const string & Event::getName ( ) const
virtual

Returns the value of the "name" attribute of this Event.

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.

Returns
the name of this SBML object, or the empty string if not set or unsettable.
See also
getIdAttribute()
isSetName()
setName(const std::string& sid)
unsetName()

Reimplemented from SBase.

XMLNamespaces * SBase::getNamespaces ( ) const
virtualinherited

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.

Returns
the XML Namespaces associated with this SBML object, or NULL in certain very usual circumstances where a namespace is not set.
See also
getLevel()
getVersion()

Reimplemented in SBMLDocument.

XMLNode * SBase::getNotes ( )
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().

Returns
the content of the "notes" subelement of this SBML object as a tree structure composed of XMLNode objects.
See also
getNotesString()
isSetNotes()
setNotes(const XMLNode* notes)
setNotes(const std::string& notes, bool addXHTMLMarkup)
appendNotes(const XMLNode* notes)
appendNotes(const std::string& notes)
unsetNotes()
SyntaxChecker::hasExpectedXHTMLSyntax()
XMLNode * SBase::getNotes ( ) const
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().

Returns
the content of the "notes" subelement of this SBML object as a tree structure composed of XMLNode objects.
See also
getNotesString()
isSetNotes()
setNotes(const XMLNode* notes)
setNotes(const std::string& notes, bool addXHTMLMarkup)
appendNotes(const XMLNode* notes)
appendNotes(const std::string& notes)
unsetNotes()
SyntaxChecker::hasExpectedXHTMLSyntax()
std::string SBase::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.

Returns
the content of the "notes" subelement of this SBML object as a string.
See also
getNotes()
isSetNotes()
setNotes(const XMLNode* notes)
setNotes(const std::string& notes, bool addXHTMLMarkup)
appendNotes(const XMLNode* notes)
appendNotes(const std::string& notes)
unsetNotes()
SyntaxChecker::hasExpectedXHTMLSyntax()
Examples:
printNotes.cpp, and SBMLHttpResolverExample.cpp.
std::string SBase::getNotesString ( ) const
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.

Returns
the content of the "notes" subelement of this SBML object as a string.
See also
getNotes()
isSetNotes()
setNotes(const XMLNode* notes)
setNotes(const std::string& notes, bool addXHTMLMarkup)
appendNotes(const XMLNode* notes)
appendNotes(const std::string& notes)
unsetNotes()
SyntaxChecker::hasExpectedXHTMLSyntax()
unsigned int SBase::getNumCVTerms ( )
inherited

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

Returns
the number of CVTerms for this SBML object.
unsigned int SBase::getNumDisabledPlugins ( ) const
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.
Returns
the number of disabled plug-in objects (extension interfaces) of package extensions known by this instance of libSBML.
unsigned int Event::getNumEventAssignments ( ) const

Returns the number of EventAssignment objects attached to this Event.

Returns
the number of EventAssignments in this Event.
Examples:
printAnnotation.cpp, printMath.cpp, printNotes.cpp, printUnits.cpp, unsetAnnotation.cpp, and unsetNotes.cpp.
unsigned int SBase::getNumPlugins ( ) const
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.
Returns
the number of plug-in objects (extension interfaces) of package extensions known by this instance of libSBML.
See also
getPlugin(unsigned int n)
unsigned int SBase::getPackageCoreVersion ( ) const
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.)
Returns
the SBML core version of this SBML object.
const std::string & SBase::getPackageName ( ) const
inherited

Returns the name of the SBML Level 3 package in which this element is defined.

Returns
the name of the SBML package in which this element is defined. The string "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.
unsigned int SBase::getPackageVersion ( ) const
inherited

Returns the Version of the SBML Level 3 package to which this element belongs to.

Returns
the version of the SBML Level 3 package to which this element belongs. The value 0 will be returned if this element belongs to the SBML Level 3 Core package.
See also
getLevel()
getVersion()
SBase * SBase::getParentSBMLObject ( )
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.

Returns
the parent SBML object of this SBML object.
See also
getSBMLDocument()
getModel()
const SBase * SBase::getParentSBMLObject ( ) const
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.

Returns
the parent SBML object of this SBML object.
See also
getSBMLDocument()
getModel()
SBasePlugin * SBase::getPlugin ( const std::string &  package)
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.
Parameters
packagethe name or URI of the package.
Returns
the plug-in object (the libSBML extension interface) of a package extension with the given package name or URI.
See also
getPlugin(unsigned int n)
Examples:
addLayout.cpp, convertLayout.cpp, example1-L3.cpp, example1.cpp, example2-L3.cpp, example2.cpp, example3-L3.cpp, example3.cpp, fbc_example1.cpp, groups_example1.cpp, groups_example2.cpp, qual_example1.cpp, SBMLHttpResolverExample.cpp, spec_example1.cpp, spec_example2.cpp, spec_example3.cpp, and spec_example4.cpp.
const SBasePlugin * SBase::getPlugin ( const std::string &  package) const
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.
Parameters
packagethe name or URI of the package.
Returns
the plug-in object (the libSBML extension interface) of a package extension with the given package name or URI.
See also
getPlugin(unsigned int n)
SBasePlugin * SBase::getPlugin ( unsigned int  n)
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.
Parameters
nthe index of the plug-in to return.
Returns
the nth plug-in object (the libSBML extension interface) of a package extension. If the index n is invalid, NULL is returned.
See also
getNumPlugins()
getPlugin(const std::string& package)
const SBasePlugin * SBase::getPlugin ( unsigned int  n) const
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.
Parameters
nthe index of the plug-in to return.
Returns
the nth plug-in object (the libSBML extension interface) of a package extension. If the index n is invalid, NULL is returned.
See also
getNumPlugins()
getPlugin(const std::string& package)
std::string SBase::getPrefix ( ) const
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.

Returns
a text string representing the XML namespace prefix.
const Priority * Event::getPriority ( ) const

(SBML Level 3 only) Get the event priority portion of this Event.

Returns
the Priority object of this Event, or NULL if the Priority has not been set.
Note
The element "priority" is available in SBML Level 3, but is not present in lower Levels of SBML.
Priority * Event::getPriority ( )

(SBML Level 3 only) Get the event priority portion of this Event.

Returns
the Priority object of this Event, or NULL if the Priority has not been set.
Note
The element "priority" is available in SBML Level 3, but is not present in lower Levels of SBML.
BiolQualifierType_t SBase::getResourceBiologicalQualifier ( std::string  resource)
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 values from the enumeration type BiolQualifierType_t.

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 value from the enumeration type BiolQualifierType_t.

Parameters
resourcestring representing the resource; e.g., "http://www.geneontology.org/#GO:0005892".
Returns
the qualifier associated with the resource, or BQB_UNKNOWN if the resource does not exist.
Note
The set of MIRIAM biological qualifiers grows over time, although relatively slowly. The values in the enumeration BiolQualifierType_t are up to date with MIRIAM at the time of a given libSBML release. The set of values may be expanded in later libSBML releases, to match the values defined by MIRIAM at that later time.
ModelQualifierType_t SBase::getResourceModelQualifier ( std::string  resource)
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 values from the enumeration type ModelQualifierType_t.

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 value from the enumeration type ModelQualifierType_t.

Parameters
resourcestring representing the resource; e.g., "http://www.geneontology.org/#GO:0005892".
Returns
the ModelQualifierType_t value associated with the resource, or BQM_UNKNOWN if the resource does not exist.
Note
The set of MIRIAM biological qualifiers grows over time, although relatively slowly. The values in the enumeration ModelQualifierType_t are up to date with MIRIAM at the time of a given libSBML release. The set of values may be expanded in later libSBML releases, to match the values defined by MIRIAM at that later time.
const SBMLDocument * SBase::getSBMLDocument ( ) const
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.

Returns
the parent SBMLDocument object of this SBML object.
See also
getParentSBMLObject()
getModel()
SBMLDocument * SBase::getSBMLDocument ( )
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.

Returns
the parent SBMLDocument object of this SBML object.
See also
getParentSBMLObject()
getModel()
int SBase::getSBOTerm ( ) const
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.
Returns
the value of the "sboTerm" attribute as an integer, or -1 if the value is not set.
Examples:
printSBML.cpp.
std::string SBase::getSBOTermAsURL ( ) const
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.
Returns
the value of the "sboTerm" attribute as an identifiers.org URL, or an empty string if the value is not set.
std::string SBase::getSBOTermID ( ) const
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.
Returns
the value of the "sboTerm" attribute as a string (its value will be of the form "SBO:NNNNNNN"), or an empty string if the value is not set.
const string & Event::getTimeUnits ( ) const

Get the value of the "timeUnits" attribute of this Event, if it has one.

Returns
the value of the attribute "timeUnits" as a string.
Warning
Definitions of Event in SBML Level 2 Versions 1 and 2 included the additional attribute called "timeUnits", but it was removed in SBML Level 2 Version 3. LibSBML supports this attribute for compatibility with previous versions of SBML Level 2, but its use is discouraged since models in Level 2 Versions 3 and 4 cannot contain it. If a Version 3 or 4 model sets the attribute, the consistency-checking method SBMLDocument::checkConsistency() will report an error.
const Trigger * Event::getTrigger ( ) const

Get the event trigger portion of this Event.

Returns
the Trigger object of this Event, or NULL if the trigger is not set.
Examples:
printAnnotation.cpp, printMath.cpp, and printNotes.cpp.
Trigger * Event::getTrigger ( )

Get the event trigger portion of this Event.

Returns
the Trigger object of this Event.
int Event::getTypeCode ( ) const
virtual

Returns the libSBML type code of this object instance.

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_. The set of possible type codes for core elements is defined in the enumeration SBMLTypeCode_t, and in addition, libSBML plug-ins for SBML Level 3 packages define their own extra enumerations of type codes (e.g., SBMLLayoutTypeCode_t for the Level 3 Layout package). 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.

Returns
the SBML type code for this object: SBML_EVENT (default).
Warning
The specific integer values of the possible type codes may be reused by different libSBML plug-ins for SBML Level 3. packages, To fully identify the correct code, it is necessary to invoke both getPackageName() and getTypeCode() (or ListOf::getItemTypeCode()).
See also
getElementName()
getPackageName()

Reimplemented from SBase.

std::string SBase::getURI ( ) const
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.

Returns
the URI of this element, as a text string.
See also
getSBMLDocument()
getPackageName()
void * SBase::getUserData ( ) const
inherited

Returns the user data that has been previously set via setUserData().

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 attribute will passed as it is. The attribute will never be interpreted by libSBML.
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.
Returns
the user data of this node, or NULL if no user data has been set.
See also
ASTNode::setUserData(void *userData)
bool Event::getUseValuesFromTriggerTime ( ) const

Get the value of the "useValuesFromTriggerTime" attribute of this Event.

The optional Delay on Event and the fact that multiple events may be simultaneously executed means there are two times to consider when computing the results of an event: the time at which the event is triggered, and the time at which assignments are executed. It is also possible to distinguish between the time at which the EventAssignment's expression is calculated, and the time at which the assignment is made: the expression could be evaluated at the same time the assignments are performed, i.e., when the event is executed, but it could also be defined to be evaluated at the time the event is triggered.

In SBML Level 2 versions prior to Version 4, the semantics of Event time delays were defined such that the expressions in the event's assignments were always evaluated at the time the event was triggered. This definition made it difficult to define an event whose assignment formulas were meant to be evaluated at the time the event was executed (i.e., after the time period defined by the value of the Delay element, or after any other simultaneous event may have been executed and changed the model state). In SBML Level 2 Version 4, the attribute "useValuesFromTriggerTime" on Event allows a model to indicate the time at which the event's assignments are intended to be evaluated. In SBML Level 2, the attribute has a default value of true, which corresponds to the interpretation of event assignments prior to Version 4: the values of the assignment formulas are computed at the moment the event is triggered, not after the delay. If "useValuesFromTriggerTime"=false, it means that the formulas in the event's assignments are to be computed after the delay, at the time the event is executed. In SBML Level 3, the attribute is mandatory, not optional, and all events must specify a value for it.

Returns
the value of the attribute "useValuesFromTriggerTime" as a boolean.
Warning
The attribute "useValuesFromTriggerTime" was introduced in SBML Level 2 Version 4. It is not valid in models defined using SBML Level 2 versions prior to Version 4. If a Level 2 Version 1–3 model sets the attribute, the consistency-checking method SBMLDocument::checkConsistency() will report an error.
unsigned int SBase::getVersion ( ) const
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.)
Returns
the SBML version of this SBML object.
See also
getLevel()
getNamespaces()
Examples:
addLayout.cpp, convertSBML.cpp, and printSBML.cpp.
bool Event::hasRequiredAttributes ( ) const
virtual

Predicate returning true if all the required attributes for this Event object have been set.

The required attributes for an Event object are:

  • "useValuesfromTriggerTime" (required in SBML Level 3)
Returns
true if the required attributes have been set, false otherwise.
bool Event::hasRequiredElements ( ) const
virtual

Predicate returning true if all the required elements for this Event object have been set.

Note
The required elements for an Event object are:
  • "trigger" (required in SBML Level 2 and Level 3 Version 1; optional in SBML Level 3 Version 2+
  • "listOfEventAssignments" (required in SBML Level 2; optional in Level 3)
bool SBase::hasValidLevelVersionNamespaceCombination ( )
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:

  • Level 1 Version 2: "http://www.sbml.org/sbml/level1"
  • Level 2 Version 1: "http://www.sbml.org/sbml/level2"
  • Level 2 Version 2: "http://www.sbml.org/sbml/level2/version2"
  • Level 2 Version 3: "http://www.sbml.org/sbml/level2/version3"
  • Level 2 Version 4: "http://www.sbml.org/sbml/level2/version4"
  • Level 2 Version 5: "http://www.sbml.org/sbml/level2/version5"
  • Level 3 Version 1 Core: "http://www.sbml.org/sbml/level3/version1/core"
  • Level 3 Version 2 Core: "http://www.sbml.org/sbml/level3/version2/core"
Returns
true if the level, version and namespace values of this SBML object correspond to a valid set of values, false otherwise.
void Event::initDefaults ( )

Initializes the fields of this Event object to "typical" default values.

The SBML Event component has slightly different aspects and default attribute values in different SBML Levels and Versions. This method sets the values to certain common defaults, based mostly on what they are in SBML Level 2. Specifically:

  • Sets attribute "useValuesFromTriggerTime" to true
bool SBase::isPackageEnabled ( const std::string &  pkgName) const
inherited

Predicate returning true if the given SBML Level 3 package is enabled with this object.

The search ignores the package version.

Parameters
pkgNamethe name of the package.
Returns
true if the given package is enabled within this object, false otherwise.
See also
isPackageURIEnabled()
bool SBase::isPackageURIEnabled ( const std::string &  pkgURI) const
inherited

Predicate returning true if an SBML Level 3 package with the given URI is enabled with this object.

Parameters
pkgURIthe URI of the package.
Returns
true if the given package is enabled within this object, false otherwise.
See also
isPackageEnabled()
bool SBase::isPkgEnabled ( const std::string &  pkgName) const
inherited

Predicate returning true if the given SBML Level 3 package is enabled with this object.

The search ignores the package version.

Parameters
pkgNamethe name of the package.
Returns
true if the given package is enabled within this object, false otherwise.
See also
isPkgURIEnabled()
bool SBase::isPkgURIEnabled ( const std::string &  pkgURI) const
inherited

Predicate returning true if an SBML Level 3 package with the given URI is enabled with this object.

Parameters
pkgURIthe URI of the package.
Returns
true if the given package is enabled within this object, false otherwise.
See also
isPkgEnabled()
bool SBase::isSetAnnotation ( ) const
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.

Returns
true if a "annotation" subelement exists, false otherwise.
See also
getAnnotation()
getAnnotationString()
setAnnotation(const XMLNode* annotation)
setAnnotation(const std::string& annotation)
appendAnnotation(const XMLNode* annotation)
appendAnnotation(const std::string& annotation)
unsetAnnotation()
Examples:
printAnnotation.cpp.
bool Event::isSetDelay ( ) const

Predicate for testing whether the delay for this Event is set.

Returns
true if the delay of this Event is set, false otherwise.
Examples:
printAnnotation.cpp, printMath.cpp, printNotes.cpp, and printUnits.cpp.
bool Event::isSetId ( ) const
virtual

Predicate returning true if this Event'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.

Returns
true if the "id" attribute of this SBML object is set, false otherwise.
Note
Because of the inconsistent behavior of this function with respect to assignments and rules, it is recommended that callers use isSetIdAttribute() instead.
See also
getIdAttribute()
setIdAttribute(const std::string& sid)
unsetIdAttribute()
isSetIdAttribute()

Reimplemented from SBase.

bool SBase::isSetIdAttribute ( ) const
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.

Returns
true if the "id" attribute of this SBML object is set, false otherwise.
See also
getIdAttribute()
setIdAttribute(const std::string& sid)
unsetIdAttribute()
bool SBase::isSetMetaId ( ) const
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.
Returns
true if the "metaid" attribute of this SBML object is set, false otherwise.
See also
getMetaId()
setMetaId(const std::string& metaid)
Examples:
addingEvidenceCodes_1.cpp, and addingEvidenceCodes_2.cpp.
bool SBase::isSetModelHistory ( )
inherited

Predicate returning true if this object has a ModelHistory object attached to it.

Returns
true if the ModelHistory of this object is set, false otherwise.
Note
In SBML Level 2, model history annotations were only permitted on the Model element. In SBML Level 3, they are permitted on all SBML components derived from SBase.
bool Event::isSetName ( ) const
virtual

Predicate returning true if this Event'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.

Returns
true if the "name" attribute of this SBML object is set, false otherwise.
See also
getName()
setName(const std::string& sid)
unsetName()

Reimplemented from SBase.

bool SBase::isSetNotes ( ) const
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.

Returns
true if a "notes" subelement exists, false otherwise.
See also
getNotes()
getNotesString()
setNotes(const XMLNode* notes)
setNotes(const std::string& notes, bool addXHTMLMarkup)
appendNotes(const XMLNode* notes)
appendNotes(const std::string& notes)
unsetNotes()
SyntaxChecker::hasExpectedXHTMLSyntax()
Examples:
getAllElementsWithNotes.cpp, printNotes.cpp, and SBMLHttpResolverExample.cpp.
bool Event::isSetPriority ( ) const

(SBML Level 3 only) Predicate for testing whether the priority for this Event is set.

Returns
true if the priority of this Event is set, false otherwise.
Note
The element "priority" is available in SBML Level 3, but is not present in lower Levels of SBML.
bool SBase::isSetSBOTerm ( ) const
inherited

Predicate returning true if this object's "sboTerm" attribute is set.

Returns
true if the "sboTerm" attribute of this SBML object is set, false otherwise.
Examples:
printSBML.cpp.
bool Event::isSetTimeUnits ( ) const

Predicate for testing whether the "timeUnits" attribute of this Event is set.

Returns
true if the "timeUnits" attribute of this Event is set, false otherwise.
Warning
Definitions of Event in SBML Level 2 Versions 1 and 2 included the additional attribute called "timeUnits", but it was removed in SBML Level 2 Version 3. LibSBML supports this attribute for compatibility with previous versions of SBML Level 2, but its use is discouraged since models in Level 2 Versions 3 and 4 cannot contain it. If a Version 3 or 4 model sets the attribute, the consistency-checking method SBMLDocument::checkConsistency() will report an error.
bool Event::isSetTrigger ( ) const

Predicate for testing whether the trigger for this Event is set.

Returns
true if the trigger of this Event is set, false otherwise.
Examples:
printAnnotation.cpp, printMath.cpp, and printNotes.cpp.
bool SBase::isSetUserData ( ) const
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 attribute will passed as it is. The attribute will never be interpreted by libSBML.
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.
Returns
boolean, true if this object's user data has been set, false otherwise.
bool Event::isSetUseValuesFromTriggerTime ( ) const

Predicate for testing whether the "useValuesFromTriggerTime" attribute of this Event is set.

Returns
true if the "useValuesFromTriggerTime" attribute of this Event is set, false otherwise.
Note
In SBML Level 2, this attribute is optional and has a default value of true, whereas in Level 3, this optional is mandatory and has no default value.
bool SBase::matchesRequiredSBMLNamespacesForAddition ( const SBase sb)
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.
Parameters
sban object to compare with respect to namespaces.
Returns
boolean, true if this object's collection of namespaces is a subset of sb's, false otherwise.
bool SBase::matchesRequiredSBMLNamespacesForAddition ( const SBase sb) const
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.
Parameters
sban object to compare with respect to namespaces.
Returns
boolean, true if this object's collection of namespaces is a subset of sb's, false otherwise.
bool SBase::matchesSBMLNamespaces ( const SBase sb)
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.
Parameters
sban object to compare with respect to namespaces.
Returns
boolean, true if this object's collection of namespaces is the same as sb's, false otherwise.
bool SBase::matchesSBMLNamespaces ( const SBase sb) const
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.
Parameters
sban object to compare with respect to namespaces.
Returns
boolean, true if this object's collection of namespaces is the same as sb's, false otherwise.
Event & Event::operator= ( const Event rhs)

Assignment operator for Event.

Parameters
rhsthe object whose values are used as the basis of the assignment.
void SBase::read ( XMLNode node,
XMLErrorSeverityOverride_t  flag = LIBSBML_OVERRIDE_DISABLED 
)
inherited

Reads (initializes) this SBML object by reading from the given XMLNode.

Parameters
nodethe XMLNode to read from.
flagan optional flag that determines how how errors are logged during the reading process.
Warning
This method is computationally expensive, because the given node has to be serialized to a string first. Attempting to serialize a large tree structure (e.g., a large Model) may consume significant computer memory and time.
EventAssignment * Event::removeEventAssignment ( unsigned int  n)

Removes the nth EventAssignment object from this Event object and returns a pointer to it.

The caller owns the returned object and is responsible for deleting it.

Parameters
nthe index of the EventAssignment object to remove.
Returns
the EventAssignment object removed. As mentioned above, the caller owns the returned item. NULL is returned if the given index is out of range.
EventAssignment * Event::removeEventAssignment ( const std::string &  variable)

Removes the EventAssignment object with the given "variable" attribute from this Event object and returns a pointer to it.

The caller owns the returned object and is responsible for deleting it. If none of the EventAssignment objects in this Event object have the "variable" attribute variable, then NULL is returned.

Parameters
variablethe "variable" attribute of the EventAssignment object to remove.
Returns
the EventAssignment object removed. As mentioned above, the caller owns the returned object. NULL is returned if no EventAssignment object with the "variable" attribute exists in this Event object.
int SBase::removeFromParentAndDelete ( )
virtualinherited

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.

Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:

Reimplemented in Model, KineticLaw, SBaseRef, StoichiometryMath, Trigger, Delay, ListOf, Priority, ModelDefinition, and ReplacedBy.

int SBase::removeTopLevelAnnotationElement ( const std::string &  elementName,
const std::string  elementURI = "",
bool  removeEmpty = true 
)
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.

Parameters
elementNamea string representing the name of the top level annotation element that is to be removed.
elementURIan optional string that is used to check both the name and URI of the top level element to be removed.
removeEmptyif after removing of the element, the annotation is empty, and the removeEmpty argument is true, the annotation node will be deleted (default).
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
See also
replaceTopLevelAnnotationElement(const XMLNode *)
replaceTopLevelAnnotationElement(const std::string&)
void SBase::renameMetaIdRefs ( const std::string &  oldid,
const std::string &  newid 
)
virtualinherited

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.

Parameters
oldidthe old identifier.
newidthe new identifier.

Reimplemented in Port, and GraphicalObject.

void SBase::renameSIdRefs ( const std::string &  oldid,
const std::string &  newid 
)
virtualinherited

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.

Parameters
oldidthe old identifier.
newidthe new identifier.

Reimplemented in Model, DefaultValues, Species, RenderInformationBase, ListOfObjectives, RenderGroup, Compartment, KineticLaw, Rule, MultiSpeciesType, Submodel, EventAssignment, InitialAssignment, StoichiometryMath, SpeciesFeature, Delay, SBaseRef, RenderCurve, Trigger, Input, FluxBound, QualitativeSpecies, OutwardBindingSite, ReactionGlyph, Priority, SpeciesTypeComponentMapInProduct, Output, GeneralGlyph, FluxObjective, Constraint, GeneProduct, SpeciesTypeComponentIndex, Reaction, SpeciesTypeInstance, InSpeciesTypeBond, ReplacedElement, Member, Port, PossibleSpeciesFeatureValue, SimpleSpeciesReference, GeneProductRef, CompartmentReference, AssignmentRule, RateRule, FunctionTerm, SpeciesReferenceGlyph, CompartmentGlyph, SpeciesFeatureValue, Replacing, ReferenceGlyph, TextGlyph, and SpeciesGlyph.

void SBase::renameUnitSIdRefs ( const std::string &  oldid,
const std::string &  newid 
)
virtualinherited

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.

Parameters
oldidthe old identifier.
newidthe new identifier.

Reimplemented in Model, Species, Compartment, KineticLaw, Rule, Parameter, EventAssignment, InitialAssignment, StoichiometryMath, Delay, FunctionDefinition, Trigger, Priority, Constraint, and Port.

int SBase::replaceTopLevelAnnotationElement ( const XMLNode 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.

Parameters
annotationXMLNode representing the replacement top level annotation.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
See also
removeTopLevelAnnotationElement(const std::string elementName, const std::string elementURI, bool removeEmpty)
replaceTopLevelAnnotationElement(const std::string&)
int SBase::replaceTopLevelAnnotationElement ( const std::string &  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.

Parameters
annotationstring representing the replacement top level annotation.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
See also
removeTopLevelAnnotationElement(const std::string elementName, const std::string elementURI)
replaceTopLevelAnnotationElement(const XMLNode*)
int SBase::setAnnotation ( const XMLNode annotation)
virtualinherited

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(const XMLNode* annotation) or SBase::appendAnnotation(const std::string& annotation).

Parameters
annotationan XML structure that is to be used as the new content of the "annotation" subelement of this object.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. This particular function only does one thing irrespective of user input or object state, and thus will only return a single value:
See also
getAnnotationString()
isSetAnnotation()
setAnnotation(const std::string& annotation)
appendAnnotation(const XMLNode* annotation)
appendAnnotation(const std::string& annotation)
unsetAnnotation()

Reimplemented in Model, and SpeciesReference.

int SBase::setAnnotation ( const std::string &  annotation)
virtualinherited

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(const XMLNode* annotation) or SBase::appendAnnotation(const std::string& annotation).

Parameters
annotationan XML string that is to be used as the content of the "annotation" subelement of this object.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
See also
getAnnotationString()
isSetAnnotation()
setAnnotation(const XMLNode* annotation)
appendAnnotation(const XMLNode* annotation)
appendAnnotation(const std::string& annotation)
unsetAnnotation()

Reimplemented in Model, and SpeciesReference.

int Event::setDelay ( const Delay delay)

Sets the delay definition of this Event to a copy of the given Delay object instance.

Parameters
delaythe Delay object instance to use.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
void SBase::setElementText ( const std::string &  text)
protectedvirtualinherited

When overridden allows SBase elements to use the text included in between the elements tags.

The default implementation does nothing.

Parameters
textthe text string found between the element tags.
int Event::setId ( const std::string &  sid)
virtual

Sets the value of the "id" attribute of this Event.

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.

Parameters
sidthe string to use as the identifier of this object.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
See also
getIdAttribute()
setIdAttribute(const std::string& sid)
isSetIdAttribute()
unsetIdAttribute()

Reimplemented from SBase.

int SBase::setIdAttribute ( const std::string &  sid)
virtualinherited

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.

Parameters
sidthe string to use as the identifier of this object.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
See also
getIdAttribute()
setIdAttribute(const std::string& sid)
isSetIdAttribute()
unsetIdAttribute()
int SBase::setMetaId ( const std::string &  metaid)
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.

Parameters
metaidthe identifier string to use as the value of the "metaid" attribute.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
See also
getMetaId()
isSetMetaId()
Examples:
addingEvidenceCodes_1.cpp, and addingEvidenceCodes_2.cpp.
int SBase::setModelHistory ( ModelHistory history)
inherited

Sets the ModelHistory of this object.

The content of history is copied, and this object's existing model history content is deleted.

Parameters
historyModelHistory of this object.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
Note
In SBML Level 2, model history annotations were only permitted on the Model element. In SBML Level 3, they are permitted on all SBML components derived from SBase.
Examples:
addModelHistory.cpp.
int Event::setName ( const std::string &  name)
virtual

Sets the value of the "name" attribute of this Event.

The string in name is copied.

Parameters
namethe new name for the SBML object.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:

Reimplemented from SBase.

int SBase::setNamespaces ( XMLNamespaces xmlns)
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.

Parameters
xmlnsthe namespaces to set.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
int SBase::setNotes ( const XMLNode notes)
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.

Parameters
notesan XML structure that is to be used as the content of the "notes" subelement of this object.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
See also
getNotesString()
isSetNotes()
setNotes(const std::string& notes, bool addXHTMLMarkup)
appendNotes(const XMLNode* notes)
appendNotes(const std::string& notes)
unsetNotes()
SyntaxChecker::hasExpectedXHTMLSyntax()
Examples:
createExampleSBML.cpp.
int SBase::setNotes ( const std::string &  notes,
bool  addXHTMLMarkup = false 
)
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.

SBMLDocument* s = new SBMLDocument(3, 1);
s->setNotes("<body xmlns='http://www.w3.org/1999/xhtml'><p>here is my note</p></body>");
Parameters
notesan XML string that is to be used as the content of the "notes" subelement of this object.
addXHTMLMarkupa 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.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
See also
getNotesString()
isSetNotes()
setNotes(const XMLNode* notes)
appendNotes(const XMLNode* notes)
appendNotes(const std::string& notes)
unsetNotes()
SyntaxChecker::hasExpectedXHTMLSyntax()
int Event::setPriority ( const Priority priority)

(SBML Level 3 only) Sets the priority definition of this Event to a copy of the given Priority object instance.

Parameters
prioritythe Priority object instance to use.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
Note
The element "priority" is available in SBML Level 3, but is not present in lower Levels of SBML.
int SBase::setSBOTerm ( int  value)
virtualinherited

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.
Parameters
valuethe NNNNNNN integer portion of the SBO identifier.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
See also
setSBOTerm(const std::string &sboid)
Examples:
groups_example1.cpp, and qual_example1.cpp.
int SBase::setSBOTerm ( const std::string &  sboid)
virtualinherited

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.
Parameters
sboidthe SBO identifier string of the form "SBO:NNNNNNN".
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
See also
setSBOTerm(int value)
int Event::setTimeUnits ( const std::string &  sid)

Sets the "timeUnits" attribute of this Event to a copy of sid.

Parameters
sidthe identifier of the time units to use.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
Warning
Definitions of Event in SBML Level 2 Versions 1 and 2 included the additional attribute called "timeUnits", but it was removed in SBML Level 2 Version 3. LibSBML supports this attribute for compatibility with previous versions of SBML Level 2, but its use is discouraged since models in Level 2 Versions 3 and 4 cannot contain it. If a Version 3 or 4 model sets the attribute, the consistency-checking method SBMLDocument::checkConsistency() will report an error.
int Event::setTrigger ( const Trigger trigger)

Sets the trigger definition of this Event to a copy of the given Trigger object instance.

Parameters
triggerthe Trigger object instance to use.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
int SBase::setUserData ( void *  userData)
inherited

Sets 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 attribute will passed as it is. The attribute will never be interpreted by libSBML.
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.
Parameters
userDataspecifies the new user data.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
int Event::setUseValuesFromTriggerTime ( bool  value)

Sets the "useValuesFromTriggerTime" attribute of this Event to a value.

The optional Delay on Event and the fact that multiple events may be simultaneously executed means there are two times to consider when computing the results of an event: the time at which the event is triggered, and the time at which assignments are executed. It is also possible to distinguish between the time at which the EventAssignment's expression is calculated, and the time at which the assignment is made: the expression could be evaluated at the same time the assignments are performed, i.e., when the event is executed, but it could also be defined to be evaluated at the time the event is triggered.

In SBML Level 2 versions prior to Version 4, the semantics of Event time delays were defined such that the expressions in the event's assignments were always evaluated at the time the event was triggered. This definition made it difficult to define an event whose assignment formulas were meant to be evaluated at the time the event was executed (i.e., after the time period defined by the value of the Delay element, or after any other simultaneous event may have been executed and changed the model state). In SBML Level 2 Version 4, the attribute "useValuesFromTriggerTime" on Event allows a model to indicate the time at which the event's assignments are intended to be evaluated. In SBML Level 2, the attribute has a default value of true, which corresponds to the interpretation of event assignments prior to Version 4: the values of the assignment formulas are computed at the moment the event is triggered, not after the delay. If "useValuesFromTriggerTime"=false, it means that the formulas in the event's assignments are to be computed after the delay, at the time the event is executed. In SBML Level 3, the attribute is mandatory, not optional, and all events must specify a value for it.

Parameters
valuethe value of useValuesFromTriggerTime to use.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
Warning
The attribute "useValuesFromTriggerTime" was introduced in SBML Level 2 Version 4. It is not valid in models defined using SBML Level 2 versions prior to Version 4. If a Level 2 Version 1–3 model sets the attribute, the consistency-checking method SBMLDocument::checkConsistency() will report an error.
char * SBase::toSBML ( )
inherited

Returns a string consisting of a partial SBML corresponding to just this object.

Returns
the partial SBML that describes this SBML object.
Warning
This is primarily provided for testing and debugging purposes. It may be removed in a future version of libSBML.
XMLNode* SBase::toXMLNode ( )
inherited

Returns this element as an XMLNode.

Returns
this element as an XMLNode.
Warning
This operation is computationally expensive, because the element has to be fully serialized to a string and then parsed into the XMLNode structure. Attempting to convert a large tree structure (e.g., a large Model) may consume significant computer memory and time.
int SBase::unsetAnnotation ( )
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.

Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. This particular function only does one thing irrespective of user input or object state, and thus will only return a single value:
See also
getAnnotation()
getAnnotationString()
isSetAnnotation()
setAnnotation(const XMLNode* annotation)
setAnnotation(const std::string& annotation)
appendAnnotation(const XMLNode* annotation)
appendAnnotation(const std::string& annotation)
Examples:
unsetAnnotation.cpp.
int SBase::unsetCVTerms ( )
inherited

Clears the list of CVTerm objects attached to this SBML object.

Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
int Event::unsetDelay ( )

Unsets the Delay of this Event.

Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
int Event::unsetId ( )
virtual

Unsets the value of the "id" attribute of this Event.

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.

Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
See also
getIdAttribute()
setIdAttribute(const std::string& sid)
isSetIdAttribute()
unsetIdAttribute()

Reimplemented from SBase.

int SBase::unsetIdAttribute ( )
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.

Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
See also
getIdAttribute()
setIdAttribute(const std::string& sid)
isSetIdAttribute()
int SBase::unsetMetaId ( )
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.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
int SBase::unsetModelHistory ( )
inherited

Unsets the ModelHistory object attached to this object.

Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
Note
In SBML Level 2, model history annotations were only permitted on the Model element. In SBML Level 3, they are permitted on all SBML components derived from SBase.
int Event::unsetName ( )
virtual

Unsets the value of the "name" attribute of this Event.

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.

Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
See also
getName()
setName(const std::string& sid)
isSetName()

Reimplemented from SBase.

int SBase::unsetNotes ( )
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.

Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. This particular function only does one thing irrespective of user input or object state, and thus will only return a single value:
See also
getNotesString()
isSetNotes()
setNotes(const XMLNode* notes)
setNotes(const std::string& notes, bool addXHTMLMarkup)
appendNotes(const XMLNode* notes)
appendNotes(const std::string& notes)
SyntaxChecker::hasExpectedXHTMLSyntax()
Examples:
unsetNotes.cpp.
int Event::unsetPriority ( )

(SBML Level 3 only) Unsets the Priority of this Event.

Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
Note
The element "priority" is available in SBML Level 3, but is not present in lower Levels of SBML.
int SBase::unsetSBOTerm ( )
inherited

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

Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
int Event::unsetTimeUnits ( )

Unsets the "timeUnits" attribute of this Event.

Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
Warning
Definitions of Event in SBML Level 2 Versions 1 and 2 included the additional attribute called "timeUnits", but it was removed in SBML Level 2 Version 3. LibSBML supports this attribute for compatibility with previous versions of SBML Level 2, but its use is discouraged since models in Level 2 Versions 3 and 4 cannot contain it. If a Version 3 or 4 model sets the attribute, the consistency-checking method SBMLDocument::checkConsistency() will report an error.
int Event::unsetTrigger ( )

Unsets the Trigger of this Event.

Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
Note
The element "priority" is available in SBML Level 3, but is not present in lower Levels of SBML.
int SBase::unsetUserData ( )
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 attribute will passed as it is. The attribute will never be interpreted by libSBML.
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.
Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
int Event::unsetUseValuesFromTriggerTime ( )

Unsets the value of the "useValuesFromTriggerTime" attribute of this Event.

The optional Delay on Event and the fact that multiple events may be simultaneously executed means there are two times to consider when computing the results of an event: the time at which the event is triggered, and the time at which assignments are executed. It is also possible to distinguish between the time at which the EventAssignment's expression is calculated, and the time at which the assignment is made: the expression could be evaluated at the same time the assignments are performed, i.e., when the event is executed, but it could also be defined to be evaluated at the time the event is triggered.

In SBML Level 2 versions prior to Version 4, the semantics of Event time delays were defined such that the expressions in the event's assignments were always evaluated at the time the event was triggered. This definition made it difficult to define an event whose assignment formulas were meant to be evaluated at the time the event was executed (i.e., after the time period defined by the value of the Delay element, or after any other simultaneous event may have been executed and changed the model state). In SBML Level 2 Version 4, the attribute "useValuesFromTriggerTime" on Event allows a model to indicate the time at which the event's assignments are intended to be evaluated. In SBML Level 2, the attribute has a default value of true, which corresponds to the interpretation of event assignments prior to Version 4: the values of the assignment formulas are computed at the moment the event is triggered, not after the delay. If "useValuesFromTriggerTime"=false, it means that the formulas in the event's assignments are to be computed after the delay, at the time the event is executed. In SBML Level 3, the attribute is mandatory, not optional, and all events must specify a value for it.

Returns
integer value indicating success/failure of the function. The value is drawn from the enumeration OperationReturnValues_t. The possible values returned by this function are:
Warning
The attribute "useValuesFromTriggerTime" was introduced in SBML Level 2 Version 4. It is not valid in models defined using SBML Level 2 versions prior to Version 4. If a Level 2 Version 1–3 model sets the attribute, the consistency-checking method SBMLDocument::checkConsistency() will report an error.