Hi Acrefawn,
Thanks for your excellent work here.
I am finding that I am experiencing a couple of issues with this using DSTM's miner 0.5.6 with Autorun ver 1.8.1.
Issue 1:
When the server changes difficulty on several GPU's at once, there is sometimes a significant, temporary hashrate drop which autorun incorrectly identifies as a real problem and restarts the miner.
Issue 2:
I regularly receive the "Loaded too many GPUs" report on only one of my rigs.
This is a 7 card rig but for some reason Autorun is detecting 14/7 cards despite the problem not actually existing in the miner.
I suspect that this is related to an erroneous log output from the miner as follows; note that the miner has reported two iterations of each card before outputting the "average" line (the last line of the extract below)
2017-12-07 9:39:51 AM| ========== Sol/s: 2898.4 Sol/W: 3.89 Avg: 2874.0 I/s: 1565.8 Sh: 39.13 1.00 357
2017-12-07 9:39:51 AM|# GPU4 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:53 AM|# GPU5 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:55 AM|# GPU6 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:58 AM| GPU0 63C Sol/s: 291.4 Sol/W: 3.94 Avg: 432.1 I/s: 158.8 Sh: 4.97 1.00 349
2017-12-07 9:39:59 AM| GPU1 67C Sol/s: 279.9 Sol/W: 3.80 Avg: 419.6 I/s: 149.5 Sh: 5.31 1.00 352 ++
2017-12-07 9:40:01 AM| GPU2 54C Sol/s: 295.4 Sol/W: 3.99 Avg: 424.5 I/s: 154.2 Sh: 3.82 1.00 344
2017-12-07 9:40:03 AM| GPU3 66C Sol/s: 284.6 Sol/W: 3.74 Avg: 421.5 I/s: 152.0 Sh: 6.15 1.00 375 +
2017-12-07 9:40:05 AM| GPU4 70C Sol/s: 298.7 Sol/W: 3.83 Avg: 435.5 I/s: 159.8 Sh: 6.31 1.00 416
2017-12-07 9:40:05 AM|> GPU0 62C Sol/s: 229.0 Sol/W: 2.06 Avg: 229.0 I/s: 121.5 Sh: 5.99 1.00 343 ++
2017-12-07 9:40:06 AM|> GPU1 67C Sol/s: 225.1 Sol/W: 2.02 Avg: 225.1 I/s: 120.1 Sh: 2.96 1.00 344 +
2017-12-07 9:40:08 AM|> GPU2 54C Sol/s: 219.8 Sol/W: 2.06 Avg: 219.8 I/s: 119.7 Sh: 5.99 1.00 352 ++
2017-12-07 9:40:09 AM| GPU5 71C Sol/s: 276.1 Sol/W: 3.73 Avg: 437.3 I/s: 148.8 Sh: 7.44 1.00 344 +
2017-12-07 9:40:10 AM|> GPU3 66C Sol/s: 222.7 Sol/W: 1.95 Avg: 222.7 I/s: 119.4 Sh: 5.81 1.00 351 ++
2017-12-07 9:40:11 AM| GPU6 49C Sol/s: 162.0 Sol/W: 3.69 Avg: 248.7 I/s: 84.8 Sh: 3.79 0.96 360 +
2017-12-07 9:40:11 AM| ========== Sol/s: 1888.2 Sol/W: 3.82 Avg: 2819.2 I/s: 1008.0 Sh: 37.79 1.00 362
As a side note;
Inputting the real "average" hashrate into the config.bat file tends to cause autorun to detect too many instances of low hashrate because any reported hashrate below the average appears to be considered an error.
I'd suggest this parameter would be better if named "minimum acceptable hashrate" or similar
or
Add a configurable tolerance to the acceptable range of hashrates. ie, within (say) 10% of the average is -not- considered to be a hashrate error.
Further, (just an idea) rather than the user nominating the average hashrate, perhaps autorun could automatically detect the actual average hashrate from all log files and store it in the config.bat file.
Happy to discuss this with you if the issue isn't clear from my description. Sorry that my input is not in the form of code change suggestions, it's beyond my capability.
That said, using this script has been educational and I'm thankful that you have released it open source.
Thanks again.