mirror of https://github.com/d0zingcat/gocryptotrader.git synced 2026-05-19 07:26:49 +00:00

Files

Adrian Gallagher 051675255d CI: Add support for GitHub actions (#680 )

* Add initial workflows config

* Add PSQL service

* Add 32bit and frontend jobs

* Add gcc-multilib and fix typo

* Fix backtester test for linux/unix filesystem errors and npm commands

* 32-bit Add -race to purposefully throw an error to ensure envs are set correctly (will revert)

* Revert "32-bit Add -race to purposefully throw an error to ensure envs are set correctly (will revert)"

This reverts commit b97e66c49fca859f8738e01107f96f9ca4040b2e.

* Bump workers count for orderbook processing

* Remove comments to trigger 32-bit cache hit after job success

* Cancel addition plus version bump, spawn more overlords

* Update build badge to Github Actions

* Brach -> Branch

2021-05-06 14:35:05 +10:00

README.md

CI: Add support for GitHub actions (#680 )

2021-05-06 14:35:05 +10:00

signal_test.go

Backtester: Add buy and sell limit for strategies (#658 )

2021-04-28 14:43:21 +10:00

signal_types.go

Backtester: Add buy and sell limit for strategies (#658 )

2021-04-28 14:43:21 +10:00

signal.go

Backtester: Add buy and sell limit for strategies (#658 )

2021-04-28 14:43:21 +10:00

README.md

GoCryptoTrader Backtester: Signal package

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

Signal package overview

The signal event is created as a result of a data event being analysed via a strategy. Typically, there are three types of signal that should be expected buy, sell and donothing. An example of this is demonstrated in the RSI strategy. However, other signals can be raised such as MissingData. The signal event will contain data such as price, the direction as well as the reasoning for the signal decision with the GetWhy() function

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