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

MQL4 지표 EA

작업 종료됨

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

명시

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
등급
(212)
프로젝트
316
34%
중재
63
37% / 40%
기한 초과
102
32%
작업중
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%
무료
비슷한 주문
KOKIE FX 30 - 200 USD
PROGRAM: PSMI Market Intelligence Engine v1.0 OBJECTIVE: Analyse the market from higher timeframes to lower timeframes, build a market narrative, and only allow execution when every condition is confirmed. ========================================================= STEP 1 LOAD DATA ========================================================= Read: Monthly (future) Daily H4 H1 M15 M5
Hello, I am looking for someone to Run and Monitor the EA and Signals in the account. Should be able to monitor daily and fix any issue in the signal Copying and EA running. The Settings and configuration to be checked and updated periodically. Should be available to report and update on daily basis. Tell me the cost and your previous experience for the same. Thanks
Looking for an Experienced MQL4/MQL5 Developer to Build a Professional Scalping Expert Advisor (EA) I am looking for an experienced MQL4/MQL5 developer to build a professional Expert Advisor (EA) for MetaTrader 4 or MetaTrader 5 from scratch. My goal is to develop a high-quality scalping system with strong risk management and long-term profitability potential. I am not looking for unrealistic promises or "100%
void OnTick() { // Check if we already have an open trade if(OrdersTotal() == 0) { // Get the value of a 14-period Moving Average double ma = iMA(Symbol(), 0, 14, 0, MODE_SMA, PRICE_CLOSE, 0); // Basic Condition: If current close price moves above the MA, buy if(Close[0] > ma) { int ticket = OrderSend(Symbol(), OP_BUY, 0.1, Ask, 3, 0, 0, "My First Bot", 0, 0, clrGreen); } } }
i brought an EA called profit hunter killer and the file is not working any more its a scalper type EA can anyone here decomplie the file as i cam not abe to reach the seller i brought it on Shopee malaysian website
Recently I have backtested more than 100 EAs and I have come to a conclusion that in the long-term all of them produce catastrophic results. I used 99.9% data quality and whenever possible decades of data. In the short-term almost all of them can have nice gains. But there is hardly any EA that could survive even just 3-5 years, let alone decades ! This got me thinking: if almost all EAs are unfit for long-term
I need to connect my online store to the NinjaTrader API for automated order fulfillment and license creation/revocation. If you have experience integrating with the NinjaTrader Ecosystem API or implementing vendor licensing, please contact me with your relevant experience and approach
I am looking for an experienced MQL5 developer to convert a TradingView indicator into an MT5 indicator. The objective is to recreate the TradingView indicator in MQL5 so that it produces the same calculations, plots, values, and signals as closely as possible. Requirements: Convert the TradingView Pine Script into an MT5 indicator (.mq5). Ensure the MT5 version matches the TradingView version as accurately as
EA WILL BE FOR GBPUSD ON M5 TIMEFRAME. IT IS A REJECTION/REVERSAL STRATEGY. IT FOCUSES ON BREAK OF LEVEL (M5 CANDLE CLOSE ABOVE HIGH, BELOW LOW (ASIA HIGH/LOW, YESTERDAYS HIGH/LOW, LAST WEEK HIGH/LOW, AND THEN ALSO SWING LEVELS BREAK AND REVERSALS BOTH INSIDE AND OUTSIDE PRICE ACTION) IN THIS STRATEGY WICKS ARE IGNORED, ONLY A SOLID CANDLE BREAK AND CLOSE AND REVERSAL CONSTITUTES AS A VALID TRADE. * EA TIME START +
1) The EA must identity CRT High and CRT Low ,,,,, it must wait for liquidity sweep before entering a trade ,,,to confirm the trade only after sweep and market structure confirmation and support buy and sell trades ,,,,risk. Should be adjustable (default 1% per trade) ,,stop loss should be placed beyond the liquidity sweep ,,take profit should be adjustable with risk reward from 1:2 to 1:5 ,,should allow trading only

프로젝트 정보

예산
30+ USD