nice work...

Be it popov, I downloaded the file and even disabled the statuses that input to make my exchange GBP optimization I realized that basically it makes a grid without any logic or maybe it even has some built-in strategy like that, but within it wouldn't it be better to add these designer functions spacing in the strategies generated by eadwize, just as I do manually, for example, the code I will leave here as an example

I am very excited for this one

I'm running this robot on a demo for a month and it works well.

Please note that this robot is developed for academic purposes. Grid systems are risky!

Trade Safe!

Hi All,

I have started exploring with Grid and Martingale. This is a wonderful tool for research. I have a couple of questions.

1. What is the logic for opening a position? Is it based on some indicator value or based on some predefined price value?

2. I was trying to run the MT5 optimizer but somehow it is not enabling the Input panel for selecting a variable and then setting the Start, Step and Stop values. What am I doing wrong?

> 1. What is the logic for opening a position? Is it based on some indicator value or based on some predefined price value?

The expert opens new positions whenever the price touches a new Grid level. It does not use indicators. It simple opens both long and short trades (that's why I called it hedging)
Please watch the video.

> 2. I was trying to run the MT5 optimizer but somehow it is not enabling the Input panel

Correct. The robot does not have indicator parameters. However, you may adjust the Grid size. Other parameters are mainly for money management, scaling and protection.

Hello Mohammad,

Please watch the video attached to the first post. I explained how the expert is working there.

I'm also attaching another video for the Grid Explorer expert att he first post.

Why don't you try using the optimiser?

The Grid Explorer does not use indicators and indicator parameters correspondingly.
It has parameters that can be adjusted manually, but I decided it is too risky to allow them to be optimized.

If you are sure you understand the risks of overoptimization, you can easily make the parameters available for optimizations.

Please do it by removing the "static" keyword before a parameter.

Here is an example of the "Grid_Size" parameter:

static input int    Grid_Size              =       50; // Grid size (in pips)

Remove the "static" keyword to become like that:

input int    Grid_Size              =       50; // Grid size (in pips)

Hi Popov,

Just wondering if the latest Grid Explorer (Hedging) v1.2 is the final version or you are working on a newer version.

By the way, it is very useful.

Thank you.