Quote from: JuAnAuJ69 on February 12, 2014, 08:30:25 PM

Thanks Stephan. This look like the right move. With a known interface and the new capabilities, the real potential of this bot should start to show...

Also, great idea to have the Auto-tune. Will be very useful for initial set-.up.

As for benchmarking and graphs, how far back will we be able to go?

Thanks again,

At this moment i am trying to go as far as possible. Initially i started with a fixed length of 2 hours back but i already scaled this up to 26-hours. If you start the software then the 26 hours will be directly available from the cache server. So this is the hard limit at the moment, but it is not the place where i draw the line. As you might have seen the bitcoincharts DLL is also present. This DLL allows me to go back for a much longer period. I am planning on making use of this DLL so benchmarking on very long periods becomes possible to. (please do not expect i have this working directly, the entire benchmark project exists out of 3 parts. First the basics, then the tuning and then the upscaling)

Quote from: papasmurph on February 12, 2014, 10:54:57 PM

@Stephan:
by looking at the depth field it was exactly wht I thought would be nice to be able to be modified by user. In this way you can define if the bit reacts on 2, 3 or 4 signals ?!??? Grin

This is a great idea but i believe it will make things very unclear. The problem that will raise is that you are unable to maintain control of whats happening exactly. I have tried such a concept here and i got results i did not expect. I totally lost the feeling of control because of it.

As a replacement i designed the progressing of separate buy and sell signals per indicator. This concept comes very close to what you suggest, but it is not course not the same.

Quote from: smlu on February 13, 2014, 12:44:02 AM

@Stephan,

there's a bug with btc-e api keys. This usually occurs when i visit bot edit page. I've specified keys for btce and when i go to btce settings it says connected, but if I visit wallet overview or bot edit page it show nothing.

Log says: 2014-13-02 04:26:10.701 |ERROR| api key not specified

At this moment i only have a few users who report issues at Cryptsy (as always Cry

) . ~~But not other exchanges, so it should be operational.~~

Quote from: silverston on February 13, 2014, 01:34:28 PM

Now BTC-e have api problem, because under DDOS attack

Confirmed. (so worries, the software can handle this kind of situations. Trading will get on hold until the attack stops and then it will resume as usual)

Edit:
i just a finished a article of how the timespan (timer, updatespeed) impacts the trade signals produced by the indicators. Of course this description is based on the benchmark i am working on right now, but is shows very clear the effects of the timespan. I recommend to have a look, i do believe this is usefll to create a better feeling what the impact is.

https://www.haasbot.com/update-speed-and-trading/