MatthewA
Active member
I believe those are Stochastic, I am not currently using those and I do not have those. You might try Multiple Stochastic in a search?
If I have any ideas I will post something like that my friend.
A trend, momentum and cycle Trading System v3.0 (CSA)
- Thread starter diazlaz
- Start date
If I have any ideas I will post something like that my friend.
A member created a thread which mimics TTM
https://usethinkscript.com/threads/my-version-of-the-ttm-trend-for-thinkorswim.3067/
@diazlaz Hi! I stumbled to this site while Googling for Heiken-Ashi charts and trading strategies. Been going thru the many many posts from the original thread and this one. So much to learn and it is kinda scary realising the huge gap in knowledge between the experts here and myself.
I was fiddling around with the scan code in Post #4 (https://usethinkscript.com/threads/...cycle-trading-system-v3-0-csa.1596/post-14870), trying to tweak it for fast execution when some indicators are disabled. I am not familiar with ThinkScript, still getting used to it. I am posting the changed version here, need some help in figuring out a NaN result in the Frema logic. Did some reading regarding possible causes but since I am not really familiar with the actual calculation, was not able to resolve it at that level. So, decided to just handle it at the end of the Frema code by checking for NaN on the EMA_Signal variable and return a not-matched condition but no matter how I construct the code, the end result is still a NaN. This then causes the final scan result to fail (regardless of other indicators) as well at the end of execution for such stock (INST, VTEX are two of the stocks having this issue due to lack of sufficient data). Hoping you can advise how best to handle such not a number conditions in ThinkScript. Note that the variable 'bodoh' actually is a local word in our national language that means 'stupid', kinda how I feel now! I tested the result by disabling all other indicators except Frema and having the value displayed in a custom column of a watchlist. Thanks for assisting.
Modified code:
I was fiddling around with the scan code in Post #4 (https://usethinkscript.com/threads/...cycle-trading-system-v3-0-csa.1596/post-14870), trying to tweak it for fast execution when some indicators are disabled. I am not familiar with ThinkScript, still getting used to it. I am posting the changed version here, need some help in figuring out a NaN result in the Frema logic. Did some reading regarding possible causes but since I am not really familiar with the actual calculation, was not able to resolve it at that level. So, decided to just handle it at the end of the Frema code by checking for NaN on the EMA_Signal variable and return a not-matched condition but no matter how I construct the code, the end result is still a NaN. This then causes the final scan result to fail (regardless of other indicators) as well at the end of execution for such stock (INST, VTEX are two of the stocks having this issue due to lack of sufficient data). Hoping you can advise how best to handle such not a number conditions in ThinkScript. Note that the variable 'bodoh' actually is a local word in our national language that means 'stupid', kinda how I feel now! I tested the result by disabling all other indicators except Frema and having the value displayed in a custom column of a watchlist. Thanks for assisting.
Modified code:
Code:
# Trend v1.7 Bullish Scan
# tomsk
# 1.4.2020
# tomsk: Here is a bullish scan of the Trend V1.7 study, based on the study that @diazlaz posted
# If you'd like to configure this as a bearish scan, just replace the plot statement with
#
# plot scan = sBearish >= threshold;
#
#
#trend, a momentum and a cycle based indicator for ThinkorSwim V1.7
#@hockeycoachdoug Community Request
#
# https://usethinkscript.com/threads/i-request-combining-3-indicators-into-1-paintbar-study.1390/page-3#post-13087
#
#VERSION
# 2020.01.04 V1.7 @diazlaz - Integrated Slim Ribbon.
# 2020.01.02 V1.6 @diazlaz - Integrated DMI and BOP, restructured INPUTS to each module.
# threshold increased to 4 by default.
# 2020.01.01 V1.5 @diazlaz - Integrated ADX Trending States and BAR Line
# 2020.01.01 V1.4 @diazlaz - Integrated TTM Trends, modules selection
# and added threshold for signals
# 2019.12.31 V1.2 @diazlaz - Integrated FREMA
# 2019.12.30 V1.1 @diazlaz - Labels, Additional Dashboard, Lower Study
# 2019.12.30 V1.0 @diazlaz - Community Ask/Release
# Bullish or bearish scan
input bullish = yes;
# Minimum number of indicators that meet the scan conditions
input threshold = 1;
# The indicators to be enabled
input enableTTM = no;
input enableSuperTrend = no;
input enableFrema = yes;
input enableTMO = no;
input enableSlim = no;
input enableTOP = no;
input enableDMI = no;
input enableBOP = no;
input displace = 0;
# Count number of indicators that are enabled via configuration
def ethreshold = enableTTM + enableSuperTrend + enableFrema + enableTMO +
enableSlim + enableTOP + enableDMI + enableBOP;
# Final threshold count that will be used. Was thinking that threshold was number of indicators that need to be true for stock to meet scan criterion.
def cthreshold;
# Ensure that configured threshold count is not higher than the number of actual indicators that are enabled.
if threshold > ethreshold then
{
cthreshold = ethreshold; # Reset to actual number of enabled indicators
} else {
cthreshold = threshold; # Minimum number of indicators to meet the scan condition.
}
def h = high;
def l = low;
def o = open;
def c = close;
# TTM Trend
def sBullish_TTM;
if enableTTM then
{
sBullish_TTM = if TTM_Trend().TrendUp == 1 then 1 else 0;
} else {
sBullish_TTM = 0;
}
def sBearish_TTM;
if enableTTM then
{
sBearish_TTM = if TTM_Trend().TrendDown == 1 then 1 else 0;
} else {
sBearish_TTM = 0;
}
# SuperTrend (Mobius)
input AtrMult = 1.0;
input nATR = 4;
input AvgType = AverageType.HULL;
def ATR;
def UP;
def DN;
def ST;
def sBullish_SuperTrend;
def sBearish_SuperTrend;
# Restructured code so that disabled indicators related code is not executed to reduce running time. The same has been done for all below.
if enableSuperTrend then
{
ATR = MovingAverage(AvgType, TrueRange(high, close, low), nATR);
UP = HL2 + (AtrMult * ATR);
DN = HL2 + (-AtrMult * ATR);
ST = if close < ST[1] then UP else DN;
sBullish_SuperTrend = close >= ST;
sBearish_SuperTrend = close < ST;
} else {
ATR = 0;
UP = 0;
DN = 0;
ST = 0;
sBullish_SuperTrend = 0;
sBearish_SuperTrend = 0;
}
# FREMA
input AA = .1;
def CC;
def EMA;
def RE1;
def RE2;
def RE3;
def RE4;
def RE5;
def RE6;
def RE7;
def RE8;
def EMA_Signal;
def sBullish_Frema;
def sBearish_Frema;
def bodoh;
if enableFrema then
{
CC = if CC[1] == 0 then .9 else 1 – AA;
EMA = AA * close + CC * EMA[1];
RE1 = CC * EMA + EMA[1];
RE2 = Power(CC, 2) * RE1 + RE1[1];
RE3 = Power(CC, 4) * RE2 + RE2[1];
RE4 = Power(CC, 8) * RE3 + RE3[1];
RE5 = Power(CC, 16) * RE4 + RE4[1];
RE6 = Power(CC, 32) * RE5 + RE5[1];
RE7 = Power(CC, 64) * RE6 + RE6[1];
RE8 = Power(CC, 128) * RE7 + RE7[1];
EMA_Signal = EMA – AA * RE8;
bodoh = isNaN(EMA_Signal);
if bodoh then {
sBullish_Frema = 0;
sBearish_Frema = 0;
} else {
sBullish_Frema = EMA_Signal > 0;
sBearish_Frema = EMA_Signal <= 0;
}
} else {
bodoh =0;
CC = 0;
EMA = 0;
RE1 = 0;
RE2 = 0;
RE3 = 0;
RE4 = 0;
RE5 = 0;
RE6 = 0;
RE7 = 0;
RE8 = 0;
EMA_Signal = 0;
sBullish_Frema = 0;
sBearish_Frema = 0;
}
# TMO
input length = 14;
input calcLength = 5;
input smoothLength = 3;
def data;
def EMA5;
def Main;
def Signal;
def sBullish_TMO;
def sBearish_TMO;
if enableTMO then
{
data = fold i = 0 to length
with s
do s + (if c > getValue(o, i)
then 1
else if c < getValue(o, i)
then - 1
else 0);
EMA5 = ExpAverage(data, calcLength);
Main = ExpAverage(EMA5, smoothLength);
Signal = ExpAverage(Main, smoothLength);
sBullish_TMO = Main > Signal;
sBearish_TMO = Main <= Signal;
} else {
data = 0;
EMA5 = 0;
Main = 0;
Signal = 0;
sBullish_TMO = 0;
sBearish_TMO = 0;
}
# SLIM
input sSuperFast = 8;
input sFast = 13;
input sSlow = 21;
def SuperFastM1;
def FastM1;
def SlowM1;
def buyM1;
def stopbuyM1;
def buynowM1;
def buysignalM1;
def Buy_SignalM1;
def sellM1;
def stopsellM1;
def sellnowM1;
def sellsignalM1;
def Sell_SignalM1;
def sBullish_SLIM;
def sBearish_SLIM;
if enableSLIM then
{
SuperFastM1 = ExpAverage(close[-displace], sSuperFast);
FastM1 = ExpAverage(close[-displace], sFast);
SlowM1 = ExpAverage(close[-displace], sSlow);
buyM1 = SuperFastM1 > FastM1 and FastM1 > SlowM1 and low > SuperFastM1;
stopbuyM1 = SuperFastM1 <= FastM1;
buynowM1 = buyM1 and !buyM1[1];
buysignalM1 = if buynowM1 and !stopbuyM1 then 1
else if buysignalM1[1] and stopbuyM1 then 0
else buysignalM1[1];
Buy_SignalM1 = buysignalM1 and !buysignalM1[1];
sellM1 = SuperFastM1 < FastM1 and FastM1 < SlowM1 and high < SuperFastM1;
stopsellM1 = SuperFastM1 >= FastM1;
sellnowM1 = sellM1 and !SellM1[1];
sellsignalM1 = if sellnowM1 and !stopsellM1 then 1
else if sellsignalM1[1] and stopsellM1 then 0
else sellsignalM1[1];
Sell_SignalM1 = sellsignalM1 and !sellsignalM1[1];
sBullish_SLIM = Buy_SignalM1;
sBearish_SLIM = Sell_SignalM1;
} else {
SuperFastM1 = 0;
FastM1 = 0;
SlowM1 = 0;
buyM1 = 0;
stopbuyM1 = 0;
buynowM1 = 0;
buysignalM1 = 0;
Buy_SignalM1 = 0;
sellM1 = 0;
stopsellM1 = 0;
sellnowM1 = 0;
sellsignalM1 = 0;
Sell_SignalM1 = 0;
sBullish_SLIM = 0;
sBearish_SLIM = 0;
}
# TOP Cycle Trader
input FastCycleLength = 5;
input SlowCycleLength = 8;
def FastVar;
def SlowVar;
def DiffVar;
def sBullish_TOP;
def sBearish_TOP;
if enableTOP then
{
FastVar = ExpAverage((H + L) / 2, FastCycleLength);
SlowVar = Average((H + L) / 2, SlowCycleLength);
DiffVar = FastVar - SlowVar;
sBullish_TOP = DiffVar > 0;
sBearish_TOP = DiffVar <= 0;
} else {
FastVar = 0;
SlowVar = 0;
DiffVar = 0;
sBullish_TOP = 0;
sBearish_TOP = 0;
}
# DMITrend
input DMIlength = 13;
def hiDiff;
def loDiff;
def plusDM;
def minusDM;
def ATRDMI;
Def DIPlus;
Def DIMinus;
def sBullish_DMI;
def sBearish_DMI;
if enableDMI then
{
hiDiff = high - high[1];
loDiff = low[1] - low;
plusDM = if hiDiff > loDiff and hiDiff > 0 then hiDiff else 0;
minusDM = if loDiff > hiDiff and loDiff > 0 then loDiff else 0;
ATRDMI = WildersAverage(TrueRange(high, close, low), DMIlength);
DIPlus = 100 * WildersAverage(plusDM, DMIlength) / ATRDMI;
DIMinus = 100 * WildersAverage(minusDM, DMIlength) / ATRDMI;
sBullish_DMI = DIPlus > DIMinus;
sBearish_DMI = DIMinus > DIPlus;
} else {
hiDiff = 0;
loDiff = 0;
plusDM = 0;
minusDM = 0;
ATRDMI = 0;
DIPlus = 0;
DIMinus = 0;
sBullish_DMI = 0;
sBearish_DMI = 0;
}
# BOP indicator
input averageType = {Simple, Exponential, default Weighted, Wilders, Hull, Disabled};
input BoPlength = 16;
def rawBMP = if high != low then (close - open) / (high - low) else 1;
def BMP;
def sBullish_BOP;
def sBearish_BOP;
if enableBOP then
{
switch (averageType) {
case Simple:
BMP = Average(rawBMP, BoPlength);
case Exponential:
BMP = ExpAverage(rawBMP, BoPlength);
case Weighted:
BMP = wma(rawBMP, BoPlength);
case Wilders:
BMP = WildersAverage(rawBMP, BoPlength);
case Hull:
BMP = HullMovingAvg(rawBMP, BoPlength);
case Disabled:
BMP = rawBMP;
}
sBullish_BOP = BMP > 0;
sBearish_BOP = BMP <= 0;
} else {
BMP = 0;
sBullish_BOP = 0;
sBearish_BOP = 0;
}
# SCAN
plot scan;
if bullish then
{
scan = cthreshold <= sBullish_TTM + sBullish_SuperTrend + sBullish_Frema + sBullish_TMO + sBullish_TOP + sBullish_DMI + sBullish_BOP + sBullish_SLIM;
} else {
scan = cthreshold <= sBearish_TTM + sBearish_SuperTrend + sBearish_Frema + sBearish_TMO + sBearish_TOP + sBearish_DMI + sBearish_BOP + sBearish_SLIM;
}
# End Trend v1.7 Bullish Scan@MerryDay thanks for replying. I truly understand what you mean. This is just me trying to learn thinkscript by making changes to the code I find here. Too complex scans tend to take too long to run and timeout anyways, it generally is a waste of time and defeats the usability of such scans.
The main reason for the post was to get help to understand how NaN behavior is in thinkscript code. I actually got the scan code to work fine in entirety but it looks like once a NaN value is assigned to variable, the behavior of the code is not as I would expect. The Frema logic works fine if written like below. If I attempt to assign the result of EMA – AA * RE8 to a variable, and then use the variable in isNan() test, it will fail. I might have this wrong in some manner, anyways, just learning. Anyways, please disregard the earlier post.
The main reason for the post was to get help to understand how NaN behavior is in thinkscript code. I actually got the scan code to work fine in entirety but it looks like once a NaN value is assigned to variable, the behavior of the code is not as I would expect. The Frema logic works fine if written like below. If I attempt to assign the result of EMA – AA * RE8 to a variable, and then use the variable in isNan() test, it will fail. I might have this wrong in some manner, anyways, just learning. Anyways, please disregard the earlier post.
Code:
if enableFrema then
{
CC = if CC[1] == 0 then .9 else 1 – AA;
EMA = AA * close + CC * EMA[1];
RE1 = CC * EMA + EMA[1];
RE2 = Power(CC, 2) * RE1 + RE1[1];
RE3 = Power(CC, 4) * RE2 + RE2[1];
RE4 = Power(CC, 8) * RE3 + RE3[1];
RE5 = Power(CC, 16) * RE4 + RE4[1];
RE6 = Power(CC, 32) * RE5 + RE5[1];
RE7 = Power(CC, 64) * RE6 + RE6[1];
RE8 = Power(CC, 128) * RE7 + RE7[1];
# EMA_Signal = EMA – AA * RE8;
# bodoh = isNaN(EMA_Signal);
# if bodoh then {
# sBullish_Frema = 0;
# sBearish_Frema = 0;
# } else {
# sBullish_Frema = EMA_Signal > 0;
# sBearish_Frema = EMA_Signal <= 0;
# }
EMA_Signal = if !isNaN(EMA – AA * RE8) then EMA – AA * RE8 else 0;
sBullish_Frema = EMA_Signal > 0;
sBearish_Frema = EMA_Signal <= 0;
} else {
CC = 0;
EMA = 0;
RE1 = 0;
RE2 = 0;
RE3 = 0;
RE4 = 0;
RE5 = 0;
RE6 = 0;
RE7 = 0;
RE8 = 0;
EMA_Signal = 0;
sBullish_Frema = 0;
sBearish_Frema = 0;
}
Last edited:
Pretty incredible work u did on this.Inspired by the work of the community here, this is the continuation of the CSA studies series.
The studies integrates and unifies a number of community studies and provides signals allowing the construction of trading strategies and the development of trading plans. It's community driven initiative. It includes studies such as TTM Trend, Super Trend, Frema, TMO, TOP, DMI , BOP, Slim Ribbon, ADX as Trending/Non-Trending, Super Trend w/CCI and ATR combo and a tri-fecta of CCI + TTM squeeze + TTM trend Combo with entry signals on LONG/SHORT/HOLD.
fingerlakes
New member
The scan says its to complex for the scanner. Is it possible to scan for the green bars and red bars only?
A workaround that members have had success with when encountering the too complex error is to scan for each study individually. Each study is identified by name within this script. Search the forum for each of those individual studies and build them into your scan.
fingerlakes
New member
thanks for the reply...I cut and pasted the code below and it has several errors, couldn't find a copy of his on the site...Do you have one? thanksA workaround that members have had success with when encountering the too complex error is to scan for each study individually. Each study is identified by name within this script. Search the forum for each of those individual studies and build them into your scan.
#ADX TRENDING
input ADXlength = 8; #ADX
input ADXTrending = 25; #ADX
input showADXBar = yes;
input DI_length = 8;
def DX = if (diplus(di_length) + diminus(di_length) > 0) then 100 * AbsValue(diplus(di_length) - diminus(di_length)) / (diplus(di_length) + diminus(di_length)) else 0;
def ADX = WildersAverage(DX, adxlength);
plot ADXCross = LowestAll(low);
ADXCross.SetPaintingStrategy(PaintingStrategy.LINE);
ADXCross.AssignValueColor(
if ADX > ADXTrending then Color.LIME
else Color.DARK_GRAY);
ADXCross.SetLineWeight(5);
ADXCross.SetHiding(!showADXBar);
#MACD Neutal Eval
input fastLength_1 = 12;
input slowLength_1 = 26;
input MACDLength_1 = 9;
input AverageType_1 = {SMA, default EMA};
def macd_Val_1 = MACD(fastLength_1, slowLength_1, MACDLength_1, AverageType_1).Value;
def macd_Avg1 = MACD(fastLength_1, slowLength_1, MACDLength_1, AverageType_1).Avg;
def MACD_trig = if MACD().value > MACD().avg then 1 else 0;
AddLabel(showlabels,
if ADX > ADXTrending then "Trending" else
"Non Trending",
if IsNan(c) then COLOR.DARK_GRAY else
if ADX > ADXTrending then COLOR.GREEN else
COLOR.DARK_GRAY);
AddLabel(showlabels,
"MACD",
if IsNan(c) then COLOR.DARK_GRAY else
if macd_Val_1 > macd_Avg1 then COLOR.DARK_GREEN else
COLOR.DARK_RED);
#STATE
def sResults = HA1_sState + HAMTF_sState + TTM_sState + ST1_ssupertrend + STHA_ssupertrend + FRE_sfrema + TMO_stmo + SL1_sstate + TOP_stop + DMI_sdmi + BOP_sbop
+ STCCI_ssupertrendcci + CTT_sccittm + DRSI_sstate + SWCA_sstate;
def sBullish = HA1_sBullish + HAMTF_sBullish + TTM_sBullish + ST1_sbullish + STHA_sbullish + FRE_sbullish + TMO_sbullish + SL1_sbullish + TOP_sbullish + DMI_sbullish + BOP_sbullish + STCCI_sbullish + CTT_sbullish + DRSI_sbullish + SWCA_sbullish;
def sBearish = HA1_sBearish + HAMTF_sBearish + TTM_sBearish + ST1_sbearish + STHA_sbearish + FRE_sbearish + TMO_sbearish + SL1_sbearish + TOP_sbearish + DMI_sbearish + BOP_sbearish + STCCI_sbearish + CTT_sbearish + DRSI_sbearish + SWCA_sbearish;
def bullish = if(sBullish >= threshold,1,0);
def bearish = if(sBearish >= threshold,1,0);
def sState = if bullish then 100 else if bearish then -100 else 0;
def sState2 = if sState != 0 then sState else sState2[1];
#COLORBARS
AssignPriceColor(
if PaintBars then
if ADXPaintBarsMode then if ADX > ADXTrending then COLOR.ORANGE else COLOR.DARK_GRAY
else
if bullish then COLOR.GREEN else if bearish then COLOR.RED
else
if enableNeutralMACDPainter then
if macd_Val_1 > macd_Avg1 then COLOR.DARK_GREEN else COLOR.DARK_RED
else
COLOR.GRAY
else COLOR.CURRENT);
Are you asking about ADX and MACD indicators? Those are built-in TOS studies. You can place them individually in your scanner.
stockscouter87
Member
Hey Merry! So ive been backtesting this strategy and if you follow the system over time it is very profitable the only problem i have is I do not know how to set alerts when there is a buy or sell signal..... can you help me with that?
I do not recommend using this. As @irishgold states this is monitoring multiple signals. Any 7 of the 10 could be firing at any time; alerts could end up firing almost constantly.
But ask and thou shallt receive. Here is an alert for whenever the threshold of 7 indicators is breached. Should be added to the bottom of your study:
Code:
# Alert
Alert(bullish and !bullish[1], "Bullish", Alert.Bar, Sound.Chimes);
# Alert
Alert(!bullish and bullish[1], "Bearish", Alert.Bar, Sound.Chimes);stockscouter87
Member
what causes the strategy to buy or sell? I checked the "show report" and it takes trades off of something.... Are you saying that whenever anyone of the 10 fires off it buys?
Sorry, I can't help you. The original code in this thread has no "addstrategy" to trigger a buy, no arrows, or anything else.
The original code is written to show trend. There is a default threshold of 7. IE: if 7 out of the 10 indicators are positive then a label states bullish.
DGreenleaf17
New member
Did you ever get this bottom indicator figured out!?
Did you know that clicking on a member's name will allow you to see when a member was last seen on the uTS forum? @MatthewA has not been seen in a while.
Join useThinkScript to post your question to a community of 21,000+ developers and traders.
| Thread starter | Similar threads | Forum | Replies | Date |
|---|---|---|---|---|
|
A Serving of Trend and Momentum Indicators for ThinkorSwim | Indicators | 2 | |
|
EZ Trend and Momentum Indicator for ThinkorSwim | Indicators | 14 | |
|
|
Trend Momentum Divergence Indicator for ThinkorSwim | Indicators | 5 | |
|
L3 Banker Fund Flow Trend Oscillator for ThinkOrSwim | Indicators | 28 | |
|
|
Trend Meter For ThinkOrSwim | Indicators | 19 |
Similar threads
-
A Serving of Trend and Momentum Indicators for ThinkorSwim
- Started by MerryDay
- Replies: 2
-
-
-
-
Similar threads
-
A Serving of Trend and Momentum Indicators for ThinkorSwim
- Started by MerryDay
- Replies: 2
-
-
-
-
Similar threads
-
A Serving of Trend and Momentum Indicators for ThinkorSwim
- Started by MerryDay
- Replies: 2
-
-
-
-
The Market Trading Game Changer
Join 2,500+ subscribers inside the useThinkScript VIP Membership Club
- Exclusive indicators
- Proven strategies & setups
- Private Discord community
- ‘Buy The Dip’ signal alerts
- Exclusive members-only content
- Add-ons and resources
- 1 full year of unlimited support
Frequently Asked Questions
What is useThinkScript?
useThinkScript is the #1 community of stock market investors using indicators and other tools to power their trading strategies. Traders of all skill levels use our forums to learn about scripting and indicators, help each other, and discover new ways to gain an edge in the markets.
How do I get started?
We get it. Our forum can be intimidating, if not overwhelming. With thousands of topics, tens of thousands of posts, our community has created an incredibly deep knowledge base for stock traders. No one can ever exhaust every resource provided on our site.
If you are new, or just looking for guidance, here are some helpful links to get you started.
- The most viewed thread:
https://usethinkscript.com/threads/repainting-trend-reversal-for-thinkorswim.183/ - Our most popular indicator:
https://usethinkscript.com/threads/buy-the-dip-indicator-for-thinkorswim.3553/ - Answers to frequently asked questions:
https://usethinkscript.com/threads/answers-to-commonly-asked-questions.6006/
What are the benefits of VIP Membership?
VIP members get exclusive access to these proven and tested premium indicators: Buy the Dip, Advanced Market Moves 2.0, Take Profit, and Volatility Trading Range. In addition, VIP members get access to over 50 VIP-only custom indicators, add-ons, and strategies, private VIP-only forums, private Discord channel to discuss trades and strategies in real-time, customer support, trade alerts, and much more. Learn all about VIP membership here.
How can I access the premium indicators?
To access the premium indicators, which are plug and play ready, sign up for VIP membership here.