There are lots of reasons to for me to write about the technology we will use for CondorGP. So here goes, first pass. Bear in mind that this is as I see it now, and it’ll likely change.
Genetic Programming is the fundamental, underpinning technology application. I’ll write seperately about Genetic Programming in another post. Here I want to describe the technology stack the project is currently using.
Refresh on what CondorGP is
First, let’s start with a little of what the CondorGP project is. You can also, see the CondorGP aims, to refresh. They are high level, but give a picture. CondorGP looks to use Genetic Programming to build an automated trading system.
What technology CondorGP uses
Here I will attempt to write simply and clearly, so that each technology is identified with a clear utility, to explain why each technology is used. In brackets is the current status of usage, today, e.g. (in use).
I’ll work from output down, from trading on the financial markets ‘downwards’.
- Interactive Brokers – a trading platform that will provide paper and real trading on financial markets (planned)
- Amibroker – a trading analysis tool, that provides data and allows testing of potential trading systems we have evolved (in use) NB. Headline image for this post is an Amibroker screenshot from amibroker.com, and not the way CondorGP will use Amibroker…
- Amazon Web Services or AWS – a massive cloud services platform, that allows processing of our genetic programming evolution and everything else (in use, nascent)
- Bit Bucket – Atlassian’s git code management platform, that provides pipelines for code to be tested, deployed and uplinked to AWS (in use)
- Git – distributed version control for software, allows sharing and co-working by teams on software projects (in use)
- Egit for the free Eclipse IDE (both in use)
- Jbehave – software project that enables BDD or Behaviour Driven Development to allow easy and accessible tests to be written and run (in use)
- Junit – to run the tests (in use, currently Junit 4)
- Maven – Apache’s method for control software project libraries, called dependencies (in use, via Eclipse’s Maven plugin)
- ECJ – the Evolutionary Computation in Java package, from George Mason University, that provides a powerful and wide ranging list of evolutionary capabilites (in use, version 22 from the maven repository)
- Jacob – the Java com bridge, currently limits the project to Jave version 8, see below. This enables Java to run Amibroker in Windows (in use)
- AWS toolkit for Eclipse – AWS integration for Eclipse, to help run AWS from the Java IDE (in use)
- Spring – the software development framework from Pivotal, to help with dependency injection and other coding paradigms (in use, 2.0.1.RELEASE)
- Java – the object-oriented software language that ECJ is written in, that we use to run ECJ, and write our tests, run AWS etc (in use, currently JDK 8u211 and JRE 8)