Hiding limit orders

Viewing 15 posts - 1 through 15 (of 17 total)
  • Author
    Posts
  • #184434 quote
    Albaran
    Participant
    Average

    Hi there,

    It’s all in the topic title; is there a way?

    I had thought to use the 1second timeframe but unfortunately, you need too much data – which is not supported by PRT – in order to achieve this so I’m a bit stuck..

    Can someone help me out? The idea is to avoid short/long hunters of course..

    Cheers,

    #184470 quote
    JS
    Participant
    Senior

    Hi @Albaran

    You can link an order (bestens) to Alerts, the order is hidden until the alert is triggered.

    Orders linked to Alerts are deleted if they have not been executed when you close the platform.

    #184831 quote
    Albaran
    Participant
    Average

    My bad, I posted my topic in the wrong forum..

    It was a question for automated trading..

    #184862 quote
    PeterSt
    Participant
    Master

    It’s all in the topic title; is there a way?

     

    It was a question for automated trading..

    Hi Albaran – possibly you think too difficult …

    Personally I can’t even imagine a limit order with Autotrading because it would be a kind of redundant operation; the program code would wait for a price to occur (from the one bar to the next and so on), and when it’s there it enters. This could obviously be done with a Limit order as well, but for me this would feel “out of control”.

    In the end you wouldn’t be waiting for a price to occur, but for a situation to happen. For example if a short average crosses a long average and a trend you like to see is occurring. Then enter. There are no Limit Orders anywhere and no-one would be able to see what you are heading for.

    Is this the answer you were looking for ?

    #184865 quote
    JS
    Participant
    Senior

    Hi @Albaran

    Example for automated trading:

    DefParam CumulateOrders = False
    
    A1 = Average[25](Close)
    A2 = Average[50](Close)
    
    Cond1 = A1 Crosses Over A2
    Cond2 = A1 Crosses Under A2
    
    If Cond1 then
    Buy 1 Contract at Close - 2 Limit
    EndIf
    
    If Cond2 then
    Sell 1 Contract at Close + 2 Limit
    EndIf
    
    

    The order will be in the order book at the moment one of the conditions is triggered, till then the (limit) order is “hidden”.

    For Buy orders set the Limit below the Close (actual price)
    For Sell order set the Limit above the Close

    If you want to buy (sell) above (below) the actual price use Stop orders.

    #184866 quote
    JS
    Participant
    Senior

    Edit:
    If Cond2 then
    SellShort 1 Contract at Close + 2 Limit
    EndIf

    #184867 quote
    Eric
    Participant
    Master

    MTF (multi timeframe) and market orders?

    #184868 quote
    JS
    Participant
    Senior

    Hi @Eric

    The question was about “Hiding Limit orders”

    #184869 quote
    PeterSt
    Participant
    Master

    The order will be in the order book at the moment one of the conditions is triggered, till then the (limit) order is “hidden”.

    Actually it is a nice subject. Anyway, this is exactly what Albaran does not want. My suggestion (implied by my previous post) – copied from your example, would be like this :

    DefParam CumulateOrders = False
     
    A1 = Average[25](Close)
    A2 = Average[50](Close)
     
    Cond1 = A1 Crosses Over A2
    Cond2 = A1 Crosses Under A2
     
    If Cond1 then
      Buy 1 Contract at Close - 2
    EndIf
     
    If Cond2 then
      SellShort 1 Contract at Close + 2
    EndIf

    Thus

    MTF (multi timeframe) and market orders?

    Something like that. However :

    I had thought to use the 1second timeframe but unfortunately, you need too much data – which is not supported by PRT

    then we’d have that issue, which seems the main issue for Albaran.

    @Albaran
    , the Premium version of PRT supports 1M bars, which would be 1 month for 1 second bars.

    Summarised, when a Limit order is put on an e.g. 1 minute time frame, it can be hunted for 1 minute. 😉
    Now how to solve this ? …

    #184870 quote
    PeterSt
    Participant
    Master

    The question was about “Hiding Limit orders”

    which you did not hide. Haha.

    #184872 quote
    GraHal
    Participant
    Master

    Do we really think any big traders would waste time directly hunting our little Orders?

    Even if we manage to hide an Order (but still there) then when the big boys gobble up the big visible Orders then our (invisible) Order would get gobbled up at same time anyway!? 🙂

    PeterSt thanked this post
    #184874 quote
    JS
    Participant
    Senior

    @PeterSt

    Do you really think your suggestion will work?

    If Cond1 then
      Buy 1 Contract at Close 2
    EndIf
    #184875 quote
    PeterSt
    Participant
    Master
    // Pseudo Code
    
    DefParam CumulateOrders = True   // !
     
    If Not OnMarket then
    
      A1 = Average[25](Close)
      A2 = Average[50](Close)
     
      Cond1 = A1 Crosses Over A2
      Cond2 = A1 Crosses Under A2
     
      If Cond1 then
        Buy 1 Contract at Close - 2 At Market
      EndIf
     
      If Cond2 then
        SellShort 1 Contract at Close + 2 At Market
      EndIf
    
    else
    
      // OnMarket.
    
      If abs(CountOfPosition) = 1 then
    
        If LongOnMarket then
          Buy 100000 Contract At Market
        else
          SellShort 100000 Contract At Market
        endif
    
        // Still too few for GraHal's likings ? then add more !! That'll teach them.
    
      endif
    
    endif
    
    GraHal thanked this post
    #184876 quote
    PeterSt
    Participant
    Master

    Do you really think your suggestion will work?

    With At Market, yes. 🙂
    And decent price calculation, obviously. It’s about the gist.

    #184877 quote
    JS
    Participant
    Senior

    Sorry but this is total nonsense:

    If Cond1 then
        Buy 1 Contract at Close 2 At Market
      EndIf
Viewing 15 posts - 1 through 15 (of 17 total)
  • You must be logged in to reply to this topic.

Hiding limit orders


ProOrder: Automated Strategies & Backtesting

New Reply
Author
author-avatar
Albaran @albaran Participant
Summary

This topic contains 16 replies,
has 5 voices, and was last updated by JS
4 years, 1 month ago.

Topic Details
Forum: ProOrder: Automated Strategies & Backtesting
Language: English
Started: 01/03/2022
Status: Active
Attachments: No files
Logo Logo
Loading...