NAS 2m HULL-SAR trading system

Forums ProRealTime English forum ProOrder support NAS 2m HULL-SAR trading system

  • This topic has 343 replies, 42 voices, and was last updated 1 year ago by avatarbege.
Viewing 15 posts - 196 through 210 (of 344 total)
  • #165045

    “Code is invalid. Please correct it. Line 18: Characters missing. Suggestions: end of code”

    Which file are you referring to above??

    The .itf I posted starts and runs on ProOrder (no errors) … see attached running since last night (no trades yet).

     

    #165050

    I have been experimenting with v5.3 on different markets

    It seemed to be the same type of problem LaurentBZH35 experienced on v7.5.

    #165066

    When MM=0, does it then matter at all the settings for MM?

    if MM = 0 then the rest is irrelevant, positionsize just stays the same.

    1 user thanked author for this post.
    #165105

    Optimiser giving weird results now?

    Attached is a good result .itf … with std back in (at line 65) but also accepted (no errors) by ProOrder.

    CTime is optimised between Hour > 10 and Hour < 23 on attached … hence version – GHv1 – se we don’t get mixed up.

    Only long position?

    #165111

    Sorry

    How can I test with long AND SHORT position

    ????

     

    Thanks

     

    #165140

    How can I test with long AND SHORT position

    Rework the code to introduce conditions for short positions , then optimise all the many variables, then Walk Forward Test, then Monte Carlo Test then Robustness Test then share the code with us all so we can all then Demo Forward Test short positions. 🙂

    1 user thanked author for this post.
    #165147

    Actually with NAS-2m-HULL-SAR-v5.3L.itf you can also change Tradetype = 1 to go Long/Short but it was never very successful, so Grahal’s is the better answer!

    2 users thanked author for this post.
    #165337

    How can I test with long AND SHORT position

    Rework the code to introduce conditions for short positions , then optimise all the many variables, then Walk Forward Test, then Monte Carlo Test then Robustness Test then share the code with us all so we can all then Demo Forward Test short positions. 🙂

    Of course I’ll do all that you write…. but I don’t understand why T.S. doesn’t go short with this  instructions…..

     

    #165340

    because positionsize*0 = 0

    it should be

     

    2 users thanked author for this post.
    #165347

    Of course I’ll do all that you write

    Apologies for my ‘outburst‘, I should have checked the code, I was not getting any short trades either, so I kinda was telling myself I needed to do all I wrote! 🙂

     

    #165357

    Of course I’ll do all that you write

    Apologies for my ‘outburst‘, I should have checked the code, I was not getting any short trades either, so I kinda was telling myself I needed to do all I wrote! 🙂

    Absolutely no problem. You and others in this forum are doing an amazing job EVEN for someone like me who is starting programming with PRT. Personally I just have to thank you for that

     

    1 user thanked author for this post.
    #165505

    I have been experimenting with v5.3 SHORT versions (Tradetype = 3 to go Short) on different markets but can´t make it work at all.
    I use MM = 0 and Cumulateorders = false.

    -If I try to start attached “Dow 2m HULL-SAR v5.3S” in Proorder I get the message:

    “Code is invalid. Please correct it.
    Line 24:
    Characters missing. Suggestions: end of code”

    -If I remove the first line “// 2021-03-08: Optimerat…” I don´t get the error message above any more.

    -I then proceed with “Prepare for automatic trading”. Now the values at line 18 and 22 gets changed for some reason (see image) and I can´t change it back at this stage.

    -I can start it in Proorder but it soon stops due to “Division by zero”.

    I would be very grateful if someone could take a look at this and find a solution! I think there is some potential with this algo also on the short side fore several markets.

    #165510

    I have made a copy with fixed values in the code instead to work around if the problem was that  line 18 and 22 gets changed as in the Picture above.

    -I then don´t get the “Code is invalid…” even if I have the first line “// 2021-03-08: Optimerat…” is in the code.

    -I can start it in Proorder but it soon stops due to “Division by zero”.

    #165513

    line 18 and 22 gets changed for some reason

    Changed to  … as shown in the image …  or changed from … what is shown in the image?

    Weird … 17 decimal places, optimiser doesn’t accept more than 6 decimal places.

    #165516

    Changed to … as shown in the image … or changed from … what is shown in the image?

    Changed to whats shown in image with a lot of decimals.

Viewing 15 posts - 196 through 210 (of 344 total)

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