Modification of Existing EA | Adding OR/ELSE IF Functions to Existing EA. - MQL5.community 프리랜싱 서비스에서 기술 지표을(를) 개발하기 위한 주문 - 예산: 30+ USD - MQL4

작업 종료됨

실행 시간 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----------*/    

         }

}

파일:

MQ4

stop_hammertime_canat_touch_this.mq4

197.1 Kb

PNG

Slide1.PNG

15.5 Kb

PNG

Slide2.PNG

15.7 Kb

응답함

등급

(169)

프로젝트

204

30%

중재

40% / 44%

기한 초과

무료

등급

(3)

프로젝트

중재

0% / 100%

기한 초과

25%

무료

등급

(155)

프로젝트

239

70%

중재

67% / 33%

기한 초과

무료

등급

(214)

프로젝트

316

34%

중재

37% / 40%

기한 초과

102

32%

작업중

등급

(298)

프로젝트

478

40%

중재

105

40% / 24%

기한 초과

17%

로드됨

게재됨: 2 코드

등급

(5)

프로젝트

18%

중재

기한 초과

27%

무료

등급

(42)

프로젝트

30%

중재

17% / 75%

기한 초과

13%

무료

비슷한 주문

I need an MT5 Expert Advisor (EA) specifically for NFP news trading. Strategy: - Trade EURUSD during the US Non-Farm Payroll (NFP) release. - Automatically identify the NFP release time. - Place a Buy Stop above the current price and a Sell Stop below the current price shortly before NFP. - Adjustable distance from current price for both pending orders. - When one order is triggered, automatically cancel the opposite

yoo i want to make a trading bot i have my strategy in videos and also the rules to if anyone can work it out for me i will be glad welcome your bid and it urget let connect here on ninjatrader

Bonjour ! Je vous ai contactÃ© pour le dÃ©veloppement de mon EA sur MetaTrader. Je souhaite intÃ©grer une stratÃ©gie prÃ©cise avec une gestion stricte des rÃ¨gles du courtier Exness. J'ai dÃ©jÃ prÃ©parÃ© le cahier des charges complet sous format PDF avec toutes les spÃ©cifications techniques

want an MQL5 Expert Advisor (EA) for MetaTrader 5, mainly for XAUUSD (Gold). Strategy: The EA should trade based on market structure, Break of Structure (BOS), Fair Value Gaps (FVG), Order Blocks (OB), and Fibonacci retracement levels. BUY setup: Detect bullish market structure. Detect a bullish Break of Structure (BOS). Identify the relevant bullish FVG and/or Order Block created around the structure move. Use

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%" "MaxTotalDrawdown = 10%" - Once either limit is

Hello, I'm looking for developer or coder to create a custom expert advisor (EA) on mql4 according to my strategy. The developer should be able deliver both indicator and source code for the job. Thanks

Indicators: Fast MA (Period 10, Exponential) and Slow MA (Period 50, Exponential). Buy Signal: When Fast MA crosses above Slow MA. Sell Signal: When Fast MA crosses below Slow MA. Risk Management & Parameters: Customizable Lot Size (Default: 0.01). Stop Loss (SL) and Take Profit (TP) in pips. Trailing Stop options. Max Spread filter. Platform: MetaTrader 5 (MQL5)

Je souhaite trouver un développeur pour réaliser ce travail et effectuer les paiements via cette application. Je m'engage à ne communiquer avec les candidats que par cette application, y compris par messageries tierces, correspondance personnelle ou courriel. Je comprends que toute personne ne respectant pas ces conditions sera interdite de publier des commandes sur la plateforme Freelance

I am looking for an experienced MQL5/MT5 developer to develop a custom Expert Advisor based on a complete technical architecture already prepared by the client. This is not a request to design a trading strategy from scratch . The strategy architecture, entry/exit concepts, filters, risk-management requirements and testing requirements are already documented. The main responsibility will be MQL5 development

프로젝트 정보

예산

30+ USD

상세내용의 질
결과 확인의 질
능력과 커뮤니케이션 스킬