Author

Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 182. (Read 703563 times)

jr. member
Activity: 348
Merit: 5
Awesome Miner version 6.3.1

 ASIC mining
  - Support for Antminer Z11
 Features
  - Configuration of Network Hashrate and Block Time per coin
  - Added an additional way to calculate coin revenue, based on Network Hashrate, Block Time and Block Reward. Calculation method configurable per coin.
  - New trigger Detect Miner State to detect specific mining states
 Mining softare
  - SrbMiner 1.8.3
  - NBMiner 22.3
  - Gminer 1.38
  - Nanominer 1.2
  - Bminer 15.5
 Corrections
  - Improved compatibility for change of frequency on Antminers
  - Corrected calculation of average hashrate for benchmarks
  - Handle invalid JSON responses from JCE miner

Hi Patrike,

thank you for the continual implementation of the coin statistics features.

Just wondering if this would be something easy for you to implement, now coins with custom properties will have the "Coin" column shown in blue font, can this be extended to individual overridden properties such that if I specify custom value for Block time/Block reward/Difficulty/Hash rate/Exchange....that they can be highlighted individually depending on if their properties were overridden in the Coin Properties dialog?

Best Regards,
newbie
Activity: 162
Merit: 0
You dont need another 100's of clocking profiles, you just need 1 profile with your fixed 80% speed. Nothing else. Apply it with a rule to your miners, nothing else will be changed.

I think you're wrong in what you say. Although I create another profile, if I leave the other values at 0, in the end it will be 100PL 0 core 0 memory and fan speed.

When you apply an oc profile, the entire complete profile is applied, not just one parameter.

If I'm wrong, leave me here a screenshot of how I should leave the OC profile, but before you try it, it really works.

https://i.imgur.com/cMBfDAC.jpg

Tienes que entrar enGPU Clocking->Cambiar el FAN de cualquiera-> Y cuando grabes el profile, marcar solo el FAN. Así ya tienes el profile 80% FAN

how do you do it? I do the profiles, but I always get the fields of Core, Mem, PL, FAN and auto. I can not remove those fields. I can not create a profile from 0, I duplicate one and there are all those fields.

How do you manage to make a clocking profile with only the data of the fans? You have left me crazy, I do not do that. I have more than 100 profiles and I do not make a profile with only one value, I do not see any way to make a new one nor do I see the way to remove the other fields in one already created.

How do you do it?

And thank you very much for the capture, you have left me very intrigued

https://i.imgur.com/HTdZGl3.jpg


1st / Select any miner and you go down where the GPUs that compose it are.
2nd / Select GPU clocking
3º / In this box, select any card and put the value you want in the FAN
4th / Profile-> Save as->
5 /  and select only the FAN

You can do it for any value, the FAN, core, memory, etc ... It is very useful for partial configurations in the clocking profile  Wink

En español para evitar el traductor.

1º/ Selecciona cualquier minero y te vas abajo donde están las GPU's que lo componen.
2º/ Selecciona alli GPU clocking
3º/ En este cuadro, selecciona cualquier tarjeta y pon el valor que quieras en el FAN
4º/ Profile->Save as->
5º/ y selecciona solo el FAN

Puedes hacerlo para cualquier valor, el FAN, core, memory, etc... Es muy util para configuraciones parciales en el clocking profile  Wink
 
jr. member
Activity: 756
Merit: 2
It seems that I have some problem with nethash, whether I buy it from for example BSOD, or even selecting CTM or CC, to obtain Nethash. There are moments that correctly shows the nethash and gives a realistic profir, in this case right now about 500 ghs for veil, but at times it goes to 240 Th / s of nethash and the currency sinks.
One way to see what values Awesome Miner reads for these properties is to look in the Awesome Miner log file for "Dynamic update of coin property". These lines will indicate the coin to be updated, the property to be updated and the new value. Can you for example see the large variations of NetHash here?

the culprit was BSOD, I was seeing his api in the browser and updating and certainly gives some exaggerated values ​​at times. From the Explorer, CC and CTM are far from reality, in the end take the value in this case of WTM, although whenever you can we get it directly from the Explorer.

We have already measured about 5 coins and the precision is better, the profit does not go down much, 0.95 0-90, the logical thing removing the Fees and the hash that does not reach the Pool, for now I have not seen any at 0.70 or lower as before.

The exponential formula is the easiest but the most inaccurate. A profit measure in a currency that has 400 ghs of nethash, changes if that same currency and hash rise to 800 Ghs, because any deviation will be greater by the exponential factor.

The formula with all the data, it is more laborious to obtain, but for now it is giving us more reliable results than before, that more the benchmark corrected the profit should increase, but the hahahahaha market fell. Everything is fine, thanks patrike, a great job.

Hey by the way, you will not create an OC profile with just the fan control. How is it done?
jr. member
Activity: 756
Merit: 2
You dont need another 100's of clocking profiles, you just need 1 profile with your fixed 80% speed. Nothing else. Apply it with a rule to your miners, nothing else will be changed.

I think you're wrong in what you say. Although I create another profile, if I leave the other values at 0, in the end it will be 100PL 0 core 0 memory and fan speed.

When you apply an oc profile, the entire complete profile is applied, not just one parameter.

If I'm wrong, leave me here a screenshot of how I should leave the OC profile, but before you try it, it really works.



Tienes que entrar enGPU Clocking->Cambiar el FAN de cualquiera-> Y cuando grabes el profile, marcar solo el FAN. Así ya tienes el profile 80% FAN

how do you do it? I do the profiles, but I always get the fields of Core, Mem, PL, FAN and auto. I can not remove those fields. I can not create a profile from 0, I duplicate one and there are all those fields.

How do you manage to make a clocking profile with only the data of the fans? You have left me crazy, I do not do that. I have more than 100 profiles and I do not make a profile with only one value, I do not see any way to make a new one nor do I see the way to remove the other fields in one already created.

How do you do it?

And thank you very much for the capture, you have left me very intrigued
legendary
Activity: 3346
Merit: 1094
Hi Patrike,

we have many times the problem, that some miners (especially Antminer L3+) get the Status (in Red) Disconnected - API Access Denied
if we send the command: Reboot (via SSH), the miner is working fine again (after a reboot)

so we would like to make a rule for that event - but unfortunatly i don't find any trigger for this event?! there is the Trigger Offline detection... but no one for this specific event?! is there another option??

BR Ralf
Hi Ralf,

Thanks for your question. Unfortunately it can happen sometimes that Antminers stop responding to monitoring request requests. In some cases the Antminers are more sensitive to this problem when mining on specific pools, but in other cases it's more difficult to find an exact reason.

The predefined rule "Offline Detection" should be able to detect this scenario. By default it will only give a notification (only once, until you acknowledge the notification), but you can also add actions to perform a reboot or similar. Can you please try check if this rule detects the issue in your cae?

Hi Patrike,

thank you for your suggestion - actually the state Disconnected - API Access Denied is different to only Disconnected... but i will try with a rule, that execute only every 40 minutes for this problem.
allthough it would be helpfull, if one could choose the 2 different states in the rule-triggers...

BR Ralf

Hi Patrike,

we have to narrow the 40 minutes to 15 minutes - otherwise, the rule is not effective... but now the rule doesn't work well either... the problem is, that the rule is also triggering if you reboot a miner and he needs more then 15 minutes until actively mining - then the rule reboots him again and again and again...

so we would be very happy, if we could select the state "Disconnected - API Access Denied" in this case, we can run the rule without time-limit and in a stable way...

thank you in advance!!

BR Ralf
Hi Ralf,
I've looked into this earlier based on your previous feedback and I have now created a new Trigger type for you ("Detect Miner State") where you can detect this specific state.
Please let me know your feedback once the next version is released. Thanks!

Hi Patrike,

thank you so much - i installed the new version and adapted the trigger - but unfortunatly this event don't work - i just had a miner with this state - but the event was not triggered - even after i activated the trigger through the Actions-Button it not worked ...

BR Ralf
Thanks for the comments Ralf.
If the activation of the rule doesn't work from the Action-button, it sounds like it's the action that isn't working. The Triggers are never considered when using this button.

Do you see any log entry "Detected miner state" in the Awesome Miner log file (toolbar: Tools -> Log File)?

Hi Patrike,

no there is nothing in the logfile...

BR Ralf
Thanks for the update. I might have identified the scenario better now. You can expect a correction no later than tomorrow.
newbie
Activity: 52
Merit: 0
Hi Patrike,

we have many times the problem, that some miners (especially Antminer L3+) get the Status (in Red) Disconnected - API Access Denied
if we send the command: Reboot (via SSH), the miner is working fine again (after a reboot)

so we would like to make a rule for that event - but unfortunatly i don't find any trigger for this event?! there is the Trigger Offline detection... but no one for this specific event?! is there another option??

BR Ralf
Hi Ralf,

Thanks for your question. Unfortunately it can happen sometimes that Antminers stop responding to monitoring request requests. In some cases the Antminers are more sensitive to this problem when mining on specific pools, but in other cases it's more difficult to find an exact reason.

The predefined rule "Offline Detection" should be able to detect this scenario. By default it will only give a notification (only once, until you acknowledge the notification), but you can also add actions to perform a reboot or similar. Can you please try check if this rule detects the issue in your cae?

Hi Patrike,

thank you for your suggestion - actually the state Disconnected - API Access Denied is different to only Disconnected... but i will try with a rule, that execute only every 40 minutes for this problem.
allthough it would be helpfull, if one could choose the 2 different states in the rule-triggers...

BR Ralf

Hi Patrike,

we have to narrow the 40 minutes to 15 minutes - otherwise, the rule is not effective... but now the rule doesn't work well either... the problem is, that the rule is also triggering if you reboot a miner and he needs more then 15 minutes until actively mining - then the rule reboots him again and again and again...

so we would be very happy, if we could select the state "Disconnected - API Access Denied" in this case, we can run the rule without time-limit and in a stable way...

thank you in advance!!

BR Ralf
Hi Ralf,
I've looked into this earlier based on your previous feedback and I have now created a new Trigger type for you ("Detect Miner State") where you can detect this specific state.
Please let me know your feedback once the next version is released. Thanks!

Hi Patrike,

thank you so much - i installed the new version and adapted the trigger - but unfortunatly this event don't work - i just had a miner with this state - but the event was not triggered - even after i activated the trigger through the Actions-Button it not worked ...

BR Ralf
Thanks for the comments Ralf.
If the activation of the rule doesn't work from the Action-button, it sounds like it's the action that isn't working. The Triggers are never considered when using this button.

Do you see any log entry "Detected miner state" in the Awesome Miner log file (toolbar: Tools -> Log File)?

Hi Patrike,

no there is nothing in the logfile...

BR Ralf
legendary
Activity: 3346
Merit: 1094
Hi Patrike,

we have many times the problem, that some miners (especially Antminer L3+) get the Status (in Red) Disconnected - API Access Denied
if we send the command: Reboot (via SSH), the miner is working fine again (after a reboot)

so we would like to make a rule for that event - but unfortunatly i don't find any trigger for this event?! there is the Trigger Offline detection... but no one for this specific event?! is there another option??

BR Ralf
Hi Ralf,

Thanks for your question. Unfortunately it can happen sometimes that Antminers stop responding to monitoring request requests. In some cases the Antminers are more sensitive to this problem when mining on specific pools, but in other cases it's more difficult to find an exact reason.

The predefined rule "Offline Detection" should be able to detect this scenario. By default it will only give a notification (only once, until you acknowledge the notification), but you can also add actions to perform a reboot or similar. Can you please try check if this rule detects the issue in your cae?

Hi Patrike,

thank you for your suggestion - actually the state Disconnected - API Access Denied is different to only Disconnected... but i will try with a rule, that execute only every 40 minutes for this problem.
allthough it would be helpfull, if one could choose the 2 different states in the rule-triggers...

BR Ralf

Hi Patrike,

we have to narrow the 40 minutes to 15 minutes - otherwise, the rule is not effective... but now the rule doesn't work well either... the problem is, that the rule is also triggering if you reboot a miner and he needs more then 15 minutes until actively mining - then the rule reboots him again and again and again...

so we would be very happy, if we could select the state "Disconnected - API Access Denied" in this case, we can run the rule without time-limit and in a stable way...

thank you in advance!!

BR Ralf
Hi Ralf,
I've looked into this earlier based on your previous feedback and I have now created a new Trigger type for you ("Detect Miner State") where you can detect this specific state.
Please let me know your feedback once the next version is released. Thanks!

Hi Patrike,

thank you so much - i installed the new version and adapted the trigger - but unfortunatly this event don't work - i just had a miner with this state - but the event was not triggered - even after i activated the trigger through the Actions-Button it not worked ...

BR Ralf
Thanks for the comments Ralf.
If the activation of the rule doesn't work from the Action-button, it sounds like it's the action that isn't working. The Triggers are never considered when using this button.

Do you see any log entry "Detected miner state" in the Awesome Miner log file (toolbar: Tools -> Log File)?
legendary
Activity: 3346
Merit: 1094
It seems that I have some problem with nethash, whether I buy it from for example BSOD, or even selecting CTM or CC, to obtain Nethash. There are moments that correctly shows the nethash and gives a realistic profir, in this case right now about 500 ghs for veil, but at times it goes to 240 Th / s of nethash and the currency sinks.
One way to see what values Awesome Miner reads for these properties is to look in the Awesome Miner log file for "Dynamic update of coin property". These lines will indicate the coin to be updated, the property to be updated and the new value. Can you for example see the large variations of NetHash here?
newbie
Activity: 52
Merit: 0
Hi Patrike,

we have many times the problem, that some miners (especially Antminer L3+) get the Status (in Red) Disconnected - API Access Denied
if we send the command: Reboot (via SSH), the miner is working fine again (after a reboot)

so we would like to make a rule for that event - but unfortunatly i don't find any trigger for this event?! there is the Trigger Offline detection... but no one for this specific event?! is there another option??

BR Ralf
Hi Ralf,

Thanks for your question. Unfortunately it can happen sometimes that Antminers stop responding to monitoring request requests. In some cases the Antminers are more sensitive to this problem when mining on specific pools, but in other cases it's more difficult to find an exact reason.

The predefined rule "Offline Detection" should be able to detect this scenario. By default it will only give a notification (only once, until you acknowledge the notification), but you can also add actions to perform a reboot or similar. Can you please try check if this rule detects the issue in your cae?

Hi Patrike,

thank you for your suggestion - actually the state Disconnected - API Access Denied is different to only Disconnected... but i will try with a rule, that execute only every 40 minutes for this problem.
allthough it would be helpfull, if one could choose the 2 different states in the rule-triggers...

BR Ralf

Hi Patrike,

we have to narrow the 40 minutes to 15 minutes - otherwise, the rule is not effective... but now the rule doesn't work well either... the problem is, that the rule is also triggering if you reboot a miner and he needs more then 15 minutes until actively mining - then the rule reboots him again and again and again...

so we would be very happy, if we could select the state "Disconnected - API Access Denied" in this case, we can run the rule without time-limit and in a stable way...

thank you in advance!!

BR Ralf
Hi Ralf,
I've looked into this earlier based on your previous feedback and I have now created a new Trigger type for you ("Detect Miner State") where you can detect this specific state.
Please let me know your feedback once the next version is released. Thanks!

Hi Patrike,

thank you so much - i installed the new version and adapted the trigger - but unfortunatly this event don't work - i just had a miner with this state - but the event was not triggered - even after i activated the trigger through the Actions-Button it not worked ...

BR Ralf
jr. member
Activity: 238
Merit: 3
But all yiimp pools take the data from a central api and iimp, and I do not know what that url is for that api.
yiimp pools don't have anything like a central api. they receive all the stats from the coin daemons that are running on their servers.
jr. member
Activity: 756
Merit: 2
@patrike or @moppidoo can you provide me with the general Yiimp API url, where all the yimmp pools take the data?
https://api.zergpool.com/api/currenc
https://zpool.ca/api/status


I will try, but zergpool reads the hash from the general yiimp database, so when I read it from zergpool it is late, I prefer to read it directly from the source closest to the original one. Anyway, thank you very much, I will try, because this update will give us a lot of work
if I understand your question correct, then you can click the "define coin" button on Pool tab while mining on Zerg to override the profitability source for it, afaik.

Sorry I did not understand what you want to tell me. I'm doing tests with BSOD but the same thing gives you the correct value that gives you an exaggeration.

Now I will try other methods. Is that VEIL does not have an explorer type inquidus, if not, it would be easier

But all yiimp pools take the data from a central api and iimp, and I do not know what that url is for that api.
jr. member
Activity: 238
Merit: 3
@patrike or @moppidoo can you provide me with the general Yiimp API url, where all the yimmp pools take the data?
https://api.zergpool.com/api/currenc
https://zpool.ca/api/status


I will try, but zergpool reads the hash from the general yiimp database, so when I read it from zergpool it is late, I prefer to read it directly from the source closest to the original one. Anyway, thank you very much, I will try, because this update will give us a lot of work
if I understand your question correct, then you can click the "define coin" button on Pool tab while mining on Zerg to override the profitability source for it, afaik.
jr. member
Activity: 756
Merit: 2
@patrike or @moppidoo can you provide me with the general Yiimp API url, where all the yimmp pools take the data?
https://api.zergpool.com/api/status
https://zpool.ca/api/status

The values of hashrates they give are averaged to 24 hours, it is far from the current one.
jr. member
Activity: 756
Merit: 2
@patrike or @moppidoo can you provide me with the general Yiimp API url, where all the yimmp pools take the data?
https://api.zergpool.com/api/status
https://zpool.ca/api/status


I will try, but zergpool reads the hash from the general yiimp database, so when I read it from zergpool it is late, I prefer to read it directly from the source closest to the original one. Anyway, thank you very much, I will try, because this update will give us a lot of work
jr. member
Activity: 756
Merit: 2
It seems that I have some problem with nethash, whether I buy it from for example BSOD, or even selecting CTM or CC, to obtain Nethash. There are moments that correctly shows the nethash and gives a realistic profir, in this case right now about 500 ghs for veil, but at times it goes to 240 Th / s of nethash and the currency sinks.

At times shows the nethash well, at times shows the burrada of 240 THs.

If I use the CC APi in custom and look for the value, I exceed 500 requests per day, because each currency is a request. In addition, the CC data is well below the real hash according to other sources.

https://www.coincalculators.io/api.aspx?name=veil&hashrate=1
json currentNethash

VEIL has a pretty weird explorer
https://explorer.veil-project.com/
where we can not extract the nethash. IF I use the providers, because you give to choose the 3 that there are, it also gives me failure.

If I use the BSOD data, I get the data well for a while and more or less well, but then it goes to 240 Ths, then it's fine again then again it gives it badly
http://api.bsod.pw/api/currencies
json VEIL.network_hashrate

I do not put data out of laziness.

For that I ask who can pass me the general API of Yiimp, where all the pools based on Yiimp take the data, to request them there, or could even be defined as a nethash provider.

Anyway the formula of obtaining BSOD serves me, the problem is that at times I show the correct nethash, about 500 right now and suddenly it goes to more than 200 ths, then it goes well, then badly and so all the time .
jr. member
Activity: 238
Merit: 3
@patrike or @moppidoo can you provide me with the general Yiimp API url, where all the yimmp pools take the data?
https://api.zergpool.com/api/status
https://zpool.ca/api/status
jr. member
Activity: 756
Merit: 2
@patrike or @moppidoo can you provide me with the general Yiimp API url, where all the yimmp pools take the data?
legendary
Activity: 3346
Merit: 1094
Awesome Miner version 6.3.1

 ASIC mining
  - Support for Antminer Z11
 Features
  - Configuration of Network Hashrate and Block Time per coin
  - Added an additional way to calculate coin revenue, based on Network Hashrate, Block Time and Block Reward. Calculation method configurable per coin.
  - New trigger Detect Miner State to detect specific mining states
 Mining softare
  - SrbMiner 1.8.3
  - NBMiner 22.3
  - Gminer 1.38
  - Nanominer 1.2
  - Bminer 15.5
 Corrections
  - Improved compatibility for change of frequency on Antminers
  - Corrected calculation of average hashrate for benchmarks
  - Handle invalid JSON responses from JCE miner
legendary
Activity: 3346
Merit: 1094
https://www.dropbox.com/s/6i4nu2mjviw3y67/Captura%20de%20pantalla%202019-04-13%20a%20las%206.35.30.png?dl=0


You will see the Xfox currency and its estimate of more than 7000 coins in a day (rigti 1080ti). But it's wrong, I think the formula of your profit is not very accurate and I can say it because we measure and test all the currencies / pool and elprofit is between 0.70 to 0.95 90% of the time, but it's not what same mine to 0.80 that to 1.

In this case, this Xfox coin has a blocking time of 2 minutes and has a reward of 2.79 (removing fee from the pool), the maximum coins per day is from 2008, it does not matter how many machines and the hash is the same because the difficulty it adjusts itself, the maximum is 2008 coins per day.

With which his estimate is completely wrong in this currency and slightly deviated in many others, but it is no longer a question of data, it is a question of formula.
The formula itself is correct and gives the exact same results are WhatToMine and CoinCalculators in general. There can however be specific coins that do something differently where you manually need to adjust the profit factor as it's not possible to compute the number of coins per day the standard way.

You must take into account block time, reward and nethash, to have a more accurate profit. It is a more complex formula, more data to take into account and we must take into account the maximum coins per day for the estimates offered by AM

It is only a constructive criticism, we customize all fields, difficulty, recommensa, price of exchanges directly (that's why it would be good to cache results between requests)

It's just an example where the formula is not right. Neither can it be to mine ZEL when its real profit is 0.65 and so many currencies. You imagine mining ZEL to profit 1, but then only receive 65% of the mined. That's why I recommend everyone to do pool and coin tests, if you change the pool you have to repeat the test.
Yes, the plan is to add support for the "NetHash" way of doing the calculations as well, where Block Time is one of the factors. The idea is also have this configurable per coin so if you run into a coin where the standard way of doing the calculations doesn't give the expected results, you should be able to switch to this other mode.


Last detail, the benchmark. When I do a 2 or 5 hour test, what value does it give?

The last value he had at the end of the test
The highest peak of hash
The average of the hash of those 5 hours (This would be the correct one)
@patrike should average the benchmar hash, if not, the benchmark is totally useless for AL-GOS that change subalways, it just is not worth it.

@PAtrike is there no way to average the hash value of 2, 5 or 10 hours, during a benchmark?
It should be the average but excluding a few samples in the beginning as those first samples are typically too low. However, I did notice an issue here with long running benchmarks so I will make a correction for that case. Thanks for finding it.

Update - coin properties:
I've just finished the implementation for Network Hashrate and Block Time in the Coin Properties, together with a setting where you can select one of the following calculation methods:
- Difficulty, Block Reward and Exponential factor
- Network Hashrate, Block Reward and Block Time

As always, thank you for your compression of the problems and be the first to want to solve them. That says a lot about you as a good programmer.

As a last suggestion doubt. A rule that changes the fan speed of the rigs graphics without having to restart the mining.

Thanks in advance for the types of profit. It is clear that the other type of profit requires much more work, we in our group assume it, and when closer to reality better.
Thanks for the nice feedback.

The plan is to add support for setting GPU properties like fan speed directly via the rule actions. Today you can use Clocking Profiles via the actions as discussed earlier, but it will be easier once you can do it without the profiles.
jr. member
Activity: 756
Merit: 2
https://www.dropbox.com/s/6i4nu2mjviw3y67/Captura%20de%20pantalla%202019-04-13%20a%20las%206.35.30.png?dl=0


You will see the Xfox currency and its estimate of more than 7000 coins in a day (rigti 1080ti). But it's wrong, I think the formula of your profit is not very accurate and I can say it because we measure and test all the currencies / pool and elprofit is between 0.70 to 0.95 90% of the time, but it's not what same mine to 0.80 that to 1.

In this case, this Xfox coin has a blocking time of 2 minutes and has a reward of 2.79 (removing fee from the pool), the maximum coins per day is from 2008, it does not matter how many machines and the hash is the same because the difficulty it adjusts itself, the maximum is 2008 coins per day.

With which his estimate is completely wrong in this currency and slightly deviated in many others, but it is no longer a question of data, it is a question of formula.
The formula itself is correct and gives the exact same results are WhatToMine and CoinCalculators in general. There can however be specific coins that do something differently where you manually need to adjust the profit factor as it's not possible to compute the number of coins per day the standard way.

You must take into account block time, reward and nethash, to have a more accurate profit. It is a more complex formula, more data to take into account and we must take into account the maximum coins per day for the estimates offered by AM

It is only a constructive criticism, we customize all fields, difficulty, recommensa, price of exchanges directly (that's why it would be good to cache results between requests)

It's just an example where the formula is not right. Neither can it be to mine ZEL when its real profit is 0.65 and so many currencies. You imagine mining ZEL to profit 1, but then only receive 65% of the mined. That's why I recommend everyone to do pool and coin tests, if you change the pool you have to repeat the test.
Yes, the plan is to add support for the "NetHash" way of doing the calculations as well, where Block Time is one of the factors. The idea is also have this configurable per coin so if you run into a coin where the standard way of doing the calculations doesn't give the expected results, you should be able to switch to this other mode.


Last detail, the benchmark. When I do a 2 or 5 hour test, what value does it give?

The last value he had at the end of the test
The highest peak of hash
The average of the hash of those 5 hours (This would be the correct one)
@patrike should average the benchmar hash, if not, the benchmark is totally useless for AL-GOS that change subalways, it just is not worth it.

@PAtrike is there no way to average the hash value of 2, 5 or 10 hours, during a benchmark?
It should be the average but excluding a few samples in the beginning as those first samples are typically too low. However, I did notice an issue here with long running benchmarks so I will make a correction for that case. Thanks for finding it.

Update - coin properties:
I've just finished the implementation for Network Hashrate and Block Time in the Coin Properties, together with a setting where you can select one of the following calculation methods:
- Difficulty, Block Reward and Exponential factor
- Network Hashrate, Block Reward and Block Time

As always, thank you for your compression of the problems and be the first to want to solve them. That says a lot about you as a good programmer.

As a last suggestion doubt. A rule that changes the fan speed of the rigs graphics without having to restart the mining.

Thanks in advance for the types of profit. It is clear that the other type of profit requires much more work, we in our group assume it, and when closer to reality better.
Jump to: