フリーランスセクション

120x ticker screener (composite tickers)

MQL5 インディケータ エキスパート 外国為替 売買ロボット/指標のデバッグ 統計と数学 ストラテジーの最適化 ストラテジーモジュール 株式

指定

In specific circumstances, it is possible to extract data, far above the  for 1 single script .
The following technique uses composite tickers. Changing tickers needs to be done in the code itself as will be explained further.

          ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

🔶 PRINCIPLE

        Standard example:

  c1 = request.security('MTLUSDT' , 'D', close)


        This will give the close value from 1 ticker (MTLUSDT); c1 for example is 1.153

        Now let's add 2 tickers to MTLUSDT; XMRUSDT and ORNUSDT with, for example, values of 1.153 (I), 143.4 (II) and 0.8242 (III) respectively.

        Just adding them up 'MTLUSDT+XMRUSDT+ORNUSDT' would give 145.3772 as a result, which is not something we can use...

        Let's multiply ORNUSDT by                  100 ->            14340
        and   multiply MTLUSDT  by 1000000000 -> 1153000000                 (from now, 10e8 will be used instead of 1000000000)
        Then we make the sum.

        When we put this in a security call (just the close value) we get:

  c1 = request.security('MTLUSDT*10e8+XMRUSDT*100+ORNUSDT', 'D', close)


        'MTLUSDT*10e8+XMRUSDT*100+ORNUSDT' -> 1153000000 + 14340 + 0.8242 = 1153014340.8242 (a)

        This (a) will be split later on, for example:

        1153014330.8242 / 10e8 = 1.1530143408242 -> round -> in this case to 1.153 (I), multiply again by 10e8 -> 1153000000.00 (b)
        We subtract this from the initial number:

            1153014340.8242   (a)
         - 1153000000.0000   (b)
          –––––––––––––––––
                       14340.8242   (c)

        Then -> 14340.8242 / 100 = 143.408242 -> round -> 143.4 (II) -> multiply -> 14340.0000 (d)
         -> subtract

            14340.8242   (c)
         - 14340.0000   (d)
          ––––––––––––
                     0.8242   (III)

        Now we have split the number again into 3 tickers: 1.153 (I), 143.4 (II) and 0.8242 (III)

          ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯


In this publication the function compose_3_() will make a composite ticker of 3 tickers, and the split_3_() function will split these 3 tickers again after passing 1 request.security() call.

In this example:

t46 = 'BINANCE:MTLUSDT', n46 = 10e8 , r46 = 3, t47 = 'BINANCE:XMRUSDT', n47 = 10e1, r47 = 1, t48 = 'BINANCE:ORNUSDT', r48 = 4 // T16 ••• T16= compose_3_(t48, t47, n47, t46, n46) ••• [o16, h16, l16, c16] = request.security(T16, res, [open, high, low, close]) ••• [MTLc , XMRc , ORNc ] = split_3_(c16, n46, r46, n47, r47, r48)



🔶 CHANGING TICKERS

If you need to change tickers, you only have to change the first part of the script, USER DEFINED TICKERS

Back to our example, at line 26 in the code, you'll find:

t46 = 'BINANCE:MTLUSDT', n46 = 10e8 , r46 = 3, t47 = 'BINANCE:XMRUSDT', n47 = 10e1, r47 = 1, t48 = 'BINANCE:ORNUSDT', r48 = 4 // T16
(t46, T16,... will be explained later)

You need to figure out how much you need to multiply each ticker, and the number for rounding, to get a good result.

In this case:
'BINANCE:MTLUSDT', multiply number = 10e8, round number is 3 (example value 1.153)
'BINANCE:XMRUSDT', multiply number = 10e1, round number is 1 (example value 143.4)
'BINANCE:ORNUSDT', NO multiply number, round number is 4 (example value 0.8242)

The value with most digits after the decimal point by preference is placed to the right side (ORNUSDT)

If you want to change these 3, how would you do so?

First pick your tickers and look for the round values, for example:
'MATICUSDT', example value =   0.5876 -> round -> 4
'LTCUSDT'    , example value = 77.47      -> round -> 2
'ARBUSDT'    , example value =   1.0231 -> round -> 4

Value with most digits after the decimal point -> MATIC or ARB, let's pick ARB to go on the right side, LTC at the left of ARB, and MATIC at the most left side.
-> 'MATICUSDT', LTCUSDT', ARBUSDT'

Then check with how much 'LTCUSDT' and 'MATICUSDT' needs to be multiplied to get this: 5876 0 7747 0 1.0231

'MATICUSDT' -> 10e10
'LTCUSDT'      -> 10e3

Replace:

t46 = 'BINANCE:MTLUSDT', n46 = 10e8 , r46 = 3, t47 = 'BINANCE:XMRUSDT', n47 = 10e1, r47 = 1, t48 = 'BINANCE:ORNUSDT', r48 = 4 // T16

->

t46 = 'BINANCE:MATICUSDT', n46 = 10e10 , r46 = 4, t47 = 'BINANCE:LTCUSDT', n47 = 10e3, r47 = 2, t48 = 'BINANCE:ARBUSDT', r48 = 4 // T16


DO NOT change anything at t46, n46,... if you don't know what you're doing!

Only
 • tickers ('BINANCE:MTLUSDT', 'BINANCE:XMRUSDT', 'BINANCE:ORNUSDT', ...),
 • multiply numbers (10e8, 10e1, ...) and
 • round numbers (3, 1, 4, ...)
should be changed.

There you go!


🔶 LIMITATIONS

🔹 The composite ticker fails when 1 of the 3 isn't in market in the weekend, while the other 2 are.
     That is the reason all tickers are crypto. I think it is possible to combine stock,... tickers, but they have to share the same market hours.

🔹 The number cannot be as large as you want, the limit lays around 15-16 digits.
     This means when you have for example 123, 45.67 and 0.000000000089, you'll get issues when composing to this:
     -> 123045670.000000000089 (21 digits)

     Make sure the numbers are close to each other as possible, with 1 zero (or 2) in between:
     -> 1.230045670089 (13 digits by doing -> (123 * 10e-3) + (45.67 * 10e-7) + 0.000000000089)

🔹 This script contains examples of calculated values, % change, SMA, RMA and RSI.
     These values need to be calculated from HTF close data at current TF (timeframe).
     This gives challenges. For example the SMA / %change is not a problem (same values at 1h TF from Daily data).
     RMA, RSI is not so easy though...

     Daily values are rather similar on a 2-3h TF, but 1h TF and lower is quite different.

     At the moment I haven't figured out why, if someone has an idea, don't hesitate to share.
     The main goal of this publication is 'composite tickers ~ request.security()' though.



🔹 When a ticker value changes substantially (x10, x100), the multiply number needs to be adjusted accordingly.


🔶 SETTINGS

  • SHOW SETS


  • SET
       • Length: length of SMA, RMA and RSI
       • HTF: Higher TimeFrame (default Daily)

  • TABLE
       • Size table:                         \ _ Self-explanatory
       • Include exchange name:  /
       • Sort: If exchange names are shown, the exchanges will be sorted first

  • COLOURS
       • CH%
       • RSI
       • SMA (RMA)

  • DEBUG

    Remember t46, T16,... ?
    This can be used for debugging/checking
    ALWAYS DISABLE "sort" when doing so.

    Example:

    Set string -> T1 (tickers FIL, CAKE, SOL)
    (Numbers are slightly different due to time passing by between screen captures)

    Placing your tickers at the side panel makes it easy to compare with the printed label below the table (right side, 332201415014.45),
    together with the line T1 in the script:

    t1 = 'BINANCE:FILUSDT' , n1 = 10e10, r1 = 4, t2 = 'BINANCE:CAKEUSDT' , n2 = 10e5 , r2 = 3, t3 = 'BINANCE:SOLUSDT' , r3 = 2 // T1


    FIL     :    3.322
    CAKE:    1.415
    SOL   : 14.56

    Now it is easy to check whether the tickers are placed close enough to each other, with 1-2 zero's in between.

    If you want to check a specific ticker, use "Show Ticker", see out initial example:
    Set string    -> T16
    Show ticker -> 46 (in the code -> t46 = 'BINANCE:MTLUSDT')

    (Set at 0 to disable "check string" and NONE to disable "Set string")

    -> Debug/check/set away! 😀


🔶 OTHER TECHNIQUES

 • REGEX (Regular expression) and  is used to delete the exchange name from the ticker, in other words, everything before ":" is deleted by following regex:
exch(t) => incl_exch ? t : str.match(t, "(?<=:)[\\w]+")

 • To sort,  is used (line 675 in the code), just as in my first "sort" publication Sort array alphabetically - educational

aSort = arrT.copy() sort_Indices = array.sort_indices(id= aSort, order= order.ascending)


 • Numbers and text colour will adjust automatically when switching between light/dark mode by using  / 

🔹 DISCLAIMER
Please don't ask me for custom screeners, thank you.

ファイル:

TXT
120x_ticker_screener_mcomposite_tickersq.txt
54.6 Kb

応答済み

1
開発者 1
評価
(7)
プロジェクト
6
0%
仲裁
5
0% / 100%
期限切れ
1
17%
暇
類似した注文
My expert needs logic adjustment . Present logic needs correct implementation . 30+ USD
Expert should be able to place trades across all Forex symbols (solution is advised) . xauusd live chart execution error . Deletion and Cleaning the Code (if required) . Live Chart Only
Debug EA to work efficiently and to be available on the market of MQL5 30 - 35 USD
Title: MT5 Forex Trading Robot Development I need a MetaTrader 5 (MT5) Expert Advisor (EA) for automated Forex trading. Requirements: 1. The robot must be fully automated and capable of opening and closing trades without manual intervention. 2. Compatible with MetaTrader 5 (MT5). 3. Adjustable lot size, Stop Loss, and Take Profit settings. 4. Built-in risk management based on account balance. 5. Ability to trade
GRID EA with PRUNING 80+ USD
MT5 Expert Advisor Development Project Overview I am looking for an experienced MQL5 developer to build a custom MetaTrader 5 Expert Advisor based on a grid-cycle trading framework. This is not a standard grid EA . The system combines: Session-based trade initiation Multi-filter signal generation Dynamic grid management Advanced basket management State-machine-driven trade lifecycle management Dynamic take-profit
Minor adjustment needs to be implemented to my expert . 30+ USD
Prepare expert for xauusd live chart [ expert is not executing trades on xauusd ] . Deletion and cleaning code . Trailing Stop Rule to follow the given method . Live Chart Only
Robot oluşturmama yardım rica ediyorum. 30+ USD
Matriks programında güzel bir stratejim var, meta da kayıtlı olmayan iki indikatörümü de metaya yükledim, stratejim belli, ama robot oluşturmak konusunda bilgim eksik. Yardım istiyorum. Acil dönüş bekliyorum. 12-276 üssel ortalamayı hangi yöne keserse, alphatrend indikaörüde bunu desteklesin, kendi gömdüpüm diğer bir indikatörde seviyelere göre alsın satsın
Institutional MT5 EA with ICT/SMC Market Structure and Liquidity Logic 150 - 400 USD
MT5 EA Developer for Structured ICT/SMC Market Logic Requirements Specification: I need an MT5 Expert Advisor only in MQL5. No indicator, no script, no DLL, and no external API. The EA must be built on a rule-based ICT/SMC-style framework with objective, backtestable logic. I am not looking for social-media-style ICT/SMC interpretation. I need a developer who can convert trading concepts into clear coding rules. The
MT4 Expert Advisor Developer Needed – Debug & Live Test Existing EX4 Bot 59+ USD
I’m looking for an experienced MetaTrader 4 (MT4) developer to analyze, repair, and live-test an existing .EX4 Expert Advisor. Project Details Existing file: GannMadeEasy_pro.ex4 Platform: MetaTrader 4 Issue: EA is not loading properly on charts in newer MT4 builds Goal: Make the EA fully functional and compatible with current MT4 versions Requirements The developer must: Analyze the existing EX4 file Identify
Junior EA 30+ USD
1. EA for MT5, hedging allowed. 2. Entry: 50 EMA crosses 200 EMA on H1. Buy on bullish cross, sell on bearish. 3. SL: 100 pips, TP: 200 pips. No trailing stop. 4. Lot size: 0.01 fixed. Max 3 trades at once. 5. Trade only 08:00-18:00 GMT. No trades if spread > 20 points. 6. Inputs: EMA periods, SL, TP, lot size, start/end time
Need Custom MT4 Indicator through cracking file (Non-Repaint, Same Signal Logic as Existing Tool, Legit PC ID system ) 150 - 350 USD
I am looking for an experienced MQL4/MQL5 developer to build a custom MT4 indicator from scratch or cracking my ex4 file that i provide to you. I already have an existing indicator (EX4) which produces highly accurate buy/sell signals. I want a similar indicator developed based on its observable behavior and signal structure. my existing indicator is pc id protected so you have to do PC ID security bypass and source
Advanced XAUUSD Trend Scalping EA for MT5 — Professional Risk Management & Smart Filters 100 - 200 USD
OBJETIVO Criar um Expert Advisor MT5 profissional para XAUUSD focado em: Consistência Baixo drawdown Scalping profissional Proteção da conta Crescimento sustentável Compatibilidade com conta micro e prop firms NÃO utilizar: Martingale Grid Hedge agressivo Recovery system Multiplicação de lotes após perda --- ATIVO XAUUSD apenas --- TIMEFRAMES Timeframe principal M5 Confirmação tendência M15 Confirmação macro opcional

プロジェクト情報

予算
30 - 200 USD
締め切り
最高 20 日