Files
gocryptotrader/backtester/config
Scott 197ef2df21 Feature: Data history manager engine subsystem (#693)
* Adds lovely initial concept for historical data doer

* Adds ability to save tasks. Adds config. Adds startStop to engine

* Has a database microservice without use of globals! Further infrastructure design. Adds readme

* Commentary to help design

* Adds migrations for database

* readme and adds database models

* Some modelling that doesn't work end of day

* Completes datahistoryjob sql.Begins datahistoryjobresult

* Adds datahistoryjob functions to retreive job results. Adapts subsystem

* Adds process for upserting jobs and job results to the database

* Broken end of day weird sqlboiler crap

* Fixes issue with SQL generation.

* RPC generation and addition of basic upsert command

* Renames types

* Adds rpc functions

* quick commit before context swithc. Exchanges aren't being populated

* Begin the tests!

* complete sql tests. stop failed jobs. CLI command creation

* Defines rpc commands

* Fleshes out RPC implementation

* Expands testing

* Expands testing, removes double remove

* Adds coverage of data history subsystem, expands errors and nil checks

* Minor logic improvement

* streamlines datahistory test setup

* End of day minor linting

* Lint, convert simplify, rpc expansion, type expansion, readme expansion

* Documentation update

* Renames for consistency

* Completes RPC server commands

* Fixes tests

* Speeds up testing by reducing unnecessary actions. Adds maxjobspercycle config

* Comments for everything

* Adds missing result string. checks interval supported. default start end cli

* Fixes ID problem. Improves binance trade fetch. job ranges are processed

* adds dbservice coverage. adds rpcserver coverage

* docs regen, uses dbcon interface, reverts binance, fixes races, toggle manager

* Speed up tests, remove bad global usage, fix uuid check

* Adds verbose. Updates docs. Fixes postgres

* Minor changes to logging and start stop

* Fixes postgres db tests, fixes postgres column typo

* Fixes old string typo,removes constraint,error parsing for nonreaders

* prevents dhm running when table doesn't exist. Adds prereq documentation

* Adds parallel, rmlines, err fix, comment fix, minor param fixes

* doc regen, common time range check and test updating

* Fixes job validation issues. Updates candle range checker.

* Ensures test cannot fail due to time.Now() shenanigans

* Fixes oopsie, adds documentation and a warn

* Fixes another time test, adjusts copy

* Drastically speeds up data history manager tests via function overrides

* Fixes summary bug and better logs

* Fixes local time test, fixes websocket tests

* removes defaults and comment,updates error messages,sets cli command args

* Fixes FTX trade processing

* Fixes issue where jobs got stuck if data wasn't returned but retrieval was successful

* Improves test speed. Simplifies trade verification SQL. Adds command help

* Fixes the oopsies

* Fixes use of query within transaction. Fixes trade err

* oopsie, not needed

* Adds missing data status. Properly ends job even when data is missing

* errors are more verbose and so have more words to describe them

* Doc regen for new status

* tiny test tinkering

* str := string("Removes .String()").String()

* Merge fixups

* Fixes a data race discovered during github actions

* Allows websocket test to pass consistently

* Fixes merge issue preventing datahistorymanager from starting via config

* Niterinos cmd defaults and explanations

* fixes default oopsie

* Fixes lack of nil protection

* Additional oopsie

* More detailed error for validating job exchange
2021-07-01 16:21:48 +10:00
..

GoCryptoTrader Backtester: Config package

Build Status Software License GoDoc Coverage Status Go Report Card

This config package is part of the GoCryptoTrader codebase.

This is still in active development

You can track ideas, planned features and what's in progress on this Trello board: https://trello.com/b/ZAhMhpOy/gocryptotrader.

Join our slack to discuss all things related to GoCryptoTrader! GoCryptoTrader Slack

Config package overview

What does the config package do?

The config package contains a set of structs which allow for the customisation of the GoCryptoTrader Backtester when running. The GoCryptoTrader Backtester runs from reading config files (.strat files by default under /examples).

What does Simultaneous Processing mean?

GoCryptoTrader Backtester config files may contain multiple ExchangeSettings which defined exchange, asset and currency pairs to iterate through a period of time.

If there are multiple entries to ExchangeSettings and SimultaneousProcessing is disabled, then each individual exchange, asset and currency pair candle event is evaluated individually and does not know about other exchange, asset and currency pair data events. It is a way to test a singular strategy against multiple assets simultaneously. But it isn't defined as Simultaneous Processing Simultaneous Signal Processing is a setting which allows multiple ExchangeSettings data events for a candle event to be considered simultaneously. This means that you can check if the price of BTC-USDT is 5% greater on Binance than it is on Kraken and choose to make signal a BUY event for Kraken and not Binance.

It allows for complex strategical decisions to be made when you consider the scope of the entire market at a given time, rather than in a vacuum when SimultaneousSignalProcessing is disabled.

How do I customise the GoCryptoTrader Backtester?

See below for a set of tables and fields, expected values and what they can do

Config

Key Description
Nickname A nickname for the specific config. When running multiple variants of the same strategy, use the nickname to help differentiate between runs
Goal A description of what you would hope the outcome to be. When verifying output, you can review and confirm whether the strategy met that goal
CurrencySettings Currency settings is an array of settings for each individual currency you wish to run the strategy against.
StrategySettings Select which strategy to run, what custom settings to load and whether the strategy can assess multiple currencies at once to make more in-depth decisions
PortfolioSettings Contains a list of global rules for the portfolio manager. CurrencySettings contain their own rules on things like how big a position is allowable, the portfolio manager rules are the same, but override any individual currency's settings
StatisticSettings Contains settings that impact statistics calculation. Such as the risk-free rate for the sharpe ratio
GoCryptoTraderConfigPath The filepath for the location of GoCryptoTrader's config path. The Backtester utilises settings from GoCryptoTrader. If unset, will utilise the default filepath via config.DefaultFilePath, implemented here

Currency Settings

Key Description Example
ExchangeName The exchange to load. See here for a list of supported exchanges Binance
Asset The asset type. Typically, this will be spot, however, see this package for the various asset types GoCryptoTrader supports spot
Base The base of a currency BTC
Quote The quote of a currency USDT
InitialFunds The funds that the GoCryptoTraderBacktester has for the specific currency 10000
Leverage This struct defines the leverage rules that this specific currency setting must abide by 1
BuySide This struct defines the buying side rules this specific currency setting must abide by such as maximum purchase amount -
SellSide This struct defines the selling side rules this specific currency setting must abide by such as maximum selling amount -
MinimumSlippagePercent Is the lower bounds in a random number generated that make purchases more expensive, or sell events less valuable. If this value is 90, then the most a price can be affected is 10% 90
MaximumSlippagePercent Is the upper bounds in a random number generated that make purchases more expensive, or sell events less valuable. If this value is 99, then the least a price can be affected is 1%. Set both upper and lower to 100 to have no randomness applied to purchase events 100
MakerFee The fee to use when sizing and purchasing currency 0.001
TakerFee Unused fee for when an order is placed in the orderbook, rather than taken from the orderbook 0.002
MaximumHoldingsRatio When multiple currency settings are used, you may set a maximum holdings ratio to prevent having too large a stake in a single currency 0.5

Strategy Settings

Key Description Example
Name The strategy to use. rsi
UsesSimultaneousProcessing This denotes whether multiple currencies are processed simultaneously with the strategy function OnSimultaneousSignals. Eg If you have multiple CurrencySettings and only wish to purchase BTC-USDT when XRP-DOGE is 1337, this setting is useful as you can analyse both signal events to output a purchase call for BTC. true
CustomSettings This is a map where you can enter custom settings for a strategy. The RSI strategy allows for customisation of the upper, lower and length variables to allow you to change them from 70, 30 and 14 respectively to 69, 36, 12 "custom-settings": { "rsi-high": 70, "rsi-low": 30, "rsi-period": 14 }

PortfolioSettings

Key Description
Leverage This struct defines the leverage rules that this specific currency setting must abide by
BuySide This struct defines the buying side rules this specific currency setting must abide by such as maximum purchase amount
SellSide This struct defines the selling side rules this specific currency setting must abide by such as maximum selling amount

StatisticsSettings

Key Description Example
RiskFreeRate The risk free rate used in the calculation of sharpe and sortino ratios 0.03

APIData

Key Description Example
DataType Choose whether candle or trade data is used. If trades are used, they will be converted to candles trade
Interval The candle interval in time.Duration format eg set as15000000000 for a value of time.Second * 15 15000000000
StartDate The start date to retrieve data 2021-01-23T11:00:00+11:00
EndDate The end date to retrieve data 2021-01-24T11:00:00+11:00
InclusiveEndDate When enabled, the end date's candle is included in the results. ie 2021-01-24T11:00:00+11:00 with a one hour candle, the final candle will be 2021-01-24T11:00:00+11:00 to 2021-01-24T12:00:00+11:00 false

CSVData

Key Description Example
DataType Choose whether candle or trade data is used. If trades are used, they will be converted to candles candle
Interval The candle interval in time.Duration format eg set as15000000000 for a value of time.Second * 15 15000000000
FullPath The file to load /data/exchangelist.csv

DatabaseData

Key Description Example
DataType Choose whether candle or trade data is used. If trades are used, they will be converted to candles trade
Interval The candle interval in time.Duration format eg set as15000000000 for a value of time.Second * 15 15000000000
StartDate The start date to retrieve data 2021-01-23T11:00:00+11:00
EndDate The end date to retrieve data 2021-01-24T11:00:00+11:00
ConfigOverride Override GoCryptoTrader's config database data with custom settings true
InclusiveEndDate When enabled, the end date's candle is included in the results. ie 2021-01-24T11:00:00+11:00 with a one hour candle, the final candle will be 2021-01-24T11:00:00+11:00 to 2021-01-24T12:00:00+11:00 false

LiveData

Key Description Example
DataType Choose whether candle or trade data is used. If trades are used, they will be converted to candles candle
Interval The candle interval in time.Duration format eg set as15000000000 for a value of time.Second * 15 15000000000
APIKeyOverride Will set the GoCryptoTrader exchange to use the following API Key 1234
APISecretOverride Will set the GoCryptoTrader exchange to use the following API Secret 5678
APIClientIDOverride Will set the GoCryptoTrader exchange to use the following API Client ID 9012
API2FAOverride Will set the GoCryptoTrader exchange to use the following 2FA seed hello-moto
APISubaccountOverride Will set the GoCryptoTrader exchange to use the following subaccount on supported exchanges subzero
RealOrders Whether to place real orders. You really should never consider using this. Ever ever. true
Leverage Settings
Key Description Example
CanUseLeverage Allows the use of leverage false
MaximumOrdersWithLeverageRatio If the ratio of leveraged orders for a currency exceeds this, the order cannot be placed 0.5
MaximumLeverageRate Orders cannot be placed with leverage over this amount 100
Buy/Sell Settings
Key Description Example
MinimumSize If the order's quantity is below this, the order cannot be placed 0.1
MaximumSize If the order's quantity is over this amount, it cannot be placed and will be reduced to the maximum amount 10
MaximumTotal If the order's price * amount exceeds this number, the order cannot be placed and will be reduced to this figure 1337

Please click GoDocs chevron above to view current GoDoc information for this package

Contribution

Please feel free to submit any pull requests or suggest any desired features to be added.

When submitting a PR, please abide by our coding guidelines:

  • Code must adhere to the official Go formatting guidelines (i.e. uses gofmt).
  • Code must be documented adhering to the official Go commentary guidelines.
  • Code must adhere to our coding style.
  • Pull requests need to be based on and opened against the master branch.

Donations

If this framework helped you in any way, or you would like to support the developers working on it, please donate Bitcoin to:

bc1qk0jareu4jytc0cfrhr5wgshsq8282awpavfahc