Project 5: Marketsim

Due Date

06/28/2020 11:59PM Anywhere on Earth time

Revisions

This assignment is subject to change up until 3 weeks prior to the due date. We do not anticipate changes; any changes will be logged in this section.

Overview

In this project you will create a market simulator that accepts trading orders and keeps track of a portfolio’s value over time and then assesses the performance of that portfolio.

Template

Instructions:

• Download the appropriate zip file File:Marketsim_2020Summer.zip
• Implement the compute_portvals() function in the file marketsim/marketsim.py.
• The grading script is marketsim/grade_marketsim.py. For more details see here: ML4T_Software_Setup#Running_the_grading_scripts

Tasks

Part 1: Basic simulator (90 points)

Your job is to implement your market simulator as a function, compute_portvals() that returns a dataframe with one column. You should implement it within the file marketsim.py. It should adhere to the following API:

The start date and end date of the simulation are the first and last dates with orders in the orders_file. The arguments are as follows:

• orders_file is the name of a file from which to read orders, and
• start_val is the starting value of the portfolio (initial cash available)
• commission is the fixed amount in dollars charged for each transaction (both entry and exit)
• impact is the amount the price moves against the trader compared to the historical data at each transaction

Return the result (portvals) as a single-column pandas.DataFrame (column name does not matter), containing the value of the portfolio for each trading day in the first column from start_date to end_date, inclusive.

The files containing orders are CSV files with the following columns:

• Date (yyyy-mm-dd)
• Symbol (e.g. AAPL, GOOG)
• Order (BUY or SELL)
• Shares (no. of shares to trade)

For example:

Your simulator should calculate the total value of the portfolio for each day using adjusted closing prices. The value for each day is cash plus the current value of equities. The resulting data frame should contain values like this:

How It Should Work

Your code should keep account of how many shares of each stock are in the portfolio on each day and how much cash is available on each day. Note that negative shares and negative cash are possible. Negative shares mean that the portfolio is in a short position for that stock. Negative cash means that you’ve borrowed money from the broker.

When a BUY order occurs, you should add the appropriate number of shares to the count for that stock and subtract the appropriate cost of the shares from the cash account. The cost should be determined using the adjusted close price for that stock on that day.

When a SELL order occurs, it works in reverse: You should subtract the number of shares from the count and add to the cash account.

Evaluation

We will evaluate your code by calling compute_portvals() with multiple test cases. No other function in your code will be called by us, so do not depend on “main” code being called. Do not depend on global variables.

For debugging purposes, you should write your own additional helper function to call compute_portvals() with your own test cases. We suggest that you report the following factors:

• Plot the price history over the trading period.
• Sharpe ratio (Always assume you have 252 trading days in an year. And risk free rate = 0) of the total portfolio
• Cumulative return of the total portfolio
• Standard deviation of daily returns of the total portfolio
• Average daily return of the total portfolio
• Ending value of the portfolio

Part 2: Transaction Costs (10 points)

Note: We strongly encourage you to get the basic simulator working before you implement the transaction cost and market impact components of this project. Ok, now on to transaction costs.

Transaction costs are an important consideration for investing strategy. Transaction costs include things like commissions, slippage, market impact and tax considerations. High transaction costs encourage less frequent trading, and accordingly a search for strategies that pay out over longer periods of time rather than just intraday or over several days. For this project we will consider two components of transaction cost: Commissions and market impact:

• Commissions: For each trade that you execute, charge a commission according to the parameter sent. Treat that as a deduction from your cash balance.
• Market impact: For each trade that you execute, assume that the stock price moves against you according to the impact parameter. So if you are buying, assume the price goes up before your purchase. Similarly, if selling, assume the price drops 50 bps before the sale. For simplicity treat the market impact penalty as a deduction from your cash balance.

Both of these penalties should be applied for EACH transaction, for instance, depending on the parameter settings, a complete entry and exit will cost 2 * $9.95, plus 0.5% of the entry price and 0.5% of the exit price.

Part 3: Implement author() function (deduction if not implemented)

You should implement a function called author() that returns your Georgia Tech user ID as a string. This is the ID you use to log into Canvas. It is not your 9 digit student number. Here is an example of how you might implement author():

And here’s an example of how it could be called from a testing program:

Check the template code for examples. We are adding those to the repo now, but it might not be there if you check right away. Implementing this method correctly does not provide any points, but there will be a penalty for not implementing it.

Example Tests/Checks

Orders File Code Check Examples

Example orders files are available in the orders subdirectory.

Here are some additional test cases:

• testcases_mc2p1.zip
• additional_orders.zip

Short Code Check Example

Here is a very very short example that you can use to check your code. Starting conditions:

For the orders file orders-short.csv, the orders are:

The daily value of the portfolio (spaces added to help things line up):

For reference, here are the adjusted close values for AAPL on the relevant days:

The full results:

More Comprehensive Examples

orders.csv

We provide an example, orders.csv that you can use to test your code, and compare with others. All of these runs assume a starting portfolio of 1000000 ($1M).

orders2.csv

The other sample file is orders2.csv that you can use to test your code, and compare with others.

Hints & Resources

Here is a video outlining an approach to solving this problem [youtube video].

Hint, use code like this to read in the orders file:

In terms of execution prices, you should assume you get the adjusted close price for the day of the trade.

What To Turn In

Be sure to follow these instructions diligently!

Via Canvas, submit as attachment (no zip files; refer to schedule for deadline):

• Project 5: Marketsim
  • Your code as marketsim.py (only the function compute_portvals() will be tested)

Unlimited resubmissions are allowed up to the deadline for the project.

Rubric

Report

No report

Code

See auto-grader

Auto-Grader

Out of a total of 100 points:

• Basic simulator: 90 points: 10 test cases: We will test your code against 10 cases (9 points per case) without transaction costs. Points per case are allocated as follows:
  • 2.0: Correct number of days reported in the dataframe (should be the number of trading days between the start date and end date, inclusive).
  • 5.0: Correct portfolio value on the last day +-0.1%
  • 1.0: Correct Sharpe Ratio +-0.1%
  • 1.0: Correct average daily return +-0.1%
• Transaction costs: 10 points: 5 test cases: We will test your code against 5 cases as follows:
  • 2.0: Two test cases that evaluate commissions only (impact = 0)
  • 2.0: Two test cases that evaluate impact only (commission = 0)
  • 1.0: One test case with non-zero commission and impact.

Legacy Test Cases

Here are the test cases we used while grading. These are updated each semester but can be used as additional checks.

• MC2-Project-1-Test-Cases-spr2016

Required, Allowed & Prohibited

Required

• Your project must be coded in Python 3.6.x.
• Your code must run on one of the university-provided computers (e.g. buffet0.cc.gatech.edu).
• When utilizing any of the example orders files code must run in less than 10 seconds on one of the university-provided computers.
• To read in stock data, use only the functions in util.py. Only use the API methods provided here. Do NOT modify this file. For grading, we will use our own unmodified version.

Allowed

• You can develop your code on your personal machine, but it must also run successfully on one of the university provided machines or virtual images.
• Your code may use standard Python libraries.
• Unladen African swallows.
• You may use the NumPy, SciPy, matplotlib and Pandas libraries. Be sure you are using the correct versions.
• Code provided by the instructor, or allowed by the instructor to be shared.
• To read in orders files pandas.read_csv() is allowed.

Prohibited

• Global variables.
• Reading in data by any means other than the API functions in util.py or pandas.read_csv()
• Any libraries or modules not listed in the “allowed” section above.
• Any code you did not write yourself.
• Code that takes longer than 10 seconds to run.
• Any Classes (other than Random) that create their own instance variables for later use (e.g., learners like kdtree).

FAQ

• Q: How can I be sure that my function is returning a DataFrame?
  A: Check the type of the returned item foo with type(foo)

• Q: Do we have to reject the order if the stock is not trading on that day?
  A: You should fill orders for any day the market is open, and reject orders for any day the market is closed. Suggested operation: Drop days when the market is not open (check by looking at SPY), fill forward, then fill back.

• Q: Is it true that the orders might not be in order in the csv?
  A: Yes.

• Q: Are we supposed to sort the date column after?
  A: Yes.

• Q: If we were to sort, we can assume that multiple orders on the same date won’t have any side-effect if they are executed in random orders?
  A: Yes.

• Q: Should we assume the prices stay the same the whole day?
  A: Assume execution prices are adjusted close.

• Q: Do we return portvals daily for the entire periods including weekends, holidays and non-trading days?
  A: Only consider trading days. This should happen for you automatically when using get_data() from util.py

• Q: It seems like my avg_daily_returns and std are off compared to the wiki’s because of this. If not, do we count trading days only for when list of symbols (or SPY) are traded
  A: Assume the market was open iff SPY was traded.

• Q: Is it okay to have NaNs in the final portfolio values that the function outputs?
  A: No, you should have a real number value for every date in the final portfolio value.