Before you continue with the next steps, a quick explanation is in order. What you will do now involves installing markets in network manager node to later move the specific tasks to each node on the network.
When you install a market, several structures of nodes are created in each of the main sections of the network manager node: data storage, data mining, testing environment, and production environment. Each set of tasks is grouped by exchange under the corresponding exchange tasks node.
If you are planning to set up a large network of nodes, it is recommended to install the first set of markets, distribute the corresponding tasks among the appropriate nodes in the network, and run a few tests before moving forwards. You may repeat this process as many times as required.
Start Here
1. Install markets. In your network manager node, install the first few markets you wish to work with. For example, let’s say you wish to run data mining operations for the BTC/USDT, ETH/USDT, and ETH/BTC markets on Binance in your Machine 01 network node. Then, install those three markets on the network manager node.
Click to learn how to install a new market
| In brief: To install a new market, click Run on the install market super action corresponding to the market you wish to install. If the market is not set up, then you must set it up first. |
If the market is set up in your preferred exchange, click Run on the corresponding install market super action node menu.
1. Expand the exchange markets node of your preferred crypto exchange in the crypto ecosystem hierarchy.
Click to learn how to find a hierarchy
| In brief: To find a hierarchy, access the design space map with a right-click of the mouse, and left-click on your desired destination. |
The image illustrates points 1 and 2 below.
1. Access the design space map.
Right click anywhere on the design space to access the design space map.
2. Left-click on your desired destination.
That should take you to the exact point you clicked on the map.
For your information, the design space is organized over a square perimeter around the workspace node, and each hierarchy is located on one of the cardinal directions. Hierarchies feature an ever-present white ring. The ring hints the direction in which a hierarchy is located.
| Hierarchy | Cardinal Direction | Direction | Keyboard Shortcut (Windows only) |
|---|---|---|---|
| Sparta Data Mine | North | ↑ | Ctrl + Alt + S (S for Sparta) |
| BRR trading System | North East | ↗ | Ctrl + Alt + W (W for Weak Hands Buster) |
| WHB Trading System | East | → | Ctrl + Alt + B (B for Bull Run Rider) |
| Super Scripts | South East | ↘ | Ctrl + Alt + Z (Z for, well…) |
| Network | South | ↓ | Ctrl + Alt + N (N for Network) |
| Crypto Ecosystem | South West | ↙ | Ctrl + Alt + E (E for Ecosystem) |
| Charting System | West | ← | Ctrl + Alt + C (C for Charting System) |
| Masters Data Mine | North West | ↖ | Ctrl + Alt + M (M for Masters) |
2. Click Run on the Install Market super action node menu corresponding to the market you wish to install.
Running the super action deploys all the infrastructure required to start using the new market, including the following:
-
Data storage structures of nodes.
-
Data mining operation for the corresponding exchange and market.
-
Testing environment and production environment task managers featuring tasks for all types of trading sessions referencing the Weak-hands Buster trading system. You may change the reference for any other trading system you may be using.
-
A time machine containing a timeline chart for the market, made readily available on the charting space.
2. Move data mining tasks and data storage session independent data. Data mining tasks work together with definitions in the data storage section of the network hierarchy, in particular, the so-called session independent data. Therefore, wherever you decide to run each specific data mining task, the associated session independent data must go with it too.
The easiest way to transfer the data mining and data storage definitions to the remote network node is to do it at the level of the exchange tasks node in case of data mining tasks, and at the level of the exchange data products node in the case of data storage session independent data.
Continuing with the example started on the previous step, this is what you would do:
A. Detach the Binance exchange tasks node from the data mining section of the network manager node and attach it to the data mining section of the Machine 01 network node.
Moving a data mining tasks to Node 01.
B. Detach the Binance exchange data products node from the session independent data node of the data storage section of the network manager node and attach it to the session independent data node of the data storage section of the Machine 01 network node.
Moving exchange data products to Node 01.
That’s it! Your data mining operation for those three markets will now run on Machine 01.
3. Test the operation. You may now test the data mining operation on Machine 01. Click Run on the Binance exchange tasks node and wait a few seconds. The tasks should start processing. Once the sensor bots instances for each market reach 100%, you may log in to Machine 01 to verify that the data files are being created as expected.
4. Move trading sessions and data storage session dependent data. You will likely want to run trading sessions from a third machine. Trading session tasks work together with definitions in the data storage section of the network hierarchy, in particular, the so-called session based data. Therefore, wherever you decide to run each specific trading session task, the associated session based data must go with it too.
The easiest way to transfer trading session tasks and data storage definitions to the remote network node is to do it at the level of the exchange tasks node in case of trading session tasks, and at the level of the exchange sessions node in the case of data storage session based data.
Continuing with the example started earlies, this is what you would do:
A. Move the Binance exchange tasks node in the production environment of the network manager node to the production environment of Machine 02, the third machine. You may set exchange keys and reference the appropriate trading systems at any point, either before or after moving the tasks.
Moving a trading sessions tasks to Node 02.
B. Move the Binance exchange sessions node from the session based data node of the data storage section of the network manager node to the session based data node of the data storage section of the Machine 02 network node.
Moving exchange sessions to Node 02.
5. Test the operation. Once the data mining operation is running up to date, at 100%, you may test your trading sessions on Machine 2.
Notice that moving the data structures at the level of the exchange tasks node and the exchange data products node is the easiest way to do it. If you wish to move individual tasks in the same exchange to different machines, you may need to manually create the exchange tasks node or exchange data products node in some of the machines. If you do that, remember you need to establish a reference from those nodes to the corresponding crypto exchange node in the Crypto Ecosystem hierarchy.
Also worth noting is that you may also move data structures at the level of the task manager node, and up to the task node itself. A task is the smallest unit you may move to a node in the network. Bear in mind that if you move task managers or tasks, you will need to move the specific single market data nodes and the specific session reference nodes for data mining and trading session tasks repectively.