Help coding reference to DAILY bars

Viewing 9 posts - 1 through 9 (of 9 total)

Author

Posts
06/20/2017 at 11:33 AM #38635 quote
robertogozzi
Moderator

Master
I still need some help to reference current/past bars.

In the pic I’m showing two cases about daily bars (but I think this can apply to any TF, as well):

A – I want to screen all current bar ranges to be > than the previous closed ones. Are
```
IF Range > Range[1] THEN....
```
and
```
IF Range[0] > Range[1] THEN....
```
both correct?

B – I want to screen all previous closed bar ranges to be > than the second previous closed ones. Is
```
IF Range[1] > Range[2] THEN....
```
correct?

I hope I can manage to understand and code ProScreener correctly sooner or later!!! Thank you so much.

x.jpg
06/20/2017 at 12:57 PM #38646 quote

Nicolas
Keymaster

Master

Both A and B codes are correct. Do you got some problems with your screener?

06/20/2017 at 3:23 PM #38659 quote

robertogozzi
Moderator

Master

I hope now the rules remain in my brain!

I’ll try again and I’ll let you know if I am still in trouble.

Thank you so much Nicolas for your invaluable help.

06/21/2017 at 12:27 AM #38700 quote
robertogozzi
Moderator

Master
This screener applied to DAILY GbpUsd (and a couple more pairs) chart returns the current RANGE as >= than that of the previous bar, which is not as you can see.
```
Value = 0
IF Range[0] > Range[1] THEN
   Value = 1
ENDIF
SCREENER [Value]
```
What’s wrong?

Thank you.

GbpUsd-screener.jpg GbpUsd-screener-2.jpg
06/21/2017 at 8:35 AM #38710 quote

Nicolas
Keymaster

Master

What’s wrong with you? 😀 I got good results this morning with your code..

forex-screener-range-value.png

06/21/2017 at 1:10 PM #38733 quote

robertogozzi
Moderator

Master

I see, but my pic did not show good results.

I tried just a minute ago on OIL 4h TF and still got bad results. The current bar has NOT a greater range than the previous one!

It’s not the first time I notice strange results and that’s why I don’t rely on screener! This scares me a bit because ProScreener may not be a great issue, but what if ProOrder has similar bugs?

Anyway, thank you Nicolas, I know it’s not your fault.

4h-oil.jpg

06/21/2017 at 1:28 PM #38739 quote

Nicolas
Keymaster

Master

Did not test it in demo, only with a live PRT-CFD account, have you tested it with your live account too?

06/21/2017 at 3:54 PM #38758 quote

robertogozzi
Moderator

Master

I am using that screener on IG live account.

No longer that 1 hour ago I have experienced a “Server Unavailable” message on ProScreener (while ProOrder was still working fine) for about 30 minutes and now everything seems to work as expected.

Is PRT likely to have “removed” some unwanted data/bug in the meantime? If yes it would be great if they just say YES, so we know for sure they are doing their best to make PRT better and better and that they listen to customers’ remarks/suggestions.

Thanks again Nicolas for your help.

GraHal thanked this post

06/21/2017 at 5:08 PM #38765 quote

Nicolas
Keymaster

Master

Seems related to the IG server then.. You are an IG customer, data problem are linked to them, I think it’s not a platform issue since I didn’t have the issue with PRT-CFD.

robertogozzi and GraHal thanked this post
Author

Posts