ProRealTime bug? Different results in ProOrder to Indicator

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #27029 quote
    robdavrobdav
    Participant
    Veteran

    I have some code which gives completely different results when used in an indicator than when back tested in a ProOrder system. How can I raise this as a support case? Does anyone know?

    #27092 quote
    DerekDerek
    Participant
    Veteran

    Hi robdav,

    maybe it is caused by your market’s time settings. Here is a thread about it:

    WARNING! IG Backtests are currently wrong!

    robdav thanked this post
    #27131 quote
    robdavrobdav
    Participant
    Veteran

    So, the code is the same but you need to implement it slightly differently in the ProOrder system than in the indicator.

    In case it helps anyone going forward. You need to do this:

    PriceCrossesUnderWA5 = open CROSSES UNDER WA5 OR close CROSSES UNDER WA5 OR high CROSSES UNDER WA5 OR low CROSSES UNDER WA5

    instead of this:
    PriceCrossesUnderWA5 = open OR close OR high or low CROSSES UNDER WA5

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.
ProRealAI ProRealAI New

Stuck on this ProBuilder code?

Describe what this topic is trying to build, in plain English, and ProRealAI writes the ProRealTime™ indicator, screener or system for you.

Available in 7 languages
Try ProRealAI

ProRealTime bug? Different results in ProOrder to Indicator


ProOrder: Automated Strategies & Backtesting

New Reply
Author
author-avatar
robdav @robdav Participant
Summary

This topic contains 2 replies,
has 2 voices, and was last updated by robdavrobdav
9 years, 7 months ago.

Topic Details
Forum: ProOrder: Automated Strategies & Backtesting
Language: English
Started: 03/03/2017
Status: Active
Attachments: No files
ProRealCode ProRealCode
Loading...