Available translations

Data Mining - Status Dependencies

foundations.png
Summary: Status Dependencies are another type of relationship between Bots. Sometimes bots don't depend on the Datasets produced by other bots, but they depend directly on the status of other bots.
Status Dependency Tree
Status dependencies operate using the same idea of a tree as execution and data dependencies. Any Bot can have from zero to many status dependencies. For each Status Dependency, the Bot's process at runtime will load the Status Report file of the dependent Bot and will extract from there the information it needs.
A good way to undestand why Status Dependencies are needed is with an example:
The Indicator Bot Bollinger-Bands depends on Candles-Volumes Dataset in order to calculate the Bollinger Bands, but it depend's on Exchange Raw Data Sensor Bot in order to know where the market begins, which is the date of the first piece of data. That information is part of the Status information that Exchange Raw Data Sensor Bot keeps at it's Status Report.
Classification by Utility
A Status Dependency can be classified by it's utility. This makes it easier for processes to handle them in code. There are currently three different utilities:
  • Self Reference: this is used to load a bot's Status Report to extract data from it or modify it.
  • Market Starting Point: this means that the referenced Status Report is to be used to extract the information of where the market begins.
  • Market Ending Point: this means that the referenced Status Report is to be used to extract the information of where the market ends, meaning which date the market ends.
Previous
Data Mining - Status Reports
Next
Data Mining - Deployments