ending a program-what to type

Forums › ProRealTime English forum › ProOrder support › ending a program-what to type

This topic contains 13 replies, has 5 voices, and was last updated by avatar Brisvegas 10 months, 1 week ago.

View all attachments
Viewing 14 posts - 1 through 14 (of 14 total)
  • 12/06/2017 at 5:32 PM #54906
    avatarcyrillic

    Hi
    Ive written a program but when i try to backtest it i get a message “syntax error line 35 character 1 please complete the syntax of this line ” but there’s nothing in line 35. what should I type there ?? The last line is the stoploss value. Please advise

    12/06/2017 at 6:12 PM #54908
    avatarrobertogozzi

    Place your cursor after the last character of your strategy, then keep the DEL key pressed for a while, just in case there’s some garbage you can’t see!

    Another way is to copy the whole strategy, from the first character to the last one, then cancel the strategy, then again paste it in a new strategy.

    I don’t know if either works but it’s worth trying!

    Roberto

    12/06/2017 at 8:55 PM #54917
    avatarcyrillic

    Thanks Roberto.
    I’ve done that but it still comes back with the same thing and there’s nothing on the line.
    The previous line was the stoploss which was accepted by the syntax indicator on the left.
    What is the last thing you guys write into your programs ??
    As you can guess I am a complete newcomer to programming, I find it very interesting but
    I just don’t understand this last bit. Also what are BBCodes ??

    Regards Paul

    12/06/2017 at 10:21 PM #54927
    avatarVonasi

    Usually this is because you are short of an ENDIF somewhere.

    12/07/2017 at 12:51 AM #54934
    avatarrobertogozzi

    You should easily spot a missing ENDIF because your last lines should be indented, if this is the case.

    12/07/2017 at 10:30 AM #54951
    avatarcyrillic

    Thanks Roberto and Vonasi that’s what I have done, so now it backtests but the result is nil over a year so it looks like I’ve screwed up somewhere. Wow, this is quite a learning curve. This is my first attempt (fail) can you see what’s wrong with it please

    DEFPARAM CumulateOrders = False
    DEFPARAM FlatBefore = 065000
    DEFPARAM FlatAfter= 160000
    // Conditions to enter long positions
    sto=Stochastic[15,3](close)
    if sto=20 then
    ma=Average[50](close)
    a=ma>ma[10]
    if a then
    BUY 1 CONTRACTS AT MARKET
    ENDIF
    ENDIF

    // Conditions to exit long positions
    ema=ExponentialAverage[21](close)
    if close CROSSES UNDER ema then
    SELL AT MARKET
    ENDIF

    // Conditions to enter short positions
    if sto=80 then
    a=Average[50](close)
    if a>average[10](close) then
    SELLSHORT 1 CONTRACTS AT MARKET
    ENDIF
    ENDIF

    // Conditions to exit short positions
    if a>average[10](close) then
    if sto=20 then
    EXITSHORT AT MARKET
    ENDIF
    ENDIF
    SET STOP $LOSS10

    12/07/2017 at 10:38 AM #54952
    avatarNoobywan

    Your “if sto=20” and “if sto=80” will almost never happen, most of the time it will cross over or under those levels without ever being exactly equal to 20 or 80, so what’s inside your if statement wouldn’t be visited.

    >> For clarity of messages on ProRealCode’s forums, please use the “<>” (insert PRT code) button in the message editor toolbar to separate the text of the code part! Thank you! <<

    12/07/2017 at 8:25 PM #55011
    avatarcyrillic

    Thank you Nooywan, I have changed the symbol but it now seems to backtest but there is no result, only a flat line, and that’s over a year so I must still be doing something dire.
    Is there a strict protocol for constructing a procedure ?
    This PRT code doesnt seem to copy/paste too accurately, i will repeat in normal code if you wish.

    12/07/2017 at 11:34 PM #55017
    avatarrobertogozzi

    I tested it on Dax and EurUsd 1,2,5,10,15,30 minutes,1,2,4 hours and it works. It is a losing strategy, but it works!

    12/08/2017 at 5:45 PM #55171
    avatarcyrillic

    I have to modify it but ATT i’m having problems with the backtest. First it displayed just a flat line, but now every time I click on a share it goes through the backtest routine and has changed the graph from candlestick to line chart. It does this with every chart. How do I get it back to candlestick display and turn off this backtest routine. It must be here somewhere but I can’t find it.

    12/13/2017 at 8:59 PM #55606
    avatarcyrillic

    Hi
    When writing code , does it have to be presented in a certain sequence, could you please check this piece of a simple program and tell me what is wrong with it ?

    I ran it against todays(13th) GBPCAD using 1000 units and 2 min timeframe.
    Visibly I see strikes at 1138, out at 1156
    1258, out at 1316, 1350 (loss), 1557 out at 1612, 1821 out at 1850
    The backtest showed 1 strike which was not correct so am I writing the code in the wrong order? Please advise.

    12/13/2017 at 9:41 PM #55607
    avatarBrisvegas

    try this ,  i assume the second buy is a short given the parameters 

    12/13/2017 at 10:22 PM #55610
    avatarrobertogozzi

    You should simply use

    and you will discover that, today, sto is never <=20 so the outer block (and inner ones as well, of course) IF…ENDIF is never true.

    12/13/2017 at 10:28 PM #55614
    avatarBrisvegas

    Stops too tight and if thats a mean reverting strat id have shorts and longs same position size as well   

  • Author
    Posts
Viewing 14 posts - 1 through 14 (of 14 total)
Similar topics:
custom parameter type for variables
last position type
type of contract

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