In this notebook, we'll take a look at EventVestor's 13D Filings dataset, available on the Quantopian Store. This dataset spans January 01, 2007 through the current day, and documents 13D filings with the SEC by activist shareholders disclosing a beneficial ownership of 5% or more.
There are two ways to access the data and you'll find both of them listed below. Just click on the section you'd like to read through.
One key caveat: we limit the number of results returned from any given expression to 10,000 to protect against runaway memory usage. To be clear, you have access to all the data server side. We are limiting the size of the responses back from Blaze.
There is a free version of this dataset as well as a paid one. The free sample includes data until 2 months prior to the current date.
To access the most up-to-date values for this data set for trading a live algorithm (as with other partner sets), you need to purchase acess to the full set.
With preamble in place, let's get started:
Partner datasets are available on Quantopian Research through an API service known as Blaze. Blaze provides the Quantopian user with a convenient interface to access very large datasets, in an interactive, generic manner.
Blaze provides an important function for accessing these datasets. Some of these sets are many millions of records. Bringing that data directly into Quantopian Research directly just is not viable. So Blaze allows us to provide a simple querying interface and shift the burden over to the server side.
It is common to use Blaze to reduce your dataset in size, convert it over to Pandas and then to use Pandas for further computation, manipulation and visualization.
Helpful links:
Once you've limited the size of your Blaze object, you can convert it to a Pandas DataFrames using:
from odo import odo
odo(expr, pandas.DataFrame)
Pipeline Overview section of this notebook or head straight to Pipeline Overview
In [3]:
# import the dataset
# from quantopian.interactive.data.eventvestor import _13d_filings as dataset
# or if you want to import the free dataset, use:
from quantopian.interactive.data.eventvestor import _13d_filings_free as dataset
# import data operations
from odo import odo
# import other libraries we will use
import pandas as pd
In [4]:
# Let's use blaze to understand the data a bit using Blaze dshape()
dataset.dshape
Out[4]:
In [6]:
# And how many rows are there?
# N.B. we're using a Blaze function to do this, not len()
dataset.count()
Out[6]:
In [7]:
# Let's see what the data looks like. We'll grab the first three rows.
dataset[:3]
Out[7]:
Let's go over the columns:
percent_shares with market cap (from Fundamentals) to get the total value of shares owned, and dividing by the close_price (from price data) to get the number of shares.We've done much of the data processing for you. Fields like timestamp and sid are standardized across all our Store Datasets, so the datasets are easy to combine. We have standardized the sid across all our equity databases.
We can select columns and rows with ease. Below, we'll fetch all 13D filings by Carl Icahn.
In [9]:
# first we find how Icahn is represented exactly in the `acquiring_entity` column
icahns = set(filter(lambda x: "Icahn" in x, dataset.acquiring_entity))
icahns
Out[9]:
In [10]:
# Since Carl Icahn is represented in several ways, we use `like` to capture all those ways
names = dataset[dataset.acquiring_entity.like("*Icahn*")]
# now let's filter down to the percentage of shares, timestamp, and sid
names = names[['timestamp', 'percent_shares', 'sid', 'acquiring_entity']]
# # When displaying a Blaze Data Object, the printout is automatically truncated to ten rows.
names.sort('timestamp')
Out[10]:
Finally, suppose we want a DataFrame of all 13D Filings in June 2013:
In [13]:
# we can call odo on the entire dataset
filings_df = odo(dataset, pd.DataFrame)
june = filings_df[(filings_df.timestamp < '2013-07-01') & ('2013-05-31'< filings_df.timestamp)]
june
Out[13]:
The only method for accessing partner data within algorithms running on Quantopian is via the pipeline API. Different data sets work differently but in the case of this data, you can add this data to your pipeline as follows:
Import the data set here
from quantopian.pipeline.data.eventvestor import _13DFilings
Then in intialize() you could do something simple like adding the raw value of one of the fields to your pipeline:
pipe.add(_13DFilings.disclosure_date.latest, 'disclosure_date')
Pipeline usage is very similar between the backtester and Research so let's go over how to import this data through pipeline and view its outputs.
In [14]:
# Import necessary Pipeline modules
from quantopian.pipeline import Pipeline
from quantopian.research import run_pipeline
from quantopian.pipeline.factors import AverageDollarVolume
In [15]:
# Import the datasets available
from quantopian.pipeline.data.eventvestor import _13DFilings
# Builtin Factors for easy access
from quantopian.pipeline.factors.eventvestor import BusinessDaysSince13DFilingsDate
Now that we've imported the data, let's take a look at which fields are available for each dataset.
You'll find the dataset, the available fields, and the datatypes for each of those fields.
In [70]:
print "Here are the list of available fields per dataset:"
print "---------------------------------------------------\n"
def _print_fields(dataset):
print "Dataset: %s\n" % dataset.__name__
print "Fields:"
for field in list(dataset.columns):
print "%s - %s" % (field.name, field.dtype)
print "\n"
_print_fields(_13DFilings)
print "---------------------------------------------------\n"
Now that we know what fields we have access to, let's see what this data looks like when we run it through Pipeline.
This is constructed the same way as you would in the backtester. For more information on using Pipeline in Research view this thread: https://www.quantopian.com/posts/pipeline-in-research-build-test-and-visualize-your-factors-and-filters
In [65]:
pipe = Pipeline()
pipe.add(_13DFilings.disclosure_date.latest, "last_disclosure_date")
pipe.add(_13DFilings.percent_shares.latest, "percent_shares")
pipe.add(_13DFilings.number_shares.latest, "number_shares")
pipe.add(BusinessDaysSince13DFilingsDate(), "business_days_since_last_filing")
In [66]:
# Setting some basic liquidity strings (just for good habit)
dollar_volume = AverageDollarVolume(window_length=20)
top_1000_most_liquid = dollar_volume.rank(ascending=False) < 1000
pipe.set_screen(top_1000_most_liquid & BusinessDaysSince13DFilingsDate().notnan())
In [67]:
# The show_graph() method of pipeline objects produces a graph to show how it is being calculated.
pipe.show_graph(format='png')
Out[67]:
In [68]:
# run_pipeline will show the output of your pipeline
pipe_output = run_pipeline(pipe, start_date='2013-11-01', end_date='2013-11-25')
pipe_output
Out[68]:
Taking what we've seen from above, let's see how we'd move that into the backtester.
In [75]:
# This section is only importable in the backtester
from quantopian.algorithm import attach_pipeline, pipeline_output
# General pipeline imports
from quantopian.pipeline import Pipeline
from quantopian.pipeline.factors import AverageDollarVolume
# Import the datasets available
from quantopian.pipeline.data.eventvestor import _13DFilings
# Builtin Factors for easy access
from quantopian.pipeline.factors.eventvestor import BusinessDaysSince13DFilingsDate
def make_pipeline():
# Create our pipeline
pipe = Pipeline()
# Screen out penny stocks and low liquidity securities.
dollar_volume = AverageDollarVolume(window_length=20)
is_liquid = dollar_volume.rank(ascending=False) < 1000
# Create the mask that we will use for our percentile methods.
base_universe = (is_liquid)
# Add pipeline factors
pipe.add(_13DFilings.disclosure_date.latest, "last_disclosure_date")
pipe.add(_13DFilings.percent_shares.latest, "percent_shares")
pipe.add(_13DFilings.number_shares.latest, "number_shares")
pipe.add(BusinessDaysSince13DFilingsDate(), "business_days_since_last_filing")
# Set our pipeline screens
pipe.set_screen(is_liquid)
return pipe
def initialize(context):
attach_pipeline(make_pipeline(), "pipeline")
def before_trading_start(context, data):
results = pipeline_output('pipeline')
Now you can take that and begin to use it as a building block for your algorithms, for more examples on how to do that you can visit our data pipeline factor library