Modification of Existing EA | Adding OR/ELSE IF Functions to Existing EA.

MQL4 지표 EA

작업 종료됨

실행 시간 9 일
피고용인의 피드백
I appreciate and am honored working with you. I look forward to more endeavors. Thank you.
고객의 피드백
A pleasure to work with, very patient and understanding & would have no problem working with Maxwell again.

명시

I have an algorithm which is based on candlestick formations - specifically the hammer candle formation. 

Previously, the algorithm only executed short positions on bearish hammers & long positions on bullish hammers.

Now, however, I'm wanting to introduce inverse hammers, but keeping the wicks in the same positions (i.e., extended lower wicks for short positions and extended upper wicks for long positions)

It's not so much the interpretations of the global & local declarations themselves that are the issue, but it's the placement of the brackets that needs to be altered, as well as maybe introducing the "OR" or "ELSE IF" logic but I'll leave that up to you.

The instructions I'm needing it to follow - in layman’s terms - is the following:

"If '(BarTime != Time[0])' is true,
then assess if '(hammerHeadClose < hammerHeadOpen)' is True.
If (hammerHeadClose < hammerHeadOpen) is True, then assess if all of it's child statements are true. 
If all of its child statements are also True, then execute a position.

Alternatively (OR/ELSE IF) if '(hammerHeadClose > hammerHeadOpen)' is true, 
then assess if all of it's child statements are true.
If all of its child statements are true, then execute a position”.  

Therefore, if(BarTime != Time[0]) must always be TRUE, but dependant on weather  '(hammerHeadClose < hammerHeadOpen)' or '(hammerHeadClose > hammerHeadOpen)' will determine which set of child statements will be assessed to determine if a poition should be open.

Obviously (hammerHeadClose > hammerHeadOpen) & (hammerHeadClose < hammerHeadOpen) are mutually exclusive criteria (the closing price can either be above the opening or below the opening - doji's aren't allowed), there is no point in the EA assessing the child statements under (hammerHeadClose > hammerHeadOpen) when (hammerHeadClose < hammerHeadOpen) and visa-versa.

To put it another way "if(BarTime != Time[0]), assess "if(hammerHeadClose > hammerHeadOpen)". 
If "if(hammerHeadClose > hammerHeadOpen)" is FALSE (for example), go straight to if(hammerHeadClose < hammerHeadOpen) and assess all child statements here".

I hope this helps, if you need any clarification, let me know. 

The code in question is on line 315 (short position criteria) and line 795 (long position criteria).

I have enclosed documentation for the EA which includes the explanations to the Global Declarations which you will come across.


if(BarTime != Time[0])
     
     {
     
       if((hammerHeadClose < hammerHeadOpen)

         && (bearHammerHead >= Transform(candleBodyLength,2))
         && (bearHammerHandle!=0 && (bearHammerHead / bearHammerHandle) <= hammerHandlePct)
         && (bullRetracementCandle!=0 && (bearHammerHead / bullRetracementCandle) <= hammerHeadPct)
         && (bullRetracementCandle!=0 && (initialTrendBearCandle / bullRetracementCandle) <= retracePercentage)
         && (bullRetracementCandle >= Transform(candleBodyLength,2))
         && (trendFast < trendSlow)
         && (momentumFast < momentumSlow)
         && (NewBar)
         && (spread <= MaxSpread)
         && (hourOfDay >= startingHour && hourOfDay < endingHour)
         && (OrdersTotal()== 0))
         
       if((hammerHeadClose > hammerHeadOpen)

         && (bullHammerHead >= Transform(candleBodyLength,2))
         && (bearHammerHandleInv!=0 && (bullHammerHead / bearHammerHandleInv) <= hammerHandlePct)
         && (bullRetracementCandle!=0 && (bullHammerHead / bullRetracementCandle) <= hammerHeadPct)
         && (bullRetracementCandle!=0 && (initialTrendBearCandle / bullRetracementCandle) <= retracePercentage)
         && (bullRetracementCandle >= Transform(candleBodyLength,2))
         && (trendFast < trendSlow)
         && (momentumFast < momentumSlow)
         && (NewBar)
         && (spread <= MaxSpread)
         && (hourOfDay >= startingHour && hourOfDay < endingHour)
         && (OrdersTotal()== 0))
 
         {

         bool OpenShort = OrderSend(.....);

         /*----------code----------*/   
        /*----------code----------*/    
        /*----------code----------*/    

         }

}

응답함

1
개발자 1
등급
(169)
프로젝트
204
30%
중재
25
40% / 44%
기한 초과
12
6%
무료
2
개발자 2
등급
(3)
프로젝트
4
0%
중재
2
0% / 100%
기한 초과
1
25%
무료
3
개발자 3
등급
(155)
프로젝트
239
70%
중재
3
67% / 33%
기한 초과
20
8%
무료
4
개발자 4
등급
(215)
프로젝트
317
34%
중재
63
37% / 40%
기한 초과
102
32%
무료
게재됨: 1 기고글
5
개발자 5
등급
(298)
프로젝트
478
40%
중재
105
40% / 24%
기한 초과
82
17%
로드됨
게재됨: 2 코드
6
개발자 6
등급
(5)
프로젝트
11
18%
중재
0
기한 초과
3
27%
무료
7
개발자 7
등급
(42)
프로젝트
47
30%
중재
12
17% / 75%
기한 초과
6
13%
무료
비슷한 주문
Okay, this is a big one for MT5 traders. Let's do it properly. In Python, the "Merge Tool" usually means 2 things: 1. *Merge MT5 data from different symbols / timeframes into one DataFrame* 2. *Plot it as a clean graph* Here is a complete working setup: *Step 1: Install* pip install MetaTrader5 pandas matplotlib mplfinance *Step 2: Full Code - Get MT5 Data + Merge + Plot* import MetaTrader5 as mt5 import pandas as pd
Bestehenden MT5-EA prüfen und Wartungsfunktion ergänzen Mein selbst entwickelter EA „MARC HybridTrend“ hat einen dauerhaft gespeicherten Peak-Halt und keine eingebaute Wiederfreigabefunktion. Vollständiger MQL5-Quellcode und eine Funktionsspezifikation sind vorhanden. Gewünscht ist eine ausdrücklich bestätigte Wartungsfunktion mit Integritätsprüfung, Wiederholungsschutz und nachvollziehbarer Protokollierung
EA Application & MT5 Account Verification Requirements To apply, you must already have your EA running on an active MT5 trading account connected to the market. The account must have genuine trading history that can be independently reviewed and verified. EA Requirements 1. Prop-Firm Compatible Risk Management - The EA must include daily and overall drawdown protection. - Required inputs: "MaxDailyLoss = 5%"
Seeking Experienced Forex EA Developer – Currency Strength Meter Strategy Optimization (MT4/MT5) I am looking for an experienced Forex EA developer and quantitative trading strategist to help improve, optimize, and professionally test my existing Expert Advisor (EA). My EA is based on a Currency Strength Meter strategy, which identifies strong and weak currencies and automatically executes trades by pairing a strong
I need someone to develop a simple EA that makes random orders. Just random orders no indicators needed. I should be able to set my TP and SL of choice
Project Overview We are looking for talented and experienced programmers, MQL5 developers, algorithmic traders, Forex automation specialists and trading system developers for an MT5 Gold (XAUUSD) Scalping EA development project. We welcome applications from developers with different backgrounds in automated trading, Expert Advisors, algorithmic strategies, trading indicators and financial technology. Our objective is
EA RE 200+ USD
EA Application & MT5 Account Verification Requirements To apply, you must already have your EA running on an active MT5 trading account connected to the market. The account must have genuine trading history that can be independently reviewed and verified. EA Requirements 1. Prop-Firm Compatible Risk Management - The EA must include daily and overall drawdown protection. - Required inputs: "MaxDailyLoss = 5%"
Smart Fibo indicator 30 - 100 USD
Can you create a Smart Tool Like a Smart Fib Just one click on where you position your highest point or the Low to high. with color for each percent
the job underlying algorithms. An algorithm is a set of actions that need to be performed in response to certain events. For example, the most common task in algo trading is the identification of the "New bar" event . When the event occurs, the robot checks the emergence of trading signals and acts accordingly. Before you decide to program or order a trading robot, you need to formulate a trading system with clear
I have an existing C# trading strategy that I’d like to integrate into Quantower’s Strategy Manager so I can manage, configure, and execute it directly within the platform. I’m looking for a developer familiar with Quantower C# to handle the integration

프로젝트 정보

예산
30+ USD