작업 종료됨
실행 시간 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
등급
프로젝트
204
30%
중재
25
40%
/
44%
기한 초과
12
6%
무료
2
등급
프로젝트
4
0%
중재
2
0%
/
100%
기한 초과
1
25%
무료
3
등급
프로젝트
239
70%
중재
3
67%
/
33%
기한 초과
20
8%
무료
4
등급
프로젝트
313
34%
중재
63
37%
/
38%
기한 초과
100
32%
로드됨
5
등급
프로젝트
477
40%
중재
105
40%
/
24%
기한 초과
81
17%
로드됨
게재됨: 2 코드
6
등급
프로젝트
11
18%
중재
0
기한 초과
3
27%
무료
7
등급
프로젝트
47
30%
중재
12
17%
/
75%
기한 초과
6
13%
무료
비슷한 주문
Hello Developers I have a Project to get done! i have a simple strategy can you please create the automated forex ea to execute my trading strategy? i need custom ea for tradingview and mt4/mt5 correction: i need a tradingview indicator created that tells me when to buy or sell. and ea in mt4/mt5
Mam kody EA Bot. Chciałbym je dokończyć, dopracować i ukończyć projekty. Chciałbym otrzymać pliki SET po ukończeniu EA. Jeśli jesteś zainteresowany, skontaktuj się ze mną. Szukam doświadczonego programisty do stworzenia dedykowanego doradcy eksperckiego (EA) do tradingu. Programista powinien posiadać solidną wiedzę z zakresu MT5, logiki strategii, wskaźników, zarządzania ryzykiem i backtestingu. Doświadczenie w
Salary ₹25,000 – ₹75,000 per month (based on capability, not years) Performance bonuses based on execution quality & system edge Project-based incentives for high-impact deliveries Annual bonus for consistent performers Perks & Benefits 4 months leave/year (designed for deep work cycles) 15 casual leaves Work on real trading engines, not basic bots Qualification 2–5+ years in MQL5 / MT5 development (preferred) Must
I am looking for an experienced MQL5 developer to create a custom technical indicator for MetaTrader 5. The indicator should combine Supertrend logic with Support/Resistance pullback levels to generate high-probability entry signals. 1. Core Logic The indicator must follow a two-step confirmation process: Trend Identification: Use the Supertrend indicator to determine the primary trend. Entry Signal (The
Hello, I am looking for a highly experienced developer to build a professional Smart Money Concepts indicator for TradingView using Pine Script . ⚠️ Platform Requirement This indicator must be developed in: Pine Script (TradingView) Compatible with the latest Pine Script version (v5 or newer) ❌ NOT for MT4 / MT5 ❌ NOT MQL5 ❌ NOT any other platform ⚠️ Important I do NOT want basic or noisy signals. I only want
TradingView Futures Automation Robot
100+ USD
I need a robot for TradingView that automates trading specifically for futures markets. The robot should implement the opening range strategy. I want this one: Getting this strategy is my goal https://www.youtube.com/watch?v=E3McKlAp3qk
I have discovered this indicator called RMA ADAPTIVE Ema. I am looking for a programmer that will create a dashboard and an indicator that will work in a similar way as the indicator in the picture attached below. Let's chat
Hello traders, I am currently looking for a professional and experienced trading coach/mentor and would like to connect with individuals who offer structured coaching services. Before proceeding, I would appreciate clarity on the following: Your primary trading strategy (scalping, intraday, swing, or long-term investing) Markets you specialize in (Forex, crypto, indices, stocks, etc.) Availability of verified track
Buy and sell indicator non ripaint
30 - 100 USD
Hello, I am looking for an experienced MQL5 developer to build a professional Buy/Sell indicator for MT5, specifically optimized for XAUUSD (Gold) on the M15 timeframe. The indicator must focus on high-quality signals with clean logic, not frequent signals. Main requirements: 1. True Non-Repainting - Signals must appear only after candle close. - No signal changes after the candle closes. 2. Signal Logic The
I am looking for a highly skilled and professional developer to create a custom Buy/Sell indicator for MT5. The indicator must be fully non-repainting on the chart and must include separate Buy and Sell buffers for possible future EA integration. What I need is not a noisy indicator that produces frequent random signals. I want the exact opposite: the indicator should be highly selective, with few but strong signals
프로젝트 정보
예산
30+ USD