bitreport-org / bitreport Goto Github PK

Automated technical analysis reports for cryptocurrencies 🚀

License: MIT License

Python 42.80% HTML 4.42% CSS 0.66% Ruby 41.28% JavaScript 2.01% CoffeeScript 1.33% Shell 0.47% Dockerfile 1.45% Mako 0.21% SCSS 0.70% Slim 4.66%

crypto technical-analysis reporting exchanges python ruby

bitreport's Introduction

Bitreport

Automated technical analysis reports for cryptocurrencies 🚀

This project was used to generate content for: https://twitter.com/Bitreport_org.

However, we decided to abandond it and open-source our code. Hopefully someone may find this helpfull.

Setup

Everything is dockerized here, so all you need is docker. Just run docker-compose up and you're good to go. Additonaly if you would like use pre-commit then:

install pre-commit with pip install pre-commit or brew install pre-commit
install required git hook pre-commit install

If you want you can run pylint over core but then you are obligated to fix errors 💁🏻‍♂️

pylint --output-format=colorized core/app/

Deployment

We have CI/CD and stuff 🎉

bitreport's People

Contributors

Stargazers

Watchers

Forkers

mossene

bitreport's Issues

Hide Y axis values on some indicators which don't use it

Influx - records out of RP

Writing points outside retention policy makes core restart longer.

Volume

Volume jest po za wskaźnikami ale jest zawsze rysowany. @Bombasarkadian czy Twój słownik to ogarnia?

Create application architecture diagram

For future reference in the documentation

Only draw levels for top chart

Direction chart

if time(low) < time(high) : up
if time(low > time(high): down
Ex. up, up, up, down, up, down, down....

To check time we should use faster timeframe

Create decision tree for chart drawing

Traceback (most recent call last): File "/Users/Macintosh/Desktop/Bitreport/core/core/core.py", line 101, in data_service indidict['wedge'] = channels.fallingwedge(data) File "/Users/Macintosh/Desktop/Bitreport/core/core/ta/channels.py", line 128, in fallingwedge point3 = point1 + talib.MININDEX(close[point1: point2], timeperiod=len(close[point1: point2]))[-1] File "/Users/Macintosh/Desktop/Bitreport/core/virtual/lib/python3.6/site-packages/talib/__init__.py", line 24, in wrapper return func(*args, **kwargs) File "talib/_func.pxi", line 8701, in talib._ta_lib.MININDEX Exception: inputs are all NaN

Talib linear regresion

What if no. candles < magic limit?

Zdarzają się pary / timeframe takie, że mają mniej niż 56 (?) świec. Co wtedy robimy? Pusty response nie wygląda najlepiej 🗡

IOTBTC wrong Y format

0.00019, 0.00020, 0.00020, 0.00021, 0.00021

Ichimoku + TDS = TDS is wrong

Ichimoku tokens

Dodac tokeny i pamiętać o tym, że chmura jest rysowana w przyszłość.

Use proper logging

Use info instead of warning and etc

Divergence

Patterns time range slider

Change price and volume into indicators

We may unify API by only leaving dates array and indicators dictionary. This would require to change price and volume into indicators.

{
  dates: [...],
  indicators: {
    price: {
      info: [...],
      close: [...],
      high: [...],
      low: [...],
      open: [...]
    },
    volume: {
      info: [...],
      volume: [...]
    },
    BB: {
      info: [...],
      upperband: [...],
      lowerband: [...]
    },
    ...,
    sentiment: {
      info: [...]
    }
  }
}

This way each indicator will be a dictionary containing info array with tokens and some optional arrays with data used for drawing

Fix Y axis formatting

Plot wedge history

Channel position

Support and resistance levels

Limit levels to visible ones

SMA/EMA tokens

Handle creating invalid pairs

Does core give any information about failure? Use it to do something smart

Log scale

Pairs management dashboard

Eliot waves recognition

Implementation Of Glen Neely-Mastering Elliot Wave:
http://ewavetrade.cvs.sourceforge.net/viewvc/ewavetrade/ElliotEngine/ewave_lib.cpp?revision=1.13&view=markup

Wedge issues

Does this look ok? ETHBTC 24h (120-140 candles)

Indicators for 0.00000001 coins

Update to new twitter media API

Chart classification

Klasyfikować:

uptrend
downtrend
reversals: UD, DU
consolidation (potrzebna definicja)

SMA / EMA Tokens

Check crosses in last 10 (?) periods?

Update nginx config

web_1 | 2018/11/10 13:33:11 [warn] 1#1: the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /etc/nginx/conf.d/default.conf:30