bitreport-org / bitreport Goto Github PK

Add:

• expansion recognition
• bounces recognition

Fix:

• for automated images prediction precision > recall

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

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

• Refactor wedges to simple form
• Add tokens translations

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

Use info instead of warning and etc

twitter_image is basically a twitter_response without a tweet to respond to. Unifying this would allow using same scripts for creating new and replying to tweets

0.00019, 0.00020, 0.00020, 0.00021, 0.00021

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

For future reference in the documentation

Throwback etc.

Writing points outside retention policy makes core restart longer.

Ex. STOCH RSI is far from being like trading view one.

After adding a new pair in dashboard send a request for 200 candles. Doing this will create historical channel, wedge etc.

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

Return only info on the beginning of new phase

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

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

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

Może ujednolicimy do
data?query
fill?query

?

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

https://woobull.com/nvt-signal-a-new-trading-indicator-to-pick-tops-and-bottoms/

Klasyfikować:

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

Check crosses in last 10 (?) periods?

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

For our need activestorage built into rails is enough for storing files. We can remove shrine dependency from dashboard

Poziomy rysują się dwa razy przy EOSBTC 12h i MOM.

Check and fix how many candles are being updated.
Use start, end from Bitfinex API.