Skip to content
This repository has been archived by the owner on Feb 15, 2022. It is now read-only.

Charting strategy performance #431

Open
michaelr524 opened this issue Aug 2, 2017 · 3 comments
Open

Charting strategy performance #431

michaelr524 opened this issue Aug 2, 2017 · 3 comments

Comments

@michaelr524
Copy link

Hello friends!

I'm currently testing/evaluating the bot and doing some trading in paper mode.
It's not easy to understand what's going on by just reading the console output.
So I thought that a chart with the following properties could really be useful in order to understand (and later tune) the performance of a given strategy:

  1. The price line
  2. A line for each indicator used by the strategy
  3. The points at which buy/sell order were placed and the points where they've been executed

I did notice that the simulator can generate a chart with 1 and 3. But I also understood from other issues that the results of the simulator don't represent the results of live trading.

My questions are:

  1. Does anyone else also thinks that this can be useful (or not)?
  2. Is anyone already working on such feature?
  3. How else do you usually measure/evaluate/investigate the performance of a strategy with a given set of arguments?
@DeviaVir
Copy link
Owner

DeviaVir commented Aug 2, 2017

An HTML file is generated after a SIM, that gives you exactly what you're asking for here.

@michaelr524
Copy link
Author

I mean, something like this, but for live/paper mode.

@l-j-g
Copy link

l-j-g commented Aug 5, 2017

@DeviaVir as I understand the default charting app (techan?) is very limited, generating ema from its own prewritten algorithms. It would be much more convient to for the charting app to read the indicator .period data. This would be very easy to implement but is currently beyond my programming skill.. time to enter the 36 chambers and skill up I suppose

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants