Topic: [~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More - page 95. (Read 379078 times)

I'm getting "Failed to connect to UK server." while trying to open my account page. Also when loading api.

I think the site is down. I can view block stats but not my worker stats. I get a "Failed to connect to UK BTCGuild."

Yes, as long as the temperature doesn't vary by more than a few degrees, it isn't a risk, but if it varies by 10 or more degrees C, then it will start causing physical expansion or contraction [the latter in the case of idle and temperature drops].  I use MSI Afterburner, so if there is a big spike in GPU utilization [note that the sample period affects the graph, so what may have been a 0.2s gap, may show as a 1s gap on the graph], I just look up at the temperature line and see if it moved more than a "blip" meaning a couple of degrees.  If I see this happen often, and especially in relatively close succession, I stop the miner and either wait it out, or mine a different pool for a bit [sometimes, conditions are such that nearly every significant pool was having similar issues].  I have not had to leave my miners down for long before I found a place to land   I give it a day or so and then test the waters.  I watch my stales carefully, compare to the fee/donation that I am paying and the variability of the pool to determine my threshold of what is acceptable.  No mathematical analysis, but I do make educated conclusions about whether I think it is a good idea to leave my miners connected to a given pool when unattended [i.e. when I am sleeping, or in the office away from my mining computers].

That's why I call it babysitting when all hell breaks loose among multiple pools

I realize that my display tweak focuses on my worker's name as opposed to yours. Probably time for me to start using ncurses to display things a bit more easily, and put the whole script in a delay loop so I don't have to run it with watch -n 300 ./btcguild.py anymore.

Accepted.  I tweaked the formatting a bit, but please keep it coming I'm really glad to not be the only one using the script. I'll likely refactor a bit in the coming days but don't let that stop you from submitting more pull request.

Thanks for the hard work! All has been smooth sailing for me now that the loads are balanced better. I like choosing my own servers.

Fixed a bug with updating stats from US Central on the My Account page.  No data was lost, it just wasn't updating the worker's share counts when displaying the worker summary/estimated reward.

Whenever you want really. It's not like you're gaining interest by it being in your wallet or btc guild account.

I also wonder why they dont redirect.

Didn't want to create a new topic for this or anything sense it's more directed at people using this pool, but I was wondering how often most people payout? Do you wait to accumulate a certain amount, or payout each day? Any recommendations? Just curious.

I've sent you a pull request for a small calculation fix and also individual worker stats

Any way to get pre-configured python script? Cant figure it out... What paste where... Feel dumb now.
EDIT:
Forget it. Used option "edit with idle" amd thats why I got everything messed... And save target as also misleaded me.

Use http://www.btcguild.com

Glad to hear it works.  I just updated it to have a CURL_PATH directly below the API_KEY so you only have to change the path in one place. It now displays the current Round Time next to the Average Block time as well.

Thanks, pretty cool.

For the Windows users that want to check it out I used the following:
Curl - http://www.paehl.com/open_source/?CURL_7.21.6
Python - http://www.python.org/ftp/python/2.7.2/python-2.7.2.msi

I installed Python with default selections. Then I copied the curl.exe into C:\BTCGuild_Stats folder along with the btcguild.py file. You will need to add your API key on line 6, keep the ' on each end, and then remove the /usr/bin/ from line 9,10,11. Then just be in a command prompt in the directory and type btcguild.py

Fixed.  US Central shares were not sync'ing up properly when resetting shares.

Worker counters reset don't seem to be working properly. Reset All seems to do nothing, and when I (later) reset an individual worker, it became 76 (3).

Nice! Very helpful, with the change in difficulties.

This update has been pushed back far too long given how easy it is, but I finally have some time to breathe again and get to work on features .

My Account -> Rewards Summary now display how much BTC you've generated in the last 24 hours.