This is the Alerts part of this pair of Scripts. This part creates alerts to be picked up by the Chrome Add-on .
- Resolve issue with Orange Close alerts not showing up in the TradingView alarm notifications when using Candlestick Charts.
- Resolve issue with multiple Long/Short signals before Close by better use of the "tradeState" engine to keep control. This also made some of the Risk Management Code simpler.
This is an implementation of a strategy based on two MA Ribbon, a Fast Ribbon and a Slow Ribbon. The strategy revolves around a pair of scripts: to generate alerts signals for Autoview and for Backtesting, to tune your settings.
Trade Management options:
- Option to specify a Strategy start and end time script only.
- Trailing Stop Level, TSL (as % of price), activated on open trade
- Target Profit Level, TP (as % of price)
- Trailing Profit Level, TTP (as % of price below/above TP), activated on price passing TP Level
- Stop Loss Level, SL (as % of price)
- LONG green triangles and SHORT dark red triangles
> Dark Red = Stop Loss Hit
> Green = Target Profit Hit
> Purple = Trailing Stop Hit
> Orange = Opposite (Sell) Order Close
Trade Management Indication:
- TSL = Fuschia solid stepping line
- TP = Lime '+' line
- TTP = Black solid stepping Line.
- SL = Red '+' line
- If you choose to use Renko charts, make sure you have enabled the "IS This a RENKO Chart" option, (I have not so far found a way to Detect the type of chart is running).
- If you want non-repainting Renko charts you MUST use TRADITIONAL Renko Bricks. This type of brick is fixed and will not change size.
- Also use Renko bricks with WICKS DISABLED. Wicks are not part of Renko, the whole idea of using Renko bricks is not to see the wick noise.
- Set you chart Time Frame to the lowest possible one that will build enough bricks to give a reasonable history, start at 1min TimeFrame. Renko bricks are not dependent on time, they represent a movement in price. But the chart candlestick data is used to create the bricks, so lower TF gives more accurate Brick creation.
- You want to size your bricks to divide the pair price by 500, so for ETHBTC the price is say 0.0805 then your Renko Brick size should be about 0.0805/500 = 0.0002 (round up).
- You may find there is some slippage in value, but this can be accounted for in the Backtest by setting your commission a bit higher, for example I use 0.2 - 0.3 for Binance.
Autoview alert syntax:
NOTE: This assumes you are trading coins BUY and SELL orders on the Binance Exchange
WARNING***Only use Autoview to automate a strategy after you've sufficiently backtested and forward tested the strategy.
You can learn more about the syntax here http://autoview.with.pink/#syntax and you can watch this video here: https://www.youtube.com/watch?v=epN5Tjinuxw
- For the trade opens you will want to trigger BUY orders on LONGS (eg ETHBTC) with alert option "Once Per Bar Close" and SELL orders on SHORTS (eg BTCUSDT)
> b=buy q=0.0011 e=binance s=ethbtc u=currency t=market ( LONG )
> or b=sell q=0.0011 e=binance s=btcusdt t=market ( SHORT )
- For the trade closes you will want to trigger these alerts on condition with alert option "Once Per Bar" to get the quickest close. "Once per Bar Close" can also be used. (NOTE: with Renko you can only use "Once Per Bar Close" option)
> b=sell q=99% e=binance s=ethbtc t=market ( CLOSE LONGS )
> or b=buy q=99% e=binance s=btcusdt u=currency t=market ( CLOSE SHORTS )
Also, as you can see, with Once Per Bar Close - there could be 5 more renko bricks on the same minute between the Buy Signal (marker on chart) and the Alert fired. As a result again, the price can be significantly different than the Buy Signal on chart. Besides entry/exit price differences, the List of Trades in the strategy mode and the Strategy Performance in general when you tune you MAs parameters will never be close to the reality when you are going to trade realtime. The strategy can give you a very nice gain % but you could never enter/exit at the same prices which can make the strategy a losing one in real trading.
Just wanted to ask for your opinion on this, how you've worked around it.
And another thing - on 1m timeframe, TradingView only gives you about 1 week of actual 1min data (10,000 bars of 1min tf), after that it becomes 1h type of data injected into your strategy in backtest if you look in List of Trades you will see all entries/exits at round hours instead of of on a 1min timeframe. So the parameters you tune in your MAs really gives you result as if you are trading on 1h timeframe.
Knowing how there is an issue with alerts to enter/exit at the chart prices on 1min timeframe at Once Per Bar Close, trading on 1h timeframe becomes completely impossible as the price will change so much there is no more momentum to trade.
With that in mind, how do you really tune your MAs on 1min timeframe if you cannot really test in 1min time frame due to TradingView limit of 10,000 bars?
Appreciate your thoughts on this. Thanks!
There is nothing stopping you using this script with normal candles, this will then get away from some of the Renko building issues and possibly give you faster Entries and Exits. However, if you want non-repainting trading then the Entry must still use "Once Per Bar Close" alerts, but the Exits can use "Once per Bar" alerts.
Wondering if you did you it on regular candles if you were able to achieve profits similar to when using on renko candles.
thanks a lot for your replies!
I have not looked at this script for some time, these pair of scripts were really made to show how to convert a normal alerting script into a AutoView/ProfitView Trading script and provide a means for tuning.
and (barstate.isconfirmed or barstate.ishistory)
clause on lines 365 and 366.