Username: Password:

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - Zeke

Pages: [1]
1
Hi friends,

I am currently experimenting with futures. And I've discovered a problem.

After gunbot once went short/long, it will bot be able to change direction. An exemple: gunbot shorted XRP but it went up and at some point the stop loss triggered. All indicators (actually I just use ADX) would now suggest to go long. But the bot does not. He somehow just does not go long anymore after have been short.

Yes I do allow short and long in the settings.

Gunbot says actually: "Directional Index is good yet...waiting to buy...". But he never does. As soon as the indicators point towards a short, he is completely capable of doing so...

Does somebody know a solution?

Thanks you guys!

2
Hi friends

I am constantly getting the following error:

TypeError: Cannot read property '-1' of undefined
    at timeseries.SolveLE (/snapshot/node14Win/node_modules/timeseries-analysis/timeseries-analysis.js:993:22)
    at timeseries.ARLeastSquare (/snapshot/node14Win/node_modules/timeseries-analysis/timeseries-analysis.js:942:20)
    at /snapshot/node14Win/gain.js
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

Dowloading gunbot again does not help. Running gb on a raspi.

What's wrong? And could this error affect the trading? The bot seems to have a crossup-, crossdown-recognition problem. It constantly buys at a crossdown (macd, SMAcross).

All the best!
Zeke

3
Hi friends

I set up a strategy with MACD-buy and TSSL-sell. I use it on several alts. Base is btc.
Now sometimes a buy order is sent out, right when the MACD-line crosses the signal-line from above (which should be a sell signal actually).

How can this be? Any suggestions?

Edit: I might have found a pattern/the reason. It's if the TSSL-sell fires if the MACD ist still above the signal-line. If MACD crosses now down over the signal line, a buy order gets out. I really don't think this should be like that. Any clue how to overrule this?

Pages: [1]