No, still moving along. Equity has been nearly flat this month. After a total of 1170 trades, here is my latest pip chart.
Much smoother, but I have never looked at a metric showing all 10 strategies combined. Its always been individual strategies. However, I would expect further smoothing from combining. I believe part of my problem is several of the strategies I am trading are fairly weak. I still consider this sort of an "information" gathering period. Slowly trying to tweak and make each strategy better. At some point I will look at all this data collected and determine the best strategies to trade with increased money. For now, I have to sit back, watch, and learn how the strategies trade live. This information is far superior to anything I can get from backtesting or out of sample testing.
FYI, I've tried contacting you via PM to no avail...I've been curious how things have been going with MBTrading and NT and if you're still using Pay for Limits? Well I can tell you that I started using an MBTrading demo this week and NT executing orders against its Sim101 account. Yes I am aware of the potential fundamental Sim101 issues here. But even with this setup, position management seems completely broken beyond belief. I'll enable a strategy and suddenly its in a position, but the Positions tab has no entry. And there is no way to "clear" this position except until the strategy gets an exit signal. I understand there are some issues noted in the NT-MBTrading disclaimer (when you add the account connection), but this is beyond what is to be expected. I'm using the latest software from both companies and the bottom line is its completely unusable. Its hard to believe that a brokers API that is only being used for a data feed has this much affect on NTs position management. I'll give FXCM a shot next because this is unusable as is. TLDR; MBTrading is unusable with NT automated strategies.
Amending a correction. These phantom orders are not specific to MB Trading. They occurred with FXCM also. Maybe Kinetick is better, I dunno.
the MBT platform freezes if you make a mistake. All it tells you is that you made a mistake . You have to figure out what went wrong. I spent a weekend debugging my mind and wrote out how to not make mistakes. If you get to trading using a master account and linking in subordinate accounts, then going flat by phone after a freeze up, the desk requires that you provide a lot of information serially. The desk also goes through "proving" the POA exists for each account; MBT does not have an orderly search process in thier shop. It can be time consuming. Finally, the desk has no "link in" capability; that is MBT cannot see from a master account what is linked in to it. Since this was not an operating possibility for me, I did a "workaround" that is satisfactory for not having to go through "proving" anything and not knowing the linkages automatically. Result: No proving and automatic knowlege of linkages "outside" of the "system"; I am taken "flat" in a flash.
Mr You: If you look on the Tools/Options/Strategys menu and click the NinjaScript tab, you will see a radiobox choice of 'Wait Until Flat before executing live' and 'Immediatly Submit Live Working Orders'. These box's work in conjunction with the 'Sync Account Position T/F' choice in the 'Edit Strategy' menu that appears when you apply a strategy in the control center 'Strategys' area. Depending on the combination of these choices you get 4 different possible entry handling caracteristics with NinjaTrader. Look in the help documentation with the keyword search 'Syncing Account Positions' for the combination that suits your goals
Hey, IB has a demo account or you can just eat the cost of the commissions until youre ready to go with big size or maybe u should try another NT compatible broker? I have another idea, why dont you run IB and the other one at the same time, see which one gives you better fills? Let us know.
Looks like these phantom orders have something to do with historical data influence. Doing the following or similar within OnBarUpdate() seems to clear it up: Code: if (Historical) return;