ProScreener changing the code itself

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • 03/05/2018 at 9:36 AM #64394 quote
    voigtbs
    Participant
    Average

    Hi everyone. First timer. My ProScreener keeps changing the codes that I have written. For example this is what I coded

    Timeframe (15 Minutes)

    c101 = ExponentialAverage[10](close) > ExponentialAverage[22](close)

    c102 = ExponentialAverage[22](close) > ExponentialAverage[50](close)

    c103 = close > open

    If I check the screener an hour later this is what I have

    c101 = close = open

    Secondly – my screeners are not producing the results that they should. They are including lots of securities that do not meet the criteria

    IS ANYONE ELSE HAVING THIS SAME ISSUE

    Thanks

    Bernard

    03/05/2018 at 10:12 AM #64403 quote
    Nicolas
    Keymaster
    Master

    Topic moved to ProScreener support forum.

    This is a very strange behavior that I have never been confronted with! My code has never changed by itself! really very curious …
    For results that do not match the criteria, do you have access to the real-time data or just the end-of-day data?

    03/05/2018 at 10:54 AM #64409 quote
    voigtbs
    Participant
    Average

    I have real-time data and that is my main concern. I have also tested it on end of day data with the same results.

    03/05/2018 at 2:15 PM #64445 quote
    Nicolas
    Keymaster
    Master

    Ok, could you please post here your full screener code, then I should be able to understand why it returns wrong results, thanks.

    03/07/2018 at 6:21 AM #64642 quote
    voigtbs
    Participant
    Average

    Thanks. The codes changed every day for at least 30 days. Now that you have asked nothing has changed. I will post a change as soon as it happens.

    03/07/2018 at 11:11 PM #64706 quote
    voigtbs
    Participant
    Average

    Hi. When I started up this morning this is the code I had for Mov Ave

    indicator1 = (DHigh(1) + DLow(1) + DClose(1))/3
    c1 = (close = indicator1)

    indicator2 = 2*((DHigh(1) + DLow(1) + DClose(1))/3) – DLow(1)
    c2 = (close = indicator2)

    indicator3 = (DHigh(1) + DLow(1) + DClose(1))/3+(DHigh(1)-DLow(1))
    c3 = (close = indicator3)

    indicator4 = DHigh(1)+2*((DHigh(1) + DLow(1) + DClose(1))/3-DLow(1))
    c4 = (close = indicator4)

    indicator5 = 2*((DHigh(1) + DLow(1) + DClose(1))/3) – DHigh(1)
    c5 = (close = indicator5)

    indicator6 = (DHigh(1) + DLow(1) + DClose(1))/3-(DHigh(1)-DLow(1))
    c6 = (close = indicator6)

    indicator7 = DHigh(1)+2*(((DHigh(1) + DLow(1) + DClose(1))/3)-DLow(1))
    c7 = (close = indicator7)

    SCREENER[c1 AND c2 AND c3 AND c4 AND c5 AND c6 AND c7] (null AS “null”)

    Before I shut down last night I checked all the codes to ensure that they were what I had coded. This is what the code was for mov ave (I had saved it and this is the import)

    Timeframe (15 minutes)

    c1 = ExponentialAverage[10](close) > ExponentialAverage[22](close)

    c2 = ExponentialAverage[22](close) > ExponentialAverage[50](close)

    c3 = close > open

    Timeframe (30 minutes)

    c11 = ExponentialAverage[10](close) > ExponentialAverage[22](close)

    c12 = ExponentialAverage[22](close) > ExponentialAverage[50](close)

    Timeframe (1 hour)

    c21 = ExponentialAverage[10](close) > ExponentialAverage[22](close)

    c22 = ExponentialAverage[22](close) > ExponentialAverage[50](close)

    Timeframe (15 minutes)

    c101 = ExponentialAverage[10](close) < ExponentialAverage[22](close)

    c102 = ExponentialAverage[22](close) < ExponentialAverage[50](close)

    c103 = close > open

    Timeframe (30 minutes)

    c111 = ExponentialAverage[10](close) < ExponentialAverage[22](close)

    c112 = ExponentialAverage[22](close) < ExponentialAverage[50](close)

    Timeframe (1 hour)

    c121 = ExponentialAverage[10](close) < ExponentialAverage[22](close)

    c122 = ExponentialAverage[22](close) < ExponentialAverage[50](close)

    SCREENER[(c1 AND c2 AND c3 and c11 and c12 and c21 and c22) or (c101 AND c102 AND c103 and c111 and c112 and c121 and c122)]

    Thanks Bernard

    03/07/2018 at 11:17 PM #64709 quote
    voigtbs
    Participant
    Average

    Another one of the screeners also changed. This is what it changed to

    indicator1 = ExponentialAverage[10](close)
    indicator2 = ExponentialAverage[22](close)
    c1 = (indicator1 >= indicator2)

    c2 = (close > open)

    SCREENER[c1 AND c2] ((close/DClose(1)-1)*100 AS “%Chg yest.”)

    I do not have the original but c2 was not close > open but a Trader Dynamic Index crossover. I originally downloaded the TDI from this site.

    03/14/2018 at 2:34 AM #65271 quote
    voigtbs
    Participant
    Average

    Hi Nicolas. Have you got any thoughts or a possible solution to this problem

  • Author
    Posts
Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.

ProScreener changing the code itself


ProScreener: Market Scanners & Detection

New Reply
Author
author-avatar
voigtbs @voigtbs Participant
Summary

This topic contains 7 replies,
has 2 voices, and was last updated by voigtbs
8 years ago.

Topic Details
Forum: ProScreener: Market Scanners & Detection
Language: English
Started: 03/05/2018
Status: Active
Attachments: No files
Logo Logo
Loading...
Do you like cookies? 🍪 We use cookies to ensure you get the best experience on our website. (Learn more)
©2026 ProRealCode - Trading & Coding with ProRealTime™