Quantopian's community platform is shutting down. Please read this post for more information and download your code.
Back to Community
Issues Faced in Going Live

My biggest issue is that I'm an RIA that trades with discretion for multiple subaccounts. When I go to add a "U...." type account to the account list, it takes the account, but when I go to deploy, it prompts me for a password, and does not accept the master password with which I log into all accounts to place trades, specifying the subaccount in each trade.

Anybody else faced this? Is there a work around? I reckon I can ask each of my clients for their password, but this seems like a tedious way of doing things, since they've already authorized me to trade on their behalf.

2) This issue has to do with limit orders. Due to history of flash crashes (up and down), I am reluctant to place ANY trade at "market". I always use Limit orders.

In live trading, according to Q's help pages, "All open orders are cancelled at end of day."

  • I take it this means that partially filled orders are also cancelled? Is that accurate?
  • It says that "order_target" and "order_target_percent" will still be relaunched the next day.

Does this mean, in my use of limit orders, that I can use

order_target(someStock, totalSharesToAcquire,MaxPriceToPay)

and be confident that after being cancelled for not having filled one day, the order will be relaunched the next morning?

3) If the answer to 2 is in the negative, does anybody have a simple function for storing all unfilled orders into a context variable
every night and relaunching? If not, I'll have to put my limited Python skills to the test, and I'll post the results later to the community.

Appreciate any input.

8 responses
  1. Sorry, I trade each account separately since I am not an RIA doing master/sub. I am not sure they support what you are trying to do at all.
  2. No, orders are cancelled, and that's it. I always cancel all my own orders at 3:59 to simulate this in backtest.
  3. I would not do this if I were you, rather I would separate the logic of deciding upon an allocation and trying to execute towards that allocation, and run the latter every morning. the downside is then you introduce some continuous rebalancing, so then you need code to prevent unnecessary/small orders, etc etc. it gets tedious.

FWIW: https://www.interactivebrokers.com/en/index.php?f=2827&ns=T

Hi Simon,
Thanks for your response. As to 1), I just heard from Q that they DO NOT support master/sub accounts. So I wll have to call my customer, obtain his password, and do it as an individual account.

2) OK . I don't know what I had seen that suggested that order_target orders would remain in force. I can no longer find the reference in Q 's help documentation.

3) Well I was just trying to avoid having Q generate unnecessary computer cycles performing the same weekly or monthly analysis every day. But maybe I should just store the desired results (rather than orders) to context variables, and run a daily task against that, e.g.

desired positions: 5240 shares of TLT limit 121.80
2122 shares of SPY limit $222.33
etc

daily procedure would check portfolio against that and resend orders accordingly.

Any reason not to do that?

Thanks
Serge

Yes that is the sort of thing I have been doing. If you are directing orders (IEX) there may be a cancellation fee, but regular SMART orders should be free.

Thanks Simon

@Serge did you find a way to execute an algo through the master RIA account?

From what I have read from this thread it seems that you need to hook up an algo for each subaccount. If you have many clients, this is really going to be difficult (imagine updating your algo when you have 200 accounts!).

HI Mohammad

No there is no way to execute through the master account. :<(

Yeah updating the accounts for 200 odd accounts would be a bitch... I only have about a half dozen that I need to run on these algos . Unfortunately.
(I'd rather have more accounts, as I'm a greedy sob...)

Bottom line, you'd better not have to stop and start that algo too often. So make damn sure you've backtested the hell out of it before running on that many live accounts. Of course, we know there are going to be things failing on Q's side (server glitches, power outages despite redundant servers, software updates, etc, etc) . Who knows how often this brings down the algo?

Nor can one simply write a batch file to automate the starting/stopping. Because all my clients use the security devices I cannot use a batch file. My computers are still relatively primitive beings that still have a problem with anything requiring sight and character recognition... lol.

I would love this functionality, even if only to implement some 'robo-advisor' algos for friends and family.

Hey guys, I noted the feature request, thanks!

Disclaimer

The material on this website is provided for informational purposes only and does not constitute an offer to sell, a solicitation to buy, or a recommendation or endorsement for any security or strategy, nor does it constitute an offer to provide investment advisory services by Quantopian. In addition, the material offers no opinion with respect to the suitability of any security or specific investment. No information contained herein should be regarded as a suggestion to engage in or refrain from any investment-related course of action as none of Quantopian nor any of its affiliates is undertaking to provide investment advice, act as an adviser to any plan or entity subject to the Employee Retirement Income Security Act of 1974, as amended, individual retirement account or individual retirement annuity, or give advice in a fiduciary capacity with respect to the materials presented herein. If you are an individual retirement or other investor, contact your financial advisor or other fiduciary unrelated to Quantopian about whether any given investment idea, strategy, product or service described herein may be appropriate for your circumstances. All investments involve risk, including loss of principal. Quantopian makes no guarantees as to the accuracy or completeness of the views expressed in the website. The views are subject to change, and may have become unreliable for various reasons, including changes in market conditions or economic circumstances.