New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strange API values for HMQ1725 #1043
Comments
I just realised my config files weren't on hour average as I expected, but were on minute_10. So I've switch over now to see if it's better. Is there a way to check on local host which average is in play? |
Only possiblity to find the infos on localhost, is the "Running Config" page. Just search for "ZergPoolCoins" on that page. I have best results with |
Yea I use current estimates too but have been using a value other than 'live' for the stat average. I think I figured it out though. I was using hour as the stat average for anything other than nicehash in the expectation that this, along with the switch prevention, would keep my miners away from highly volatile shitcoins. Unfortunately it seems this had an unintended consequence, because the HMQ1725 coins are crazy volatily it actually meant the hour average was pushed so high, that the estimate stayed high for a long time. This probably wouldn't have been so bad with minute_10. I've switch back to live and the estimates seem more reasonable again. |
Were you experiencing the same high estimates using 'hour' as your stat average? |
Yes, there has been a high (but reasonable) value for the HMQ1725 BRAZ coin. I think, the major uplift has been with ESP coin - which I have on my ExcludeCoinSymbol list on ZergPoolCoins. So I expect I didn't see much of a shocking value. |
Ok, I have listed "ESP" on ZergPoolCoins as unprofitable. |
Ok. I don't mind if you leave it in there if it's due to a legitimate difficulty drop. I'm mining BRAZ coin right now. |
I discovered the error ratio for the HMQ coins had hit as high as 2, which seems a bit silly so I have disabled the error ratio setting. Is there a way to limit the error ratio number to have a maximum value? |
- add param "MaxErrorRatio" to config.txt (issue #1043) - "MaxErrorRatio": Maxium error ratio for yiimp pool price auto-correction [default=1.5]
I have added a "MaxErrorRatio" parameter to config.txt (which defaults to 1.5, currently) |
Nice thanks! |
I have zergpoolcoins enabled and I keep getting crazy estimates from the API, even though I have it set to an hour average....
I've checked the zergpool page and the estimates seem fine, so could there be an issue with the API?
The text was updated successfully, but these errors were encountered: