Available translations
loading results
Data Tasks Section
Summary: The Data Tasks structure of nodes controls the bots you need to run to extract data from exchanges and process it into indicators or technical studies.
Foundations->Node->Data Tasks->Definition
Data tasks referes to data-mining, that is, the activity of processing data. You need to process data to feed charts, and so that your trading systems may make decisions based on quality information.
Foundations->Concept->Reusable Snippets->Note for Hierarchy Tables
Note: This page discusses the top-level information about the section of the hierarchy represented in the below table. Click on any of the nodes to get the details, including particulars on their configuration, when applicable.
|  | | | | | | | ||
 |
| | | | | | | ||
| |
| | | | | | ||
| | |
| | | | | ||
| | | |
| | | | ||
| | | | |
| | | ||
| | | | | |
| |
Project Data Tasks
Foundations->Node->Project Data Tasks->Definition
The Project Data Tasks node is an organizational device grouping all Data Tasks corresponding to the same Project.
Exchange Data Tasks
Foundations->Node->Exchange Data Tasks->Definition
The exchange data tasks node organizes data mining tasks by exchange. That is, each exchange installed in the system has an exchange data tasks node grouping all market data tasks corresponding to the said exchange.
Foundations->Node->Exchange Data Tasks->Content
The exchange data tasks node must reference the exchange of choice. This reference constraints the rest of the definitions to the context of the said exchange.
When representing an exchange featured in the system's icons library, the standard exchange data tasks icon is replaced by the exchange's logo.
Data Mine Tasks
Foundations->Node->Data Mine Tasks->Definition
The data mine tasks node is an organizational device that groups tasks corresponding to the referenced data mine.
Foundations->Node->Data Mine Tasks->Content
The data mine tasks node must reference the definition of a data mine. The node may spawn tasks for each bot in the data mine.
Task Manager
Foundations->Node->Task Manager->Definition
A task manager is a device used to organize and control any number of tasks, which, in turn, control bot instances. You use a task manager to start or stop several tasks at the same time.
Foundations->Node->Task Manager->Content
Task managers are used both in the context of data mining and trading operations, to facilitate the organization of tasks.
For example, you may set up a task manager to handle tasks related to a particular set of indicators used with a certain strategy. Or, for example, to organize multiple backtesting sessions.
Tip: The key aspect of a task manager is that it allows starting and stopping all tasks at once.
Task
Foundations->Node->Task->Definition
A task is the device used to control bot instances, that is, to start and stop bots, including sensors, indicators and the trading bot.
Foundations->Node->Task->Content
Each task controls a single bot. A bot instance running on its own task is independent from other bots at the operating system level, thus, may not be affected by errors ocurring on those other bots.
When a task is started, the process instance of the bot instance attached to the task is started. Also, a visual indication that both the task and the process instance are running appear surrounding the corresponding nodes, in the form of a progress ring.
Data tasks may run instances of Indicator Bots or Sensor Bots. We'll cover those two in the next page. Some exchanges may require an API key for downloading certain kinds or amounts of data. Let's look into the Key Reference node.
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 3 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