IMPORTANT : BIG BUG ON SPREAD !

Forums ProRealTime English forum ProOrder support IMPORTANT : BIG BUG ON SPREAD !

Viewing 15 posts - 31 through 45 (of 66 total)
  • #184340

    More tests needed. 🙁

    So the last thing I did was using a spread of 1,9 in the Editor, with this for results on 960.000 of position : see first attachment.

    Let’s say that we’re now anticipating the middle of the night where spreads can be 1.6 (twice the 0.8 I anticipate for day time). Now, should I enter 3,8 (twice the 1,9) in the editor to approach reality ?
    In order to mimic that situation, I need to enter the 1,6 in the program code as well.

    So hopefully this is not too confusing … In order to reach 0,8 I entered 1,9 in the Editor. Now I want to reach 1,9 and what to enter in the Editor for that. I start with 3,8 …
    Well, see 3rd attachment. It works great.

    Can I now work towards a desired spread of 0,4 as well ?

    Well, not entirely because I would need to enter 0,95 (0,36 / 4) in the Editor and I can’t (that other issue). So to be on the safe side, I make 1 of that. The result is in the 3rd attachment. Thus, 0.00004 * 960.000 = 38,40 and you see that in the SpreadAmount (Orange) again.

    I seem to be showing the exact same as in earlier posts, but this is not true because I off set the Spread in the Editor;
    I empirically found that offset to be 1,9 over 0,8 (which seems to be 2x + 0,3 which I don’t care about) but this derived offset seems to be linear. So what I did in this post – I multiplied and divided both editor and program code numbers with the same factor, and all remains linear (and the changing of the required 0,95 for the Editor to 1 is harmless but should be rounded upwards for safety).

    Crazy.
    And it (thus ?) does not seem to be a rounding error.

    Here’s another suspicious aspect :
    So I require two times the expected spread plus “something”. EUR/USD is 1,13 today. 2x 0,8 = 1,6. 1,13 x 1,6 = 1,808. This is mighty close to the 1,9 needed, knowing that I can’t test for 1,808 in the Editor and it is either 1,8 or 1,9 (the 1,8 not giving the required results).
    *This* now could be my own culprit, starting with taking position in my base currency of thinking, EUR, while the portfolio works in USD. So with some more “base” hoopla, this additional offset could be my own issue. Someone normally working in EUR (or in USD with USD portfolio) may not see this required additional offset. But the required times 2 should remain …

    ?

     

    1 user thanked author for this post.
    #184346

    For those who want to check for themselves … See the attachment.

    Find yourself an Entry which stays flat the next bar. See the white vertical line and the one-line red to the right of the down-arrow (short in this case).
    The drop in the yellow line, is the instant drop because of the denoted spread (my empirically found 1,9 for the desired 0,8 for my situation).

    Calculate the spread yourself from the number you entered in the Editor. Graph that (the orange one in the top in my case).
    Take PositionPerf to calculate the spread as how PRT calculates it (PositonPerf shows on the 4th line here).
    Multiply that with the PositionAmount.  This would give you the bottom “Loss” line and it should resemble-ish the self calculated orange line.

    Notice that right after entry, the price remaining flat, should always provide a loss.

    The Detailed Report now should show realistic results. And Yes, they will be lower than you are used to, depending on the resilience of your system/algo.

    Do not forget to check (per this post) whether you are subject to the culprit in the first place. Match the top (orange) and bottom (yellow) lines;
    Want to change the spread your system works with ? change it in the program for graphing (it is nowhere used for formal calculations in my case) and match the Editor number to that (observe orange vs yellow again).

    See it as a renewed opportunity to be able to put systems Live which not readily run into a loss because of these issues. You will do better now. 🙂

    Lastly, please notice that this is a real issue only when you’re a kind of scalping. I mean, with one trade per month you won’t notice the 40 euros etc. difference on a required profit of say 1000. But if the profit is set to 50 or so to begin with (short trades), the spread is crucial.

    Happy New Year !

    1 user thanked author for this post.
    #184356

    So, to summarise 🙂 … if we use spread set at whole numbers we are good to go … True or False?

    #184358

    Re my flippant remark above … I’m looking for a work around so we can continue optimising until PRT fix the bug?

    #184361

    Well, to me this is not about using integer spread numbers (pls see my posts – I never arrived at that).

    But using some crazy high spread in the Editor like 1.9 in my case, also does not seems to be the solution. Not even with strong curve fitting I am able to make any profit with that anywhere.
    And so there is even more going on. I mean, Live I am doing quite fine, despite the spread seems to be way off. With the spread set as I propose myself, I would be broke soon.

    I am a bit out of ideas as to what is actually going on.
    I tend to set all back to how it was, see that the eaten spread is off by 50% or so, but make profit because my “consistent” strategy is able to cope with that. And mind you, this could be in order for anyone working so enormously long on everything. @zilliq, what do you think yourself ? others ?
    Could this be stirring the pot / stoking fires without real reason ? –> Well, I know what I presented is correct. But I also know I learned to tune with that given. And personally I really can’t start all over.

    @GraHal, I think I feel the same as you do. It feels unsafe. Unsecure …

    1 user thanked author for this post.
    #184377

    Dear all,

    This is just a quick note to let you know that what I started to work out ~ 24 hours ago, is incorrect;
    I couldn’t sleep of the fact that backtesting would not workout any more, while Live is just fine.
    The main culprit in my thinking will have been the taking of all of the spread right at the Enter of the trade, while PRT – and most probably the Broker as well, will take half of it at the Enter and the other half at the Exit. So, it is at my convenience that I take the 100% at the Enter because that works more easily. The error occurs when I start to use PositionPerf to check all out; PositionPerf will only show half of the eventually taken spread.
    StrategyProfit will show (incorporate) all taken spread, but (obviously) after the trade has been closed.

    I will check upon this the soonest, but currently it is the only explanation for what I see happening.
    When this is normalised again, we can and should continue with what zilliq has noticed; most probably this is about the rounding issue I started out with yesterday (a typical phenomenon which makes results “jump”; it flips from rounded down to rounded up).

    For now, apologies for the stir from my side !
    Peter

    #184390

    Allow me to show unambiguous test results (without subjective judgment) …

    I have used one trade – and one trade only, for which a varied the Spread in the Editor from 0 to 1.7. The 1st attachment is just for reference. All the trades look like that except for the spread of 0 which shows in the 2nd attachment. I have organised it so that the TP is not relative to the desired profit, but merely is a fixed position (during trailing).

    0,0   93,50
    0,1   267,75
    0,2  267,75
    0,3  259,25
    0,4  259,25
    0,5  250,75
    0,6  250,75
    0,7  242,25
    0,8  242,25
    0,9  233,75
    1,0  233,75
    1,1  225,25
    1,2  225,25
    1,3  216,75
    1,4  216,75
    1,5  208,25
    1,6  208,25
    1,7  199,75

    The 0,0 (2nd attachment) is different because very coincidentally my system takes profit at a lower level which occurs – again coincidentally – because of a retrace at a level sufficient profit to exit is present. The sufficient profit in relation to the higher spreads, occurs because of the lower spread (is more profit to begin with).

    All increments are linear with 8,50, if we only accept that increasing the spread with 0,1 pips will jump because 0,15 is really required for smoother increase (decrease of profit).
    Subjective : I suppose this relates to the internal (PositionPerf) calculations with 5 digits, while the spread as given in the editor also works with 5 digits and should be one more (6) in order to see a smooth increase. I did not work this out further;
    Most important is that spread is just working – also with decimals – and just linearly.

    The figures were taken from PRT itself, and not from my own graphing. As an example, see 3rd attachment for the spread of 0,8.

    #184497

    Hi @PeterSt

    Sorry, lot of works

    Globally agree with you

    If I resume

    Seems this bug is only on Forex not Indices

    The impact if more important if you do scalping, have small position, small unit of time …

    Seems to be a bug of “rounding” number. PRT don’t consider the decimal on spread (1.2=1.3=1.5 and so on…)

    Can be “replace” by cost by order. After some trials seems to give quite the same results

    So difficult to estimate as there are so many diferences between backtest/real/proorder…And as I previsously said in many post I don’t like backtest because there are actually not accurate and so Walking Forward

    But clearly hope they will correct this big bug

    Have a nice day

    #184504

    Seems to be a bug of “rounding” number. PRT don’t consider the decimal on spread (1.2=1.3=1.5 and so on…)

    Hi zilliq,

    It is difficult for me to understand how you can see that the decimals are not recognized. The table I showed in my previous post clearly show that the decimals *are* recognized.

    1,1  225,25
    1,2  225,25
    1,3  216,75
    1,4  216,75
    1,5  208,25
    1,6  208,25
    1,7  199,75

    etc.

    That for example the spread of 1,3 and 1,4 lead to the same result is something we may not like, but this is a rounding error and quite normal. Thus, if you don’t like 1,3 (too low) and you also don’t like 1,4 (because the result is the same and again too low), just use 1,5. *That* is theoretically too high (it overshoots a little), but on the safe side, so OK.

    Not clear ?
    Don’t agree ?

     

     

    #184508

    Seems to be a bug of “rounding” number. PRT don’t consider the decimal on spread (1.2=1.3=1.5 and so on…)

    Hi zilliq,

    It is difficult for me to understand how you can see that the decimals are not recognized. The table I showed in my previous post clearly show that the decimals *are* recognized.

    1,1 225,25

    1,2 225,25

    1,3 216,75

    1,4 216,75

    1,5 208,25

    1,6 208,25

    1,7 199,75

    etc.

    That for example the spread of 1,3 and 1,4 lead to the same result is something we may not like, but this is a rounding error and quite normal. Thus, if you don’t like 1,3 (too low) and you also don’t like 1,4 (because the result is the same and again too low), just use 1,5. *That* is theoretically too high (it overshoots a little), but on the safe side, so OK.

    Not clear ?

    Don’t agree ?

    On EUR/USD as you can see, with spread 0.1, 0.3, 0.7 same result 29 770 USD

    And 1, 1.2, 1.7 same (bad) result -10200

    That’s why I say it doesn’t consider decimals

    #184513

    If you limit that to one trade by means of limiting the time period over which trades can be taken (like I did – first look at the total result and then pick a random trade so that in the limited result one trade is visible only)  … do you see the same culprit by varying the spread ?

    #184516

    Sorry I don’t understand what you want to do ? Block the algo to one trade ? Don’t see why it could be different ?

    As you see, same number of trades, and when the spread varies, the total gain don’t

    #184523

    Block the algo to one trade ? Don’t see why it could be different ? As you see, same number of trades, and when the spread varies, the total gain don’t

    – Yes.
    – Because with me it is OK ?

    If for you this (one trade) is OK like with me, it is for you to explain to yourself. 🙂
    If it is not OK again for you, we will both try to explain.
    (you know that) I am with you ! … but in the end I can’t mimic the issue. The contrary …

     

    #184530

    Ok i will change the code to have only one trade, but I think the conclusion will be the same

    See U

    #184560

    @PeterSt

    One trade only on EUR/USD 1 minute

    Same conclusion/bug  : spread 0.1 or 0.5 or 0.9 = Gain 10 USD

    Bye

Viewing 15 posts - 31 through 45 (of 66 total)

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