Available translations
loading results
Indicator and Sensor Bot Instances
Summary: Data tasks may run instances of Indicator Bots or Sensor Bots, and some exchange may require an API key for downloading certain kinds or amounts of data. We will look into each of these cases.
Indicator Bot Instance
Foundations->Node->Indicator Bot Instance->Definition
An indicator bot instance is a reference to an Indicator Bot as defined in a data mine. The instance of the bot runs the defined processes and generates the defined data products.
Foundations->Node->Indicator Bot Instance->Content
The indicator bot instance holds no definitions as to what the bot does. Instead, its processes instances reference the process definitions in the corresponding Data Mine. That is how the indicator bot instance obtains the information of what it needs to do once it is run.
Indicator Process Instance
Foundations->Node->Indicator Process Instance->Definition
An indicator process instance is a reference to the process definition of an indicator bot, as defined in a data mine.
Foundations->Node->Indicator Process Instance->Content
Indicator bot instances usually require two indicator process instances. One of them references the indicator's Multi-Time-Frame-Market process definition and the second references the Multi-Time-Frame-Daily process definition.
Once the reference is established, the indicator process instance adopts the name of the process definition it references.
Time Frames Filter
Foundations->Node->Time Frames Filter->Definition
The time frame filters node allows control over which time frames are to be calculated by each indicator bot instance running on the data mining operation.
Foundations->Node->Time Frames Filter->Content->
Limiting the number of time frames calculated by any given indicator to the few that may be required by a particular trading system has a significant positive impact on performance: it reduces the load on the CPU, the memory requirements, and the requirements of storage space, in proportion with the time frames you remove.
When a time frames filter is set up, a Time.Frames.json file is created by the indicator process in the corresponding output folder. This file is read by others—such as the charting system—to get the information regarding which time frames are available and which are not, to avoid reporting errors.
Important: Before applying a time frames filter or changing the configuration, that is, changing which time frames are produced and which are not, it is highly recommended to delete the data corresponding to the affected indicator, to avoid inconsistencies in the data that may later cause confusion.
Note: When no time frames filter is defined, the bot processes all time frames by default.
Sensor Bot Instance
Foundations->Node->Sensor Bot Instance->Definition
A sensor bot instance is a reference to a Sensor Bot as defined in a data mine. The instance of the bot runs the defined processes and generates the defined data products.
Foundations->Node->Sensor Bot Instance->Content
The sensor bot instance holds no definitions as to what the bot does. Instead, its process instance references a process definition in the corresponding data mine. That is how the sensor bot instance obtains the information regarding what it needs to do once it is run.
Sensor Process Instance
Foundations->Node->Sensor Process Instance->Definition
A sensor process instance is a reference to the process definition of a sensor bot, as defined in a data mine.
Foundations->Node->Sensor Process Instance->Content
For example, in the case of an instance of the Masters data mine Exchange Raw Data sensor bot, the bot process instance references the Historic OHLCVs process definition. Once the reference is established, the sensor process instance adopts the name of the process definition it references.
Key Reference
Foundations->Node->Key Reference->Definition
The key reference is a reference to an exchange account key as defined in a specific user account, in a specific exchange, on the Crypto Ecosystem hierarchy.
Foundations->Node->Key Reference->Content
Usually, exchanges require authentication via your exchange account key for monetary transactions only. However, some exchanges may require autentication in other contexts as well, for instance, to retrieve information above a certain quota, or to retrieve raw trades data instead of OHLCV data.
For those reasons, exchange key references are available both in the context of data mining and trading operations, and are always attached to the corresponding task.
Forward testing and live trading sessions always require setting up key references, as that is the kind of scenario in which the user must validate with the exchange.
In all cases, the key reference node must reference a valid exchange account key from an account with the exchange, as defined in the Crypto Ecosystem hierarchy.
Important: Most exchanges do not allow the same exchange account key to be used with multiple processes querying the exchange API. This means that if you are trading with multiple trading systems or multiple sessions on the same exchange, each session requires different exchange account keys.
LAN Network — TOC
You just read page 4 in the topic.
4. Indicator and Sensor Bot Instances
5. Testing Trading Tasks Section
6. Production Trading Tasks Section
7. Trading Bot Instance and Trading Sessions
12. Trading Mines Data Section