Available translations

Trading Engine

trading-engine.png
The trading engine hierarchy is the data structure used by the trading bot to keep runtime information highly accessible and exposed to others.
Content
You will use this hierarchy for two main purposes:
  • To let your trading systems access the information processed by the trading bot. This allows strategies to keep track of and react to current and past events—including those involving the exchange, such as orders placed or filled—as the bot is running.
  • To keep track of the actions of the trading bot via the design space visual environment and panels over the charts. By analyzing runtime information, you may gain a detailed understanding of what happens, when, and why, throughout a trading session.
Frequently Asked Questions
Can a Trading Engine be shared between two Trading Bots?
The same trading engine can be used from multiple trading sessions, because it is just a node-based representation of a data structure.
Every time a Task is ran, a snapshot of that data structure, together with a snapshot of the Network and the Bots definitions at their Data Mine is sent from the UI to the Task Server, and from there is consumed by the running Bot. That means that a second Bot can receive the same Trading Engine snapshot and it will never know if other bots were fed with the same information or not.
Do I need to change something at the Trading Engine?
You don't need to physically change anything inside trading engine via the UI. The trading engine is a visual representation of the data structure that the trading system uses to store its values, so to speak.
Can I change the values inside the Trading Engine?
You access the Trading Engine from within your trading system if there is something in there you would like to change. This is the whole purpose of the User Defined Code node.
Trading Engine Menu
The Trading Engine node has the following Node Menu items:
The Add Missing Children menu item has the following properties:
  • action: Add Missing Children
  • label: Add Missing Children
  • relatedUiObject: Trading Engine
  • actionFunction: payload.executeAction
  • actionProject: Visual-Scripting
  • relatedUiObjectProject: Algorithmic-Trading
The Delete menu item has the following properties:
  • action: Delete UI Object
  • actionProject: Visual-Scripting
  • askConfirmation: true
  • confirmationLabel: Confirm to Delete
  • label: Delete
  • iconPathOn: delete-entity
  • iconPathOff: delete-entity
  • actionFunction: payload.executeAction
Trading Engine Children
The Trading Engine node has the following childrenNodesProperties:
The Trading Current node property features the following properties:
  • name: tradingCurrent
  • type: node
  • autoAdd: false
  • project: Foundations
The Trading Last node property features the following properties:
  • name: tradingLast
  • type: node
  • autoAdd: false
  • project: Foundations
The Exchange Orders node property features the following properties:
  • name: exchangeOrders
  • type: node
  • autoAdd: false
  • project: Foundations