Hi there, I’ve had issues with screeners and using the ‘Average’ command before (apparently ProScreener doesn’t like the second argument in the parenthesis so much…), but thought they would have been fixed by now. Can anyone spot the problem with this (doesn’t return any results on any list of instruments)?
It seems ProScreener will only return results up to the value of 6 as the MA type…
Even when I manually calculate the Hull MA I don’t get any results, even though translating to an indicator to obtain e.g. a histogram when the condition is true works just fine:
Doesn’t fill me with confidence in ProRealTime as a platform if simple things like this can’t be programmed. I know v11 is coming out soon with a designated HullAverage instruction, but still…
Yes I did that thanks, Roberto, as alluded to in my post (“even though translating to an indicator to obtain e.g. a histogram when the condition is true works just fine”). I can confirm it works fine as an indicator, yet ProScreener doesn’t pick it up…
The screener is designed for cryptos so am not so interested in backtesting on ProOrder, GraHal, but thanks for your observation.
What myself and Roberto were trying to provide is information to show if Hull MA works in a ProScreener as your original post suspected that Hull MA didnt work in ProScreener.
Roberto’s code / results proves that HullMA does work in ProScreener.
I think most people would regard that as sub-optimal.
Maybe and we take / agree your point, but Roberto code shows that ProScreener can read the Hull MA type 8 … which your original post read / doubted that HullMA could be used at all at any lookback period / in any way at all in ProScreener?.
I guess now we are onto the next phase of coding … to get a Screener that gives you want you want (now we know / have proven that Hull MA works in ProScreener).
.
