hi guys, it seems some issue in indonind function. if you add optimize , the result will be wrong.
if no optimize
![](/api/discussion/download/image/7946-1-png)
and the result seems like normal
![](/api/discussion/download/image/7947-图片2-png)
but if add optimize, even do not run optimize, just add a range.
![](/api/discussion/download/image/7948-3-png)
it result will be strange
![](/api/discussion/download/image/7949-图片4-png)
i guess some function conflict.
hope can get this fixed.
thanks .
if no optimize
and the result seems like normal
but if add optimize, even do not run optimize, just add a range.
it result will be strange
i guess some function conflict.
hope can get this fixed.
thanks .
Rename
and the same issue happens when add other scaleind indicator, no matter select optimze or not, it will cause a wrong calculation of indonind function.
just FYI
just FYI
Yes, as can be seen on your screenshot the IndOnInd takes the wrong parameter's value. It's a bug. Workaround: open the strategy as C# code and adjust as shown below:
CODE:
public override void Initialize(BarHistory bars) { //indicator = new IndOnInd(bars,new ExpDevBandUpper(bars.Close,Parameters[0].AsInt,Parameters[0].AsDouble,false),new TR(bars)); indicator = new IndOnInd(bars,new ExpDevBandUpper(bars.Close,Parameters[0].AsInt,Parameters[1].AsDouble,false),new TR(bars));
it works, but after adding another indonind indicator (which is EMA in different timeframe)in stratergy, the bug happens again.
here is some code:
![](/api/discussion/download/image/7950-图片1-png)
here is some code:
Verified a fix for this in upcoming B94.
thanks Eugene. it is great.
Your Response
Post
Edit Post
Login is required