Build Status
Coverage
License
PyPI
Docs
aat
is an asynchronous, event-driven framework for writing algorithmic trading strategies in python with optional acceleration in C++. It is designed to be modular and extensible, with support for a wide variety of instruments and strategies, live trading across (and between) multiple exchanges, fully integrated backtesting support, slippage and transaction cost modeling, and robust reporting and risk mitigation through manual and programatic algorithm controls.
Like Zipline and Lean, aat
exposes a single strategy class which is utilized for both live trading and backtesting. The strategy class is simple enough to write and test algorithms quickly, but extensible enough to allow for complex slippage and transaction cost modeling, as well as mid- and post- trade analysis.
aat
is in active use for live algorithmic trading on equities, commodity futures contracts, and commodity futures spreads by undisclosed funds.
Overview¶
A complete overview of the core components of aat
is provided in the GETTING_STARTED file.
Internals¶
aat
’s engine is composed of 4 major parts.
- trading engine
- risk management engine
- execution engine
- backtest engine
Trading Engine¶
The trading engine initializes all exchanges and strategies, then martials data, trade requests, and trade responses between the strategy, risk, execution, and exchange objects, while keeping track of high-level statistics on the system
Risk Management Engine¶
The risk management engine enforces trading limits, making sure that stategies are limited to certain risk profiles. It can modify or remove trade requests prior to execution depending on user preferences and outstanding positions and orders.
Execution engine¶
The execution engine is a simple passthrough to the underlying exchanges. It provides a unified interface for creating various types of orders.
Backtest engine¶
The backtest engine provides the ability to run the same stragegy offline against historical data.
Core Components¶
aat
has a variety of core classes and data structures, the most important of which are the Strategy
and Exchange
classes.
Trading Strategy¶
The core element of aat
is the trading strategy interface. It includes both data processing and order management functionality. Users subclass this class in order to implement their strategies. Methods of the form onNoun
are used to handle market data events, while methods of the form onVerb
are used to handle order entry events. There are also a variety of order management and data subscription methods available.
The only method that is required to be implemented is the onTrade
method. The full specification of a strategy is given in GETTING_STARTED.
Other Components¶
aat
also provides a complete limit-order book implementation, including flags like fill-or-kill
and all-or-nothing
, which is used to power the synthetic testing exchange.
Support / Contributors¶
Thanks to the following organizations for providing code or financial support.
API Documentation¶
Logging package for Python. Based on PEP 282 and comments thereto in comp.lang.python.
Copyright (C) 2001-2017 Vinay Sajip. All Rights Reserved.
To use, simply ‘import logging’ and log away!
-
class
logging.
BufferingFormatter
(linefmt=None)[source]¶ Bases:
object
A formatter suitable for formatting a number of records.
Return the footer string for the specified records.
-
class
logging.
FileHandler
(filename, mode='a', encoding=None, delay=False)[source]¶ Bases:
logging.StreamHandler
A handler class which writes formatted logging records to disk files.
-
class
logging.
Filter
(name='')[source]¶ Bases:
object
Filter instances are used to perform arbitrary filtering of LogRecords.
Loggers and Handlers can optionally use Filter instances to filter records as desired. The base filter class only allows events which are below a certain point in the logger hierarchy. For example, a filter initialized with “A.B” will allow events logged by loggers “A.B”, “A.B.C”, “A.B.C.D”, “A.B.D” etc. but not “A.BB”, “B.A.B” etc. If initialized with the empty string, all events are passed.
-
class
logging.
Formatter
(fmt=None, datefmt=None, style='%')[source]¶ Bases:
object
Formatter instances are used to convert a LogRecord to text.
Formatters need to know how a LogRecord is constructed. They are responsible for converting a LogRecord to (usually) a string which can be interpreted by either a human or an external system. The base Formatter allows a formatting string to be specified. If none is supplied, the the style-dependent default value, “%(message)s”, “{message}”, or “${message}”, is used.
The Formatter can be initialized with a format string which makes use of knowledge of the LogRecord attributes - e.g. the default value mentioned above makes use of the fact that the user’s message and arguments are pre- formatted into a LogRecord’s message attribute. Currently, the useful attributes in a LogRecord are described by:
%(name)s Name of the logger (logging channel) %(levelno)s Numeric logging level for the message (DEBUG, INFO,
WARNING, ERROR, CRITICAL)- %(levelname)s Text logging level for the message (“DEBUG”, “INFO”,
- “WARNING”, “ERROR”, “CRITICAL”)
- %(pathname)s Full pathname of the source file where the logging
- call was issued (if available)
%(filename)s Filename portion of pathname %(module)s Module (name portion of filename) %(lineno)d Source line number where the logging call was issued
(if available)%(funcName)s Function name %(created)f Time when the LogRecord was created (time.time()
return value)%(asctime)s Textual time when the LogRecord was created %(msecs)d Millisecond portion of the creation time %(relativeCreated)d Time in milliseconds when the LogRecord was created,
relative to the time the logging module was loaded (typically at application startup time)%(thread)d Thread ID (if available) %(threadName)s Thread name (if available) %(process)d Process ID (if available) %(message)s The result of record.getMessage(), computed just as
the record is emitted-
converter
()¶ - localtime([seconds]) -> (tm_year,tm_mon,tm_mday,tm_hour,tm_min,
- tm_sec,tm_wday,tm_yday,tm_isdst)
Convert seconds since the Epoch to a time tuple expressing local time. When ‘seconds’ is not passed in, convert the current time instead.
-
default_msec_format
= '%s,%03d'¶
-
default_time_format
= '%Y-%m-%d %H:%M:%S'¶
-
format
(record)[source]¶ Format the specified record as text.
The record’s attribute dictionary is used as the operand to a string formatting operation which yields the returned string. Before formatting the dictionary, a couple of preparatory steps are carried out. The message attribute of the record is computed using LogRecord.getMessage(). If the formatting string uses the time (as determined by a call to usesTime(), formatTime() is called to format the event time. If there is exception information, it is formatted using formatException() and appended to the message.
-
formatException
(ei)[source]¶ Format and return the specified exception information as a string.
This default implementation just uses traceback.print_exception()
-
formatStack
(stack_info)[source]¶ This method is provided as an extension point for specialized formatting of stack information.
The input data is a string as returned from a call to
traceback.print_stack()
, but with the last trailing newline removed.The base implementation just returns the value passed in.
-
formatTime
(record, datefmt=None)[source]¶ Return the creation time of the specified LogRecord as formatted text.
This method should be called from format() by a formatter which wants to make use of a formatted time. This method can be overridden in formatters to provide for any specific requirement, but the basic behaviour is as follows: if datefmt (a string) is specified, it is used with time.strftime() to format the creation time of the record. Otherwise, an ISO8601-like (or RFC 3339-like) format is used. The resulting string is returned. This function uses a user-configurable function to convert the creation time to a tuple. By default, time.localtime() is used; to change this for a particular formatter instance, set the ‘converter’ attribute to a function with the same signature as time.localtime() or time.gmtime(). To change it for all formatters, for example if you want all logging times to be shown in GMT, set the ‘converter’ attribute in the Formatter class.
-
class
logging.
Handler
(level=0)[source]¶ Bases:
logging.Filterer
Handler instances dispatch logging events to specific destinations.
The base handler class. Acts as a placeholder which defines the Handler interface. Handlers can optionally use Formatter instances to format records as desired. By default, no formatter is specified; in this case, the ‘raw’ message as determined by record.message is logged.
-
close
()[source]¶ Tidy up any resources used by the handler.
This version removes the handler from an internal map of handlers, _handlers, which is used for handler lookup by name. Subclasses should ensure that this gets called from overridden close() methods.
-
emit
(record)[source]¶ Do whatever it takes to actually log the specified logging record.
This version is intended to be implemented by subclasses and so raises a NotImplementedError.
-
flush
()[source]¶ Ensure all logging output has been flushed.
This version does nothing and is intended to be implemented by subclasses.
-
format
(record)[source]¶ Format the specified record.
If a formatter is set, use it. Otherwise, use the default formatter for the module.
-
handle
(record)[source]¶ Conditionally emit the specified logging record.
Emission depends on filters which may have been added to the handler. Wrap the actual emission of the record with acquisition/release of the I/O thread lock. Returns whether the filter passed the record for emission.
-
handleError
(record)[source]¶ Handle errors which occur during an emit() call.
This method should be called from handlers when an exception is encountered during an emit() call. If raiseExceptions is false, exceptions get silently ignored. This is what is mostly wanted for a logging system - most users will not care about errors in the logging system, they are more interested in application errors. You could, however, replace this with a custom handler if you wish. The record which was being processed is passed in to this method.
-
name
¶
-
-
class
logging.
LogRecord
(name, level, pathname, lineno, msg, args, exc_info, func=None, sinfo=None, **kwargs)[source]¶ Bases:
object
A LogRecord instance represents an event being logged.
LogRecord instances are created every time something is logged. They contain all the information pertinent to the event being logged. The main information passed in is in msg and args, which are combined using str(msg) % args to create the message field of the record. The record also includes information such as when the record was created, the source line where the logging call was made, and any exception information to be logged.
-
class
logging.
Logger
(name, level=0)[source]¶ Bases:
logging.Filterer
Instances of the Logger class represent a single logging channel. A “logging channel” indicates an area of an application. Exactly how an “area” is defined is up to the application developer. Since an application can have any number of areas, logging channels are identified by a unique string. Application areas can be nested (e.g. an area of “input processing” might include sub-areas “read CSV files”, “read XLS files” and “read Gnumeric files”). To cater for this natural nesting, channel names are organized into a namespace hierarchy where levels are separated by periods, much like the Java or Python package namespace. So in the instance given above, channel names might be “input” for the upper level, and “input.csv”, “input.xls” and “input.gnu” for the sub-levels. There is no arbitrary limit to the depth of nesting.
-
callHandlers
(record)[source]¶ Pass a record to all relevant handlers.
Loop through all handlers for this logger and its parents in the logger hierarchy. If no handler was found, output a one-off error message to sys.stderr. Stop searching up the hierarchy whenever a logger with the “propagate” attribute set to zero is found - that will be the last logger whose handlers are called.
-
critical
(msg, *args, **kwargs)[source]¶ Log ‘msg % args’ with severity ‘CRITICAL’.
To pass exception information, use the keyword argument exc_info with a true value, e.g.
logger.critical(“Houston, we have a %s”, “major disaster”, exc_info=1)
-
debug
(msg, *args, **kwargs)[source]¶ Log ‘msg % args’ with severity ‘DEBUG’.
To pass exception information, use the keyword argument exc_info with a true value, e.g.
logger.debug(“Houston, we have a %s”, “thorny problem”, exc_info=1)
-
error
(msg, *args, **kwargs)[source]¶ Log ‘msg % args’ with severity ‘ERROR’.
To pass exception information, use the keyword argument exc_info with a true value, e.g.
logger.error(“Houston, we have a %s”, “major problem”, exc_info=1)
-
exception
(msg, *args, exc_info=True, **kwargs)[source]¶ Convenience method for logging an ERROR with exception information.
-
fatal
(msg, *args, **kwargs)¶ Log ‘msg % args’ with severity ‘CRITICAL’.
To pass exception information, use the keyword argument exc_info with a true value, e.g.
logger.critical(“Houston, we have a %s”, “major disaster”, exc_info=1)
-
findCaller
(stack_info=False)[source]¶ Find the stack frame of the caller so that we can note the source file name, line number and function name.
-
getChild
(suffix)[source]¶ Get a logger which is a descendant to this one.
This is a convenience method, such that
logging.getLogger(‘abc’).getChild(‘def.ghi’)
is the same as
logging.getLogger(‘abc.def.ghi’)
It’s useful, for example, when the parent logger is named using __name__ rather than a literal string.
-
getEffectiveLevel
()[source]¶ Get the effective level for this logger.
Loop through this logger and its parents in the logger hierarchy, looking for a non-zero logging level. Return the first one found.
-
handle
(record)[source]¶ Call the handlers for the specified record.
This method is used for unpickled records received from a socket, as well as those created locally. Logger-level filtering is applied.
-
hasHandlers
()[source]¶ See if this logger has any handlers configured.
Loop through all handlers for this logger and its parents in the logger hierarchy. Return True if a handler was found, else False. Stop searching up the hierarchy whenever a logger with the “propagate” attribute set to zero is found - that will be the last logger which is checked for the existence of handlers.
-
info
(msg, *args, **kwargs)[source]¶ Log ‘msg % args’ with severity ‘INFO’.
To pass exception information, use the keyword argument exc_info with a true value, e.g.
logger.info(“Houston, we have a %s”, “interesting problem”, exc_info=1)
-
log
(level, msg, *args, **kwargs)[source]¶ Log ‘msg % args’ with the integer severity ‘level’.
To pass exception information, use the keyword argument exc_info with a true value, e.g.
logger.log(level, “We have a %s”, “mysterious problem”, exc_info=1)
-
makeRecord
(name, level, fn, lno, msg, args, exc_info, func=None, extra=None, sinfo=None)[source]¶ A factory method which can be overridden in subclasses to create specialized LogRecords.
-
manager
= <logging.Manager object>¶
-
root
= <RootLogger root (WARNING)>¶
-
-
class
logging.
LoggerAdapter
(logger, extra)[source]¶ Bases:
object
An adapter for loggers which makes it easier to specify contextual information in logging output.
-
exception
(msg, *args, exc_info=True, **kwargs)[source]¶ Delegate an exception call to the underlying logger.
-
log
(level, msg, *args, **kwargs)[source]¶ Delegate a log call to the underlying logger, after adding contextual information from this adapter instance.
-
manager
¶
-
name
¶
-
process
(msg, kwargs)[source]¶ Process the logging message and keyword arguments passed in to a logging call to insert contextual information. You can either manipulate the message itself, the keyword args or both. Return the message and kwargs modified (or not) to suit your needs.
Normally, you’ll only need to override this one method in a LoggerAdapter subclass for your specific needs.
-
-
class
logging.
NullHandler
(level=0)[source]¶ Bases:
logging.Handler
This handler does nothing. It’s intended to be used to avoid the “No handlers could be found for logger XXX” one-off warning. This is important for library code, which may contain code to log events. If a user of the library does not configure logging, the one-off warning might be produced; to avoid this, the library developer simply needs to instantiate a NullHandler and add it to the top-level logger of the library module or package.
-
class
logging.
StreamHandler
(stream=None)[source]¶ Bases:
logging.Handler
A handler class which writes logging records, appropriately formatted, to a stream. Note that this class does not close the stream, as sys.stdout or sys.stderr may be used.
-
emit
(record)[source]¶ Emit a record.
If a formatter is specified, it is used to format the record. The record is then written to the stream with a trailing newline. If exception information is present, it is formatted using traceback.print_exception and appended to the stream. If the stream has an ‘encoding’ attribute, it is used to determine how to do the output to the stream.
-
setStream
(stream)[source]¶ Sets the StreamHandler’s stream to the specified value, if it is different.
Returns the old stream, if the stream was changed, or None if it wasn’t.
-
terminator
= '\n'¶
-
-
logging.
addLevelName
(level, levelName)[source]¶ Associate ‘levelName’ with ‘level’.
This is used when converting levels to text during message formatting.
-
logging.
basicConfig
(**kwargs)[source]¶ Do basic configuration for the logging system.
This function does nothing if the root logger already has handlers configured. It is a convenience method intended for use by simple scripts to do one-shot configuration of the logging package.
The default behaviour is to create a StreamHandler which writes to sys.stderr, set a formatter using the BASIC_FORMAT format string, and add the handler to the root logger.
A number of optional keyword arguments may be specified, which can alter the default behaviour.
- filename Specifies that a FileHandler be created, using the specified
- filename, rather than a StreamHandler.
- filemode Specifies the mode to open the file, if filename is specified
- (if filemode is unspecified, it defaults to ‘a’).
format Use the specified format string for the handler. datefmt Use the specified date/time format. style If a format string is specified, use this to specify the
type of format string (possible values ‘%’, ‘{’, ‘$’, for %-formatting,str.format()
andstring.Template
- defaults to ‘%’).level Set the root logger level to the specified level. stream Use the specified stream to initialize the StreamHandler. Note
that this argument is incompatible with ‘filename’ - if both are present, ‘stream’ is ignored.- handlers If specified, this should be an iterable of already created
- handlers, which will be added to the root handler. Any handler in the list which does not have a formatter assigned will be assigned the formatter created in this function.
Note that you could specify a stream created using open(filename, mode) rather than passing the filename and mode in. However, it should be remembered that StreamHandler does not close its stream (since it may be using sys.stdout or sys.stderr), whereas FileHandler closes its stream when the handler is closed.
Changed in version 3.2: Added the
style
parameter.Changed in version 3.3: Added the
handlers
parameter. AValueError
is now thrown for incompatible arguments (e.g.handlers
specified together withfilename
/filemode
, orfilename
/filemode
specified together withstream
, orhandlers
specified together withstream
.
-
logging.
captureWarnings
(capture)[source]¶ If capture is true, redirect all warnings to the logging package. If capture is False, ensure that warnings are not redirected to logging but to their original destinations.
-
logging.
critical
(msg, *args, **kwargs)[source]¶ Log a message with severity ‘CRITICAL’ on the root logger. If the logger has no handlers, call basicConfig() to add a console handler with a pre-defined format.
-
logging.
debug
(msg, *args, **kwargs)[source]¶ Log a message with severity ‘DEBUG’ on the root logger. If the logger has no handlers, call basicConfig() to add a console handler with a pre-defined format.
-
logging.
error
(msg, *args, **kwargs)[source]¶ Log a message with severity ‘ERROR’ on the root logger. If the logger has no handlers, call basicConfig() to add a console handler with a pre-defined format.
-
logging.
exception
(msg, *args, exc_info=True, **kwargs)[source]¶ Log a message with severity ‘ERROR’ on the root logger, with exception information. If the logger has no handlers, basicConfig() is called to add a console handler with a pre-defined format.
-
logging.
fatal
(msg, *args, **kwargs)¶ Log a message with severity ‘CRITICAL’ on the root logger. If the logger has no handlers, call basicConfig() to add a console handler with a pre-defined format.
-
logging.
getLevelName
(level)[source]¶ Return the textual representation of logging level ‘level’.
If the level is one of the predefined levels (CRITICAL, ERROR, WARNING, INFO, DEBUG) then you get the corresponding string. If you have associated levels with names using addLevelName then the name you have associated with ‘level’ is returned.
If a numeric value corresponding to one of the defined levels is passed in, the corresponding string representation is returned.
Otherwise, the string “Level %s” % level is returned.
-
logging.
getLogger
(name=None)[source]¶ Return a logger with the specified name, creating it if necessary.
If no name is specified, return the root logger.
-
logging.
info
(msg, *args, **kwargs)[source]¶ Log a message with severity ‘INFO’ on the root logger. If the logger has no handlers, call basicConfig() to add a console handler with a pre-defined format.
-
logging.
log
(level, msg, *args, **kwargs)[source]¶ Log ‘msg % args’ with the integer severity ‘level’ on the root logger. If the logger has no handlers, call basicConfig() to add a console handler with a pre-defined format.
-
logging.
makeLogRecord
(dict)[source]¶ Make a LogRecord whose attributes are defined by the specified dictionary, This function is useful for converting a logging event received over a socket connection (which is sent as a dictionary) into a LogRecord instance.
-
logging.
setLoggerClass
(klass)[source]¶ Set the class to be used when instantiating a logger. The class should define __init__() such that only a name argument is required, and the __init__() should call Logger.__init__()
-
logging.
shutdown
(handlerList=[<weakref at 0x7f95f757e830; to '_StderrHandler'>, <weakref at 0x7f95f9628fb0; to 'NewLineStreamHandlerPY3'>, <weakref at 0x7f95f95c4050; to 'WarningStreamHandler'>, <weakref at 0x7f95f95c4110; to 'StreamHandler'>, <weakref at 0x7f95f46ef410; to 'NullHandler'>, <weakref at 0x7f95f46fa830; to 'StreamHandler'>, <weakref at 0x7f95f4706e90; to 'NullHandler'>, <weakref at 0x7f95f46fa110; to 'NullHandler'>, <weakref at 0x7f95f40fa950; to 'MemoryHandler'>])[source]¶ Perform any cleanup actions in the logging system (e.g. flushing buffers).
Should be called at application exit.
-
logging.
warning
(msg, *args, **kwargs)[source]¶ Log a message with severity ‘WARNING’ on the root logger. If the logger has no handlers, call basicConfig() to add a console handler with a pre-defined format.
-
logging.
getLogRecordFactory
()[source]¶ Return the factory to be used when instantiating a log record.
-
logging.
setLogRecordFactory
(factory)[source]¶ Set the factory to be used when instantiating a log record.
Parameters: factory – A callable which will be called to instantiate a log record.
This is an interface to Python’s internal parser.
-
exception
parser.
ParserError
¶ Bases:
Exception
-
parser.
STType
¶ alias of
parser.st
-
parser.
compilest
()¶ Compiles an ST object into a code object.
-
parser.
expr
()¶ Creates an ST object from an expression.
-
parser.
isexpr
()¶ Determines if an ST object was created from an expression.
-
parser.
issuite
()¶ Determines if an ST object was created from a suite.
-
parser.
sequence2st
()¶ Creates an ST object from a tree representation.
-
parser.
st2list
()¶ Creates a list-tree representation of an ST.
-
parser.
st2tuple
()¶ Creates a tuple-tree representation of an ST.
-
parser.
suite
()¶ Creates an ST object from a suite.
-
parser.
tuple2st
()¶ Creates an ST object from a tree representation.