Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

NT 7.0.0.19 strategy positions not updating, MB Trading live

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    NT 7.0.0.19 strategy positions not updating, MB Trading live

    NT 7.0.0.19
    MB Trading, Navigator 11.5.0.5 live
    NinjaScript, run fron Strategies tab. Wait until flat option checked.

    Trade executions are not updating the "strategy position" causing it to become out of sync with the account.

    See attached picture.
    Account was flat when strategy was started.

    Click image for larger version

Name:	100726-1.jpg
Views:	1
Size:	239.8 KB
ID:	894673Using
    Last edited by Camdo; 07-26-2010, 02:03 PM.

    #2
    Thanks for reporting in Camdo - so at startup of the strategy from the tab it was also showing it's flat then, correct? Have you witnessed the same also if you ran your same strategy directly from the chart? Can you please send in the logs for this issue to us, too?

    Thanks for the support.
    BertrandNinjaTrader Customer Service

    Comment


      #3
      The strategy tab shows flat at start up and the real account is flat also.
      I have examples of this same issue with NT 7.0.0.18.
      and NT 6.5.1000.16

      I have not tried using the NS strategy on a chart. I will try that tomorrow.

      I will send log and trace files by email.
      Last edited by Camdo; 07-26-2010, 03:53 PM.

      Comment


        #4
        Ok, thanks got the files and will take a look shortly - please let me know how your testing starting the strategy from the chart goes today. Thanks.
        BertrandNinjaTrader Customer Service

        Comment


          #5
          Strategy run on chart also failed to update strategy position properly.

          I have observed that it is the last execution that is not being read correctly.
          In a string of partial fills, it is the last one that does not get its qty added into the position qty.
          If the order is filled in one execution (no partials) then the strategy position qty remains unchanged.

          Also everything works okay in a simulated account.
          Testing in NT 6.5.1000.16 had only one occurence in 1 of 7 trades.
          Testing in NT 7...18 & 19 had occurences in 7 of 7 trades.

          The conditions for occurence seem to be:
          - MB Trading live using NinjaScript

          Comment


            #6
            Thanks for the detailed reply, I'll look into reproducing here shortly.
            BertrandNinjaTrader Customer Service

            Comment


              #7
              Hello, has there been any progress on this bug? Resolution of this issue for me is essential as I cannot use NT with MB at present. I am a licensed customer but will have to look for alternatives if this cannot be resolved.

              Your earliest advice on this is greatly appreciated.

              Comment


                #8
                Unfortunately this is a limitation of the MBT API which can't be overcome/worked around by NT easily. Thus, we would not have a resolution at this time. Sorry for the bad news.

                Comment


                  #9
                  Most of the correspondence about this issue was by email. Here is the jist of it:

                  The response I got was not very clear, but I did establish a workaround.

                  1. NT recognises an issue with the MBT API although I could never establish what that issue was.

                  2. The strategy position shown on the strategies tab should be ignored.

                  3. If you need strategy info in your strategy, I was told to use IOrder methods and variables.

                  4. I had success using IOrder methods and a strategy variable in lieu of Position.MarketPosition == MarketPosition.Flat. It took me a week to figure it out, and probably a bit kludgy too. My strategies have been running about a month now with about 150 live trades without issue.

                  5. I have since discovered that if you match trades with signal names, the problem of strategy termination may be solved. This became apparent to me after rewriting with IOrder methods, so I never tried it. If someone tries this please let me know if it works by posting a relpy.
                  Last edited by Camdo; 08-31-2010, 11:39 AM.

                  Comment


                    #10
                    Camdo, thankyou for your very detailed response (certainly better than "sorry can't help you").

                    Here I was about to bin my NT subscription, but after your response I now have a path to investigate.

                    I'll look into point 5 in a bit more detail and get back to you here if I find anything useful.

                    Many thanks!

                    Comment

                    Latest Posts

                    Collapse

                    Topics Statistics Last Post
                    Started by Tin34, Today, 03:30 AM
                    2 responses
                    16 views
                    0 likes
                    Last Post Tin34
                    by Tin34
                     
                    Started by sastrades, Yesterday, 09:59 AM
                    2 responses
                    31 views
                    0 likes
                    Last Post brucerobinson  
                    Started by ETFVoyageur, Today, 12:52 AM
                    1 response
                    16 views
                    0 likes
                    Last Post Leeroy_Jenkins  
                    Started by lollers, Today, 03:26 AM
                    0 responses
                    12 views
                    0 likes
                    Last Post lollers
                    by lollers
                     
                    Started by aliyahany, Today, 03:16 AM
                    0 responses
                    4 views
                    0 likes
                    Last Post aliyahany  
                    Working...
                    X