Best posts made by roar

Hi, I am not miro, just another bored guy, but

try setting the "A: this block can create 1 object" to "no".

@MMBInvest DoubleToString() always works, I dont know what else to say. Here is an example you can actually reproduce, maybe it helps.
testtt.mq4

@jsauter86 just a basic rule in statistics. More data means more proof. Less data means less proof.

If you cant have more trades in a year, then you should test multiple years.
I would love to see this same backtest result, but started 5 years earlier.

@migen
https://fxdreema.com/shared/BNcQoJLzb
This is how I would do it.. Hope you are comfortable with variables

Looking at the source, the time model seems to use TimeLocal() and TimeGMT() but then immediately remove the difference to server time - I wonder what's up with that @fxDreema

Also a good thing to remember:

@jsauter86 pretty good! How about 2013-2021 ?

2014 and 2017 saw some big trends on eurusd, that would really stress test the ea

@migen
To build on my previous example, I would do it like this:

The 4 conditions now pass twice (for 2 timeframes) so the total "score" for buy and sell can be 8. I also added a block after the buy > sell comparison, where you can define how big the bigger "score" should be.
This doesn't exactly separate between timeframes, but I think it's close enought to your needs and you surely can modify it from there.
https://fxdreema.com/shared/h52NKD4te

@PhiLykia does the custom indicator have variable names such as "c" or "v"? Those may create the bug. You could try renaming the variables of your indicator.

I do agree these kinds of bugs should be fixed rather than finding such workarounds.

@jsauter86 for me, recovery factor optimizing works better than just balance, but that might depend on the strategy

@rafaelgrecco said in How to Select "Least profitable trade"?:

What I was missing was:

• Reseting the variable "smallestprofit" on every new loop

We must reset the variables at some point, so the ea don't get "stuck" to some big loss that is already closed. Now it resets the variable on every tick, and also calculates it again so we always have the correct value. It is not the most cpu-optimal way but should work fine.

• Using the second output of "Each Trade" to wait for all trades to be checked

I think this is the correct way, we must first check all trades in order to find the lowest profit.

The looping blocks work a bit different than other blocks, go ahead and test different logic builds

@l-andorrà fractal indicator has a value for every candle, even if there is no arrow visible. That value will be 0, and naturally 0 is always below candle high.

This is why the correct way to use fractal is simply with condition:
fractal up/down != 0

@jsauter86 I mean the optimization algorithm in the tester, you use that?

Recovery factor = net profit / biggest drawdown

Mine works differently.

Here, take this .mq4 and import it to fxdreema so you get the exact same project. I also added a trade count condition for comfort.
0_1531746692796_hedge.mq4

@gsmtricks Just replace it to the function:
MathFloor(Rate * 100) / 100

Hope it works!

@jsauter86 the genetic algo finds the best inputs using backtest information between 2009-2015. After that, it tests if those inputs hold in the "future", 2015-2020. If forward test fails, we know the good backtest was just luck ("overfitting").

https://en.wikipedia.org/wiki/Training,_validation,_and_test_sets

@line I think youre right, it's the lot sizing. And yeah, this EA will not make profit on the ETF, withouth any modifications. The ETF probably has bigger trading costs and smaller volatility, and thus the 5-min timeframe can't be very proftable in the long run.

When you find yourself copying the same block over and over again, there is usually a way to loop the process:

This method creates as many trades as you want, and assigns a special number for each one.
That number (group #) can then be used to control the trades.

Doesn't really answer to your question though, just wanted to give another way of doing it

@cesardefez add these blocks to the system. It forces the buttons to agree with the variables.
https://fxdreema.com/shared/Bto5C2CYb

I made a fun little tool that creates high-low lines based on RSI, and decided to share it here in case anyone finds use for it.

I will not bother explaining this in detail, feeling lazy lol

https://fxdreema.com/shared/n4LXpQO1b

Hi!

This is how I would go about it:

https://fxdreema.com/shared/Hmmb4zOfb

Uses 1 variable that keeps track of your daily equity, and 2 constants to set the targets for daily profit and loss