Available translations

Testing Trading Tasks Section

Summary: The testing environment organizes your strategy-testing resources, grouping tasks and associated backtesting and paper trading sessions
Foundations->Node->Testing Trading Tasks->Definition
The Testing Trading Tasks node organizes trading sessions involving testing of trading systems.
Foundations->Node->Testing Trading Tasks->Content
Thorough and comprehensive testing of strategies is at the core of successful trading. Superalgos strives to put you in control of the testing process providing you with flexible tools to fit your criteria.
Depending on how you use the system, how many markets and exchanges you work with, the number of trading systems you use, or the way you choose to test your strategies, you may find yourself with a large number of testing sessions. As explained in the sorting of tasks page, the testing environment helps you organize large numbers of tasks sorting them by exchange, market, and trading mine.
Superalgos handles two types of simulated tests: backtesting and paper trading. Backtesting involves testing over historic data, while paper trading is about testing on a live data stream, but without placing orders at the exchange.
Trading sessions are controlled by a number of parameters that determine how the session is run. The built-in parameters provide great control and flexibility as to how to handle data sets and how to produce the resulting simulations.
Foundations->Concept->Reusable Snippets->Deleting Node Warning
Foundations->Concept->Reusable Snippets->Note for Hierarchy Tables
Project Trading Tasks
Foundations->Node->Project Trading Tasks->Definition
The Project Trading Tasks node is an organizational device grouping all Trading Tasks corresponding to the same Project.
Foundations->Node->Project Trading Tasks->Content
Exchange Trading Tasks
Foundations->Node->Exchange Trading Tasks->Definition
The exchange trading tasks node organizes trading tasks by exchange. That is, each exchange installed in the system has an exchange trading tasks node grouping all market trading tasks corresponding to the said exchange.
Foundations->Node->Exchange Trading Tasks->Content
The exchange trading 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 trading tasks icon is replaced by the exchange's logo.
Market Trading Tasks
Foundations->Node->Market Trading Tasks->Definition
A market trading tasks node groups trading tasks operating in a specific market.
Foundations->Node->Market Trading Tasks->Content
The market trading tasks node must reference a market defined in the Crypto Ecosystem hierarchy.
This node may spawn individual data products or may deploy data products in bulk organized by data mine and by bots. See the data products node for the details.
Trading Mine Tasks
Foundations->Node->Trading Mine Tasks->Definition
The trading mine tasks node is an organizational device that groups tasks corresponding to the referenced trading mine.
Foundations->Node->Trading Mine Tasks->Content
The market trading 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.
A task is the device used to control bot instances, that is, to start and stop bots, including sensors, indicators and the trading bot.
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.
Trading tasks run instances of the Trading Bot, which may run four different types of trading sessions. We shall study those in the next few pages.
Indicator and Sensor Bot Instances
Production Trading Tasks Section