Unbroken highs

Viewing 12 posts - 1 through 12 (of 12 total)
  • #18915

    Hello all,

    Suppose I have an indicator that I use to generate entry signals. This indicator has the value of 1 when the signal is active and 0 when no signal exists.

    How do I create a screener that looks for stocks where the high of the week in which the BUY SIGNAL indicator flashed a signal has not been violated? In other words, if a BUY SIGNAL appeared, say, 15 weeks ago, then every week since then has had a lower high.

    Here’s what I’ve coded:

    I’m getting the following message: “An error has occurred during the execution of your ProScreener market scan”.

    Your assistance on this would be extremely helpful.
    Thank you,
    Igor

    #18922

    Hi Igor

    What is your code for the “Buy Signal” Indicator … the code might help to suss out the cause of the error?

    Cheers
    GraHal

    #18937

    Hi GraHal,

     

    The code is as follows:

    Thanks in advance.

    Igor

    #18981

    Any suggestion from anyone?

    #18982

    Hi Igor

    Below will give you the highest high in the last 15 periods up to the last period, …

     

     

     

    #18983

    I’m only saying above as that was what flashed in my mind when I read your posts and code. Above may spark some further thoughts in your mind.

    I’ll come back if I have any more ideas re your requirement. I’m having a ‘motivation crisis’ today, but nothing serious 🙂

    #57767

    Hi from8to800,

    Did you find the solution to your problem?

    I’m seeing the same message some times…

    Thank you, and good luck!

    #57807

    Here’s what I’ve coded:

    I’m getting the following message: “An error has occurred during the execution of your ProScreener market scan”. Your assistance on this would be extremely helpful. Thank you, Igor

    Your variable SIGNAL may only have value 1 ONLY when myBUYSIGNAL[20], i.e. the last iteration, will be true, else… it will ALWAYS be ZERO even if the first  iterations were all true!

    Moreover,

    will be expanded, at scan time, to, say

    and will almost always generate an error!

    Roberto

    1 user thanked author for this post.
    #57816

    Hi everyone, and thank you Roberto for your kind atention. I’m afraid I don’t completely understand your explanation.

    I’m having the same error as ‘from8to800’  but, surprisingly my code fails just some times. Most times, it works fine. I don´t think its a network problem, because it fails always with the same stocks (for example, it fails if you try to backtest OTEX with 3000 bars)

    The strategy tries to catch high capitalization breakouts, and I’m trying to optimise two variables: ‘volatilidad’ from 2 to 8 (step=3) and ‘misumacap’ from 100 to 300 (step=50).

    Thanks in advance,

     

    Miguel

     

     

    #57834

    @vitatrader35, this a ProScreener support forum, if you want to talk about a strategy you should open a new topic in the ProOrder Support Forum. Thank you.

    I’m afraid I don’t completely understand your explanation

    Let me know what it is, so I can try to explain it better. I was just pointing out a couple of logic errors, I did not mean to correct the code at all, since I did not understand exactly what from8to800 was trying to accomplish.

    #57879

    Hi, Robertogozzi

    I just posted here because yours is the only explanation I found to this kind problem. I read your message more carefully and now I think I understand.  Thank you, because I think you opened the way to find the solution (its more than possible that my code has one -or more- logic problem…). I’ll try to make the question in the right place.

    One more question, about the original post: could this also be an error?

    (wrong)

    c1= highest[high](i) >= signal

    (righ, if all the iterations were positive)

    c1= highest[i](high) >= signal

    Thank you for your help

    #58590

    Yes vitatrader35, that would work finely!

    But be aware that

    when signal IS zero will be expanded, at scan time, to

    thus making c1 TRUE!

    I don’t know if this logic behaviour is unwanted or not, I just pointed it out.

     

    1 user thanked author for this post.
Viewing 12 posts - 1 through 12 (of 12 total)

Create your free account now and post your request to benefit from the help of the community
Register or Login