Machine Learning for Trading Course

From Quantitative Analysis Software Courses
Jump to: navigation, search

Overview

This course introduces students to the real world challenges of implementing machine learning based trading strategies including the algorithmic steps from information gathering to market orders. The focus is on how to apply probabilistic machine learning approaches to trading decisions. We consider statistical approaches like linear regression, Q-Learning, KNN and regression trees and how to apply them to actual stock trading situations.

This course is composed of three mini-courses:

A set of course notes and example code can be found here: [[1]]

Video Content

The video content for this course is available for free at [Udacity].

Important note

This course ramps up in difficulty towards the end. The projects in the final 1/3 of the course are challenging. Be prepared.

Instructor information

Tucker Balch, Ph.D.
Professor, Interactive Computing at Georgia Tech
CS 7646 Course Designer
CS 7646 Instructor: Spring 2016, Fall 2016

David Byrd
Research Scientist, Interactive Media Technology Center at Georgia Tech
CS 7646 Instructor: Summer 2016
CS 7646 Head TA: Spring 2016, Fall 2016

Syllabi and schedule for specific semesters

Textbooks, Software & Other Resources

We will use the following textbooks:

  • For Mini-course 1: Python for Finance by Yves Hilpisch amazon.com (optional)
  • For Mini-course 2: What Hedge Funds Really Do by Romero and Balch amazon.com (required)
  • For Mini-course 3: Machine Learning by Tom Mitchell (optional)
    • Buy it for $218.00 at: amazon.com
    • Buy a paperback version for $61.78. IMPORTANT WARNINGS: 1) They only ship to the US 2) It takes them 3 weeks to print the book. If you order from outside the US they will quietly accept your money but never ship the book: less expensive version at mcgraw hill
    • Buy a paperback international version for $19.10. I am not certain about the reliability of this company: international

Software:

Other resources:

Prerequisites/Co-requisites

All types of students are welcome! The Machine Learning topics might be "review" for CS students, while finance parts will be review for finance students. However, even if you have experience in these topics, you will find that we consider them in a different way than you might have seen before, in particular with an eye towards implementation for trading.

If you answer "no" to the following questions, it may be beneficial to refresh your knowledge of the prerequisite material prior to taking CS 7646:

  • Do you have a working knowledge of basic statistics, including probability distributions (such as normal and uniform), calculation and differences between mean, median and mode
  • Do you understand the difference between geometric mean and arithmetic mean?
  • Do you have strong programming skills? Take this quiz compinvesti-prog-quiz if you would like help determining the strength of your programming skills.
  • Are you competent with the Unix command line?

Who this course is for: The course is intended for people with strong software programming experience and introductory level knowledge of investment practice. A primary prerequisite is an interest and excitement about the stock market.

Software we'll use: In order to complete the programming assignments you will need to a development environment that you're comfortable with. We use Unix, but you can also work with Windows and Mac OS environments. You must download and install a set of Python modules to your computer (including NumPy, SciPy, and Pandas).

How to install the software: ML4T Software Setup

Logistics

  • OMSCS: We will use Udacity for lecture videos.
  • If you have have trouble accessing Udacity content, please share your problem via email with gtech-support@udacity.com
  • We will use T-Square for ALL submissions: T-Square (pick appropriate course site)
  • We will use Piazza for interaction and discussion: Fall 2016 Piazza forum

Grading

  • A: 90.0% and above
  • B: 80.0% and above
  • C: 70.0% and above
  • D: 60.0% and above
  • F: below 60.0%

Students taking the course Pass/Fail must earn at least a 75% to pass.

The course may not be taken as "audit."

See semester syllabus for assignment weights.

Minimum technical requirements

  • Browser and connection speed: An up-to-date version of Chrome or Firefox is strongly recommended. We also support Internet Explorer 9 and the desktop versions of Internet Explorer 10 and above (not the metro versions). 2+ Mbps recommended; at minimum 0.768 Mbps download speed.
  • Hardware: A computer with at least 4GB of RAM and CPU speed of at least 2.5GHz.
  • For code development and testing, these three configurations will work
    • PC: Windows XP or higher with latest updates installed
    • Mac: OS X 10.6 or higher with latest updates installed
    • Linux: Any recent distribution that has the supported browsers installed
  • For online test taking (proctortrack) you will need one of:
    • PC: Windows XP or higher with latest updates installed
    • Mac: OS X 10.6 or higher with latest updates installed
    • Linux is NOT supported.

Office hours

To be determined.

Plagiarism

In most cases I expect that all submitted code will be written by you. I will present some libraries in class that you are allowed to use (such as pandas and numpy). Otherwise, all source code, images and write-ups you provide should have been created by you alone.

Class Policies

  • For Pass/Fail students: Your overall grade must be 75% or higher to get a passing grade.
  • Official communication is by email: We use piazza for discussions, but it is not an official communications channel. All official communications to you will be sent via t-square to your official GT email address. Similarly, you should communicate important items to us by email as well.
  • Student responsibilities: Be aware of the deadlines posted on the schedule. Read your GT email every day. Start work on projects even if they are not open on t-square.
  • Grade contest period: After a project grade is released you have 7 days to contest the grade. After that time projects will not be reevaluated. You must have a very specific issue with a compelling argument as to why your grade is incorrect. Example compelling argument: "The TA took 10 points off because I was missing a chart, but the chart is visible on page 5." Example not compelling argument: "I think I should have gotten more points, please regrade my project."
  • Grade contest process: Email your TA about the situation within 7 days of grades being released.
  • Late policy: Assignments are due at 11:55PM Eastern Time on the assignment due date. We do not use other timezones or GMT. Don't go by the time on your machine or by the time on some other way you have configured t-square. Assignments turned in after 11:55PM ET are considered late. Assignments may be turned in up to one day late with a 10% penalty. Assignments more than 24 hours late will not be accepted. There is no grace period for assignments already a full day late.
  • Exam scheduling: Exams will be held on specific days at specific times. If there is an emergency or other issue that requires changing the date of an exam for you, you will need to have it approved by the Dean of Students. You can apply for that here: http://www.deanofstudents.gatech.edu (under Resources -> Class Absences)
  • Each project for this course has it's own page on this wiki. That description includes a list of specific deliverables and usually a rubric. Be sure to double check your submission against those so you don't miss anything.
  • Many of the projects will be revised somewhat. While they are under revision, they will have a "DRAFT" note on the wiki. Once we're done with any revisions we will remove the "DRAFT" note and open submissions on t-square.
  • We require that your code run properly on one of the servers we have set up at GT. To assist you with this, and to furthermore help you test your code for each assignment we have equipped these servers with a server process that will run your code against a set of test cases.
  • The testing server will usually be running for each project one week before the due date.
  • If a problem crops up with your submitted code we will not consider reassessing it if it has not been tested as described above.
  • Once you are satisfied with your code, submit the EXACT same working code via t-square.
  • It is a good idea to submit a version of your working code early (before the deadline) in case some problem arises with your internet connection or t-square.
  • If you submit your code multiple times (perfectly fine) it is very important that you first delete the files that are there, then submit your new code. If you don't our grading software won't know which files to use.
  • The latest timestamp on any part of your submission will be used as the time of submission for your whole project. Accordingly, do not resubmit anything after the deadline, or it will be considered late.
  • After the submission deadline we will test your code on one of our servers which is configured identically to the ones available for your test.