IMO it really depends what you want to do, if you're just running a personal projects SVN is great. I've used SVN with multi-gigabyte code bases and never had a problem. GIT is more complex model, really aimed at running distributed teams. In reality either will do the job fine.
All my heavy lifting is done in C++, R is good for certain types of rough prototyping and also for providing verification of numerical functions written in C++. Fully agree with the above, strategy code should be the same in both the back-testing and live environments.
There is a overview of the structures here http://www.nanex.net/API_Explain.html, the word 'tape' occurs multiple times. I had heard that one of the things that people found irritating was that a subscriber model was not supported, in so much as you have to consume the whole exchange/market.
I'm not sure what brokers people are using here, but if we assume IB I'm not sure what the point of optimizing feed latency so heavily is if you're going to send orders though TWS? Conversely, if you have co-located DMA, you're probably not worried about the price of feeds.
Interesting replies.
BTW - I tried to ask this question on the Quantitative Finance Stack Exchange site and the question was instantly down-voted and closed for being (paraphrasing) a 'stupid question'.
I've seen this used on this site a couple of times to quantify profitability, why do people use this measure as opposed to other well known performance measures? (Sharpe ratio etc).
If I have a zoo based time-series in R, is there a simple one-liner way of turning it into a percentage from the first observation?
e.g.
1,2,3,6 -> 0,100,50,100
I've examined some of the messaging from today, you seem to be correct, it's the second filled message, I'll use this rule and keep an eye on what happens.
It seems the only place to get the execution commission for an API order is in the 'order state' structure, the problem is, how do you know when the last 'order state' (which actually arrives as part of an 'open order' message) arrives? In my testing, I see a multiple 'filled' statuses with...
It seems the only place to get the execution commission for an API order is in the 'order state' structure, the problem is, how do you know when the last 'order state' (which actually arrives as part of an 'open order' message) arrives? In my testing, I see a multiple 'filled' statuses with...