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?
Topic: [1200 TH] EMC: 0 Fee DGM. Anonymous PPS. US & EU servers. No Registration! - page 217. (Read 499835 times)
July 07, 2011, 11:02:21 AM
July 07, 2011, 10:36:06 AM
The full details are here: http://forum.bitcoin.org/index.php?topic=4787.0
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 ...
July 07, 2011, 06:28:27 AM
The full details are here: http://forum.bitcoin.org/index.php?topic=4787.0
July 07, 2011, 12: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?
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?
July 06, 2011, 10:52:20 PM
Found the problem with the EU server. It's been fixed and is rebooting now and should be good to go.
July 06, 2011, 05:10:44 PM
righteous
'monkey
'monkey
July 06, 2011, 04:42:36 PM
irc.freenode.net and channel #EclipseMC
July 06, 2011, 02:41:52 PM
what is the irc info?
i must have missed it (i'm not terribly observant anymore)
'monkey
i must have missed it (i'm not terribly observant anymore)
'monkey
July 06, 2011, 08:37:28 AM
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
Should be fixed now, I hope that doesn't break your fix
July 06, 2011, 02:26:45 AM
Making up for the block from hell we had a few days ago.
July 06, 2011, 12: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.
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)
July 06, 2011, 12: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.
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.
July 06, 2011, 12: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.
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.
July 05, 2011, 10:34:12 PM
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.
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.
July 05, 2011, 09:11:27 PM
Paypal will pay out to 8 decimal places, too, but there is still a minimum due to fees and overhead.
July 05, 2011, 08:53:50 PM
What about for paypal?
July 05, 2011, 01: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.
July 05, 2011, 10:09:30 AM
I think I see the problem. It's strictly limited to the JSON api. I will fix that when I get home.
July 05, 2011, 10:08:20 AM
I have 2 accounts, sent you a PM.
July 05, 2011, 09:30:25 AM
I show two miners active (out of 4), the two that are active seem to be showing the proper MH rate for the type of cards you are using. Neither show anywhere close to 1 GH/s much less 2.
So I am a little confused?
I am actually on IRC right now if you want to login, I can help you.
So I am a little confused?
I am actually on IRC right now if you want to login, I can help you.
Jump to: