Quote:
Originally Posted by Siesta
Is there any way to check the dEV of a flop after solving it?
The value of dEV is available and stored in the tree itself, as well as in the savefile. Currently it's however an internal value; it can not be viewed after the fact by the user in the interface. I have of course no issue in displaying it, and it's entirely possible for us to display it, however, the challenge here is which properties are displayed, and where (and how). For example, there's also a request to show the full board. And in the final version there will most likely be several icons in the upper right. After release v103 we will start the figure out which properties/icons are displayed, and where they are placed in the interface. For example, one reasonably logical place to display dEV would be in the upcoming tree navigator/editor. However, we will first need to design this navigator/editor before we can get a feel for if this is the appropriate place for it.
Quote:
Originally Posted by Siesta
Also, would it be possible to add a continue option to the solver that continues a solve from the current accuracy instead of starting from scratch?
The great advantage of the GTO+ approach is that its savefiles are tiny and that it's possible to create very large databases, with savefiles being as small as only a few dozen MB, where previously even a single tree would easily require about 200MB. I mean, previously a database of 100 trees would require 20GB of memory and storage space. This is now reduced to only as little as roughly 20MB, which is a huge step forward. The flipside of this is though that not all internal solving data is stored, meaning that continuing a solve where you left of is no longer possible. That being said, in the old approach where all internal data was stored, our database functionality would not really be possible. At least not in this form. I feel that the upsides outweigh the downsides here.
Last edited by scylla; 09-22-2017 at 03:55 PM.