End Of Day – YEN M15 Strategy

Forums ProRealTime English forum ProOrder support End Of Day – YEN M15 Strategy

Viewing 15 posts - 61 through 75 (of 96 total)
  • #213038

    let’s do the V11 with only Long position, now I will try on M5 with 200k :

    Next step is to add Short position and try do control this drawdown problem, and maybe next time is to control the quantity of share for enter with more share if the trade is positif and with more share if the equity is positif

    1 user thanked author for this post.
    #213583

    Before continuing let’s set some good rules about the GTM schedule and the Tokyo session which opens from 09Am to 3Pm local time in Tokyo, If you think I’m wrong or that the code is not good, please participate 😉 :

    1 user thanked author for this post.
    #213614

    Thank you for sharing your code.

    I only want to point out that those time offsets from UTC are valid when DST is active, when it is not, then 1 hour has to be subtracted from them.

    In addition, with GTM you probably meant GMT, right?

     

    1 user thanked author for this post.
    #213617

    Let’s say here is the new code, I reduced the size of the segments so that it stops just before the box, and I added the size of the range :

    #213619

    tks you @robertogozzi for your tips, what is DST Active or Not pls ?

    and yes GTM it’s my French mistake, it’s GMT = UTC

    #213622

    DST stands for Daylight Saving Time (heure d’été).

    In most EU it starts on the last Sunday of March at 02:00 (2am) and ends on the last Sunday of October at 02:00 (2am). In EU not all countries are at UTC+2 (UTC+1 when DST is not active), Portuga share the TZ with UK (now UTC+1), Greece, Finland, Rumenia etc… are now in UTC+3 (https://www.timeanddate.com/time/europe/).

    Not all countries, across the world, as well as some states in USA, support DST.

     

     

     

    1 user thanked author for this post.
    #213631

    Thank you very much for your answer and your tip, at first I thought it was an option I could enable or disable directly on the ProRealTime software, I think this is not the case, please correct me if I am wrong

    So I had to think differently about my indicator and it made my head hurt 😅 but anyway I hope to make progress thanks to you 😊,

    Here is a first version of the indicator with the summer hours and others

    I don’t know yet how to manipulate the dates for the weekend when the time change, For the moment I stop before the last week of March and October (< day 24)

    if you have a link on the forum or an example it would be appreciated 😊

    #213700

    hi everyone

    I am progressing slowly but surely, nothing exceptional, here is a draft in version 12, I’ll try to sort it out for version 13,

    also I made the choice deliberately to be only long on the market, the programming of a strategy is already complicated so we are not going to complicate it even more with only one code for the Long and Short position at the same time, for the Short I let you reverse the code

    at the moment I am trying to manage and control just the entries and their stop loss, I notice that if I have a position with more than one stock then the FirstSL is not well managed, this will be the next step

    I also noted some notes in the code at the end just after the “Hello ToTo” logo, it allows me to remember what I’m doing and to find my notes in the code, if you have other origanisation solutions I’m interested

    #213716

    no need answers now, just speack to myself 😁

    #213723

    I also noted some notes in the code at the end just after the “Hello ToTo” logo, it allows me to remember what I’m doing and to find my notes in the code, if you have other origanisation solutions I’m interested

    Tip: to find whatever I need to find in long codes (notes, but also groups of code lines far away from each other but related), I often add keyword(s) with //, not used anywhere else in the code, and the CTRL+F (“find”) function applied to said keyword(s), in order to save time scrolling/searching by jumping with “find” from one occurrence to the next.

    1 user thanked author for this post.
    #213735

    I found solution to my problem by adding this code at line 63 in v 13 :

    #213736

    @JC_Bywan tks you so much for you tips, but I don’t realy understand the idea, do you have a photo or link pls 😃 ?

    #213745

    Photo of your code inside an editor window: click on magnifying glass (or click mouse inside code area and press CTRL+F), then let’s say you want to find fast your “needs to be improved” comments not wasting time scrolling, you type it next to “find”/”rechercher”, then click on “next”/suivant, and it will jump from one to the next, and when reaching last one if clicking next again it goes back up to first one.

    1 user thanked author for this post.
    #213889

    Hello everyone, I hope you are well

    By the way, thank you very much @JC_Bywan for your answer 😊

    Here is version 15 of my code, before I start trying to make money I mainly want to try and control my losses, and I run into a small problem when I have multiple levels of stop output sometimes I get run on a worse level I guess it’s a programming issue,

    You can see a capture with three output levels respectively, I renamed for ease in SL 1,2 and 3
    SL-3 = BreakRangeLevel (green)
    SL-2 = BreakRangeStarter (blue)
    SL-1 = FirstSL (Red)

    Sometimes my long position is taken out only at the SL-1 level while the other levels are already there, I don’t know what to do?

    As I know it’s a bit complicated for some people to reread all the code and understand I also opened a new post where I phrased the question differently and so here’s the link you might be able to answer me on that post instead of this one I hope I don’t get rapped for a double post

    once I have mastered this problem of the three levels of SL I think I will move on to the calculation of daily losses, and latent losses or gains

    tks you

    1 user thanked author for this post.
    #213907

    I think they overcomplicate a lot and if in doubt the code is over optimized. Have you tried running the code for at least several months? What does the back test look like?

    1 user thanked author for this post.
Viewing 15 posts - 61 through 75 (of 96 total)

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