what is the best way to determine if a trade is hedged? | Forex Factory

Options

Permalinks
Print Thread

Similar Threads

2 ways handling hedged positions 2 replies

Extreme long term Hedged Carry Trade Position Building journal 15 replies

Profit on Fluctuation System: Hedged 121 replies

Hedged Carry Trading 3 replies

Looking for zero Hedged Margin broker 6 replies

Attachments: what is the best way to determine if a trade is hedged?
Exit Attachments

what is the best way to determine if a trade is hedged?

  • #1
  • First Post: Apr 10, 2017 2:32pm Apr 10, 2017 2:32pm
okay... this is melting my brain, there has to be a better way to do this?!

I want to hedge trades. When I place the hedge, I will put the original trade's ticket number along with "Hedge " in the hedge's comment. All I want to do is be able to select either the hedge OR the original trade, and determine if it is hedged or not using orderselect functions rather than long lots == short lots etc.

I can select the hedge using OrderSelect and find the OrderTicket() of the trade that it hedged quite simply buy just looking at the hedge's OrderComment(),
but what i'd really like to do is be able to select any trade and determine if it is hedged. The original trades contain no information about the hedges so I think I need to create a nested loop that selects a trade then loops through again comparing parameters with it's own but i'm not sure how to do that.

to maybe help clarify what I want to do, here's a demo of what I can't do because using a single loop means that you cant compare to other trades, but really, if you can think of a better way to do this then I am definitely all ears!!

for the code example, this is for when both trades are active so "you can search all trades simultaneously" would be a lovely result that I can't solve



Inserted Code
 
int j=OrdersTotal()-1;
for( int i=j;i>=0;i--)
  {
   if((OrderSelect(i,SELECT_BY_POS,MODE_TRADES)==true)
      && (OrderMagicNumber()==MagicNumber)
      && (OrderSymbol()==Pair)){ //order select
            
        if(StringFind(OrderComment(),"Hedge")>=0) {
        int ScalpTicket = StrToNumber(OrderComment());}
        //StrToNumber is a function removes all non-numerical characters
      
              if((StringFind(OrderComment(),"Hedge")>=0)
              &&(StringFind(OrderTicket(),IntegerToString(ScalpTicket))>=0)){
              Print("you can search all trades simultaneously");}
            
              if((StringFind(OrderComment(),"Hedge")>=0)
              &&(StringFind(OrderTicket(),IntegerToString(ScalpTicket))>=0)){
              Print("found hedge but not scalp");}
  
              if((StringFind(OrderComment(),"Hedge")<0)
              &&(StringFind(OrderTicket(),IntegerToString(ScalpTicket))>=0)){
              Print("found scalp but not hedge");}
    
        }//end order select
   }//end of loop
  • #2
  • Apr 14, 2017 9:06am Apr 14, 2017 9:06am
Quote
I can select the hedge using OrderSelect and find the OrderTicket() of the trade that it hedged quite simply buy just looking at the hedge's OrderComment(),

You've got the essential idea, which I've quoted above. What I'd do is simply maintain a list of the ticket numbers and their hedges in a two dimensional array. In your init() function, you scan all open orders looking for the OrderComment that tells what order is hedged to what, and populate the array with that information, original ticket number in column 0, hedge ticket number in column 1. If the list is expected to be fairly large, it would be a good idea to sort them, it will make searching the list easier later.

You can create a group of little helper functions to encapsulate the various operations that need to be done on this list. For example,

  1. HedgeCreateList() - creates the list initially
  2. HedgeAdd( int OrigTicket, int HedgeTicket) - adds a ticket / hedge pair to the list
  3. HedgeRemove( int OrigTicket ) - removes a ticket / hedge pair from the list
  4. bool IsHedged( int Ticket ) - returns true if Ticket has a hedge
  5. etc

Sure I have a trading plan. Buy low. Sell high. What's yours?
  • #3
  • Apr 15, 2017 11:38am Apr 15, 2017 11:38am
thanks!! ill do some more looking into is.

I think what I need to is have a trade functions void that does all of the trade logic, then a checkifhedged void and when I need to check if hedged, I just run another loop to compare OrderTicket() to all the others
  • #4
  • Apr 16, 2017 2:45am Apr 16, 2017 2:45am
Must admit I'm not 100% sure what you're trying to achieve, but have you considered using GlobalVariables?

For example (and just off the top of my head), when you hedge your trade, you could do something like:
GlobalVariableSet("@Hedge_"+NumberToStr(PrimaryTicketNum,"Z10"), SecondaryTicketNum);
and, if you need to cross reference the other way:
GlobalVariableSet("@Hedge_"+NumberToStr(SecondaryTicketNum,"Z10"), PrimaryTicketNum);

Hence you'd end with a GV named something like @Hedge_0000001001 with a value of 1002
and a GV named something like @Hedge_0000001002 with a value of 1001
(NumberToStr is a function I wrote for my own use -- see this thread, or pips4life's build 600+ update here. Or you could devise something similar......)

Then if you later want to find out if an order is hedged:
HedgedTicketNum = GlobalVariableGet("@Hedge_"+NumberToStr(TicketNum,"Z10"));
Then if HedgedTicketNum contains 0, the order TicketNum is not hedged, otherwise HedgedTicketNum will be set to the ticket number of its sister order.

Occasionally you might want to perform housekeeping, i.e. loop thru the OrdersHistory and do a GlobalVariableDel() for each pair of GVs after their respective orders have both been finally closed.

I use GVs extensively as (unlike other variables and arrays) they can be accessed across multiple EAs/charts, and they remain intact even if an EA is removed, or a chart is closed etc. I try to avoid populating the OrderComment with this type of info as it can be overwritten by MT4, e.g. if you partially close an order, the old and new orders' comments get completely overwritten.

My apologies if I've misunderstood your requirement.
  • #5
  • Edited 9:20am Apr 16, 2017 8:57am | Edited 9:20am
thanks!! I'm actually already using your StrToNumber to parse the ticket numbers that I put into the hedge comments (along with a lot of your other functions, they're great!). But basically I think I've got a solution that works like this: - there is a loop that looks at all active trades - from that void I basically call another void that has another loop and compares parameters from the first orderselct with orders in the second order select like follows:

Attached Image (click to enlarge)
Click to Enlarge Name: is hedge..PNG Size: 81 KB


i do like your idea of global variables though for this task. i agree the order comment getting overwritten with partial close is super messy so I just don't include that. maybe I should look at your idea in more detail
  • #6
  • Apr 8, 2018 8:35am Apr 8, 2018 8:35am
Quoting hanover
Must admit I'm not 100% sure what you're trying to achieve, but have you considered using GlobalVariables? ....


Hi Hanover...

Do you think this one will work? Though I am not sure if locked orders can be excluded.

regards..
Attached Image (click to enlarge)
Click to Enlarge Name: Capture.JPG Size: 107 KB
Since Frank Sinatra sings in his own way, my chart sing... I did it, my way
  • #7
  • Apr 8, 2018 9:24am Apr 8, 2018 9:24am
Quoting v2vboni
Do you think this one will work? Though I am not sure if locked orders can be excluded.
I do all my coding using Metaeditor/compiler build 509, hence I'm not familiar with some of the syntax that you're using. For example, I don't know exactly what ChartID() does.

Also I'm not certain what you're trying to achieve; and it's difficult to understand how you are using some of the other variables without seeing the rest of your EA's code.

Also, what are "locked orders"? I haven't come across that term before.

Only you know exactly what you're trying to achieve with your EA. All I can suggest is that you test your code, and see if it delivers the outcomes that you're looking for.

Sorry I can't be more help.
  • #8
  • Apr 8, 2018 9:58am Apr 8, 2018 9:58am
Quoting hanover
{quote} I do all my coding using Metaeditor/compiler build 509, hence I'm not familiar with some of the syntax that you're using. For example, I don't know exactly what ChartID() does. Also I'm not certain what you're trying to achieve; and it's difficult to understand how you are using some of the other variables without seeing the rest of your EA's code. Also, what are "locked orders"? I haven't come across that term before. Only you know exactly what you're trying to achieve with your EA. All I can suggest is that you test your code, and see...

Oh! I completely understand... no issues. I was only pertains the use of Global Variables... anyway about the locked orders... it is about the order getting locked.. with an error code 139 ERR_ORDER_LOCKED

anyway, thanks for the prompt response.
Since Frank Sinatra sings in his own way, my chart sing... I did it, my way
  • #9
  • Apr 8, 2018 10:09am Apr 8, 2018 10:09am
Quoting v2vboni
... anyway about the locked orders... it is about the order getting locked.. with an error code 139 ERR_ORDER_LOCKED
Sorry, I wasn't sure because some traders use terms lock/unlock to describe hedging/unhedging orders (e.g. here).
  • #10
  • Apr 8, 2018 2:21pm Apr 8, 2018 2:21pm
Quoting hanover
{quote} Sorry, I wasn't sure because some traders use terms lock/unlock to describe hedging/unhedging orders (e.g. here).
... or freeze/unfreeze... almost always a sign of over-leveraging. If you're (I'm not preaching at hanover when I say this BTW) using opposite orders without using "closeby" then I'd be honored to be your IB
  • #11
  • Last Post: Edited 4:03am Apr 9, 2018 3:52am | Edited 4:03am
The error 139 (ERR_ORDER_LOCKED) happens on an attempt to process an order that is currently being processed by the broker. It usually happens when a pending order, stop loss, take profit or order expiration is triggered (on the broker side) and an attempt to do some processing from the user side is made at that same moment. The error is not related to hedging
0 traders viewing now