I’m currently working with stock market trade data that is output from a backtesting engine (I’m working with backtrader currently) in a pandas dataframe. The format of the ‘transcations’ data that is provided out of the backtesting engine is shown below.
The data provided gives four crucial pieces of information:
Date – The date of a transaction.
Amount – the number of shares purchased (positive number) or sold (negative number) during the transaction.
Price – the price received or paid at the time of the sale.
Value – the cash value of the transaction.
Backtrader’s transactions dataframe is comprised of two rows make for one one transaction (the first is the ‘buy’ the second is the ‘sell). For example, in the data above, the first two rows (Jan 7 2016 and Sept 7th 2016) are the ‘buy’ data and ‘sell’ data for one transaction. What I need to do with this data is transform it (using that term loosely) into one row of data for each transaction to store into database for use in another analysis.
I could leave it in its current form, but I prefer to store transactions in one row when dealing with market backtests.
There are a few ways to attack this particular problem. You could iterate over the dataframe and manually pick each row. That would be pretty straightforward, but not necessarily the best way.
While looking around the web for some pointers, I stumbled across this answer that does exactly what I need to do. I added the following code to my script and — voila — I have my transactions transformed from two rows per transaction to one row.
Note: In the above, I only want to build rows that start with a positive amount in the ‘amount’ column because amount in the first row of a transactions is always positive. I then append each transformed transaction into an array to be used for more analysis down at a later point in the script.
In a recent post titled Working with Large CSV files in Python, I shared an approach I use when I have very large CSV files (and other file types) that are too large to load into memory. While the approach I previously highlighted works well, it can be tedious to first load data into sqllite (or any other database) and then access that database to analyze data. I just found a better approach using Dask.
While looking around the web to learn about some parallel processing capabilities, I ran across a python module named Dask, which describes itself as:
…is a flexible parallel computing library for analytic computing.
When I saw that, I was intrigued. There’s a lot that can be done with that statement and I’ve got plans to introduce Dask into my various tool sets for data analytics.
While reading the docs, I ran across the ‘dataframe‘ concept and immediately new I’d found a new tool for working with large CSV files. With Dask’s dataframe concept, you can do out-of-core analysis (e.g., analyze data in the CSV without loading the entire CSV file into memory). Other than out-of-core manipulation, dask’s dataframe uses the pandas API, which makes things extremely easy for those of us who use and love pandas.
With Dask and its dataframe construct, you set up the dataframe must like you would in pandas but rather than loading the data into pandas, this appraoch keeps the dataframe as a sort of ‘pointer’ to the data file and doesn’t load anything until you specifically tell it to do so.
One note (that I always have to share): If you are planning on working with your data set over time, its probably best to get the data into a database of some type.
An example using Dask and the Dataframe
First, let’s get everything installed. The documentation claims that you just need to install dask, but I had to install ‘toolz’ and ‘cloudpickle’ to get dask’s dataframe to import. To install dask and its requirements, open a terminal and type (you need pip for this):
pip install dask[complete]
NOTE: I mistakenly had “pip install dask” listed initially. This only installs the base dask system and not the dataframe (and other dependancies). Thanks to Kevin for pointing this out.
Set up your dataframe so you can analyze the 311_Service_Requests.csv file. This file is assumed to be stored in the directory that you are working in.
import dask.dataframe asdd
Unlike pandas, the data isn’t read into memory…we’ve just set up the dataframe to be ready to do some compute functions on the data in the csv file using familiar functions from pandas. Note: I used “dtype=’str'” in the read_csv to get around some strange formatting issues in this particular file.
Let’s take a look at the first few rows of the file using pandas’ head() call. When you run this, the first X rows (however many rows you are looking at with head(X)) and then displays those rows.
Note: a small subset of the columns are shown below for simplicity
05/09/2013 12:00:00 AM
05/14/2013 12:00:00 AM
05/09/2013 12:00:00 AM
05/13/2013 12:00:00 AM
05/09/2013 12:00:00 AM
05/22/2013 12:00:00 AM
05/09/2013 12:00:00 AM
05/12/2013 12:00:00 AM
05/09/2013 12:00:00 AM
05/11/2013 12:00:00 AM
We see that there’s some spaces in the column names. Let’s remove those spaces to make things easier to work with.
The cool thing about dask is that you can do things like renaming columns without loading all the data into memory.
There’s a column in this data called ‘Descriptor’ that has the problem types, and “radiator” is one of those problem types. Let’s take a look at how many service requests were because of some problem with a radiator. To do this, you can filter the dataframe using standard pandas filtering (see below) to create a new dataframe.
# create a new dataframe with only 'RADIATOR' service calls
Let’s see how many rows we have using the ‘count’ command
You’ll notice that when you run the above command, you don’t actually get count returned. You get a descriptor back similar like “dd.Scalar<series-…, dtype=int64>”
To actually compute the count, you have to call “compute” to get dask to run through the dataframe and count the number of records.
When you run this command, you should get something like the following
The above are just some samples for using dask’s dataframe construct. Remember, we built a new dataframe using pandas’ filters without loading the entire original data set into memory. They may not seem like much, but when working with a 7Gb+ file, you can save a great deal of time and effort using dask when compared to using the approach I previously mentioned.
Dask seems to have a ton of other great features that I’ll be diving into at some point in the near future, but for now, the dataframe construct has been an awesome find.
I’m currently working on a project that has multiple very large CSV files (6 gigabytes+). Normally when working with CSV data, I read the data in using pandas and then start munging and analyzing the data. With files this large, reading the data into pandas directly can be difficult (or impossible) due to memory constrictions, especially if you’re working on a prosumer computer. In this post, I describe a method that will help you when working with large CSV files in python.
While it would be pretty straightforward to load the data from these CSV files into a database, there might be times when you don’t have access to a database server and/or you don’t want to go through the hassle of setting up a server. If you are going to be working on a data set long-term, you absolutely should load that data into a database of some type (mySQL, postgreSQL, etc) but if you just need to do some quick checks / tests / analysis of the data, below is one way to get a look at the data in these large files with python, pandas and sqllite.
To get started, you’ll need to import pandas and sqlalchemy. The commands below will do that.
import pandas aspd
from sqlalchemy import create_engine
Next, set up a variable that points to your csv file. This isn’t necessary but it does help in re-usability.
With these three lines of code, we are ready to start analyzing our data. Let’s take a look at the ‘head’ of the csv file to see what the contents might look like.
This command uses pandas’ “read_csv” command to read in only 5 rows (nrows=5) and then print those rows to the screen. This lets you understand the structure of the csv file and make sure the data is formatted in a way that makes sense for your work.
Before we can actually work with the data, we need to do something with it so we can begin to filter it to work with subsets of the data. This is usually what I would use pandas’ dataframe for but with large data files, we need to store the data somewhere else. In this case, we’ll set up a local sqllite database, read the csv file in chunks and then write those chunks to sqllite.
To do this, we’ll first need to create the sqllite database using the following command.
With this code, we are setting the chunksize at 100,000 to keep the size of the chunks managable, initializing a couple of iterators (i=0, j=0) and then running through a for loop. The for loop reads a chunk of data from the CSV file, removes spaces from any of column names, then stores the chunk into the sqllite database (df.to_sql(…)).
This might take a while if your CSV file is sufficiently large, but the time spent waiting is worth it because you can now use pandas ‘sql’ tools to pull data from the database without worrying about memory constraints.
To access the data now, you can run commands like the following:
df=pd.read_sql_query('SELECT * FROM table',csv_database)
Of course, using ‘select *…’ will load all data into memory, which is the problem we are trying to get away from so you should throw from filters into your select statements to filter the data. For example:
df=pd.read_sql_query('SELECT COl1, COL2 FROM table where COL1 = SOMEVALUE',csv_database)