Available translations

Trading Bot Instance and Trading Sessions

foundations.png
Summary: The Trading Bot Instance may run four different types of trading tasks: Backtesting Session, Paper Trading Session, Forward Testing Session, and Live Trading Session.
Foundations->Node->Trading Bot Instance->Definition
trading-bot-instance.png
A trading bot instance is a reference to the Trading Bot as defined in the Masters Trading Mine. The instance of the bot runs the defined processes and generates the defined data products.
Foundations->Node->Trading Bot Instance->Content
The trading bot instance holds no definitions as to what the bot does. Instead, its process instance references the process definition in the Masters data mine. That is how the indicator bot instance obtains the information of what it needs to do once it is run.
Foundations->Concept->Reusable Snippets->Note for Hierarchy Tables
Trading Process Instance
Foundations->Node->Trading Process Instance->Definition
trading-process-instance.png
A trading process instance is a reference to the process definition of the trading bot, as defined in the Masters data mine.
Foundations->Node->Trading Process Instance->Content
The trading process instance must reference the Multi-Time-Frame process definition of the Jason trading bot in the Masters data mine.
Backtesting Session
Foundations->Node->Backtesting Session->Definition
backtesting-session.png
A backtesting session is a trading mode by which the trading bot instance reads historic market data in a user-defined datetime range, applies the rules defined in the associated trading system, and generates a trading simulation.
Foundations->Node->Backtesting Session->Content
A backtesting session node must reference a trading system to gain access to the trading logic to be applied during the session. Other considerations framing the session come from the set of parameters attached to it.
Paper Trading Session
Foundations->Node->Paper Trading Session->Definition
paper-trading-session.png
A paper trading session is a trading mode by which the trading bot instance reads a live market data feed, applies the rules defined in the associated trading system, and generates a trading simulation.
Foundations->Node->Paper Trading Session->Content
A paper trading session node must reference a trading system to gain access to the trading logic to be applied during the session. Other considerations framing the session come from the set of parameters attached to it.
Forward Testing Session
Foundations->Node->Forward Testing Session->Definition
forward-testing-session.png
A forward testing session is a trading mode by which the trading bot instance performs live trading with a user-defined fraction of the available capital.
Foundations->Node->Forward Testing Session->Content
A forward testing session node must reference a trading system to gain access to the trading logic to be applied during the session. Other considerations framing the session come from the set of parameters attached to it.
Foundations->Concept->Reusable Snippets->Important for Live Sessions
Live Trading Session
Foundations->Node->Live Trading Session->Definition
live-trading-session.png
A live trading session is a trading mode by which the trading bot instance reads a live market data feed, applies the rules as defined in the associated trading system, places the corresponding orders at the associated exchange, and stores the defined data products.
Foundations->Node->Live Trading Session->Content
A live trading session node must reference a trading system to gain access to the trading logic to be applied during the session. Other considerations framing the session come from the set of parameters attached to it.
Foundations->Concept->Reusable Snippets->Important for Live Sessions
Execution Started Event
Foundations->Node->Execution Started Event->Definition
execution-started-event.png
The execution started event is the event that triggers the execution of a process. It usually references the execution finished event of another process on which the process depends on.
Foundations->Node->Execution Started Event->Content
These references determine when a process is due for another run. By listening to the execution finished event of the process it depends on, it may wake up just in time to process the new batch of data the dependency has just delivered.
Bots form a sort of multi-branched execution sequence with an indeterminate number of dependencies. Every time the bot further down the tree of dependencies finishes a cycle, it triggers the execution of multiple bots listening to its execution finished event.
In the context of a trading process instance running a trading session on the network hierarchy, the execution started event may be used to force the trading process to run only after the last indicator bot dependency finishes its job. This guarantees that all dependencies are up to date and that the trading bot will evaluate the information corresponding to the same candles for all indicators used by the trading system.
Not setting up this event on a trading session may result in eventual data inconsistencies, as—in theory—the trading bot may run with some indicators up to date and some slightly delayed.
Previous
Production Trading Tasks Section
Next
Trading Session References