This is a scaled Normalized Vector Strategy with a Karobein Oscillator Original: Drkhodakarami (tradingview.com/script/Fxv2x...)
Repainting: in general there two types of repainting: * when the last candle is constantly being redrawn * when the indicator draws a different configuration after it has been deactivated/reactivated, i.e. refreshed.
The former is a natural behaviour, which presents a constant source of frustration, when a signal directly depends on the current market situation and can be overcome with various indirect techniques like divergence.
The latter suggests a flaw in the indicator design. Unfortunately, the Normalized Vector Strategy is repainting in the latter sense, although being really promising. Would be nice if our community suggests a solution to this problem )) As it is this strat should be refreshed each time a decision is being taken.
This strat consistently performs with high accuracy, showing up to 96% scores. Here are some of the best parameters: TF Lookback Performance (ca.) 1m 13 92% 3m 34 92% 5m 85 92% 15m 210 90% 30m 360 89% 1H 1440, 720 94%, 87%
The Karobein Oscillator has an intrinsic sinusoidal behaviour that helps in determining direction and timing. It does not repaint. Original: alexgrover (tradingview.com/script/JiNi0...)
Hey the indicator is best but it's may be singnal wrong then after 3/8 candel it's hide why ? Is Taher any solution to check backtesting
dpanday
⋅
Have you found a solution to resolve the repainting?
ashul.l371
⋅
Yes same question I have
shengjilin
⋅
I've been using it for a while. Good. If you add the time alarm, so much the better. There is no time alarm, will miss the opportunity to sell.
Can add an alarm?
zzzaa301
⋅
repaint.
drgentleman1
⋅
I tried adding in an alert . but in vain.neverthelessI replaced it with study as you say.
trend117
⋅
Hello, can you please edit the script for me, I just want to buy and sell "Long"
MRKCHAMPION
⋅
in tradingview documentation it says barmerge.lookahead_on is not suited for backtesting, would these results be similar if not use barmerge.lookahead
capissimo
⋅
@MRKCHAMPION, they will be worse. Trying to resolve this...
TY19
⋅
@MRKCHAMPION, Right. The statement for barmerge.lookahead_on is as follows:
"Merge strategy for the requested data position. Requested barset is merged with current barset in the order of sorting bars by their opening time. This merge strategy can lead to undesirable effect of getting data from "future" on calculation on history. This is unacceptable in backtesting strategies, but can be useful in indicators."
@capissimo I edited it to barmerge.lookahead_off. The strategy results drop to 30%.