libAntimony  2.8
enums.h File Reference

Various enums used both in the API and internally in libAntimony. More...

Go to the source code of this file.

Enumerations

enum  rd_type {
  rdBecomes = 0, rdActivates, rdInhibits, rdInfluences,
  rdBecomesIrreversibly
}
 rd_types are the different types of reactions and interactions. More...
 
enum  var_type {
  varSpeciesUndef = 0, varFormulaUndef, varDNA, varFormulaOperator,
  varReactionGene, varReactionUndef, varInteraction, varUndefined,
  varModule, varEvent, varCompartment, varStrand,
  varUnitDefinition, varDeleted, varConstraint
}
 var_types define internally what a symbol is; they are not used in the API anywhere. More...
 
enum  return_type {
  allSymbols = 0, allSpecies, allFormulas, allDNA,
  allOperators, allGenes, allReactions, allInteractions,
  allEvents, allCompartments, allUnknown, varSpecies,
  varFormulas, varOperators, varCompartments, constSpecies,
  constFormulas, constOperators, constCompartments, subModules,
  expandedStrands, modularStrands, allUnits, allDeleted,
  allConstraints
}
 return_types are used in the API when requesting information about different symbols. More...
 
enum  const_type { constDEFAULT = 0, constVAR, constCONST }
 const_type values are not used in the API, but are used internally in libAntimony. More...
 
enum  formula_type {
  formulaINITIAL = 0, formulaASSIGNMENT, formulaRATE, formulaKINETIC,
  formulaTRIGGER
}
 rule_type values are not used in the API, but are used internally in libAntimony. More...
 
enum  deletion_type {
  delFull = 0, delEventPriority, delEventDelay, delEventAssignment,
  delRateRule, delInitialAssignment, delAssignmentRule, delReactant,
  delProduct, delKineticLaw, delModifier, delInteraction
}
 deletion_type values are not used in the API, but are used internally in libAntimony. More...
 
enum  distribution_type {
  distUNKNOWN = 0, distNORMAL, distTRUNCNORMAL, distUNIFORM,
  distEXPONENTIAL, distTRUNCEXPONENTIAL, distGAMMA, distTRUNCGAMMA,
  distPOISSON, distTRUNCPOISSON
}
 distribution_type values are used to determine which distribution defined in UncertML is being used.
 
enum  constraint_type {
  constNONE = 0, constGT, constLT, constEQ,
  constGEQ, constLEQ, constNEQ
}
 constraint_type values are used to determine what kind (and whether) of a simple constraint is being defined.
 

Detailed Description

Various enums used both in the API and internally in libAntimony.

Author
Lucian Smith

Enumeration Type Documentation

enum const_type

const_type values are not used in the API, but are used internally in libAntimony.

Every symbol starts off being constDEFAULT, which means that the model never stated explicitly whether the symbol was to be constant or variable, so the program will use a heuristic to determine which is the case. Once set, the heuristic is ignored, and the type (constVAR for variable symbols, constCONST for constant ones) is permanent. Not all symbols can actually be variable or constant (for example, submodules and reactions), so attempts to set this value for those symbols will fail.

deletion_type values are not used in the API, but are used internally in libAntimony.

When a variable is deleted in Antimony, the elements it appears in may also need to be deleted. This allows 'partial' deletion of SBML elements, so (for example) if a species is deleted, it disappears from all reactions it used to appear in.

rule_type values are not used in the API, but are used internally in libAntimony.

Every symbol starts off with a default type based on its type (most things are formINITIAL; reactions are formKINETIC, and events are formTRIGGER), and those symbols that aren't reactions, events, or modules may be formASSIGNMENT (for those symbols that have assignment rules) or formRATE (for those symbols that have rate rules). formASSIGNMENT symbols have only one formula, but formRATE have two: one for their initial condition, and one for how it changes with time.

enum rd_type

rd_types are the different types of reactions and interactions.

  • rdBecomes: A reversible reaction: -> or <=>
  • rdActivates: An activation interaction: -o
  • rdInhibits: An inhibition interaction: -|
  • rdInfluences: A generic interaction: -(
  • rdBecomesIrreversibly: An irreversible reaction: '=>'

return_types are used in the API when requesting information about different symbols.

Each return_type refers to a different group of symbols, and are overlapping–i.e. a single symbol can be included in 'allGenes' and 'allReactions'.

  • allSymbols: Every symbol of every type in Antimony
  • allSpecies: All species, both const (border) and variable.
  • allFormulas: All formulas (values defined by an equation), both const and variable.
  • allDNA: All symbols defined to be DNA (operators and genes, but not strands).
  • allOperators: All symbols defined to be operators (formulas embeddable in a DNA strand).
  • allGenes: All symbols defined to be genes (reactions embeddable in a DNA strand).
  • allReactions: All reactions (species being converted or created).
  • allInteractions: All interactions (species involved in reaction rates).
  • allEvents: All events.
  • allCompartments: All compartments, both const and variable.
  • allUnknown: All symbols whose type has never been defined or used.
  • varSpecies: Variable species.
  • varFormulas: Formulas (equations) that can change (including as a result of events).
  • varOperators: Operators with variable values.
  • varCompartments: Compartments with variable sizes.
  • constSpecies: Constant species (aka 'border species').
  • constFormulas: Formulas with constant values.
  • constOperators: Operators with constant values.
  • constCompartments: Compartments with constant sizes.
  • subModules: Submodules used within the current module.
  • expandedStrands: DNA strands containing nothing but operators and genes–any sub-strands have been expanded to their component DNA objects, and those sub-strands are not included in any lists.
  • modularStrands: All defined DNA strands, with some being subparts of the others.
  • allUnits: All unit definitions.
  • allDeleted: All submodel elements that have been deleted from the containing model.
enum var_type

var_types define internally what a symbol is; they are not used in the API anywhere.

But for the curious, they are:

  • varSpeciesUndef: Generic species
  • varFormulaUndef: Generic formula (reaction rate, constant, etc.)
  • varDNA: A DNA element
  • varFormulaOperator: A DNA element that only has a formula associated with it (an operator)
  • varReactionGene: A DNA element that has a reaction associated with it (a gene)
  • varReactionUndef: A generic reaction
  • varInteraction: A generic interaction
  • varUndefined: A symbol that was used somewhere (like in a formula) that has no other definition.
  • varModule: A submodule
  • varEvent: An event
  • varCompartment: A compartment
  • varStrand: A DNA strand (an ordered list of DNA elements)
  • varUnitDefinition: A unit definition.
  • varDeleted: A deleted submodel element
  • varConstraint: A constraint (either an FBC constraint or a 'normal' constraint)