And/ or option muny problems

Bug info:

i am testing some strategies, but now with the and/or option there a complete different results , at the same several tested strategy
i didn’t change anything, same bots with the same settings but now after adding the and/ or option, different results,
its very bad update.
the results its bad that its all my tested winning bot that i tested hundreds of time with the same result ans same win rate an profit, now after adding add/or option if i testing they inter wrong positions with all losing and different bad win rate,
one example backtested:
https://app.gainium.io/bot/backtests?a=6946&aid=share-backtest&backtestShare=fa4fb352-e32d-4ca6-9c6b-da91eb9aa8d2

there a lot but i can’t share them
wish you solve it very quickly or even delete this option.
thanks you

Hello,

Can you share two comparable backtests? One before and one after with the same bot settings.

this is one example (the results in this one not bad but you can see a lot of difference almost 400 more deals…, the other bots i have almost go from 80% win rate to 10% win rate and from high profit to high lose, i cant share them but i can send you a picture of the results if you want)

before
https://app.gainium.io/bot/backtests?a=6946&aid=share-backtest&backtestShare=afb1ee53-124b-4ea6-a661-31c7cdfd71d0

after
https://app.gainium.io/bot/backtests?a=6946&aid=share-backtest&backtestShare=c395bd92-4687-40b1-be4e-aa31d3f7366c

Nothing wrong with OR conditions, it was an update on the MA indicator. It has been fixed.

@maksym.shamko , told me to mention you about this problem. the problem didn’t solved, it causes bad results, can u check it.
thanks you.

I fixed the problem and managed to reproduce your initial result
https://app.gainium.io/bot/backtests?a=1&aid=share-backtest&backtestShare=6975e30f-36db-4ecf-9363-893528d788c4

@maksym.shamko ,this test was just an example, the problem is still with my other bots, can u give me your email that i can send u 1 of my main bot that u can see how bad the problem is.

We have made an update in backtest in MA processing with multiple timeframes. If you had problem with MA with different timeframes than probably it was wrong.
You can send me message here

@maksym.shamko

Different MA timefframes as I said.
We noticed the difference between real bot and backtest, after that backtester logic was changed to be more accurate to the real bot.

very sorry but i really didn’t understand what is the problem here, and does its solved ?because i tested now and its still happen.

As for the second you send: Yes, it will be different from now on. It wasn’t accurate before
As for the first test you send: Its fixed.

The difference between first test and second that first test use moving averages with the same timeframe: SMA 1 minute > SMA 1 minute
But the second test uses different timeframes: WMA 30 minutes > TEMA 1 minute.

For those test that has moving averages with the same timframes results shouldn’t change, but the one that has moving averages with different timeframes results changed from now on

1 Like

is there a way to fix the second one to git the same results like before?

No, because results wasn’t accurate. If you create a bot of the second one, there are high chances that results wont be the same

ok thanks you. can i know what the problem with the ma was so i would try to fix my bot so to inter the same position the old ma inter,

@maksym.shamko @aressanch

In some circumstances higher timeframe MA used current candle value. In real bot this is not possible, because it just don’t know the current candle value until candle is closed.

@maksym.shamko thanks you very much, you have any tips that i can do to make it work like the old one?,

and this from chatgpt:
If Gainium allows custom scripts or advanced settings, you might be able to script this logic manually.

does this possible?

Unfortunately, with current indicators logic it’s not possible to achieve

@maksym.shamko yes so i can ask if you can provide the old ma script and logic thats will help me, i would be grateful.
thanks