self updating/refreshing grid, compare two groups of trades
-
Grid-EA full-auto v1.4:
the operand issue I could solve (my mistake int, double mismatch)
regarding the button issue:
there are two button blocks on "on Init" and "on chart", there is on "on tick" the block 227 and block 211 witch turns on pass block on "on init. Usually the buttons are appearing after I have changed the timeframe. For example H1 to H4 then the buttons usually apear and are working as expected. But now nothing is happening. I don't event touched these blocks what is wrong here?Grid-EA SF full-auto v1.4
the same like above. Buttons are not appearing. The on "on tick" relevant blocks are 960 and block 136 witch turns on pass block on "on init".p.s.
It seems it is a builder problem because my HD backup v1.2 is working correctly but the downloaded v1.2 is not working. The buttons are not appearing. Something is not working maybe because of your last changings to builder. -
Are you afraid of creating some project with 2-3 blocks only to show me something and then delete it later? I believe I suggested this many many times in this topic and... nothing. What is the problem with that?
Under On Init in these projects I can see that the "Pass" block above is disabled, I don't even expect something to be working below them.
-
If it make sense to make an example and It could help to explain what I want I will create one as in my last issue about loading the last lot size into a variable. But This time the Button was working and is still on my HD backup working but not if I download ea. All buttons are not working. Something has crashed. I was assuming you could verify the "connections" or the relevant code pices to make sure there is everything correct.
Well, how can I help you to localize the problem? What example do you expect, as for me it makes no sense to create an example.
The disabled pass block you have mentioned will be enabled on "on tick" look inside the block "Turn on blocks" upper right corner (136). I have already mentioned that.
-
Enable is not the same as Run. Enable blocks = allow them to work if another block approach them, make them part of the game. If a block is disabled, it's like it doesn't exists, like it's not connected. Enabled blocks are ready to work, disabled are not. Using "Turn ON blocks" does not run blocks, only makes them ready to work if they were disabled, for already enabled blocks this does nothing at all.
-
'Ok, but why the buttons of my backup v1.2 ea from my hd are working correctly? Did you have changed something the last weeks? The pass block there is also disabled but the buttons are working.
I will verify that tomorrow.
-
you are right, it was the disabled pass block on "on init" but only there. The disabled pass blocks on "on tick" were turned on.
Thanks so far. I have to test ea's on live demo now.
-
It seems optimization is not working correctly on my EA's. Generally and on other EA's optimization is working correctly. What could be the reason for that?
-
Define "correctly"?
-
sometimes there are no results where results should be and sometimes there are same wrong results on different test values. Optimization on some demo ea's is working as expected.
-
Give me simple project that produces certain results and tell me what the expected results should look like
-
An example makes no sense because it seems the problem is only with "Grid-EA SF full-auto v1.4". I have attached the bug free Kolier Indicator. Now you can try to backtest and optimize yourself.
-
Sorry, I'm not going to dig into a project with 100s of blocks and an indicator that I have no idea how it works. And honestly, I don't even care how this indicator works. I'm tired of explaining the same things over and over again. I still think that it's not so hard to put few blocks together in a brand new project to show some bug, other people are doing it sometimes.
-
It is not necessary to understand the strategy or indicator.
My intention was to make you able to verify (for example) the following:take parameter grid_spacing = 50 and then = 60 ->
make a backtests (for example GBP/USD last 6 month) ->
you will see backtesting is working ->
than make an optimization start 50, step 10, end 60 of grid_spacing then you will see no results or differnet results to the backtested ones and you have verified that there is something wrong.And now the question is what is wrong. There are only 131 blocks, this is not that much. Does maybe the "if testing" block makes some problems?
-
But there are 100+ blocks. I need to know how your strategy works in order to say what is wrong in it. For me even 20 blocks are much. You may think that because you know everything in your strategy, I should also know it, but I am not God. You know the whole strategy because you are working on it probably for months, but for me it means nothing. What if I show you 131 rows of code, will you understand it in 5 minute? Of couse no.
While optimizing, negative results are discarded, only when the EA is profitable you can see results. I think you know that. But if the results are some kind of wrong, can you find that something is wrong in the way trades are placed?
I remember that in the past someone reported something similar, but I forgot what was the reason back then.
-
Well, you are not God but maybe God is inside you... :).
It seems you don't have understood me correctly. EA is working on live demo and on backtesting as expected. The point is that optimization is not working. I was assuming you could look at the relevent pice of code and fix it.
Just do a quick optimization on some parameter and then do a backtest on the same parameter. As for me it seems that there is something "broken" that is responsible for optimization because the ea itself is working. Isn't it possible to verify the relevant code?
-
Well, in fact it doesn't run very quick on my laptop. Note that for optimization some features of MetaTrader doesn't work. I don't remember exactly, but I think that the work with objects is limited. Maybe something from the EA does not work because of MetaTrader 4 limitations.
Look:
https://www.mql5.com/en/articles/1512__Draw objects are not really set
The objects are disabled in order to accelerate the testing.[/quote:b2lnjxy8] -
Thanks. That was it. Optimization is working again. Drawed lines are working on backtesting but not on optimization.
-
I would like to make my ea faster on backtesting. Do you have some general tips? Is it better to connect blocks one after another or if it is possible to connect them parallel to each other.
-
Try the indicator itself first. I have seen very slow indicators before, even one single Condition with a bad programmed custom indicator is enough to slow the whole EA very much.
Every block needs some time to work and it depends on the block itself and the the things that it works with - trades, orders. But if you can, put the fastest blocks that rarely pass on top. Unfortunately it's hard to measure which block is faster than other. If you can, combine groups of blocks. For example, instead of using "No trade" for multiple groups of blocks, use it once and connect it to all groups.
-
Thanks. Much faster now. The "If testing" block is very helpfull.
