The data storage structure of nodes within the network hierarchy controls where and how the bots you run store the data they produce.
Session-based data refers to data that is generated as a consequence of running a trading session, that is, data the trading bot instance generates while running backtesting, paper trading, forward testing, or live trading sessions.

As explained in the sorting of tasks page, trading mines data is sorted by exchange, market, the corresponding trading session, and the corresponding trading mine, trading bot, and bot product. That is, most of the nodes in this section of the hierarchy play an organizational role.

Many of them require references to the nodes that delimit the context for which the data is applicable. For example, the exchange trading products node must reference one of the installed exchanges, in particular, the exchange on which the trading operation is run. These references help other entities understand the context to which the data belongs to.

Whenever you create trading tasks manually from within the Network hierarchy (as opposed to using the install market function under the exchange markets node of the Crypto Ecosystem hierarchy), you need to create the proper definitions for the storage of trading mines data.


Trading Mines Data

Exchange Trading Products

Market Trading Products

Session Reference

Trading Mine Products

Bot Products

Data Product Folder

Data Product

Data Product

Exchange Trading Products

The exchange trading products node organizes trading mines data by exchange. That is, each exchange installed in the system has an exchange trading products node grouping all session references corresponding to the said exchange.

The exchange trading products 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 products icon is replaced by the exchange’s logo.

Click to learn more about exchange trading products

Adding an Exchange Trading Products Node

To add a specific exchange trading products node, select Add Exchange Trading Products on the parent node menu.

You may also add exchange trading products nodes in bulk for all exchanges that may have been previously defined in the Crypto Ecosystem hierarchy. To do that, select Add Missing Exchanges on the trading mines data node menu. An exchange trading products node is created for each defined exchange, each with the corresponding reference.

Market Trading Products

A market trading products node features the group of data products generated by the referenced session in a specific market.

The market trading products 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 trading mine and by trading bots. See the data products node for the details.

Click to learn more about market trading products

Adding a Market Trading Products Node

To add a market trading products node, select Add Market Trading Data on the parent node menu.

Session Reference

A session reference establishes which session is the one which shall store data in the current location.

A such, the session reference node must establish a reference with a trading session. Also, its offspring nodes determine precisely which data products are stored.

Click to learn more about session references

Adding a Session Reference Node

To add a session reference node, select Add Session Reference on the network node menu.

You may also add session reference nodes in bulk for all sessions defined in the same network that are not yet defined. To do that, select Add Missing Sessions on the exchange trading products node menu. A session reference node is created for each defined trading session in the node, each with the corresponding reference.

Trading Mine Products

Trading mine products are references established with trading mines to facilitate establishing data product references with multiple products in the given mine.

At this point, Superalgos ships with a single trading mine, featuring a single low frequency trading bot. However, developers may create their own trading bots or fork the existing one.

The node may be used as an organizational device, simply to arrange bot products. However, the smart use of the node involves automating the deployment of multiple data products.

The use of the trading mine products node is optional, as data products may also exist outside of trading mine products nodes.

Click to learn more about trading mine products

Adding a Trading Mine Products Node

To add a trading mine products node, select Add Trading Mine Products on the parent node menu. This action adds the node but does not establish a reference with any trading mine.

The smarter use of the node involves using the Add All Trading Mine Products option on the parent node menu. This action creates a trading mine products node for each trading mine in the workspace, establishing a reference with the corresponding trading mines. This is the first step in the direction of quickly setting up multiple data products when needed.

Bot Products

A bot products node is an organizational device used to arrange data products corresponding to a specific bot.

The device exists as an offspring of a data or trading mine products node, and does not require a reference to a bot in the given data or trading mine.

The use of the bot products node is optional, as data products may also exist outside of bot products.

Click to learn more about bot products

Adding a Bot Products Node

To add a bot products node, select Add Bot Products on the parent node menu.

The bot products node may also be created automatically. When created using the Add All Data Products option on the data mine products node, the node inherits the label of the corresponding bot in the corresponding data mine.

Data Product Folder

A data product folder node is an organizational device used to map the arrangement of product definition folders as may exist in the bot definition of the corresponding data or trading mine.

The use of the data product folder node is optional, as data products may also exist outside of data product folders.

Click to learn more about data product folders

Adding a Data Product Folder Node

To add the data product folder node, select Add Data Product Folder on the parent node menu.

Data Product

A data product represents the collection of datasets generated by the instance of a bot as defined in the corresponding data mine or trading mine.

Data products exist in the context of trading mines data and data mines data nodes. In the first case, a data product is the collection of datasets generated by an instance of a trading bot as defined in a trading mine, running a trading session. In the latter case, it is the collection of datasets generated by either a sensor bot or an indicator bot instance, as defined in a data mine, and running a data mining task.

A data product node must reference a product definition in the corresponding bot.

Click to learn more about data products

Adding a Data Product Node

To add a single data product, select Add Data Product on the market trading products, market data products, bot products, or data products folder node menus.

In cases in which multiple data products must be added, you may use the option to create data products in bulk.

Select the Add All Data Products option on the data or trading mine products node menu. This adds a bot products node for each bot in the data or trading mine, and a data product for each product definition of each bot.

You may use this option after manually adding a data or trading mine products node and manually establishing the reference with the desired data mine, or after adding all data or trading mine data products, by which the references with data or trading mines are established automatically.