Building an ATS - Logbook

Quote from 2rosy:

is this open source? from what i gather SHELL is the infrastructure and GHOST is the algo. Considering this is python I am familiar with how remarkably fast this can be developed in.

Sorry, I'm afraid its not open source for the time being. I haven't even considered that option until you mentioned so I may give it more thought and reconsider in the future. Your interpretation on the concepts of SHELL and GHOST is correct though.
Python is indeed a nice language to quickly build a working prototype and its data structures lend well to most kinds of mathematical manipulations. Do you have experience coding ATSs in Python?
 
Will you be observing other's systems in real time?

MBT has a way for you to observe other accounts in real time. It could generate ideas for your different ghosts' useage.
 
Quote from tiagor:

Indeed. But one could argue what's the use of a ghost without a proper shell.

Seriously though, I've got a pretty decent idea for 2 GHOSTs that work on entirely different levels but I will not even try to "guess"timate their performance before some simulation and then again, with live testing.

I'm laying out the code for some of the logic of the first GHOST (I'll later provide it with the gift of a name if it proves worthy).
Even though this thread is oriented to the buildup and performance of the whole system I won't be going to the minute details of the strategies in particular (for obvious reasons). I can advance though that its decision process will be based on an estimation of the very near term market direction by shoving around some given interpretation of patterns in time, price action and tick volume. This are not fixed rules though but depend on the behavior of the market on the short term, weighting some probabilities.

Failure is already guaranteed. Let's see if I can prove it can have a different ending. :D

The shell is uninteresting. Most people on ET spend faaar too much time talking about it. I suspect it's because ET guys are more software development in background rather than quant/finance.
 
Quote from 2rosy:

Yes, it takes about a few days ... or less

I guess this is true for any language if you have proper infrastructure. At least it takes similar time with Java for me.
 
Quote from CT10Gov:

The shell is uninteresting.
The shell (OMS) is the difficult part, especially if your ATS generates complex multi-leg, algorithmic, and/or contingent orders that, once filled, need to be dynamically hedged. Dealing with partial fills, hanging legs, etc can be convoluted and error prone. I have never seen a non-pro OMS that gets these things right.

Frankly, I am skeptical of claims that an ATS, including functional OMS, can be coded up in a matter of days.
 
Quote from CT10Gov:

The shell is uninteresting. Most people on ET spend faaar too much time talking about it. I suspect it's because ET guys are more software development in background rather than quant/finance.
Exactly.

It's a never ending story of building f**king boring oms infrastructure.

Zero edge, with lots of fancy "software architecture".

Yawn...
 
Quote from Kevin Schmit:

The shell (OMS) is the difficult part, especially if your ATS generates complex multi-leg, algorithmic, and/or contingent orders that, once filled, need to be dynamically hedged. Dealing with partial fills, hanging legs, etc can be convoluted and error prone. I have never seen a non-pro OMS that gets these things right.

Frankly, I am skeptical of claims that an ATS, including functional OMS, can be coded up in a matter of days.
I kind of agree, in so far as managing a stack of orders is tricky, especially skewing and re-sizing without losing priority -- but -- none of that is sufficient to make any money.

If you can't do the quant modelling work to figure out a fair value to quote around, then don't even bother to build the oms tech masterpiece.
 
OMS is technically challenging to do right, especially on a fund level. It *can* be trivially easy if it's done on a small scale and just enough that everything works for the strategy at hand.

The GHOST is intellectually hard.

Quote from Kevin Schmit:

The shell (OMS) is the difficult part, especially if your ATS generates complex multi-leg, algorithmic, and/or contingent orders that, once filled, need to be dynamically hedged. Dealing with partial fills, hanging legs, etc can be convoluted and error prone. I have never seen a non-pro OMS that gets these things right.

Frankly, I am skeptical of claims that an ATS, including functional OMS, can be coded up in a matter of days.
 
Quote from CT10Gov:

OMS is technically challenging to do right, especially on a fund level. It *can* be trivially easy if it's done on a small scale and just enough that everything works for the strategy at hand.

The GHOST is intellectually hard.

thats what I was getting at. I meant that for personal use infrastructure (especially in python) is not difficult and can be done in a few days. Nothing needs to be fast considering you're going over the internet and most likely have a slow feed.
 
Back
Top