For code/output blocks: Use ``` (aka backtick or grave accent) in a single line before and after the block. See: http://commonmark.org/help/

Logging enter/close a long/short position in SignalStrategy



  • Hi,

    First of all, I am new to the community so apologies if I do not follow some rules I might not be aware of. I browsed through the topics and have not found a problem similar to mine. My case is a strategy built on bt.SignalStrategy where I have LONG, LONGEXIT, SHORT, SHORTEXIT signals. The precise strategy is of no importance. What troubles me if there is a way to overwrite the default notifications to log information when we enter/close a long/short position instead of the common buy/sell. So in other words providing more detailed information what is happening in the broker. Hope this makes sense.

    Would appreciate any help :)

    Cheers!


  • administrators

    @ciril-pl said in Logging enter/close a long/short position in SignalStrategy:

    Hope this makes sense.

    No it doesn't.

    @ciril-pl said in Logging enter/close a long/short position in SignalStrategy:

    What troubles me if there is a way to overwrite the default notifications to log information when we enter/close a long/short position instead of the common buy/sell

    In order for it to make sense you may want to elaborate on what you mean with this. There is no difference in the notifications and how they are delivered, whether you use signals or you don't.



  • In quickstart you show how to overwrite notifications so they log information such as BUY CREATE,
    BUY EXECUTED and you arrive at the direction by looking at order.isbuy(). I would like to create notifications such as LONG CREATED, LONG EXECUTED, LONG CLOSED and the equivalents for short positions based on the LONG, LONGEXIT, SHORT, SHORTEXIT signals embedded in bt.SignalStrategy.


  • administrators

    Those notifications as such don't exist. You can track the Trade instances you get notified via notify_trade which will contain that information


Log in to reply
 

});