I built an indicator that return one value only, such as a price level.
This indicator has several arrays in it.
Then I called this indicator in a new screener, in this way:
1
2
3
4
5
myValue=CALL"myIndicator"//(myIndicator hasn't got any parameter)
ind=myValue>lowest[20](low) //(of course this is only a test in order to be sure I'll get some results)
screener[ind]
Unfortunately I don’t get any results, although I know there are.
In my opinion, there’s something does not work properly in the function CALL…And I think this is because in myIndicator there are some arrays, and Prorealtime is not able to deal with them with a screener, yet.
Can anyone help me on that, and tell me if my feeling is correct or not.
Unfortunately I don’t get your point. I have other CALL instructions, I made some tests. They work without any parameter (because the indicator doesn’t have any) and without any (close) at the end the function CALL (if this is what you refer to).
My indicator is quite complex and I don’t want to paste it in this post. But the outcome from the return function is just a price level (just imagine a resistance or support level).
So please could you explain me better your answer.
I tried to copy&paste in the screener the entire indicator code too, avoiding the call function, but some errors come out when the program meet the arrays in the code.
That’s why I suppose the problem is related to the array in the code….
Sorry – I deleted my last post as Roberto pointed out a typo on the screener line so the test and workaround was invalid. It seems that it is not possible to call an indicator which includes arrays from a screener. That seems odd as although they are different engines I’d have thought that a returned value from ProBuilder was a returned value whether it came via arrays or not.
Yes it seems so, also because in myIndicator code, the return value was already a variable and not the array itself (at a certain point there’s the association x = $myarray etc … return x).
So Vonasi, there’s a bug in the software? Any possibility to work it out?
There is no workaround I’m afraid. It is an incompatibility issue between the ProScreener engine and the ProBuilder engine. I believe there are plans in the pipeline to update ProScreener to bring it more in line with ProBuilder and ProOrder – so we will just have to wait for that before being able to access arrays via it.
thank you for the support, unfortunately this is a very sad news and I am also very disappointed to know that after spending many hours in coding my indicator….
It would be possible to be informed as soon as the new development will be available?
Are there any ways to speed it up?
And now, what do you suggest, to modify the indicator code and replace the arrays with standard instructions?
It would be possible to be informed as soon as the new development will be available? Are there any ways to speed it up? And now, what do you suggest, to modify the indicator code and replace the arrays with standard instructions? Regards
I don’t work for PRT. I just help moderate these forums and offer assistance where I think I might be able to help so I have no way of informing you of progress. Nicolas gets regular info and updates from PRT so I am sure he will let everyone know as soon as ProScreener is improved or updated.
To try to speed things up send reports and requests to PRT or use the suggestions topic in the ProRealTime Platform Support forum.
Without the indicator code it is impossible to tell you how to adapt it so as to use standard variables and not arrays. I imagine that if it uses arrays that is so as to do something that is impossible without using them or to massively speed up an indicator that would take an eternity to calculate a result without them.
To help us continually offer you the best experience on ProRealCode, we use cookies. By clicking on "Continue" you are agreeing to our use of them. You can also check our "privacy policy" page for more information.Continue
.
