rearwheels
|
|
July 05, 2011, 03:08:20 PM |
|
I have 2 accounts, sent you a PM.
|
|
|
|
Inaba (OP)
Legendary
Offline
Activity: 1260
Merit: 1000
|
|
July 05, 2011, 03:09:30 PM |
|
I think I see the problem. It's strictly limited to the JSON api. I will fix that when I get home.
|
If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.
|
|
|
Inaba (OP)
Legendary
Offline
Activity: 1260
Merit: 1000
|
|
July 05, 2011, 06:07:15 PM |
|
I forgot to mention that we now pay out to 8 decimal places... no more storing sub .02 amounts in your account. You can get a full payout whenever you'd like.
|
If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.
|
|
|
kripz
|
|
July 06, 2011, 01:53:50 AM |
|
What about for paypal?
|
|
|
|
Inaba (OP)
Legendary
Offline
Activity: 1260
Merit: 1000
|
|
July 06, 2011, 02:11:27 AM |
|
Paypal will pay out to 8 decimal places, too, but there is still a minimum due to fees and overhead.
|
If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.
|
|
|
Inaba (OP)
Legendary
Offline
Activity: 1260
Merit: 1000
|
|
July 06, 2011, 03:34:12 AM |
|
Ok Rearwheels, I found the bug. Basically, the JSON is still using an old table and some old code to calculate hash rate instead of the newer, faster table and code. I had forgotten about that calculation routine.
I'm going to take this opportunity to centralize and rewrite the share calculation function so it won't be fixed tonight. Hopefully tomorrow. I hope it doesn't cause too much in the way of problems.
On a technical note, it has to do with the way a table is joined joining your miner twice for some reason. I didn't really investigate as to why since the whole code block needs to go away anyway.
|
If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.
|
|
|
rearwheels
|
|
July 06, 2011, 05:04:24 AM |
|
Ok Rearwheels, I found the bug. Basically, the JSON is still using an old table and some old code to calculate hash rate instead of the newer, faster table and code. I had forgotten about that calculation routine.
I'm going to take this opportunity to centralize and rewrite the share calculation function so it won't be fixed tonight. Hopefully tomorrow. I hope it doesn't cause too much in the way of problems.
On a technical note, it has to do with the way a table is joined joining your miner twice for some reason. I didn't really investigate as to why since the whole code block needs to go away anyway.
ok, but I think you broke the JSON. There's 3 numbers before the JSON starts.
|
|
|
|
organofcorti
Donator
Legendary
Offline
Activity: 2058
Merit: 1007
Poor impulse control.
|
|
July 06, 2011, 05:17:47 AM |
|
Ok Rearwheels, I found the bug. Basically, the JSON is still using an old table and some old code to calculate hash rate instead of the newer, faster table and code. I had forgotten about that calculation routine.
I'm going to take this opportunity to centralize and rewrite the share calculation function so it won't be fixed tonight. Hopefully tomorrow. I hope it doesn't cause too much in the way of problems.
On a technical note, it has to do with the way a table is joined joining your miner twice for some reason. I didn't really investigate as to why since the whole code block needs to go away anyway.
ok, but I think you broke the JSON. There's 3 numbers before the JSON starts. Semi-off-topic: Is that why the results for eclipse on btc-poolwatch is all curly braces and stuff? Looks like raw JSON.
|
|
|
|
rearwheels
|
|
July 06, 2011, 05:51:51 AM |
|
Ok Rearwheels, I found the bug. Basically, the JSON is still using an old table and some old code to calculate hash rate instead of the newer, faster table and code. I had forgotten about that calculation routine.
I'm going to take this opportunity to centralize and rewrite the share calculation function so it won't be fixed tonight. Hopefully tomorrow. I hope it doesn't cause too much in the way of problems.
On a technical note, it has to do with the way a table is joined joining your miner twice for some reason. I didn't really investigate as to why since the whole code block needs to go away anyway.
ok, but I think you broke the JSON. There's 3 numbers before the JSON starts. Semi-off-topic: Is that why the results for eclipse on btc-poolwatch is all curly braces and stuff? Looks like raw JSON. Yap, I've fixed that by chopping off the extra numbers. BTW, another block found! Woohoo! (ok, I'm 1.5hrs late)
|
|
|
|
kripz
|
|
July 06, 2011, 07:26:45 AM |
|
Making up for the block from hell we had a few days ago.
|
|
|
|
Inaba (OP)
Legendary
Offline
Activity: 1260
Merit: 1000
|
|
July 06, 2011, 01:37:28 PM |
|
Whoops, left some debug code in there. That's what I get for trying to do it late at night. Should be fixed now, I hope that doesn't break your fix
|
If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.
|
|
|
WebMonkey
|
|
July 06, 2011, 07:41:52 PM |
|
what is the irc info? i must have missed it (i'm not terribly observant anymore)
'monkey
|
Team Calvary Racing
support the ministry BTC: 1KXvwsDwRM2RUdwtnff3feuYrHH2a1JHnR LTC: LWdf2pnmQqBkg7GP7rmfGYCZaAQrjsu2Yx
|
|
|
Inaba (OP)
Legendary
Offline
Activity: 1260
Merit: 1000
|
|
July 06, 2011, 09:42:36 PM |
|
irc.freenode.net and channel #EclipseMC
|
If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.
|
|
|
WebMonkey
|
|
July 06, 2011, 10:10:44 PM |
|
righteous
'monkey
|
Team Calvary Racing
support the ministry BTC: 1KXvwsDwRM2RUdwtnff3feuYrHH2a1JHnR LTC: LWdf2pnmQqBkg7GP7rmfGYCZaAQrjsu2Yx
|
|
|
Inaba (OP)
Legendary
Offline
Activity: 1260
Merit: 1000
|
|
July 07, 2011, 03:52:20 AM |
|
Found the problem with the EU server. It's been fixed and is rebooting now and should be good to go.
|
If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.
|
|
|
tschaboo
Newbie
Offline
Activity: 42
Merit: 0
|
|
July 07, 2011, 05:59:09 AM |
|
Inaba,
you mention your scoring system in a few posts (#59, #112, #142) and seems you implemented it but I can't find any details! Can you please publish your algorithm?
|
|
|
|
Inaba (OP)
Legendary
Offline
Activity: 1260
Merit: 1000
|
|
July 07, 2011, 11:28:27 AM |
|
|
If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.
|
|
|
tschaboo
Newbie
Offline
Activity: 42
Merit: 0
|
|
July 07, 2011, 03:36:06 PM |
|
Excellent! So which values do you use for the variables c and f? The reason I'm asking: Continuumpool shuts down ( http://forum.bitcoin.org/index.php?topic=8660.msg330007#msg330007) and this pool was also using Meni's scoring method. Now there are plenty of refugees (about 13 GHash/s) searching for a new home - probably we just found it. What would be nice though, would be round dumps as we had at Continuum: http://www.continuumpool.com/history/Probably you could just use a hash of the worker name as (anonymous) identifier and produce similar output? Regards, tschaboo PS: EU-server is not working for some hours now ...
|
|
|
|
Inaba (OP)
Legendary
Offline
Activity: 1260
Merit: 1000
|
|
July 07, 2011, 04:02:21 PM |
|
c is .001 and f is (-$c)/(1-$c)
The scoring system appears to be stable at the moment (as of the last block), I have been running it in tandem with the proportional method to be sure it's computing right.
Those dumps look nice, I will look into implementing that going forward. I have been severely time limited this last week and half with the holiday and all so things have mostly been bug fixing. Things are beginning to stabilize so I should be able to get back to forward development this weekend.
As far as the EU server goes - there are people connected to it and submitting shares. What error are you getting?
|
If you're searching these lines for a point, you've probably missed it. There was never anything there in the first place.
|
|
|
tschaboo
Newbie
Offline
Activity: 42
Merit: 0
|
|
July 07, 2011, 04:16:45 PM |
|
Sounds good, I'm staying here ... As far as the EU server goes - there are people connected to it and submitting shares. What error are you getting?
Well, right now it's working, but it wasn't until a few minutes ago: (time in UTC+2) eu.eclipsemc.com:8337 07/07/2011 17:38:28, Setting pool XXXXXX_X @ eu.eclipsemc.com:8337 eu.eclipsemc.com:8337 07/07/2011 17:38:28, Attempting to fail back to primary pool api.bitcoin.cz:8332 07/07/2011 17:38:33, Setting pool XXXXXX.X @ api.bitcoin.cz:8332 api.bitcoin.cz:8332 07/07/2011 17:38:33, Still unable to reconnect to primary pool (attempt 4), failing over api.bitcoin.cz:8332 07/07/2011 17:39:26, 831cccc6, accepted api.bitcoin.cz:8332 07/07/2011 17:39:37, 98f64c76, accepted api.bitcoin.cz:8332 07/07/2011 17:40:01, f25431d9, accepted api.bitcoin.cz:8332 07/07/2011 17:40:09, 29c5be14, accepted api.bitcoin.cz:8332 07/07/2011 17:40:28, b69a9207, accepted api.bitcoin.cz:8332 07/07/2011 17:41:53, d3873a62, accepted api.bitcoin.cz:8332 07/07/2011 17:42:04, c50e060d, accepted api.bitcoin.cz:8332 07/07/2011 17:42:25, 087cdb44, accepted eu.eclipsemc.com:8337 07/07/2011 17:44:57, Setting pool XXXXXX_X @ eu.eclipsemc.com:8337 eu.eclipsemc.com:8337 07/07/2011 17:44:57, Attempting to fail back to primary pool api.bitcoin.cz:8332 07/07/2011 17:45:02, Setting pool XXXXXX.X @ api.bitcoin.cz:8332 api.bitcoin.cz:8332 07/07/2011 17:45:02, Still unable to reconnect to primary pool (attempt 5), failing over api.bitcoin.cz:8332 07/07/2011 17:45:08, 97b47e83, accepted api.bitcoin.cz:8332 07/07/2011 17:45:12, 470ed549, accepted api.bitcoin.cz:8332 07/07/2011 17:45:34, 4e60bd05, accepted api.bitcoin.cz:8332 07/07/2011 17:47:00, 4d9dfb3b, accepted api.bitcoin.cz:8332 07/07/2011 17:47:42, 58bab409, accepted api.bitcoin.cz:8332 07/07/2011 17:47:43, 7a0da52e, accepted api.bitcoin.cz:8332 07/07/2011 17:49:03, 52565484, accepted eu.eclipsemc.com:8337 07/07/2011 17:52:11, Setting pool XXXXXX_X @ eu.eclipsemc.com:8337 eu.eclipsemc.com:8337 07/07/2011 17:52:11, Attempting to fail back to primary pool api.bitcoin.cz:8332 07/07/2011 17:52:16, Setting pool XXXXXX.X @ api.bitcoin.cz:8332 api.bitcoin.cz:8332 07/07/2011 17:52:16, Still unable to reconnect to primary pool (attempt 6), failing over api.bitcoin.cz:8332 07/07/2011 17:52:20, d260c4fa, accepted api.bitcoin.cz:8332 07/07/2011 17:53:54, f76e2c85, accepted api.bitcoin.cz:8332 07/07/2011 17:56:07, df858b59, accepted api.bitcoin.cz:8332 07/07/2011 17:57:04, 74298ea5, accepted api.bitcoin.cz:8332 07/07/2011 17:57:15, 1ef04616, accepted api.bitcoin.cz:8332 07/07/2011 17:57:31, 8769c239, accepted api.bitcoin.cz:8332 07/07/2011 17:58:24, 80c620ce, accepted eu.eclipsemc.com:8337 07/07/2011 17:59:19, Setting pool XXXXXX_X @ eu.eclipsemc.com:8337 eu.eclipsemc.com:8337 07/07/2011 17:59:19, Attempting to fail back to primary pool eu.eclipsemc.com:8337 07/07/2011 17:59:21, f998fc18, invalid or stale eu.eclipsemc.com:8337 07/07/2011 18:00:02, 93921bb7, invalid or stale eu.eclipsemc.com:8337 07/07/2011 18:00:46, 8dda2ba0, accepted api.bitcoin.cz:8332 07/07/2011 18:01:35, Setting pool XXXXXX.X @ api.bitcoin.cz:8332 api.bitcoin.cz:8332 07/07/2011 18:02:48, 470affb0, accepted api.bitcoin.cz:8332 07/07/2011 18:03:23, b766c482, accepted api.bitcoin.cz:8332 07/07/2011 18:04:07, 76b55c97, accepted api.bitcoin.cz:8332 07/07/2011 18:04:16, ba0a0cc1, accepted api.bitcoin.cz:8332 07/07/2011 18:04:31, 145ac1c3, accepted api.bitcoin.cz:8332 07/07/2011 18:04:46, 3b765ef6, accepted api.bitcoin.cz:8332 07/07/2011 18:04:48, 50e48afa, accepted api.bitcoin.cz:8332 07/07/2011 18:08:14, e6e85b60, accepted eu.eclipsemc.com:8337 07/07/2011 18:08:15, Setting pool XXXXXX_X @ eu.eclipsemc.com:8337 eu.eclipsemc.com:8337 07/07/2011 18:08:15, Attempting to fail back to primary pool eu.eclipsemc.com:8337 07/07/2011 18:09:55, ed952462, accepted 0 2 eu.eclipsemc.com:8337 07/07/2011 18:10:39, 96c10445, accepted eu.eclipsemc.com:8337 07/07/2011 18:10:55, fbc1f900, accepted eu.eclipsemc.com:8337 07/07/2011 18:11:00, 4e44d940, accepted Unfortunately I can't tell what the problem is from this output.
|
|
|
|
|