작업 종료됨
실행 시간 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
등급
프로젝트
314
34%
중재
63
37%
/
40%
기한 초과
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%
무료
비슷한 주문
STRATEGY FOR GOLD XAUUSD - SMALL ACCOUNT $68 1. LOT SIZE: Fixed 0.01 lot. No auto lot. No martingale. No grid. 2. PAIR & TIMEFRAME: XAUUSD only, H1 timeframe. Gold is volatile! 3. BUY RULE: - 20 EMA crosses above 50 EMA - RSI(14) > 55 - Open buy at candle close 4. SELL RULE: - 20 EMA crosses below 50 EMA - RSI(14) < 45 - Open sell at candle close 5. RISK MANAGEMENT FOR GOLD: - Stop Loss: 1500 points = 150 pips =
STRATEGY FOR SMALL ACCOUNT $68 1. LOT SIZE: Fixed 0.01 lot. No auto lot. No martingale. No grid. 2. PAIR & TIMEFRAME: EURUSD only, H1 timeframe. 3. BUY RULE: - 20 EMA crosses above 50 EMA - RSI(14) > 55 - Open buy at candle close 4. SELL RULE: - 20 EMA crosses below 50 EMA - RSI(14) < 45 - Open sell at candle close 5. RISK MANAGEMENT: - Stop Loss: 250 points = 25 pips - Take Profit: 500 points = 50 pips - Max 1
Panda103
30 - 100000 USD
# Institutional-Grade MT5 Prop Firm Trading Bot Requirements ## Project Objective Develop a professional MetaTrader 5 Expert Advisor (EA) specifically designed to pass and maintain funded accounts such as: * FTMO * FundedNext * The5ers * MyFundedFX Primary goals: 1. Capital preservation first. 2. Consistent growth. 3. Strict drawdown compliance. 4. High-probability entries only. 5. Long-term funded account
All trades are supposed to be opened at the same time, and have different predetermined TP levels, so i will need to physically enter TP levels for individual trades trades allowed; For example, on the EA settings,like, below all settings, i should have a place to enter how many pips each trade will have to go to TP, UP TO 20 trades max, I will explain more but the job as as simply as explained above
MT5 XAUUSD Order Block and Liquidity Expert Advisor
30 - 200 USD
Use the H4 timeframe to determine the main trend direction. Identify valid order blocks on the H1 timeframe. Identify liquidity zones and liquidity sweeps. Wait for M15 confirmation before opening a trade. Only take buy trades in bullish market conditions and sell trades in bearish market conditions. Risk a fixed percentage of account balance per trade (user adjustable). Automatically calculate lot size based on
Scalping/HFT EA
30+ USD
I need someone to make an EA that is a HFT that actually works for prop firm or live accounts. Prop firm would be most preferred but it has to be from a prop firm that will allow HFT
I need a professional MT5 (MQL5) Expert Advisor for Gold (XAUUSD) scalping. Main requirements: - Work on M1 and M5 timeframes. - Trend filter using EMA 50 and EMA 200. - Entry confirmation after pullback and candle confirmation. - Open 3 positions per signal. Trade management: - Separate TP1, TP2, and TP3. - One Stop Loss for all positions. - When TP1 is reached: Close Position 1 and move remaining positions to
MC Trader's
30+ USD
If Buy: it must Buy when a conformation is done Bye the candle that would be a bullish engolfing candle or after liqudity swip or when sellers has stepped down the market and the market regains energy and trand upwards, it's stop loss must be below the Buy position and it's take profit must be at the top of all candles
Hi, I need an experienced developer to review and help repair a trading automation project. This is not a request to create a random trading bot from scratch. I already have an existing system called EXU. It uses TradingView alerts, a VPS webhook backend, a decision/guard layer, and an MT5 execution/proof layer. Current project status: * TradingView alerts are reaching the backend. * The clean VPS pipeline works. *
i am looking to upgrade my trading telegram bot and add live data to it and also make it linked to a dashboard where i can trace the users who register in my bot and pay and make them go in my private channel and manages the expiry date of each user
프로젝트 정보
예산
30+ USD