작업 종료됨
실행 시간 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
등급
프로젝트
310
34%
중재
59
36%
/
39%
기한 초과
100
32%
작업중
5
등급
프로젝트
470
39%
중재
102
40%
/
24%
기한 초과
78
17%
바쁜
게재됨: 2 코드
6
등급
프로젝트
11
18%
중재
0
기한 초과
3
27%
무료
7
등급
프로젝트
47
30%
중재
12
17%
/
75%
기한 초과
6
13%
무료
비슷한 주문
Oluwaleye Blessing Olumide
30+ USD
We're looking for a highly motivated and detail-oriented individual to fill a key position in our team. The successful candidate will be responsible for driving projects forward, analyzing complex data, and collaborating with cross-functional teams to achieve business objectives. The role requires exceptional problem-solving skills, effective communication, and adaptability in a fast-paced environment. If you're a
EA DEVELOPMENT
50+ USD
Hello, I’m interested in developing an Expert Advisor (EA). I will send you the details and examples of the type of EA I need. Please log in and review them so you can understand my requirements
Mt5 alert fix
40+ USD
i have a indicator on mt5 im using it right now , you can see the performance attached Am using the Ma filter to avoid false signals I developed this indicator myself But the signals are delaying in alerting Check if you can perfect and if you Can you work on it let me know Let me know if there anything you can do to make it perfect without lagging or delaying
An Expert Advisor (EA) robot that uses market movement-based indicators is an automated program designed for platforms like MetaTrader 4 or 5 (MT4/MT5) that monitors price fluctuations and triggers trades based on predefined technical rules. These robots, often used for trend following, scalping, or breakout strategies, analyze price action, moving averages, or volatility to automatically enter and exit trades
FPi
50 - 60 USD
The main things are the Tradovate bridge to fee bid ask price as shown in the diagram Breaking news ( Not just economic releases) on vertical lines ( not necessarily from Twitter) Entries based on candle stick pattern( consecutive candle, hammer, engulfing shooting star and inside bar) and failed entry count email alert. Bid ratio, strength indicator and csi with alert from here
Scalping EA MT5
30 - 70 USD
PHẦN 1: TIẾNG VIỆT (Cho các nhóm VN) Tiêu đề: Tìm Coder Pro: Tôi có khung Quản lý vốn/Risk chặt chẽ - Bạn lo chiến thuật "Vua Scalping" phân: Tôi cần đọc mã EA. Tôi có bộ quản lý vốn và rủi ro rất chi tiết. Chiến thuật theo lệnh (Strategy) tôi để bạn Tự QUYẾT (Yêu cầu: Chuẩn bị mở rộng quy mô đa khung, vào chắc chắn và nhiều lệnh). YÊU CẦU CỤ THỂ: 1. Phần Chiến thuật (Bạn lo): * Tự động chọn chỉ báo/phương pháp. *
W and M with zigzag
30+ USD
This Expert Advisor (EA) will use a custom indicator that connects all Higher Lows (HL), Higher Highs (HH), Lower Highs (LH), and Lower Lows (LL) using a continuous line. The line structure created by this indicator will be used to detect a valid W pattern for BUY trades
I already have an EA and willing to work together with a talented professional programmer so that we can make a profitable EA for the long-term. RazorQuant AI | Buy Trading Robot (Expert Advisor) for MetaTrader 5 RAZORQUANT AI v3.7 (MT5 EA) Purpose: Automated trading EA that combines classic technical filters with machine-learning signals and optional external AI (LLM) advice to decide BUY/SELL/HOLD and manage
I’m looking to develop an MT5 Expert Advisor based on a breakout and retracement strategy . Below is the core logic of the EA: Identify and mark the daily high and daily low Place a Buy Stop above the daily high and a Sell Stop below the daily low, using a 40-pip buffer Once a pending order is triggered: Set Stop Loss and Take Profit dynamically using ATR Apply an ATR-based trailing stop If price continues moving in
Pre pending order EA
30 - 40 USD
Hey developers I want to code for me good pre pending order EA with a good strain stop loss, break out logic, MT5, it can trade starting from 20&, pre pending breakout logic , trend filter trades Xauus , Eurusd trades real breakouts
프로젝트 정보
예산
30+ USD