Pages:
Author

Topic: bitHopper: Python Pool Hopper Proxy - page 80. (Read 355813 times)

legendary
Activity: 1526
Merit: 1002
Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na
August 05, 2011, 01:13:27 AM
talked to the guy who found the digbit coin, he is a hopper.. stuck in the newbie section.. 23 shares got him a couple coins.. thats like 1million percent eff. LOL


He sends his thanks to c00w and the new slicing.

I got 0,83BTC for 400 shares Tongue Not bad...
sr. member
Activity: 476
Merit: 250
moOo
August 05, 2011, 01:03:13 AM

Code:
Unhandled Error
Traceback (most recent call last):
  File "D:\Users\joulesbeef\Desktop\currentminer\c00w1.1\c00w-bitHopper-689817b\
bitHopper.py", line 298, in
    main()
  File "D:\Users\joulesbeef\Desktop\currentminer\c00w1.1\c00w-bitHopper-689817b\
bitHopper.py", line 294, in main
    reactor.run()
  File "D:\Python27\lib\site-packages\twisted\internet\base.py", line 1162, in r
un
    self.mainLoop()
  File "D:\Python27\lib\site-packages\twisted\internet\base.py", line 1171, in m
ainLoop
    self.runUntilCurrent()
--- ---
  File "D:\Python27\lib\site-packages\twisted\internet\base.py", line 793, in ru
nUntilCurrent
    call.func(*call.args, **call.kw)
exceptions.TypeError: pull_lp() takes exactly 3 arguments (2 given)
[02:01:00] LP triggered serving miner
[02:01:03] RPC request [getwork] submitted to MtRed.com

i got this
member
Activity: 102
Merit: 10
August 05, 2011, 12:45:11 AM
Holy contrast batman!  Refreshing was a bad idea.  Sorry to whoever updated the colors, but I have a fever, and the only prescription is more contrast.

You're probably looking at my changes. Dark grey screen? Bright red, yellow, green, blue? If so c00w already changed it back to original scheme about 12 hrs ago.
member
Activity: 102
Merit: 10
August 05, 2011, 12:40:41 AM
Also, I could really use some help making the text bold as well as possibly applying the getColor function to the linecolor of the graph.

these tags will bold html

The line color looks to be set on line 300 of index.html.
...

Once the code gets into building the chart/table, I loose my understanding of what's going on. I'm not sure where the bold tags go or how to get the getColor function to work inside of the buildtable function. " + getColor(payload, srv) + " doesn't return the right color. I may be wrong, but I'm not sure if you can dynamically change the linecolor of the chart. Any more ideas?
full member
Activity: 154
Merit: 102
August 05, 2011, 12:39:36 AM
Holy contrast batman!  Refreshing was a bad idea.  Sorry to whoever updated the colors, but I have a fever, and the only prescription is more contrast.
hero member
Activity: 504
Merit: 502
August 05, 2011, 12:39:19 AM
I do think c00w should add poolhashrate support to current slicescheduler/altslice asap to take care of these situations, most pools report the scheduler rate and for those who dont it could just be estimated based on currentroundshares and roundtime.
hero member
Activity: 504
Merit: 502
August 05, 2011, 12:33:24 AM
Ok, so BTCPool24 has a total of 18 GH and is at 41%, and MtRed has 400 GH and is at 23%.  Why would slicer choose BTCPool24?

Slicers main flaw atm is that it doesnt recognize poolhashrate, that is something dynamicpenalty will introduce once it gets added I assume.

If it isn't poolhashrate, what is making it select the 41% pool over the 23%?

Either random(?) based on name filter? B coming before M ? I really dont know but it seems it picks BTC pool above many other pools and coincidentally its the first in alphabet from the list in most cases atleast.
full member
Activity: 154
Merit: 102
August 05, 2011, 12:31:34 AM
Ok, so BTCPool24 has a total of 18 GH and is at 41%, and MtRed has 400 GH and is at 23%.  Why would slicer choose BTCPool24?

Slicers main flaw atm is that it doesnt recognize poolhashrate, that is something dynamicpenalty will introduce once it gets added I assume.

If it isn't poolhashrate, what is making it select the 41% pool over the 23%?
hero member
Activity: 504
Merit: 502
August 05, 2011, 12:29:57 AM
Ok, so BTCPool24 has a total of 18 GH and is at 41%, and MtRed has 400 GH and is at 23%.  Why would slicer choose BTCPool24?

Slicers main flaw atm is that it doesnt recognize poolhashrate, that is something dynamicpenalty will introduce once it gets added I assume.
full member
Activity: 154
Merit: 102
August 05, 2011, 12:28:45 AM
Ok, so BTCPool24 has a total of 18 GH and is at 41%, and MtRed has 400 GH and is at 23%.  Why would slicer choose BTCPool24?
full member
Activity: 196
Merit: 100
August 05, 2011, 12:25:44 AM
Also, I could really use some help making the text bold as well as possibly applying the getColor function to the linecolor of the graph.

these tags will bold html

The line color looks to be set on line 300 of index.html.

when starting using bitHopper.py --scheduler SliceScheduler

it says it cant find sliceschedular and reverts to default. am i using the right start up?

The default is SliceScheduler now
sr. member
Activity: 476
Merit: 250
moOo
August 05, 2011, 12:24:17 AM
when starting using bitHopper.py --scheduler SliceScheduler

it says it cant find sliceschedular and reverts to default. am i using the right start up?
full member
Activity: 154
Merit: 102
August 05, 2011, 12:18:26 AM
It's not just when switching roles, it just switched back to BTCPool24 on me
full member
Activity: 154
Merit: 102
August 05, 2011, 12:16:51 AM
I see, pulled latest again.  Slicing seems to have some problems though.  When you move a pool under 43.5% from info to mine, it will start mining on it for about a minute before switching over to a better pool.  For example in my case, I switched over BTCPool24 which was at 40%, and it mined it for a minute even though mtred was at 15%
full member
Activity: 196
Merit: 100
August 05, 2011, 12:00:06 AM
@gnaget
Should be fixed in latest commit.
It only reslices every 30 seconds and didn't reslice earlier if the pool had the wrong role.
sr. member
Activity: 476
Merit: 250
moOo
August 04, 2011, 11:52:52 PM
pretty sure poolmunity changed their payout scheme and you shouldnt be hopping them
sr. member
Activity: 350
Merit: 250
August 04, 2011, 11:50:42 PM
so is anyone else noticing poolmunity json acting a little funny?
full member
Activity: 154
Merit: 102
August 04, 2011, 11:35:56 PM
I'm seeing some very bad behavior right now:

MtRed = 7%
Bitcoins.lc = 43%

I start bitHopper up with bitcoins.lc on info, and when I mark it as mine, bitHopper leaves mtred to mine at bitcoins.lc.  When I mark bitcoins.lc back as info, it continues to mine there until I restart bitHopper. 

I'm on the latest version
member
Activity: 102
Merit: 10
August 04, 2011, 11:32:02 PM
Hello all. First, I'd like to apologize if my stats page "gave you a headache." I had hoped people had a chance to check it out. That being said, I'm not one to give up. I'm going to try to do a few of these with the help of kuler and post them over in paraipanakos' poll thread. I'm thinking, with enough of these, I could put a folder in where you could choose your skin and then we would have a ghetto skin system.
The first one is over here:

https://bitcointalksearch.org/topic/m.430170

I would appreciate feedback, good or bad, to try to avoid another "situation."
Also, I could really use some help making the text bold as well as possibly applying the getColor function to the linecolor of the graph.
sr. member
Activity: 476
Merit: 250
moOo
August 04, 2011, 11:17:41 PM
from btcpool24

Quote
Sure you will get the 1.95BTC extra if you find the block.

calc is exactly (myshares/totalshares)*50

he is not changing prop.. so mine him if you got him off..

they are small and some connection issues now and then.. only one block found so far

they are also my highest reject rate though.. 4% with them.. .. my other highest is 0.8% most are at 0%
so be wary or penalize them if you have the ability
Pages:
Jump to: