Output (LibSBML Java API)

java.lang.Object
- org.sbml.libsbml.SBase
- - org.sbml.libsbml.Output

```
public class Output
extends SBase
```
qual The output from a QualitativeSpecies.
Each Output refers to a QualitativeSpecies that participates in (is affected by) the corresponding Transition. In Petri net models these are the output places of the transition.
In a logical model, a QualitativeSpecies should be referenced in at most one ListOfOutputs, (that of the Transition defining the evolution of this species). When a Transition has several outputs, it is because the referenced species share the same regulators and the same logical rules.

Constructor Summary

Constructors
Constructor and Description
`Output()` Creates a new `Output` with the given level, version, and package version.
`Output(long level)` Creates a new `Output` with the given level, version, and package version.
`Output(long level, long version)` Creates a new `Output` with the given level, version, and package version.
`Output(long level, long version, long pkgVersion)` Creates a new `Output` with the given level, version, and package version.
`Output(Output orig)` Copy constructor for `Output`.
`Output(QualPkgNamespaces qualns)` Creates a new `Output` with the given `QualPkgNamespaces` object.

Method Summary

All Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`Output`	`cloneObject()` Creates and returns a deep copy of this `Output` object.
`void`	`delete()` Explicitly deletes the underlying native object.
`java.lang.String`	`getElementName()` Returns the XML name of this object.
`java.lang.String`	`getId()` Returns the value of the 'id' attribute of this `Output`.
`java.lang.String`	`getName()` Returns the value of the 'name' attribute of this `Output` object.
`int`	`getOutputLevel()` Returns the value of the 'outputLevel' attribute of this `Output`.
`java.lang.String`	`getQualitativeSpecies()` Returns the value of the 'qualitativeSpecies' attribute of this `Output`.
`int`	`getTransitionEffect()` Returns the value of the 'transitionEffect' attribute of this `Output`.
`int`	`getTypeCode()` Returns the libSBML type code of this object instance.
`boolean`	`hasRequiredAttributes()` Predicate returning `true` if all the required attributes for this `Output` object have been set.
`boolean`	`isSetId()` Predicate returning `true` or `false` depending on whether this `Output`'s 'id' attribute has been set.
`boolean`	`isSetName()` Predicate returning `true` or `false` depending on whether this `Output`'s 'name' attribute has been set.
`boolean`	`isSetOutputLevel()` Predicate returning `true` or `false` depending on whether this `Output`'s 'outputLevel' attribute has been set.
`boolean`	`isSetQualitativeSpecies()` Predicate returning `true` or `false` depending on whether this `Output`'s 'qualitativeSpecies' attribute has been set.
`boolean`	`isSetTransitionEffect()` Predicate returning `true` or `false` depending on whether this `Output`'s 'transitionEffect' attribute has been set.
`void`	`renameSIdRefs(java.lang.String oldid, java.lang.String newid)` Replaces all uses of a given `SIdRef` type attribute value with another value.
`int`	`setId(java.lang.String sid)` Sets the value of the 'id' attribute of this `Output`.
`int`	`setName(java.lang.String name)` Sets the value of the 'name' attribute of this `Output`.
`int`	`setOutputLevel(int outputLevel)` Sets the value of the 'outputLevel' attribute of this `Output`.
`int`	`setQualitativeSpecies(java.lang.String qualitativeSpecies)` Sets the value of the 'qualitativeSpecies' attribute of this `Output`.
`int`	`setTransitionEffect(int transitionEffect)` Sets the value of the 'transitionEffect' attribute of this `Output`.
`int`	`unsetId()` Unsets the value of the 'id' attribute of this `Output`.
`int`	`unsetName()` Unsets the value of the 'name' attribute of this `Output`.
`int`	`unsetOutputLevel()` Unsets the value of the 'outputLevel' attribute of this `Output`.
`int`	`unsetQualitativeSpecies()` Unsets the value of the 'qualitativeSpecies' attribute of this `Output`.
`int`	`unsetTransitionEffect()` Unsets the value of the 'transitionEffect' attribute of this `Output`.

Methods inherited from class org.sbml.libsbml.SBase
addCVTerm, addCVTerm, appendAnnotation, appendAnnotation, appendNotes, appendNotes, connectToChild, deleteDisabledPlugins, deleteDisabledPlugins, disablePackage, enablePackage, equals, getAncestorOfType, getAncestorOfType, getAnnotation, getAnnotationString, getColumn, getCVTerm, getCVTerms, getDisabledPlugin, getElementByMetaId, getElementBySId, getIdAttribute, getLevel, getLine, getListOfAllElements, getListOfAllElements, getListOfAllElementsFromPlugins, getListOfAllElementsFromPlugins, getMetaId, getModel, getModelHistory, getNamespaces, getNotes, getNotesString, getNumCVTerms, getNumDisabledPlugins, getNumPlugins, getPackageCoreVersion, getPackageName, getPackageVersion, getParentSBMLObject, getPlugin, getPlugin, getPrefix, getResourceBiologicalQualifier, getResourceModelQualifier, getSBMLDocument, getSBOTerm, getSBOTermAsURL, getSBOTermID, getURI, getVersion, hashCode, hasValidLevelVersionNamespaceCombination, isPackageEnabled, isPackageURIEnabled, isPkgEnabled, isPkgURIEnabled, isSetAnnotation, isSetIdAttribute, isSetMetaId, isSetModelHistory, isSetNotes, isSetSBOTerm, isSetUserData, matchesRequiredSBMLNamespacesForAddition, matchesSBMLNamespaces, removeFromParentAndDelete, removeTopLevelAnnotationElement, removeTopLevelAnnotationElement, removeTopLevelAnnotationElement, renameMetaIdRefs, renameUnitSIdRefs, replaceTopLevelAnnotationElement, replaceTopLevelAnnotationElement, setAnnotation, setAnnotation, setIdAttribute, setMetaId, setModelHistory, setNamespaces, setNotes, setNotes, setNotes, setSBOTerm, setSBOTerm, toSBML, toXMLNode, unsetAnnotation, unsetCVTerms, unsetIdAttribute, unsetMetaId, unsetModelHistory, unsetNotes, unsetSBOTerm, unsetUserData

Methods inherited from class java.lang.Object
getClass, notify, notifyAll, toString, wait, wait, wait

- Constructor Detail
  - Output
```
public Output(long level,
              long version,
              long pkgVersion)
       throws SBMLConstructorException
```
    Creates a new Output with the given level, version, and package version.
    
    Parameters:
    
    level - a long integer, the SBML Level to assign to this Output.
    
    version - a long integer, the SBML Version to assign to this Output.
    
    pkgVersion - a long integer, the SBML Qual Version to assign to this Output.
    
    Throws:
    
    SBMLConstructorException
    
    "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. For packages, this means that the parent object to which this package element is being added must have been created with the package namespace, or that the package namespace was added to it, even if that parent is not a package object itself.
  - Output
```
public Output(long level,
              long version)
       throws SBMLConstructorException
```
    Creates a new Output with the given level, version, and package version.
    
    Parameters:
    
    level - a long integer, the SBML Level to assign to this Output.
    
    version - a long integer, the SBML Version to assign to this Output.
    
    pkgVersion - a long integer, the SBML Qual Version to assign to this Output.
    
    Throws:
    
    SBMLConstructorException
    
    "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. For packages, this means that the parent object to which this package element is being added must have been created with the package namespace, or that the package namespace was added to it, even if that parent is not a package object itself.
  - Output
```
public Output(long level)
       throws SBMLConstructorException
```
    Creates a new Output with the given level, version, and package version.
    
    Parameters:
    
    level - a long integer, the SBML Level to assign to this Output.
    
    version - a long integer, the SBML Version to assign to this Output.
    
    pkgVersion - a long integer, the SBML Qual Version to assign to this Output.
    
    Throws:
    
    SBMLConstructorException
    
    "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. For packages, this means that the parent object to which this package element is being added must have been created with the package namespace, or that the package namespace was added to it, even if that parent is not a package object itself.
  - Output
```
public Output()
       throws SBMLConstructorException
```
    Creates a new Output with the given level, version, and package version.
    
    Parameters:
    
    level - a long integer, the SBML Level to assign to this Output.
    
    version - a long integer, the SBML Version to assign to this Output.
    
    pkgVersion - a long integer, the SBML Qual Version to assign to this Output.
    
    Throws:
    
    SBMLConstructorException
    
    "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. For packages, this means that the parent object to which this package element is being added must have been created with the package namespace, or that the package namespace was added to it, even if that parent is not a package object itself.
  - Output
```
public Output(QualPkgNamespaces qualns)
       throws SBMLConstructorException
```
    Creates a new Output with the given QualPkgNamespaces object.
    
    The package namespaces object used in this constructor is derived from a SBMLNamespaces object, which encapsulates SBML Level/Version/namespaces information. It is used to communicate the SBML Level, Version, and package version and name information used in addition to SBML Level 3 Core. A common approach to using libSBML's SBMLNamespaces facilities is to create an package namespace object somewhere in a program once, then hand that object as needed to object constructors of that package that accept it as and argument, such as this one.
    
    Parameters:
    
    qualns - the QualPkgNamespaces object.
    
    Throws:
    
    SBMLConstructorException
    
    "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. For packages, this means that the parent object to which this package element is being added must have been created with the package namespace, or that the package namespace was added to it, even if that parent is not a package object itself.
  - Output
```
public Output(Output orig)
       throws SBMLConstructorException
```
    Copy constructor for Output.
    
    Parameters:
    
    orig - the Output instance to copy.
    
    Throws:
    
    SBMLConstructorException
- Method Detail
  - delete
```
public void delete()
```
    Explicitly deletes the underlying native object.
    In general, application software will not need to call this method directly. The Java language binding for libSBML is implemented as a language wrapper that provides a Java interface to libSBML's underlying C++/C code. Some of the Java methods return objects that are linked to objects created not by Java code, but by C++ code. The Java objects wrapped around them will be deleted when the garbage collector invokes the corresponding C++ finalize() methods for the objects. The finalize() methods in turn call the Output.delete() method on the libSBML object.
    This method is exposed in case calling programs want to ensure that the underlying object is freed immediately, and not at some arbitrary time determined by the Java garbage collector. In normal usage, callers do not need to invoke Output.delete() themselves.
    
    Overrides:
    
    delete in class SBase
  - cloneObject
```
public Output cloneObject()
```
    Creates and returns a deep copy of this Output object.
    
    Overrides:
    
    cloneObject in class SBase
    
    Returns:
    
    a (deep) copy of this Output object.
  - getId
```
public java.lang.String getId()
```
    Returns the value of the 'id' attribute of this Output.
    Overrides:
    
    getId in class SBase
    
    Returns:
    
    the id of this Output.
    
    See Also:
    
    SBase.getIdAttribute(), SBase.setIdAttribute(String sid), SBase.isSetIdAttribute(), SBase.unsetIdAttribute()
    
    "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.
    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, check, 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 exception to this rule is that for InitialAssignment, EventAssignment, AssignmentRule, and RateRule objects, the getId() function and the isSetId() functions (though not the setId() or unsetId() functions) would instead reference the value of the 'variable' attribute (for the rules and event assignments) or the 'symbol' attribute (for initial assignments). The AlgebraicRule fell into this category as well, though because it contained neither a 'variable' nor a 'symbol' attribute, getId() would always return an empty string, and isSetId() would always return false. For this reason, four new functions are now provided (getIdAttribute(), setIdAttribute(String), isSetIdAttribute(), and unsetIdAttribute()) that will always act on the actual 'id' attribute, regardless of the object's type. The new functions should be used instead of the old ones 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.
  - getQualitativeSpecies
```
public java.lang.String getQualitativeSpecies()
```
    Returns the value of the 'qualitativeSpecies' attribute of this Output.
    
    Returns:
    
    the value of the 'qualitativeSpecies' attribute of this Output as a string.
  - getTransitionEffect
```
public int getTransitionEffect()
```
    Returns the value of the 'transitionEffect' attribute of this Output.
    
    Returns:
    
    the value of the 'transitionEffect' attribute of this Output as a string.
  - getName
```
public java.lang.String getName()
```
    Returns the value of the 'name' attribute of this Output object.
    
    In SBML Level 3 Version 2, the 'id' and 'name' attributes were moved to SBase directly, instead of being defined individually for many (but not all) objects. Libsbml has for a long time provided functions defined on SBase itself to get, set, and unset those attributes, which would fail or otherwise return empty strings if executed on any object for which those attributes were not defined. Now that all SBase objects define those attributes, those functions now succeed for any object with the appropriate level and version.
    The 'name' attribute is optional and is not intended to be used for cross-referencing purposes within a model. Its purpose instead is to provide a human-readable label for the component. The data type of 'name' is the type string defined in XML Schema. SBML imposes no restrictions as to the content of 'name' attributes beyond those restrictions defined by the string type in XML Schema.
    The recommended practice for handling 'name' is as follows. If a software tool has the capability for displaying the content of 'name' attributes, it should display this content to the user as a component's label instead of the component's 'id'. If the user interface does not have this capability (e.g., because it cannot display or use special characters in symbol names), or if the 'name' attribute is missing on a given component, then the user interface should display the value of the 'id' attribute instead. (Script language interpreters are especially likely to display 'id' instead of 'name'.)
    As a consequence of the above, authors of systems that automatically generate the values of 'id' attributes should be aware some systems may display the 'id''s to the user. Authors therefore may wish to take some care to have their software create 'id' values that are: (a) reasonably easy for humans to type and read and (b) likely to be meaningful, for example by making the 'id' attribute be an abbreviated form of the name attribute value.
    An additional point worth mentioning is although there are restrictions on the uniqueness of 'id' values, there are no restrictions on the uniqueness of 'name' values in a model. This allows software applications leeway in assigning component identifiers.
    Regardless of the level and version of the SBML, these functions allow client applications to use more generalized code in some situations (for instance, when manipulating objects that are all known to have names). If the object in question does not posess a 'name' attribute according to the SBML specification for the Level and Version in use, libSBML will not allow the name to be set, nor will it read or write 'name' attributes for those objects.
    
    Overrides:
    
    getName in class SBase
    
    Returns:
    
    the name of this SBML object, or the empty string if not set or unsettable.
    
    See Also:
    
    SBase.getIdAttribute(), Output.isSetName(), Output.setName(String sid), Output.unsetName()
  - getOutputLevel
```
public int getOutputLevel()
```
    Returns the value of the 'outputLevel' attribute of this Output.
    
    Returns:
    
    the value of the 'outputLevel' attribute of this Output as a integer.
  - isSetId
```
public boolean isSetId()
```
    Predicate returning true or false depending on whether this Output's 'id' attribute has been set.
    Overrides:
    
    isSetId in class SBase
    
    Returns:
    
    true if the 'id' attribute of this SBML object is set, false otherwise.
    
    See Also:
    
    SBase.getIdAttribute(), SBase.setIdAttribute(String sid), SBase.unsetIdAttribute(), SBase.isSetIdAttribute()
    
    "Note:"
    Because of the inconsistent behavior of this function with respect to assignments and rules, it is now recommended to use the isSetIdAttribute() 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.
    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, check, 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 exception to this rule is that for InitialAssignment, EventAssignment, AssignmentRule, and RateRule objects, the getId() function and the isSetId() functions (though not the setId() or unsetId() functions) would instead reference the value of the 'variable' attribute (for the rules and event assignments) or the 'symbol' attribute (for initial assignments). The AlgebraicRule fell into this category as well, though because it contained neither a 'variable' nor a 'symbol' attribute, getId() would always return an empty string, and isSetId() would always return false. For this reason, four new functions are now provided (getIdAttribute(), setIdAttribute(String), isSetIdAttribute(), and unsetIdAttribute()) that will always act on the actual 'id' attribute, regardless of the object's type. The new functions should be used instead of the old ones 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.
  - isSetQualitativeSpecies
```
public boolean isSetQualitativeSpecies()
```
    Predicate returning true or false depending on whether this Output's 'qualitativeSpecies' attribute has been set.
    
    Returns:
    
    true if this Output's 'qualitativeSpecies' attribute has been set, otherwise false is returned.
  - isSetTransitionEffect
```
public boolean isSetTransitionEffect()
```
    Predicate returning true or false depending on whether this Output's 'transitionEffect' attribute has been set.
    
    Returns:
    
    true if this Output's 'transitionEffect' attribute has been set, otherwise false is returned.
  - isSetName
```
public boolean isSetName()
```
    Predicate returning true or false depending on whether this Output's 'name' attribute has been 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.
    
    Overrides:
    
    isSetName in class SBase
    
    Returns:
    
    true if the 'name' attribute of this SBML object is set, false otherwise.
    
    See Also:
    
    Output.getName(), Output.setName(String sid), Output.unsetName()
  - isSetOutputLevel
```
public boolean isSetOutputLevel()
```
    Predicate returning true or false depending on whether this Output's 'outputLevel' attribute has been set.
    
    Returns:
    
    true if this Output's 'outputLevel' attribute has been set, otherwise false is returned.
  - setId
```
public int setId(java.lang.String sid)
```
    Sets the value of the 'id' attribute of this Output.
    
    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.
    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, check, 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 exception to this rule is that for InitialAssignment, EventAssignment, AssignmentRule, and RateRule objects, the getId() function and the isSetId() functions (though not the setId() or unsetId() functions) would instead reference the value of the 'variable' attribute (for the rules and event assignments) or the 'symbol' attribute (for initial assignments). The AlgebraicRule fell into this category as well, though because it contained neither a 'variable' nor a 'symbol' attribute, getId() would always return an empty string, and isSetId() would always return false. For this reason, four new functions are now provided (getIdAttribute(), setIdAttribute(String), isSetIdAttribute(), and unsetIdAttribute()) that will always act on the actual 'id' attribute, regardless of the object's type. The new functions should be used instead of the old ones 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.
    Overrides:
    
    setId in class SBase
    
    Parameters:
    
    sid - the string to use as the identifier of this object.
    
    Returns:
    integer value indicating success/failure of the function. The possible values returned by this function are:
    
    LIBSBML_OPERATION_SUCCESS
    LIBSBML_INVALID_ATTRIBUTE_VALUE
    LIBSBML_UNEXPECTED_ATTRIBUTE
    See Also:
    
    SBase.getIdAttribute(), SBase.setIdAttribute(String sid), SBase.isSetIdAttribute(), SBase.unsetIdAttribute()
  - setQualitativeSpecies
```
public int setQualitativeSpecies(java.lang.String qualitativeSpecies)
```
    Sets the value of the 'qualitativeSpecies' attribute of this Output.
    Parameters:
    
    qualitativeSpecies - the value of the 'qualitativeSpecies' attribute to be set.
    
    Returns:
    integer value indicating success/failure of the function. The possible values returned by this function are:
    
    LIBSBML_OPERATION_SUCCESS
    LIBSBML_INVALID_ATTRIBUTE_VALUE
  - setTransitionEffect
```
public int setTransitionEffect(int transitionEffect)
```
    Sets the value of the 'transitionEffect' attribute of this Output.
    Parameters:
    
    transitionEffect - the value of the 'transitionEffect' attribute to be set.
    
    Returns:
    integer value indicating success/failure of the function. The possible values returned by this function are:
    
    LIBSBML_OPERATION_SUCCESS
    LIBSBML_INVALID_ATTRIBUTE_VALUE
  - setName
```
public int setName(java.lang.String name)
```
    Sets the value of the 'name' attribute of this Output.
    
    The string in name is copied.
    Overrides:
    
    setName in class SBase
    
    Parameters:
    
    name - the new name for the SBML object.
    
    Returns:
    integer value indicating success/failure of the function. The possible values returned by this function are:
    
    LIBSBML_OPERATION_SUCCESS
    LIBSBML_INVALID_ATTRIBUTE_VALUE
  - setOutputLevel
```
public int setOutputLevel(int outputLevel)
```
    Sets the value of the 'outputLevel' attribute of this Output.
    Parameters:
    
    outputLevel - int value of the 'outputLevel' attribute to be set.
    
    Returns:
    integer value indicating success/failure of the function. The possible values returned by this function are:
    
    LIBSBML_OPERATION_SUCCESS
    LIBSBML_INVALID_ATTRIBUTE_VALUE
  - unsetId
```
public int unsetId()
```
    Unsets the value of the 'id' attribute of this Output.
    
    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.
    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, check, 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 exception to this rule is that for InitialAssignment, EventAssignment, AssignmentRule, and RateRule objects, the getId() function and the isSetId() functions (though not the setId() or unsetId() functions) would instead reference the value of the 'variable' attribute (for the rules and event assignments) or the 'symbol' attribute (for initial assignments). The AlgebraicRule fell into this category as well, though because it contained neither a 'variable' nor a 'symbol' attribute, getId() would always return an empty string, and isSetId() would always return false. For this reason, four new functions are now provided (getIdAttribute(), setIdAttribute(String), isSetIdAttribute(), and unsetIdAttribute()) that will always act on the actual 'id' attribute, regardless of the object's type. The new functions should be used instead of the old ones 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.
    Overrides:
    
    unsetId in class SBase
    
    Returns:
    integer value indicating success/failure of the function. The possible values returned by this function are:
    
    LIBSBML_OPERATION_SUCCESS
    LIBSBML_OPERATION_FAILED
    See Also:
    
    SBase.getIdAttribute(), SBase.setIdAttribute(String sid), SBase.isSetIdAttribute(), SBase.unsetIdAttribute()
  - unsetQualitativeSpecies
```
public int unsetQualitativeSpecies()
```
    Unsets the value of the 'qualitativeSpecies' attribute of this Output.
    Returns:
    integer value indicating success/failure of the function. The possible values returned by this function are:
    
    LIBSBML_OPERATION_SUCCESS
    LIBSBML_OPERATION_FAILED
  - unsetTransitionEffect
```
public int unsetTransitionEffect()
```
    Unsets the value of the 'transitionEffect' attribute of this Output.
    Returns:
    integer value indicating success/failure of the function. The possible values returned by this function are:
    
    LIBSBML_OPERATION_SUCCESS
    LIBSBML_OPERATION_FAILED
  - unsetName
```
public int unsetName()
```
    Unsets the value of the 'name' attribute of this Output.
    
    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.
    Overrides:
    
    unsetName in class SBase
    
    Returns:
    integer value indicating success/failure of the function. The possible values returned by this function are:
    
    LIBSBML_OPERATION_SUCCESS
    LIBSBML_OPERATION_FAILED
    See Also:
    
    Output.getName(), Output.setName(String sid), Output.isSetName()
  - unsetOutputLevel
```
public int unsetOutputLevel()
```
    Unsets the value of the 'outputLevel' attribute of this Output.
    Returns:
    integer value indicating success/failure of the function. The possible values returned by this function are:
    
    LIBSBML_OPERATION_SUCCESS
    LIBSBML_OPERATION_FAILED
  - renameSIdRefs
```
public void renameSIdRefs(java.lang.String oldid,
                          java.lang.String newid)
```
    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.
    
    Overrides:
    
    renameSIdRefs in class SBase
    
    Parameters:
    
    oldid - the old identifier.
    
    newid - the new identifier.
  - getElementName
```
public java.lang.String getElementName()
```
    Returns the XML name of this object.
    
    Overrides:
    
    getElementName in class SBase
    
    Returns:
    
    the name of this element.
  - getTypeCode
```
public int getTypeCode()
```
    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_. In the Java language interface for libSBML, the type codes are defined as static integer constants in the interface class libsbmlConstants. 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.
    
    Overrides:
    
    getTypeCode in class SBase
    
    Returns:
    
    the SBML type code for this object: SBML_QUAL_OUTPUT
    
    See Also:
    
    Output.getElementName(), SBase.getPackageName()
    
    "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 getTypeCode() and getPackageName().
  - hasRequiredAttributes
```
public boolean hasRequiredAttributes()
```
    Predicate returning true if all the required attributes for this Output object have been set.
    Overrides:
    
    hasRequiredAttributes in class SBase
    
    Returns:
    
    a boolean value indicating whether all the required attributes for this object have been defined.
    
    "Note:"
    The required attributes for a Output object are:
    
    'qualitativeSpecies'
    'transitionEffect'

Class Output

Constructor Summary

Method Summary

Methods inherited from class org.sbml.libsbml.SBase

Methods inherited from class java.lang.Object

Constructor Detail

Output

Output

Output

Output

Output

Output

Method Detail

delete

cloneObject

getId

getQualitativeSpecies

getTransitionEffect

getName

getOutputLevel

isSetId

isSetQualitativeSpecies

isSetTransitionEffect

isSetName

isSetOutputLevel

setId

setQualitativeSpecies

setTransitionEffect

setName

setOutputLevel

unsetId

unsetQualitativeSpecies

unsetTransitionEffect

unsetName

unsetOutputLevel

renameSIdRefs

getElementName

getTypeCode

hasRequiredAttributes