This page reviews the 3 main settings (Quantity, Price, Action) associated with a Trading Rule used in a Trading System. The use of SHOW statements and NOTE tokens as diagnostic tools is highlighted. A full list of RTL "backtesting" tokens, with a focus on the "Context" Token (CTX), is also presented.
The following steps will guide you through the process of setting up a quotepage to calculate and monitor these Option Analysis values:
This is Part 3 of the Three line Break Tutorial
Now, let's create a Custom Column that builds off the TLB_REV Custom Indicator that we've already created, and then add this custom column to a quotepage.
This is Part 2 of the Three line Break Tutorial
Now, let's create a custom indicator involving the TLB token. To create a custom indicator, go to "Setup: Custom Indicator", and setup the indicator based on the settings below.
Then save the custom indicator with a name like "TLB_REV" (for Three Line Break Reversal indicator).
In this custom indicator, we have set the TLB token up to use the data element "Rising?". As mentioned on the previous page, this token results numerically in a value of 1 when rising, and 0 when falling. Based on this, let's take a closer look at the syntax of our custom indicator...
If you're in a situation where your data feed is active and your charts are static (frozen), try stepping through this checklist until your charts update properly.
This 3-part tutorial series will discuss several different ways of using Three Line Break methodologies within Investor/RT, including...
Occasionally, when diagnosing a problem, Linn Software support may request that you send your data_f folder contents to enable us to reproduce the specific problem. Some problems are very specific to the particular way a chart or some other object is defined. Please do not email your database to support unless requested. The data_f folder/directory contains 59 files that constitute the Investor/RT database. Since this folder's contents can often be hundreds of megabytes in size, sending the data_f by email is impossible, even after compressing the files.
Now let's look atthe following scan...
MAFIVE > MATEN AND MAFIVE1 <= MATEN1
The first thing you may notice about this scan expression is that the tokens MAFIVE and MATEN don't exist in the list of available scan tokens. These scan tokens names were the result of the renaming of two different moving average (MA) tokens. This scan required the use of the same token (MA) twice. In order to differentiate the two moving averages, we are required to rename MA.
