does this still work?
I have never seen such a dumb question in my life.
I hope it was ironic, but I'm not sure about it
Topic: Chrome Browser extension: MtGox trading bot (Read 72509 times)
I have never seen such a dumb question in my life.
I hope it was ironic, but I'm not sure about it
does this still work?
I have never seen such a dumb question in my life.
does this still work?
edit: Im noticing a problem with function G in sha512.js, a is undefined, maybe this is related to the problem?
No. It's just chrome internal idiocy. Real error in some other place. Maybe other page (options/popup). Them all have separate console
. Call it as inspect element -> console. Bot errors you wrote about are because of caching. Simple make new settings, press save, press refresh on extensions page. No any errors.
Use latest version of bot - it's most reliable.
edit: TobliBot (I don't check previous versions) also have a timing in logic error - it shows different time at the same operations in diagram/table and log. More then one time step.
thanks for posting those. they actually all seem to have this problem. eduks version was running perfectly but as soon as I changed the settings the data seems to get corrupted. as you can see from the data I posted its enough of a change to give you unwanted sells and buys which makes these bots pretty useless for anything but an educational tool, altho I can see from the code that a lot of time has been put into them and I do appreciate that. I see that at one stage a bug corrupting data when user updated settings while fetching data was fixed, so it could be related to that
anyway, just a warning that if you are using this bot it is posibly trading at different settings from what you set at
edit: Im noticing a problem with function G in sha512.js, a is undefined, maybe this is related to the problem?
anyway, just a warning that if you are using this bot it is posibly trading at different settings from what you set at
edit: Im noticing a problem with function G in sha512.js, a is undefined, maybe this is related to the problem?
You can find piotr_n bot in google store.
Where you use TobliBot - it can be completely refreshed by using "Reload (Ctrl+R)" in Chrome "extensions" page.
For all who interested - http://www.mediafire.com/?o1yzy7u788igqer - all versions of bot
Where you use TobliBot - it can be completely refreshed by using "Reload (Ctrl+R)" in Chrome "extensions" page.
For all who interested - http://www.mediafire.com/?o1yzy7u788igqer - all versions of bot
for the "original one" you mean the first toblibot version or the piotr_n bot?
12:00 93.511 94.668 94.637 0.032%
Is there a way to clear the cache of this bot? I cant find where chrome stores it. I dont think this bot is 100% reliable when it comes to calculating a moving average, at least the version Im using TobliBot 0.2.9.1., altho its close. If you change a setting and then go back to your original one it will show crossovers where there was none before and shouldnt be any, so its somehow changing its calculations while using the same data. also it often shows crossovers which dont show when you use backtracking tools or charts. its fairly accurate so if you back off a little, say change 10/21 to 11/21 you will should be ok. I would use this bot on a conservative setting if you are sleeping but better off using manual charts if you are expecting a crossover. apart from that the bot is perfect. if it was accurate I would rely on it full time.
edit: I just installed the original bot and it seems ok, heres a comparison of the same times with the same settings, the toblibot is at the top and its crossed over whereas the original is showing the correct results
12:00 93.511 94.675 94.723 -0.051%
12:00 93.511 94.667 94.627 0.042%
edit: I just installed the original bot and it seems ok, heres a comparison of the same times with the same settings, the toblibot is at the top and its crossed over whereas the original is showing the correct results
12:00 93.511 94.675 94.723 -0.051%
12:00 93.511 94.667 94.627 0.042%
for the "original one" you mean the first toblibot version or the piotr_n bot?
Is there a way to clear the cache of this bot? I cant find where chrome stores it. I dont think this bot is 100% reliable when it comes to calculating a moving average, at least the version Im using TobliBot 0.2.9.1., altho its close. If you change a setting and then go back to your original one it will show crossovers where there was none before and shouldnt be any, so its somehow changing its calculations while using the same data. also it often shows crossovers which dont show when you use backtracking tools or charts. its fairly accurate so if you back off a little, say change 10/21 to 11/21 you will should be ok. I would use this bot on a conservative setting if you are sleeping but better off using manual charts if you are expecting a crossover. apart from that the bot is perfect. if it was accurate I would rely on it full time.
edit: I just installed the original bot and it seems ok, heres a comparison of the same times with the same settings, the toblibot is at the top and its crossed over whereas the original is showing the correct results
12:00 93.511 94.675 94.723 -0.051%
12:00 93.511 94.667 94.627 0.042%
edit: I just installed the original bot and it seems ok, heres a comparison of the same times with the same settings, the toblibot is at the top and its crossed over whereas the original is showing the correct results
12:00 93.511 94.675 94.723 -0.051%
12:00 93.511 94.667 94.627 0.042%
That's because on the chart to the left you're looking at the 15-min interval (upper left corner) and on the bot it's on the 1-hr interval (at the top). I could be wrong though.
I now have the impression that this bot is "retarded", in the sense that there seems to be a time lag of a few hours. Check out the pic below to see what I mean (notice the EMA cross unseen by the bot). Any comment /suggestion would be appreciated.
edit: I see now that changing the timespan on bitcoincharts moves the EMA crosses.
edit: I see now that changing the timespan on bitcoincharts moves the EMA crosses.
Am I blind, or this bot do nothing like "average value for fetch interval" ? Please, someone confirm this. Naturally, it fetch something, that can be interpreted as a " price on close" .... but it's absolutely wrong in mathematical sense IMHO, but correspond tradition.
I feel like the MACD trading on this bot is terribly suited for the volitile BTC market. You'd think you could figure out a short trend if you just looked at the graph moment by moment--and you can, but I have experimented with a variety of settings and like everyone else I have come to the conclusion you should just use EMA sample time 1H and long trade. Had I done that I would have sold at around $94 and would still be riding the wave down since the 1st of July.
There is money to be made on the way down, however this bot is unable to find it.
Am I blind, or this bot do nothing like "average value for fetch interval" ? Please, someone confirm this. Naturally, it fetch something, that can be interpreted as a " price on close" .... but it's absolutely wrong in mathematical sense IMHO, but correspond tradition.
Just downloaded the modified bot.. The chart zoom out or setting button on the popup will not work, like everything on the far right hand side of the popup is un-clickable.
I want to use that bot, but little bit confused - my transaction fee on Mt.Gox is standard 0,6%. What threshold should I use for not losing money? Default - 0,25?
This have nothing with Mt.Gox fee. Buy threshold and Sell threshold shows not a percentage of price, but only a relative strength of trend. Method, implemented in this bot, suppose that one can choose a trend value to make a decision to sell/buy and get the profit. It can work only when you don't pay any fee at all.
Also suppose this: price make a big rise. You see a huge trend. You pay all your money (as this bot do). Next day price jump upper and stabilize at high value. Congratulation: you loose all your money !
I call it "Zhopa".Definitely, to avoid this shit, bot must have two more options:
1. Thresholds in percentage of price between consequent trade operations
2. Limit of money for single trade operation in percentage of amount
How accurate is what this guy is saying?
this bot seems to have some problems when you go above about 90, so I would be careful using those 5 or 1 minute time samples
Problems? I didn't have any, what do you mean?
this bot seems to have some problems when you go above about 90, so I would be careful using those 5 or 1 minute time samples
Problems? I didn't have any, what do you mean? Just an advice for those who are operating the bot: if you want to reduce the time sample, while having the same (slow) ema/macd, just multiply all ema parameters by the factor you've divided the time sample with.
E.g.: macd 1h 12/26/9 is the same as macd 5m 144/312/108, same as macd 1m 720/1560/540
This should guarantee the same behaviour, plus you don't have to trade only @ multiples of the (old) timeframe. You'll have to mess around with options.html and MaxSamplesToKeep before, though.
this bot seems to have some problems when you go above about 90, so I would be careful using those 5 or 1 minute time samples E.g.: macd 1h 12/26/9 is the same as macd 5m 144/312/108, same as macd 1m 720/1560/540
This should guarantee the same behaviour, plus you don't have to trade only @ multiples of the (old) timeframe. You'll have to mess around with options.html and MaxSamplesToKeep before, though.
warning: ./org/joda/time/ReadableInstant.class: major version 51 is newer than 50, the highest major version supported by this compiler.
It is recommended that the compiler be upgraded.
is this a problem?
TIA
try upgrading your jdk to the latest version It is recommended that the compiler be upgraded.
is this a problem?
TIA
Code:
.
.
.
warning: ./org/joda/time/ReadableInstant.class: major version 51 is newer than 50, the highest major version supported by this compiler.
It is recommended that the compiler be upgraded.
8 warnings
is this a problem?.
.
warning: ./org/joda/time/ReadableInstant.class: major version 51 is newer than 50, the highest major version supported by this compiler.
It is recommended that the compiler be upgraded.
8 warnings
TIA
Jump to: