Automated overclocking/underclocking against pool luck

[Slaine]

I'm thinking about writing a script that monitors my pool luck, so that when the pool luck is high my S1 runs overclocked and when it's low it runs underclocked to save electricity.

What I'm wondering is it actually a worthwhile idea, atm it's just something to keep my tiny mind occupied  

Obviously you're at the mercy of wherever you're getting the pool luck data from, being up to date and available.

But with power usage vs btc return looking to be a major thing for most peeps, I was wondering if this could be an option in general?

No doubt I've over looked some major points, but hey ho  

[-ck]

You only know luck after the fact and by then it's too late. You cannot plan for expected luck because there is no such thing.

[Slaine]

You only know luck after the fact and by then it's too late. You cannot plan for expected luck because there is no such thing.

Yes you would always be one step behind, but from what I've seen usually you get a day or two of good luck and then it drops again.

I wonder how the pool luck is calculated and if it can be forecast say by looking at the block history.

I never said it was a good idea, just an idea 

[LendingTree]

Luck is luck, by definition it cannot be forecasted.

[Slaine]

Luck is luck, by definition it cannot be forecasted.

I know but say on Slush's pool, yes it reports pool luck daily but if you could get that down to half/quarter of a day, then you are reacting to the trend of what's happened/happening within a shorter timeframe, so the chance is you will be more accurate.

I'm going to give it a go any just to see what would be the best way to do this from a script point of view, mining is mostly a gamble anyway and this will keep me out for mischief for a little bit at least.

[LendingTree]

Luck is luck, by definition it cannot be forecasted.

I know but say on Slush's pool, yes it reports pool luck daily but if you could get that down to half/quarter of a day, then you are reacting to the trend of what's happened/happening within a shorter timeframe, so the chance is you will be more accurate.

I'm going to give it a go any just to see what would be the best way to do this from a script point of view, mining is mostly a gamble anyway and this will keep me out for mischief for a little bit at least.

Luck is not a trend.

Again, luck is luck.  Just like when rolling a dice, the last roll does not change the outcome of future roles.  Gamblers Fallacy.

Same thing applies.

[Slaine]

Luck is luck, by definition it cannot be forecasted.

I know but say on Slush's pool, yes it reports pool luck daily but if you could get that down to half/quarter of a day, then you are reacting to the trend of what's happened/happening within a shorter timeframe, so the chance is you will be more accurate.

I'm going to give it a go any just to see what would be the best way to do this from a script point of view, mining is mostly a gamble anyway and this will keep me out for mischief for a little bit at least.

Luck is not a trend.

Again, luck is luck.  Just like when rolling a dice, the last roll does not change the outcome of future roles.  Gamblers Fallacy.

Same thing applies.

Probably bad wording on my part, had a few too many brews last night.

Yes a lot of it would be down to chance and by trending I meant that if say the last half day of mining had been good then there is a chance that the next half day might be good as well, so would be worth on taking a gamble to overclock for that half.

I'll leave it at that, I'm more interested in the actual technical part of it, the whether it was worth it was more of an after thought.

[LendingTree]

Good luck!