Specification

The overbought zone is determined as candlesticks, at which the indicator value Value > Lmax (Lmax=-20).
The oversold zone is determined as candlesticks, at which the indicator value Value < Lmin (Lmin=-80).
The values of Lmax and Lmin should be included in indicator parameters.
A yellow point should be added at the High point of candlesticks in the overbought zone—it is the H point.
A green point should be added at the Low point of candlesticks in the oversold zone—it is the L point.
If there is at least one L point between two H points, search for a LL point in the interval between two H points. The candlestick with the lowest Low price will be the LL point. Generally, the LL point is not necessarily an L point. Search for candlesticks with the lowest Low price.

Responded

1
Developer 1
Rating
(3)
Projects
4
25%
Arbitration
3
0% / 100%
Overdue
0
Free
2
Developer 2
Rating
(62)
Projects
90
29%
Arbitration
24
13% / 58%
Overdue
7
8%
Working
3
Developer 3
Rating
(268)
Projects
602
34%
Arbitration
64
20% / 58%
Overdue
147
24%
Working
Published: 1 article, 22 codes
4
Developer 4
Rating
(1)
Projects
0
0%
Arbitration
0
Overdue
0
Free
5
Developer 5
Rating
(610)
Projects
709
33%
Arbitration
45
47% / 42%
Overdue
14
2%
Working
6
Developer 6
Rating
(267)
Projects
282
55%
Arbitration
0
Overdue
5
2%
Free
7
Developer 7
Rating
(7)
Projects
8
0%
Arbitration
4
0% / 100%
Overdue
3
38%
Free
8
Developer 8
Rating
(322)
Projects
499
67%
Arbitration
5
40% / 0%
Overdue
4
1%
Free
Published: 8 codes
9
Developer 9
Rating
(19)
Projects
23
48%
Arbitration
10
0% / 100%
Overdue
2
9%
Free
10
Developer 10
Rating
(513)
Projects
552
53%
Arbitration
13
69% / 15%
Overdue
3
1%
Free
11
Developer 11
Rating
(16)
Projects
35
23%
Arbitration
4
0% / 50%
Overdue
2
6%
Working
12
Developer 12
Rating
(271)
Projects
553
50%
Arbitration
57
40% / 37%
Overdue
227
41%
Working
13
Developer 13
Rating
(43)
Projects
66
12%
Arbitration
12
58% / 42%
Overdue
1
2%
Free
14
Developer 14
Rating
(258)
Projects
267
30%
Arbitration
0
Overdue
3
1%
Working
Published: 2 codes
15
Developer 15
Rating
(132)
Projects
178
39%
Arbitration
4
25% / 50%
Overdue
14
8%
Free
16
Developer 16
Rating
(318)
Projects
565
35%
Arbitration
81
31% / 44%
Overdue
204
36%
Free
17
Developer 17
Rating
(78)
Projects
246
74%
Arbitration
7
100% / 0%
Overdue
1
0%
Free
Published: 1 article
18
Developer 18
Rating
(45)
Projects
91
13%
Arbitration
34
26% / 59%
Overdue
37
41%
Free
19
Developer 19
Rating
(2672)
Projects
3407
68%
Arbitration
77
48% / 14%
Overdue
342
10%
Free
Published: 1 code
20
Developer 20
Rating
Projects
0
0%
Arbitration
1
0% / 100%
Overdue
0
Free
21
Developer 21
Rating
(1)
Projects
2
0%
Arbitration
2
50% / 50%
Overdue
0
Free
22
Developer 22
Rating
(174)
Projects
233
61%
Arbitration
3
33% / 33%
Overdue
6
3%
Free
Published: 1 code
Similar orders
I have a High-Frequency Trading (HFT) Expert Advisor for both MT4 and MT5 designed primarily for US30 (Dow Jones Index) . The EA performs consistently and profitably on demo accounts, but when I run it on an IC Markets Raw or Standard live account, it starts generating losses under what appear to be the same trading conditions. At this time, I cannot provide the source code (.mq4/.mq5). I can only provide the
EA Crafter 500+ USD
Act as a professional Quantitative Developer and Risk Manager. I want to build a systematic trading strategy rulebook that prioritizes capital preservation and statistical edge over raw performance. Please generate a structured trading strategy using the following framework: 1. ASSET CLASS & TIMEFRAME: - Asset: [e.g., Apple (AAPL), Bitcoin (BTC), or EUR/USD] - Timeframe: [e.g., 5-minute, 1-hour, Daily] 2. CORE

Project information

Budget
50 - 400 USD
Deadline
from 1 to 5 day(s)