Engine

Types

engine $tType

Does work within a CoreSense agent to produce modelets.

• Takes multiple modelets as an input modelet_set
• Uses semantic information to identify valid input modelet formalisms
  • semantics could be external (part of the type definition) or internal (modeled within the modelet itself)
• Produces one output modelet
  • May or may not impart semantic meaning to the output modelet
  • May (re)define the output modelet origin, concept, or characteristics
• Has exertion characteristics
  • e.g. time delay, resource usage, power consumption

Example

• DroneStateEngine (see tff/tests/test-wind-estimation.tff)
  • Input Model:
    • Modelet
      • formalism: IMU.msg
      • modelled concept: inertia
    • Modelet
      • formalism: NavSatFix.msg
      • modelled concept: geolocation
  • Output Modelet:
    • modelet
      • formalism: DroneState.msg
      • modelled concept: drone_state

Source: engines-and-modelets.tff

Relations

interface_of (engine>template_set)

An engine requires a set of input modelets which matches the template_set.

Source: engines-and-modelets.tff

output_modelet_formalism (engine>formalism)

The formalism of an engine output modelet.

Source: engines-and-modelets.tff

is_output_modelet_concept (engine>phenomenon)

The concept of an engine output modelet.

Source: engines-and-modelets.tff

output_property_of_engine (engine>property)

The property an engine imparts on its output modelet.

Source: properties.tff

engine_imparts_representation_class (engine>representation_class)

The representation_class an engine imparts on its output modelet.

Source: engines-and-modelets.tff