TSCI.pngTSAsymTradescape (TradeStation)


The TSAsymTradescape analysis technique generates one or more asymmetric tradescapes. Asymmetric tradescapes are useful for ascertaining the optimal asymmetric signaling for entities that have very different behaviors relative to entries and exits. They are also used for analyzing which entities are favorable to a specific signaling system that is asymmetric by design.

In a tradescape, the traded entity is signaled directly for the primary entries and exits using a symmetric signaler. This means the same time horizon is used to generate both the upside and downside transitions. In an asymmetric tradescape, separate time horizon signals are used for generating the upside and downside transitions.

int TradedEntity (1)

This input specifies a specific data stream to be analyzed. The value 1 uses data1, 2 uses data2, and so on. If TradedEntity is set to 0, and a specific Asymmetry is specified, asymmetric tradescapes are created for all data streams present in the chart. You may thus have as many as 50 tradescapes generated in a single analysis. The entities can have different time scales. Each will be created with the specified signaling asymmetry.

double Asymmetry (-1.0)

The asymmetry is the ratio of the information content used for the upside transitions (turns to the upside) relative to the downside transitions (turns to the downside). A quick to enter but slow to exit long signaling system has an asymmetry less than 1. A slow to enter but fast to exit signaling system has an asymmetry greater than 1. Typical signal asymmetries are between 0.25 and 4. The turtle HH=55 LL=20 breakout system is an example of an asymmetric signaler, one that for long trades is slow to enter and fast to exit, a signal asymmetry of 55/20=2.75.

If TradedEntity specifies a specific data stream in the chart, you can elect to generate a series of different asymmetries for that one entity. To see a full series of 25 different predefined asymmetries, set Asymmetry to -1. To see a smaller series of 9 different predefined asymmetries, set Asymmetry to -2.

In the tradescape plot, only a single EM length is used for the X axis position. The interpretation of an EM length of 20 would be as follows for an asymmetry of 0.5. The EM signal used to generate the upside transitions (the entries for a long system) will be 20*sqrt(0.5)=14.142. The EM signal used for the downside transitions (the exits for a long system) will be 20/sqrt(0.5)=28.284. The asymmetry is thus 14.142/28.284=0.5. While the point on the tradescape is plotted at an EM length of 20, the actual lengths used to generate the turns for the composite EM signal are 14.142 and 28.284. Note that the EM length assigned to an asymmetric signal is not the average of the two lengths.

Note also that an asymmetry of 1.0 generates the standard (symmetric) tradescape. If a predefined series of symmetries are generated, the symmetric case with be the center plot in the graph display matrix.

String FileName ("")

The data within the TradeStation chart is written to a disk file that is used in a separate procedure to generate the plots and analyses. If FileName is empty, , a temporary binary data file is used to store the data and this file is automatically deleted when the window is closed. If a full path filename is specified, a persistent ASCII CSV file is written. A full valid Windows path and filename must be specified. The directory path will be created if it does not currently exist. Since a comma separated value (CSV) file is written, a CSV file extension is recommended. For example, a FileName such as "c:\data\a1.csv" is valid, even if the folder c:\data doesn't yet exist.

int WalkFwd (2520)

This is the count of bars, from last non-reserved bar backward in time, to use for the analysis. In order to accommodate all of the time horizons in a tradescape, do not set this value below 250. If a value is specified that is greater than the amount of data available in the chart, all of the data that is present is used.

int Reserved (0)

This is the count of most recent bars to reserve for any walk-forward you may wish to independently carry out. These data are disregarded in the analysis. A value of 0 processes all data through the most recent bar.

int DoShort (0)

A tradescape is normally a long-side only analysis. This value can be set to 1 to perform short side tradescapes and signal analysis.

int Degap (0)

This option removes all overnight/weekend gaps in data for instances where positions are always closed prior to a trading session's closing bar.

If Degap is 1, a check is made to see if the same day fraction of data is greater than 80%. If this criterion is met, as with hourly or finer bar densities, the gap across days is mathematically removed. The price activity from the prior day's closing bar through the end of the first bar of the next day will be zeroed. This means the two bars will share the same closing values. The adjustment is based on the differential in closing prices and is applied to the open, high, and low values as well.

The adjustment is made backward in time so that the most recent bar's close will be the current price. The removal of gaps moving backward in time can result in negative prices. In such an instance, the lowest low in the de-gapped data will be set to 0.01 and all prices will be shifted accordingly.

int InactiveAtLastBar (1)

When this variable is non-zero, the last bar in the chart will automatically trigger the computation and deactivate the analysis. A progress bar is normally drawn, but if this proves a distraction, it will be omitted if this value is set to 2. If set to 0, the analysis will not take place until the Status is toggled Off in the Format Analysis Techniques option.