Ready trade busines (source codes are applied)

Anton_uz

Master Trader
Dec 26, 2009
8
0
57
Power Advisor with sources in MQL4

The given ready business has a wide spectrum of actions for the market of currency pairs. For today in the market is about 80 currency pairs for which the given project is developed.

With what to begin? :confused:
- To begin it is necessary from truthful history is Swiss server DukasCopy from which it is possible to receive any tick range histories practically on 30 trading tools in a format of a CSV-file which is located in folder C:\Program Files\Trade_Terminal\experts\files\and it is converted by means of script CSV_to_GR. In a script code there is a line:
name = "USDCHF_Ticks_2012.01.01_2013.03.04.csv";- The CSV-file name should be changed manually and to compile with the subsequent start.

Where to place the converted history and what it has a format?
- To place the converted history in a folder:
C:\Program Files\Trade_Terminal\experts\files\Recorder\.
- The format is a 8-bit file for value of unit of the price and a 4-bit file for value of a time unit to the current price. Files have a format: PAIR.ask, PAIR.bid, PAIR.dat accordingly.

The given project contains the personal tester started as the user script. Advantage of a tester in simultaneous tracing of a condition of balance for several points of an input in the market, having identical tick length while tester МТ traces only one point of an input in the market. The maximum level procorfs is regulated by parameter BALANCE MAXIMAL PERCENT OF LOSS.

The tester operating time can vary from several o'clock about several days depending on quantity of touched parameters and a range of their change.

Where there are touched parameters?
- They are in file TRACER_CFG.txt which is created automatically at the first start of a tester.

How to make touched parameters not touched and on the contrary?
- For the first case it is necessary to balance their maximum with a minimum.
- For the second case it is necessary to make these sizes various.

Some words about terminal MT indicators.
There is a set of indicators, but all of them can be ranked as one of two categories, these are advancing indicators which stick with a finger into the sky; or a category late indicators. To last category there is an example is an indicator "fractal" since considering the given indicator on history, can to start be surprised amazing accuracy of its indications, but in practice – it is late with these indications on 1-2 candles. An overall objective of the author of this article – acquaintance with ready business, therefore examples for the first category readers will find for themselves.

The given algorithm does not use indicators.
In files of touched and not touched parameters there are not used sizes.







Algorithms of a trading part.

Algorithm №1 searches of a point of an input in the market:
1. The file from N th quantity of the indexes defined in parameter ANALIZE TICK
(further matrix of tick) is filled with logs of the current tool;
2. At each new log, the latest log vanishes – there is a displacement;
3. Such file is analyzed on growth of a fresh part;
4. After the analysis the postponed orders with time of life ORDER LIFE, displacement
TRADE SHIFT which type depends on parameter USE LIMIT ORDERS ON RISE [0/1] which is in a file of not touched parameters CONFIG_GR.txt is created;
5. The given algorithm in parameter ORDER LIFE=0 is disconnected.

Algorithm №2 searches of a point of an input in the market:
1. All the same, only is analyzed growth of an old part of a trend, and recession of a fresh part (speaking in other words – there is a search of a turn of a trend);
2. In the given situation 2 variants of creation of the postponed orders depending on parameters
… ON TURN-LIMIT and … ON TURN-STOP are resolved;
3. The given algorithm in parameters ORDERLIFE ON TURN-STOP=0 and
ORDERLIFE ON TURN-LIMIT=0 is disconnected.

Algorithm №3 searches of a point of an input in the market:
1. Prove to be true on operation certain quantity of the control points defined in parameter
MAX POINT;
2. Each control point has time of a life of acknowledgement CHECK SECOND and the minimum log of chosen direction CHECK LAG;
3. The control point is considered worked if the certain log (more or equal) is in time received;
4. The given algorithm in parameter CHECK SECOND=0 is disconnected.

Martin's algorithm always will help at its reasonable use, it is activated by parameter :eek:
MG Engine [0/1 =1 and has two parameters MG DEPTH – pips procorfs for Martin's activation,
MG ZOOM [1...>] – factor of increase in a prize of the problem orders;

The exit from the market occurs on a trawl or on recognition of a turn towards the loss;
All profitable combinations are registered in a report file res_PAIR.txt;
The most profitable combinations are registered in a file-clean copy q_result_PAIR.lag.

Tester operating modes.
The tester has two modes switched by variable PROFESSIONAL MODE [0/1].
- If mode PROFESSIONAL MODE is switched off, the tester works in a mode of automatic search of the parameters which are not demanding presence of the operator;
- If mode PROFESSIONAL MODE is active, the tester works in a manual mode at which all variables become opened for change on pressing F3.

Techniques of search of profitable parameters can be much, but all of them mean serial activation of one of above described algorithms.

P.S.:
We open a demo-account in Dukascopy under the reference (for 14 days - use Go.bat with new account):
http://tradelikeapro.ru/goto/https://demo-login.dukascopy.com/fo/register/demo/

If the terminal already patched under "Dukascopy" it is possible to use script Recorder.mq4 instead of CSV_to_GR.mq4

In archive there are type files: q_result_PAIR.lag are clean copies on which robot "GRAALy3.mq4" trades
Target DC: 5 signs
 

Attachments

  • CSV_to_GR.mq4
    9.5 KB · Views: 25
  • GET_TERMINAL_DATA.mq4
    3 KB · Views: 25
  • Recorder.mq4
    2.4 KB · Views: 24
  • GRAALy3_ENG.pdf
    326.2 KB · Views: 27
  • Tracer_GR.mq4
    239.7 KB · Views: 23
  • GRAALy3.mq4
    41.2 KB · Views: 23
  • q_result.zip
    763 bytes · Views: 24
  • go.zip
    213 bytes · Views: 26
Last edited: