Gentlemen programmers, help me with creating a simple EA - page 6

 
sanyooooook >>:
кстати, что по Вашему должен делать советник после перезапуска терминала?

Same as before the launch :).

 
TheXpert >>:

То же, что и до запуска :).

there you go, i.e. practically just a fresh start.

 
sanyooooook писал(а) >>

there you go, i.e. practically just a fresh start.

continue.... All programmers who have coded EAs do this by default, as well as other features that the customer doesn't specify in the ToR - magik, slipage, etc.

 
TheXpert писал(а) >>

Same as before the restart :).

What if there is a position opened by the Expert Advisor before the restart?

 
sever29 писал(а) >>

continue....

That's the thing, "continue" depends on the trading algorithm.

 
PapaYozh >>:

А если имеется позиция, открытая советником до перезапуска?

This position should have a mage which the EA will use to find it and deal with it according to the trading algorithm.

 
PapaYozh >>:

А если имеется позиция, открытая советником до перезапуска?

What difference does it make?

 
PapaYozh >>:

Я тоже не понимаю как можно что-то за 300р накодить.

Любой советник - это время, потраченное на общение с заказчиком, написание и отладку (и это таких циклов может быть несколько). Даже если торговый алгоритм кажется простым, он может содержать нюансы, а торговый советник без обработки ошибок - это игрушка для тестера.

Уж лучше бесплатно сделать (вариант для альтруистов), либо не делать вовсе.

The guys at the illegal car park get 300-500 rubles a night per shift.

But the customers understand perfectly well that it seems there is nothing complicated, and therefore his super idea must be finished or for nothing, or for a pittance. And when you durk a month and another $200 advance payment, the customer makes a feint after the demo. There is a great desire to do everything for nothing...

 
sanyooooook >>:
кстати, что по Вашему должен делать советник после перезапуска терминала?


it must continue its work in the environment it left before the restart.

All important parameters, accumulated profits/losses (if any are required in the TOR), position maintenance parameters (for tricky trawls or MMs), controllable numbers (which affect the situation analysis of each tick), etc.

+ of course check what is now in place and update or reset everything if necessary. In case, for example, if the client closes his orders manually.

Methods of error control or server failure, forced entries in trade cycles, compulsory execution of the order until the next situation is analyzed until the current order is executed (for example, until the closure of several linked orders), and in this case we must not loop roughly while(true)! What about such surprises as prohibition to place market orders with stops at some brokers? And everything must work properly!

there are lots and lots of things that should be in a STATE FUNCTION of any coder.

PS

And majik is just a little help from MT developers.

 

For example, a prime example is setting the required stop loss...

What if, at the current moment, the broker has widened the stop level? And then what? Are you going to explain to the client that your stop level has widened? No. Normally, in such a situation, you should constantly monitor the stop and adjust it as far as possible to the required value.

And note that it should not be stipulated in TOR - it is the coder's problem.