@ Markanth: I ran a testrun with a stable hashrate and Digi in its present form should give around 450 Blocks a day. Problem with the current Digi is that it has no backward visibility so it compensates where it's designed for but does not compensate the shortage. Second problem that amplifies this behaviour is the fact that it starts oscilating the moment the hashrate differs. Also those oscilations are not compansated.
Looks good thsminer.
2 questions:
1) In theory I think you are right with your conclusions as stated on your comment to Markanth. But can you simulate the hashrateswings as well, to be sure the simulator can produce the exact behaviour for future tests? That is important for testing to the new algo, that results fit almost perfect.
So in short, can you produce big and small hashrateswings with the simulator soon? That is what GJ is busy with also with that simulator. Is that what you mean by:
Along the way of finalising the simulator a test algoritm is build in that gives us the opportunty to change a broad spectrum of parameters without changing the code every time. So with that we should be able to devellop a stable algo that is pretty jumppool resistant on short notice.
2) Can this simulator simulate faster than real time? I mean the speed of simulating in time.
Lots of succes with devolpping on this.
-------------------------------------------------------------------------------------------------------------------------
Edit: Sorry for asking on testing jumppool swings, I see the section jumppool now in the picca, so that means swings can be produced as well as it seems. That would be great progress!
(I remain by stating that first producing almost exact same results as the algo is now atm is important as first stage, to be sure the simulator is representing results almost perfectly compared to the current state of the algo, so future tests are very reliable)
