Chart shows the Non-Standardized Enhanced Time Segmented (Multi MA) with default settings on top and the Standardized version with default settings on the bottom.
Time Segmented was developed by Worden Brothers, Inc to be a leading indicator by comparing various time segments of both price and . Essentialy it is designed to measure the amount of money flowing in and out of an instrument.
Time Segmented was originally ported to TradingView by user @liw0 and later corrected by user @vitelot. I never quite understood how to read Time Segmented until I ran across a version by user @storma where they indicated when price would be long or short, but that code also utilized the incorrect calculation from user @liw0.
In an effort to make Time Segmented more accessible and easier to read, I have re-coded it here. The calculations are based on the code from @vitelot and I have added direction indicators below the chart.
If the histogram (TSV) is greater than zero and greater than the moving average, price should be moving long and there will be a green box below the chart.
If TSV falls below the moving average while still being greater than zero, the trend may be exhausting and has been coded to read Price Action Long - FAILURE with a black x below the chart.
If the histogram (TSV) is less than zero and less than the moving average, price should be moving short and there will be a red box below the chart.
If TSV rises above the moving average while still being less than zero, the trend may be exhausting and has been coded to read Price Action Short - FAILURE with a black x below the chart.
At times, the moving average may be above zero while TSV is below zero or vice versa. In these situations the chart will indicate long or short based on whether or not TSV is greater or less than zero. It is possible a new trend may be forming as the moving average obviously lags, but also possible price is consolidating with little and causing TSV to oscillate close to zero.
**Z Score // Standardized Option **
Thist Standardized code implements all of the above but also allows the user to select a threshold level that should not need to be adjusted for each instrument (since the output is standardized).
If the TSV value meets the long and short signal requirements above and TSV is greater than the threshold values a green or red box will print ABOVE the oscillator. The histogram will also change color based on which threshold TSV has met.
This calculation allows us to compare current to the mean (moving average) of the population (Z-Length). The closer the TSV Z-Score is to the mean, the closer it will be to the Zero Line and therefore price is likely consolidating and choppy. The farther TSV Z-Score is from the mean, the more likely price is trending.
The MA Mode determines the Moving Average used to calculate TSV itself. The Z-Score is ALWAYS calculated with a (as that is the standard calculation for Z-Score).
The Threshold Levels are the levels at which TSV Z-Score will change from gray to yellow, orange, green ( ), or red ( ).
Statistically speaking, confidence levels in relation to Z-Score are noted below. The built in Threshold Levels are the positive and negative values for 90%, 95%, and 99%. This would indicate when is greater than these values they are out of the ordinary from the standard range. You may wish to adjust these levels for TSV Z-Score to be more responsive to your trading needs
80% :: 1.28
85% :: 1.44
90% :: 1.64
95% :: 1.96
99% :: 2.58
The Z Length is the period for which the Z Score is calculated
More information regarding Time Segmented can be found here: http://www.worden.com/TekeChartHelp/Cont...
Original code ported by @liw0
Corrected by @vitelot
Updated/Enhancements by @StephXAGs with inspiration from @storma
Multiple MA Options Credits to @Fractured and @lejmer
Bits and Pieces from @AlexGrover, @Montyjus, and @Jiehonglim
As always, trade at your own risk.
Dans le plus pur esprit de TradingView, l'auteur de ce texte l'a publié en open-source, afin que les traders puissent le comprendre et le vérifier. Bravo à l'auteur ! Vous pouvez l'utiliser gratuitement, mais la réutilisation de ce code dans une publication est régie par les règles internes. Vous pouvez le mettre en favori pour l'utiliser sur un graphique.
line 147: The function 'sma' should be called on each calculation for consistency. It is recommended to extract the call from the ternary operator or from the scope.
line 158: Shadowing variable 'beta' which exists in parent scope. Did you want to use the ':=' operator instead of '=' ?
line 220: The function '#f19' should be called on each calculation for consistency. It is recommended to extract the call from this scope.
line 220: The function 'calcWeight' should be called on each calculation for consistency. It is recommended to extract the call from this scope.
line 229: Shadowing variable 'z' which exists in parent scope. Did you want to use the ':=' operator instead of '=' ?
line 278: Shadowing variable 'd' which exists in parent scope. Did you want to use the ':=' operator instead of '=' ?
line 329: Shadowing variable 'd' which exists in parent scope. Did you want to use the ':=' operator instead of '=' ?
line 80: The function 'cross' should be called on each calculation for consistency. It is recommended to extract the call from the ternary operator or from the scope.