Bug -1 max open deal

Bug Reports
1

Bug info: when using -1 max open deal combined with ASAP on the backtest the bot opens a deal every 1 second while in paper and real account only 1 at the time.

  • Bot URL → Gainium app
  • [Optional] Steps to reproduce → simply create a new bot leave all the standard settings and set deal start condition ASAP and max open deals -1 (picture below) - then simply run a backtest you will see in the closed deals that the bot doesn’t wait for the previous deal to close before opening a new one but fires a new deal every second - this is the correct way even if ASAP it’s just unrealistic.

Screenshot 2024-10-30 at 20.16.17
Screenshot 2024-10-30 at 20.16.171084×754 27 KB

  • Expected result → When using -1 on real or paper the bot should open a new deal every time the condition is met NOT only 1 deal at the time. If we want to open only one deal we should put 1 not -1.
    -1 should open a deal every second or every timeframe candle.
2

In all conditions except asap bot will open new deal every time condition is met. Also in ASAP with dynamic price filter.
Simple asap won’t open more than 1 deal simulatenously, no matter is it 2,3 or -1. However you will be able to open new deal manually. If you set max deals to 1, you won’t be able to open new deal manually.

3

Got you - so the backtest should be fixed as it fires deals every second when -1 with ASAP

4

I think -1 should be fixed in general.

Use -1 internal but name it max. I know for sure, that what you see at the surface hasn’t to be what you store in the database.

Make sure that we cannot select 2, 3, …, max, if only 1 is working.

If ASAP only opens 1 simultaneous deal per pair, maybe add a timeframe to allow more than 1 simultaneous deal so that we don’t have to use the RSI-7 1min > 1 hack.

5

-1 with ASAP on the backtest opens unlimited deals

6

I already made a fix, and double checked it right now. Can you send the backtest?

2 Likes
7

works now - I think I had to hard reload the page

1 Like
8

right, I found the issue - stats doesn’t display the correct numbers

Look at this backtest comparison between the same bot one using -1 and one using 200 deals (even if the bot never reached that number ever) (Gainium app)

Screenshot 2024-11-01 at 16.06.08
Screenshot 2024-11-01 at 16.06.081920×1241 159 KB

200 Max open deals - NET PROFIT 0.06%

Screenshot 2024-11-01 at 16.05.20
Screenshot 2024-11-01 at 16.05.201920×1241 169 KB

-1 Max open deals - NET PROFIT 11.52%

9

Deals with 0 time not taking into account in confidence grade.
Is there are more than 1 simultaneous deal when you set -1?

10

yes when -1 it opens simultaneous deals - look at the first and second deals for example

Screenshot 2024-11-01 at 16.28.13
Screenshot 2024-11-01 at 16.28.131920×1241 173 KB

Exactly the same behaviour when setting 200 - again look at the first and second deal

Screenshot 2024-11-01 at 16.30.24
Screenshot 2024-11-01 at 16.30.241920×1241 172 KB

11

I think the wrong one is the one using 200 deals - if you look at the green curve (realised profit) the one using 200 deals is quite flat making me feel that something hasn’t been counted properly, also I’m using a very small budget per deal (around $150) but I’m not closing any deals under 2% that’s why I think the one using 200 deals with NET PROFIT of 0.06 is wrong

12

Are you using dynamic price filter?
Of course it will open more than 1.

The case of this task was that simple ASAP opens more than 1 when having -1 in max deal

13

Yes you are right brother it’s a different bug on two different bots

14

Let me know if you want me to open a new ticket or if you are ok with that? Thanks :pray:

15

Yes, please open a new ticker with the description of the problem

16

So the question why different %?
With -1 you dont have limit on balance, you can see on the chart that balances are different, different denominator used to calculate percents

17