Files
gocryptotrader/backtester/config/examples
Adam 08f1b5d5d3 rpcserver/exchanges: Add additional param checks plus other minor bugfixes/improvements (#652)
* deleting the unwanted file created during testing + adding more verbose errors for cli

* wip

* checking params throughout wip

* improving errors

* wip

* thrasher patch

* better err name

* whip

* testing and fixing errors WIP

* upgrades and better errors

* broken test

* wip

* adding some tests

* using tempDir

* mini improvement

* little changes

* better time check

* fixing error

* more glorious changes

* end of day wip

* shazzy changes

* checking error

* appveyor

* last changes:
2021-03-30 13:40:01 +11:00
..

GoCryptoTrader Backtester: Examples package

Build Status Software License GoDoc Coverage Status Go Report Card

This examples 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

Examples package overview

Current Config Examples:

Config Description
dollar-cost-average.strat A simple dollar cost average strategy which makes a purchase on every candle.
dollar-cost-average-live.strat Using the same dollar cost average strategy, but runs the analysis against live candles
dollar-cost-average-multi-currency-assessment.strat This strategy will assess multiple currencies in the one OnSignals function, however, it also just simply makes a purchase on every candle
dollar-cost-average-multiple-currencies.strat This runs the same strategy against multiple currencies independently
rsi.strat Runs a strategy using rsi figures to make buy or sell orders based on market figures

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