- Fundamental Concepts
- ADL Learning Guide
- Basic Blocks
- Trading Blocks
- Discrete Blocks
- Round Block
- Display To Decimal Block
- Formula Block
- Average Block
- Stopwatch Block
- Clock Block
- Note Block
- Random Number Block
- Pause Block
- Log Block
- IsNumber Block
- Once True Always True Block
- Not Block
- Loop Block
- Exit Block
- Risk Block
- Workup State Block
- Alert Block
- Math Block
- Actor Blocks
- TT Analytics Block
- Sniper Algo
- Order of Discrete Event Message Propagation
- Grouped Blocks and Library Functionality
- Rules Of Virtualization
- Jump Blocks
- Safety And Preventive Design With Visual Feedback
- Flip For Sell Orders Functionality
- Dynamic Data ExchangeLink
- Leave Orders On Pause Or Cancel
- Creating and Launching Order Ticket Algorithms (OTAs)
- Breakpoint Functionality
- Algorithm Behavior At Market Close and Disconnect
- Exporting Block Output Values
Virtualization is a property that can be applied to a designated portion of an algorithm to allow multiple "copies" of the designated portion to be created and executed simultaneously. While the concept may sound complex, the necessity of virtualization becomes clear when examined through an example.
Recommended Tutorials For This Section
For a tactile learning experience, please try the following tutorials:
- Grouping Blocks
- Virtualizing Your Scalper Algorithm
1. Suppose that a user designs and runs a simple market making algorithm in E-Mini S&P 500 contract as shown in the following illustration.
2. Suppose that the current best bid price is 1313.75, and the entry logic of the algorithm quotes 10 entry side contracts at this price. Then 1 out of the 10 contracts is filled for 1313.75. In response, the exit logic of the algorithm offers 1 contract at 1314.25, two increments higher than the fill price.
3. Suppose that the market moves higher and the best bid price changes to 1314.00. The offset contract from Step 2 still rests at 1314.25 but the entry logic of the algorithm modifies the remaining 9 entry side contracts to 1314.00. Then 2 out of the 9 entry side contracts get filled for 1314.00. At this time, the algorithm's total fill count is 3, including the first partial fill from Step 2. Since the algorithm's exit side logic was designed to use the total fill count and only the most recent fill price, it offers 3 offset contracts at 1314.50, two increments higher than the most recent fill price. In addition, since the exit logic of the algorithm can only quote a single order at time, it deleted the offset contract resting at 1314.25 (from Step 2).
To avoid this undesirable behavior, the user may virtualize the exit logic of this algorithm. With virtualization, a new copy of the exit logic is created every time an entry side fill occurs so that each offset order can operate with independent logic.
By virtualizing a group of blocks, the user can arrange for a new copy of the group to be created every time a designated discrete event (e.g., fill) occurs. To be specific, the user must group a set of blocks, virtualize the group, and then link a discrete event message pathway into the virtualized group block. Whenever a discrete event message enters the virtualized block via this pathway, a fresh copy is created, with each copy operating independently of others. Each copy, while identical in the composition of blocks, can operate independently with unique inputs and outputs.
Note: Since multiple copies of a virtualized block can exist at the same time, the Designer Canvas will not always display the correct dynamic output values of the blocks contained within a virtualized block.
How to virtualize a group of blocks
Highlight a group of blocks and right-click on one of the highlighted blocks. Then select “Group Blocks.”
The highlighted blocks become consolidated into a single block:
Right-click on the grouped block and select "Virtualize Blocks."
A new copy of the virtualized blocks will be generated every time a discrete event message enters the virtualized block.
Note: A virtualized block must have a discrete event message input since it is created only when a discrete event message enters the block. See: Rules of Virtualization for more information.